Comparison
AI invoice capture vs template-based OCR.
Template-based capture learns where each field sits on each supplier's invoice. AP Receiving reads the invoice instead. Here is what that changes for your AP team, side by side.
What changes when the software reads the invoice.
AP Receiving is the receiving stage of accounts payable: it takes in every invoice, from any channel, and turns it into checked data your ERP can post.
| Topic | Template-based capture | AP Receiving by Nuntiq |
|---|---|---|
| A new supplier | Set up before it runs.A template, or a batch of training invoices, is needed per supplier layout before that supplier's invoices are read automatically. | Read from the first invoice.AI reads each supplier's layout from the first invoice. There are no templates to build or maintain. |
| A supplier changes its layout | The template breaks.A moved logo, a new column or a different font sends invoices to manual correction until someone updates the template. | Nothing to update.The new layout is read the same way as the old one. For the rare supplier that needs special handling, your team adds a short plain-language instruction once. |
| Several invoices in one PDF | Separate them first.Separator sheets, barcode cover pages or splitting the file by hand before it goes in. | Split for you.AI splits the file into separate invoices. Continuation pages, cover letters and delivery notes stay with the invoice they belong to. |
| Digital PDFs | Often treated as a scan.The page is turned into an image and read with OCR, which can introduce reading errors. | Read straight from the file.Nuntiq's own PDF reading takes the text directly from digital PDFs. OCR is used only for scans and image-based PDFs. |
| E-invoices | A separate channel.Structured formats often arrive through another system or project, outside the capture queue. | Same queue as everything else.UBL, CII, Factur-X and ZUGFeRD, plus JSON, CSV and EDI files, are mapped directly without OCR and land in the same queue as PDFs and emails. |
| Checking the result | Field by field.Low-confidence fields are flagged, but a missed line on a long invoice can go unnoticed. | Against the invoice's own totals.Lines must add up to the total and deductions to the amount due. If they do not, another AI model reads the invoice again; if it still does not add up, it goes to your team for review. Your validation rules run on every invoice. |
| Reviewing an exception | Search the page.The reviewer compares the captured data with the image by eye. | Click a value, see it on the invoice.Click any captured field or line and the invoice image moves to where that value is printed and highlights it. |
| The recognition engine | Built in.One recognition engine, improved on the vendor's schedule. | Not tied to one AI model.Nuntiq uses AI models from several leading providers. When a better model arrives, it is tested on invoice capture first, then switched in, with nothing to change on your side. |
| Your data | Check the vendor's terms.Ask whether your invoices are used to train models and how your data is separated from other customers'. | Never used for training.Your documents are never used to train AI models, and each customer's transactional data lives in its own database. |
| Getting started | Templates first.Supplier templates have to be built before volume can run. | Within a week.You can be processing your own invoices within a week, and connect your ERP whenever your IT team is ready. |
The receiving stage, done properly.
AP Receiving covers everything from the moment an invoice arrives until it is checked data in your ERP: receiving, capture, enrichment, matching and delivery. Approvals and payment runs stay where they belong, in your ERP.
That makes it a fit next to the ERP or procure-to-pay suite you already run, rather than a replacement for it.
- Email, supplier portal, API and e-invoice files in one queue
- Matched to your entities, suppliers and purchase orders
- Duplicate detection and your own validation rules before posting
- Every original stored as it arrived, every action recorded
Template-free capture, explained.
How does template-free AI invoice capture differ from template-based OCR?
Template-based OCR finds each field by its position on a known supplier layout, so every layout needs a template and every layout change breaks it. AP Receiving reads the invoice the way a person does: AI reads each supplier's layout from the first invoice, so there are no templates to build or maintain.
What happens when a supplier changes its invoice layout?
Nothing needs to be updated. AP Receiving reads the new layout the same way it read the old one. For the rare supplier whose invoices need special handling, your team adds a short plain-language instruction for that supplier, and it is applied automatically from then on.
Can AP Receiving split a PDF that contains several invoices?
Yes. AI splits the file into separate invoices, with no separator sheets or barcode cover pages. Continuation pages and pages such as a cover letter or delivery note stay with the invoice they belong to.
How accurate is the capture?
We publish our capture results on real-world test invoices, including scans, faxes and multi-invoice PDFs, with every answer unedited, at nomorebaddata.com. In production, every invoice is also checked against its own totals and your validation rules, and anything that does not add up goes to your team instead of being posted.
Is AP Receiving a full AP automation suite?
No. AP Receiving is the receiving stage: it captures, enriches, matches and validates invoices before they reach your ERP. Approvals and payment runs stay in your ERP or procure-to-pay system.
More questions about channels, e-invoices, integration and security: see the full FAQ.
See it work on your own invoices.
Send us a handful of real invoices and we will show you exactly what comes out the other side. We're working with our first customers now: join them, and help shape what we build next.
Our vision: accounts payable should be a strategic function, not an administrative burden.