Verify a table's final page is present

Distinguish a finished extraction from a complete source

Check the table's ending and source coverage so the next person does not discover the gap only after using the workbook.

For multipage invoices, use ParseMill to review extracted invoice data beside the source and export separate summary and line-item sheets. Include a page break in your trial and check that every required line made it through. Other report types need their own fit assessment.

Do not generate rows to fill an apparent sequence. A missing identifier can be intentional, and an expected final page can contain notes rather than data. The correct result may be a documented uncertainty and a request for the missing source.

Work through an invented packet

This fixture supports a statement that the packet appears incomplete, not a statement that exactly six sample rows are missing. The missing fifth page might contain two rows, ten rows or only a continuation note. Keep those possibilities separate from facts observed in the received file.

Adobe: Renumber pages in PDFs explains page labels. Record physical position alongside the printed footer so the completeness note identifies the page actually inspected.

Run the final-page check

1. Inventory every received physical page, including blank pages and attachments. Record the printed labels without renumbering away gaps.
2. Inspect the bottom of the last relevant table page and the top of the following page, if present. Look for continuation wording, closing rules and section transitions.
3. Compare any source-provided row count or total with the extracted output using the same scope and units. Document mismatches without assuming their cause.
4. Review the original delivery message or document index when available. If a final attachment is named but absent, record that precise absence.

Microsoft: Table.RowCount can count extracted rows. A count of output rows establishes the output’s size; it cannot establish how many rows an absent page should contain.

Avoid false reassurance

A final page number matching the received count does not rule out a missing internal page. A table ending cleanly does not establish that all scheduled samples were reported. Check these as separate completeness questions when they matter to the intended use.

Likewise, a continuation footer may be a template artifact. If the supplier confirms that it is erroneous, retain the confirmation and its date with the source record. Do not erase the original observation from the review history.

State the result precisely

For the fixture, report: “Pages 1–4 received; page 4 is labeled 4 of 5 and ends with Continued; final table extent unresolved.” Share the extracted rows only with that limitation visible. Revisit the check when the missing page or an authoritative clarification arrives.

In an invoice trial, include a synthetic invoice with its final page deliberately missing. Check whether your review process exposes the gap before you accept the workbook. The buying test is a usable result with understandable exceptions, not simply a completed extraction.