Check a correction did not break adjacent row data

A correction has a surrounding scope

Recheck the surrounding fields so the exported workbook reflects the complete corrected row.

In ParseMill, select an extracted invoice field to inspect its source, correct the value and export the reviewed workbook. Try your own invoices as well as the interactive sample. Compare upload, checking and correction time with your current way of building the same spreadsheet.

Keep the original output and a stable record identifier. If the repair changes the row structure, preserve a mapping from old output rows to the corrected records. This lets another reviewer distinguish a legitimate reconstruction from accidental loss or duplication.

Use a correction-impact worksheet

These invented repairs affect different scopes. A character correction does not automatically require redoing an entire unrelated document, while a shifted column may require checking every row in the affected range. Record the reason for the chosen scope rather than applying one arbitrary rule to every edit.

W3C: Provenance model primer distinguishes source entities and transformation activities. Treat a correction as a recorded activity producing a new output revision.

Review the repaired neighborhood

1. Record the source-supported correction, original value and corrected value or row mapping. Identify dependent formulas, totals and evidence columns.
2. Check the corrected record against the source, including identifier, heading, qualifiers and unit. Do not review only the edited character.
3. Inspect preceding and following records and any broader range affected by the operation. Reconcile row counts when rows were inserted, removed, merged or split.
4. Recompute affected derived fields and reopen the export. Save the new revision with the correction record and verification result.

Microsoft: Table.RowCount provides a row count that can support structural reconciliation. Combine it with identity checks, because equal counts can conceal a lost row replaced by a duplicate.

Watch repairs that look harmless

Sorting only the result column can detach every value from its identifier. Filling down a unit can cross a source section where the unit changes. Copying an entire corrected row can duplicate an internal key. These operations require checking the relationships they could disturb, not only the visible cell that motivated the edit.

If a correction exposes a repeated extraction pattern, search the affected document class for the same defect. Keep that broader investigation separate from the initial local fix so its scope is explicit.

Close the correction with evidence

For the fixture, each repair has its own verification range and recorded result. The corrected output is ready only when the direct error and its plausible side effects have been checked. Preserve unresolved dependencies in the release note.

When reviewing ParseMill output, use this worksheet for manual corrections. Measure the work needed to diagnose, repair and recheck an issue before deciding how the workflow fits your team’s register process.