Review mixed portrait and landscape pages in one report

Check the new layout, not just the page rotation

Include those pages in the fit check so the workbook is judged on the whole document rather than its easiest section.

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.

Rotation and orientation are separate issues. A sideways scan may need a viewer rotation simply to be readable, while a wide native-text table may be correctly oriented already. Preserve the original and record any view-only adjustment so another reviewer can reproduce what was checked.

Use a layout inventory at each transition

Microsoft: PDF connector describes PDF table import. Microsoft: Table.SelectColumns can select named columns, but selecting familiar names does not validate their contents or positions.

1. Record physical page, orientation, table heading, field names and the visible start/end of the table. Mark where the orientation changes.
2. Compare column labels on both sides of the transition. Look for renamed, inserted or missing fields before attempting a common schema.
3. Check one complete row near the top, one near the bottom and every visibly wrapped or shifted row on the new layout. Expand the review when the intended use requires full checking.
4. Keep layout groups separate until the mapping has been verified. If the second layout is unsupported, preserve a partial coverage statement rather than silently merging incomplete rows.

Inspect a widened table

Synthetic example: a report changes shape after page 2.

On page 3, taking the second column as Result would copy the method identifier instead of the observation. A familiar Sample column and an unchanged row count would not expose the mistake. The correct working model either maps the new Method field explicitly or leaves it in a separate table with a documented relationship.

Look for changes beyond the obvious one

Wide tables often use merged or stacked headings. A heading spanning two columns can make a value look as if it belongs to the neighboring field. Wrapped units and footnote markers can also move independently from their values. Compare the complete header region and the actual row, not a cropped number alone.

Do not infer that rotating a page repairs an extraction mapping. A viewer adjustment changes how a person sees the page; it does not establish that the parser used the intended coordinate system. Re-run or manually review the affected region and retain the before/after evidence when a setting changes.

Accept groups separately before combining them

For each layout group, record the checked fields, source range, unresolved rows and schema decision. Then compare the combined output against that inventory. Ensure that a column introduced on landscape pages does not cause values on portrait pages to shift into a different field. Empty fields should remain explained rather than filled from neighboring rows.

Use the multipage guide for the final continuity check. In the invoice trial, include any portrait-to-landscape transition your suppliers actually use and inspect the affected fields. Support for native invoice PDFs and clear printed English scans does not establish support for arbitrary report layouts.