Check filtering has not hidden unresolved export rows

Visible rows are not the whole register

Check the full result before export so the handoff includes the work still needing attention.

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.

Inspect manually hidden rows and sheets separately from filters. Clearing one filter may not reveal every excluded record, and a copied visible subset can become a new dataset with a different scope.

Use a pre-handoff visibility check

The counts reconcile to thirty, but the hidden candidate is not automatically a duplicate. Keep its status unresolved until source identity has been checked. A recipient seeing only twenty-six records should not have to infer the missing four from gaps in worksheet row numbers.

Microsoft: Filter data in a range or table explains that filtering hides rows that do not meet criteria. Treat visibility as a view setting, not evidence that the hidden records are absent from the underlying table.

Inspect the full workbook

1. Record the expected total and stable record keys from the reviewed register. Identify all sheets and table ranges used for delivery.
2. Clear or document filters, inspect manually hidden rows and columns, and review hidden sheets where relevant. Check for records outside the declared table range.
3. Reconcile accepted, unresolved, excluded and duplicate-candidate states to the full population. Include a separate exception summary with source references.
4. Save and reopen the final workbook in the intended view. Confirm that the recipient can find both the working data and the limitations without changing undocumented settings.

Microsoft: Table.RowCount counts rows in a table. Use an explicit population count alongside visible-view counts so the handoff makes clear which records each number represents.

Avoid misleading copies and totals

Copying a filtered view may transfer only selected records or behave differently depending on the application and selection method. Verify the resulting keys and counts in the destination rather than assuming the copy includes the full table.

A summary formula may count all rows or only visible rows depending on its design. Label the summary’s scope and test it against the known fixture. Do not use an unlabeled total as proof that every exception is represented.

Verify the recipient sees the limitation

For the fixture, the handoff states thirty total records, twenty-six visible accepted records and four records requiring attention. It identifies the three unresolved rows and the duplicate candidate individually. A limited accepted-only export should be named and described as that subset.

When preparing ParseMill output for another reviewer, include this visibility check after corrections and before delivery. It prevents a convenient working filter from silently changing the scope of the shared result.