Check that an exported workbook matches the reviewed revision

Review the delivered file, not just the screen

Check the revision you are handing over so the recipient receives the result you approved, not an earlier draft.

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.

Keep a small list of known corrections and critical records as comparison anchors. These should include values that changed during review, because an apparently reasonable old value can otherwise survive unnoticed in the exported file.

Use a revision comparison card

This invented card is a practical acceptance fixture. It checks both corrected data and unresolved states, rather than requiring every cell to be filled. Add records from page boundaries and different source documents if the register combines several inputs.

W3C: Data on the Web Best Practices recommends version indicators and history. Use an explicit relationship between reviewed register and exported workbook to prevent accidental revision substitution.

Compare after reopening

1. Save the final review record and note the exact source and output revisions it covers. Avoid further edits while exporting.
2. Export the intended scope and reopen the resulting file from its saved location. Confirm sheets, row count and record identifiers.
3. Check every recorded correction and unresolved exception against the reopened workbook. Verify source references and any fields affected by format conversion.
4. Record the export verification result and file identity. If a mismatch appears, regenerate or repair the export and repeat the affected checks before sharing.

Microsoft: Import or export text and CSV explains that export formats have different capabilities. If the delivery format changes, verify its contents rather than assuming it preserves everything visible in the working workbook.

Find subtle revision mismatches

A copied filename can conceal an older file, and a preview may display cached content. Open the actual saved artifact used for delivery. Check that formulas, filters or hidden sheets have not changed which records the recipient will see.

If a late correction is made after export, create a new export revision and update the review relationship. Do not leave two files with the same version label but different contents; that makes the signoff difficult to reproduce.

Close the handoff deliberately

For the fixture, acceptance requires S7’s corrected value, S12’s unresolved state and S18’s source revision to survive into the reopened workbook. The twenty-four records must remain identifiable, not merely countable. Save the completed comparison card with the deliverable.

When moving ParseMill output into a shared workflow, make this final export check part of review. It confirms that the file another person receives is the one your team actually assessed.