Keep source references when copying rows into another workbook

A copied row needs its evidence columns

Carry the evidence with the data so the next reviewer can check a figure without repeating the document search.

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 receiving workbook should not depend on hidden local paths or an unexplained row number from the original sheet. A recipient needs a reference they can resolve in their authorized environment.

Use a copy-and-handoff checklist

The key is an invented internal reference, not a supplier-issued identifier. Keep that distinction visible. If two copied rows share a sample code, their source and test context must still distinguish the observations.

W3C: Provenance model primer describes source entities and derivation relationships. A copied workbook is a new derived artifact whose connection to the source should remain explicit.

Verify the new workbook

1. Select the complete table range, including record keys, source fields and review states. Note any document manifest required to interpret those fields.
2. Copy into a new versioned workbook and preserve the relationship to the reviewed source export. Record any omitted columns and why they are unnecessary for the stated use.
3. Compare record counts and stable keys, then check source references on records from different files and pages. Verify that values and evidence moved together.
4. Test the package from the recipient’s perspective, including authorized source access. Keep unresolved permissions or missing evidence visible in the handoff.

W3C: Data on the Web Best Practices recommends version history for derived data. Record the source export revision used to create the copied workbook rather than giving it an ambiguous final label.

Avoid fragile references

A formula pointing to a cell in the original workbook may break when the file moves. A local filesystem path may be meaningless to another user. Prefer stable manifest identifiers or authorized shared locations, and test whichever reference scheme your organization uses.

Do not copy a reviewed status onto newly calculated fields. The old signoff covers the original checked fields and version; new transformations need their own review record.

Confirm the new package is reviewable

For the fixture, a recipient should locate R7 revision 2, page 4 and the correct observation using the copied row and manifest. The result should remain attached to its review state after sorting or filtering.

When moving ParseMill output into another workbook, carry the evidence relationship with the data. This keeps a convenient subset useful for later review instead of turning it into an untraceable list of values.