Treat formula-like source text as data in spreadsheets

Source text should remain source text

Check how the export and receiving application handle it so a copied description does not become active workbook content.

ParseMill exports reviewed invoices to Excel with separate summaries, line items, sources and review status. You can import an XLSX or CSV template and save a client setup. Run a real invoice through to the final workbook and check it in the application that receives your work.

Do not test with active external links or harmful formulas. A harmless synthetic expression is enough to detect whether an application evaluates a cell instead of displaying its literal text.

Use a harmless verification fixture

These strings are synthetic test data. The fixture passes only when the receiving application treats them as text and the original strings remain recoverable. Do not confuse a visible leading escape character with the original source: if a safety transformation adds characters, document that derived delivery representation.

OWASP: CSV injection describes formula injection and warns that CSV mitigations can behave differently across applications and save/reopen cycles. There is no universal quoting trick that should be assumed safe everywhere.

Verify a controlled export path

1. Identify the actual receiving application and whether it supports explicit text types in a workbook or controlled text import. Keep raw source text in a separate trusted record.
2. Configure the export to write these fields as text, using application-specific guidance. Treat ordinary CSV quoting as syntax handling rather than proof of formula safety.
3. Open the harmless fixture in the intended application and inspect the cell type or formula behavior. Save, close and reopen to check persistence.
4. Compare literal strings and record any safety transformation, application version and tested path. Hold the real delivery if the intended consumer cannot preserve inert text reliably.

Microsoft: Text/CSV connector provides controls over automatic type detection. Those controls can support a text-preserving import, but the complete receiving workflow still needs a direct check.

Keep analysis formulas separate

A workbook may intentionally contain formulas you authored for analysis. Distinguish those from imported source fields and review them separately. Never let source text silently become part of a formula expression or an external reference.

This guide provides a fixture and verification procedure; it does not claim a particular spreadsheet application was tested here. Do not label a delivery safe solely because a CSV parser returns the strings unchanged: a parser does not evaluate them as a spreadsheet might.

Record a scoped result

Acceptance names the application, version, import path and save/reopen behavior tested. If a sanitized display field differs from the raw text, the handoff explains that difference and how to recover the original.

When evaluating ParseMill exports, include this harmless fixture in the recipient compatibility check. Verify that extracted source strings remain data before incorporating the output into a shared spreadsheet workflow.