Check PDF file size and page count before processing

Where the extra work starts

Check page count and file size first, then choose a representative supported invoice that leaves room to inspect and compare the result.

ParseMill processes native invoice PDFs and clear printed English PDF scans. Try a typical supplier invoice and a difficult one. Check the extracted fields, correct exceptions and open the workbook before committing to a monthly plan.

Record the actual source file and relevant page ranges. Do not remove context merely to produce a smaller file, and do not treat a prepared excerpt as the complete original document.

A practical way to get it right

Inspect file size through the operating system or an approved PDF tool and page count in the viewer. For ParseMill invoice batches, each PDF must be within 20 MB and 300 pages, the batch can contain up to 25 PDFs, and processing must fit the remaining page allowance. Record the actual file properties and which pages contain the required rows, headings, units and qualifications.

If the file exceeds a limit, ask whether an authorized smaller original or a permitted excerpt is available. Preserve the full source in its approved location. For any derivative, record the original page ranges and verify that the excerpt retains all context required for the task.

Reopen the prepared file and check size, count, text selection and table structure again. Compression or re-creation can change text quality or produce image-only pages. Keep the preparation effort and verification in the workflow estimate rather than treating it as free preprocessing.

Adobe: PDF properties service identifies file size and page count as inspectable PDF properties. Record those actual properties rather than estimating them from the number of visible tables.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

This file fails the size check despite being under 300 pages. Copy the preflight fields and use the actual measured values. If a derivative is later prepared, add its size, page count and source-page mapping rather than overwriting the original record. Do not guess whether a borderline display value will pass; check the actual application feedback.

Catch the cases that create rework

Cropping visible margins does not necessarily remove content or reduce file size. A smaller-looking page can therefore remain oversized. Splitting pages can also separate a continuation from its headings or footnotes. Verify the intended evidence set after every preparation step.

Do not upload production material to an unapproved compression service just to pass a limit. Use the firm's permitted tools and source-sharing arrangements.

Adobe: Crop PDF pages states that cropping hides content without reducing file size. Do not use a visual crop as evidence that an oversized source now meets the upload limit.

Decide whether the change is worth keeping

The preflight passes when the exact file to be processed meets current limits and its required evidence remains complete and readable. Record any omitted pages as excluded scope, not as processed content. Then perform the separate header, row and source-review checks. A successful upload establishes transport, not extraction correctness.