Prepare an export handoff for a reviewer using another application

Compatibility includes meaning, not only opening the file

Test the actual handoff format so source references, types and unresolved fields remain usable where the work continues.

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.

The check should cover raw strings, numeric representations, formula-like text, sheets and evidence access. A screenshot of a correct-looking first row is insufficient when the reviewer must filter exceptions or follow source references elsewhere in the file.

Use a compatibility test card

The formula-like string is deliberately harmless. Test it as data without enabling external content or executing untrusted source formulas. Record any safety transformation that changes the delivery representation, while keeping the raw source string available through the approved workflow.

OWASP: CSV injection explains why spreadsheet interpretation of formula-like text requires application-specific verification, including save-and-reopen behavior.

Test the real receiving workflow

1. Record the application, version and import path the reviewer will use. Agree delimiter, encoding and types for text formats.
2. Open the fixture and verify each card item, including all relevant sheets and companion manifests. Check stored values separately from visible formatting.
3. Save, close and reopen the file if the reviewer will edit it. Recheck characters, identifiers, formula-like text and evidence references.
4. Document successful settings, known limitations and an alternative authorized handoff for unsupported features. Repeat after meaningful application or export changes.

Microsoft: Text/CSV connector documents import settings for delimiter, encoding and type detection. Other applications may expose different controls, so verify the actual recipient path rather than assuming identical behavior.

Keep unsupported features visible

If notes or evidence sheets do not transfer, provide an explicit companion file or a format the recipient can review. Do not describe the export as equivalent when required context is missing. If a link requires permissions the recipient lacks, resolve access through the source owner or state the limitation.

Avoid changing the whole organization’s application settings just to make one file work unless that is an authorized, understood choice. A documented import procedure is often easier to reproduce and review.

Approve a scoped handoff

Acceptance names the tested application and workflow, with results for each fixture item. It does not claim compatibility with every spreadsheet program. Keep the card with the delivery instructions so a later reviewer can reproduce the checks using the same fixture and declared settings.

When sharing ParseMill output across teams, include the recipient application in the evaluation. The useful outcome is a reviewable register with preserved meaning and accessible evidence in the environment where it will actually be used.