A PDF containing several invoices must be split into complete documents rather than isolated pages. Keeping continuation pages together preserves line items, totals and payment details for review and accounting delivery.
Split by invoice, not automatically by page
A page-by-page splitter works for single-page invoices. It can break a multi-page invoice by separating its line items from the final totals. Identify document boundaries from the invoice content.
For example, an eight-page PDF might contain four invoices covering page 1, pages 2–4, pages 5–6 and pages 7–8. The correct result is four files.
| Invoice | PDF pages | Output |
|---|---|---|
| A | 1 | Single-page invoice |
| B | 2–4 | One complete three-page invoice |
| C | 5–6 | One complete two-page invoice |
| D | 7–8 | One complete two-page invoice |
Review and confirm the split
Check the selected company and its delivery mode before uploading a batch. Open PDF batches to follow the job and review any uncertain boundaries.
- Upload the combined PDF for the correct company.
- The system processes the pages and proposes invoice boundaries.
- When a boundary is uncertain, compare the proposed ranges with the original.
- Correct each invoice’s first and last page as needed. Ranges must cover every page without gaps or overlap.
- Confirm the split, then check the resulting documents and their delivery status.
Recognise continuation pages
A repeated supplier logo does not necessarily start a new invoice. Look at invoice numbers, page numbering, continued tables and the totals section. Page headers and white space alone do not establish a reliable boundary.
Review specifications, delivery notes and attachments carefully. Keep each supporting page with the invoice it belongs to so the accounting reviewer receives a useful document.
Separate PDFs and structured extraction are different modes
The separate-PDF delivery mode splits and sends the original document sections without extracting accounting fields for structured export. OCR may still be used to identify invoice boundaries.
Choose structured processing when you also need suppliers, dates, VAT, totals and line items. Review the extracted result before using XML or API delivery. Select the mode according to what the receiving accounting system accepts.
Test delivery before processing a large batch
Start with a smaller sample when the document layout or destination is new. Confirm that each output contains the entire invoice and arrives under the correct company.
- Each invoice contains every continuation page.
- Page order, attachments and totals are preserved.
- The company and destination email match the documents.
- No unresolved boundary review or quota warning remains.
- The archive confirms delivery rather than only upload completion.
Estimate OCR capacity by pages
A PDF with 30 invoices is not necessarily 30 pages long. Count the pages that will be submitted to OCR, including continuation pages, when estimating the allowance you need.
Paid plans share a monthly OCR page allowance. An uploaded file may still be waiting for review, processing, an allowance renewal or an upgrade. Check the job status before treating the batch as fully delivered.
Frequently asked questions
Should every PDF be split into individual pages?
No. Split it into complete invoices, keeping all pages of the same invoice together.
What if two invoices were combined?
Review the proposed page ranges in the PDF batch and correct the boundary before confirming the split.
Does separate-PDF delivery avoid all OCR?
Not necessarily. OCR can still identify the boundaries, even though line items and other accounting fields are not extracted for structured export.
Why was the PDF uploaded but not sent?
Upload is only the first stage. Check the batch stage, unresolved review, remaining allowance and any delivery errors.
Try the workflow on your own invoice
Free: 3 invoices and 10 OCR pages per month. Review the result before sending it to accounting.