Keep a sorted register aligned with its evidence rows

Sort the record, not an isolated column

Verify that relationship so the convenience of a new order does not send reviewers to the wrong source.

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.

Check for blank separator columns, adjacent notes and data outside the table range. They can cause a selection to omit evidence fields even when the visible values appear to move together. Save a pre-sort version so the operation can be reversed if necessary.

Use a sort-safety fixture

Sorting the invented records by result ascending should produce K2, K3, K1. Each source reference must travel with its key: K2 still points to Report A page 2 row 2. If the values alone become 10, 20, 30 beside the original K1, K2, K3 order, the register has been corrupted despite looking sorted.

Microsoft: Sort data in a range or table discusses sorting ranges and keeping associated data together. Confirm the selection rather than relying on an automatic range guess.

Check the relationship after sorting

1. Save the current workbook revision and capture a key-to-value-to-source mapping for the records being sorted. Include unresolved states and qualifiers.
2. Select the complete table with headers and all evidence columns. Confirm that the sort key and ascending or descending order match the intended view.
3. Compare the post-sort records by stable key, not by row position. Check that each key retains its values, source identity and review state.
4. Reopen the saved workbook and test evidence references on records from different inputs. Record the sorted output as a derived view of the reviewed data.

Microsoft: Table.AddIndexColumn can add positional values, but an index changes meaning if it is regenerated after sorting. Preserve an original source locator separately from the current display order.

Watch formulas and partial ranges

A formula may refer to a fixed cell outside the sorted table, while a copied source note may sit beyond a blank column. Inspect these dependencies before assuming the whole record moved. Where possible, use explicit table relationships and verify their behavior in the actual application.

Do not repair a bad sort by sorting another column in the opposite direction unless you can prove the original association. Restore the saved version or rebuild from stable keys and source evidence.

Accept the intended order and unchanged meaning

The fixture passes when the order is K2, K3, K1 and every key retains its original result and evidence reference. Counts alone cannot detect a detached source column. Keep the verification result with the sorted revision.

When organizing ParseMill output in a workbook, use complete-record sorting and a post-sort identity check. This protects the source-backed relationships that make the register useful for later review.