Template-free document capture means the system reads and understands a document without anyone defining where each field sits for that supplier or customer. A new sender’s invoice or order works on the first document, and a layout change does not break anything, because the system recognises what a field is rather than where it is.
The opposite is template-based capture, where someone draws zones on a sample invoice per supplier. It works until the supplier redesigns its invoice, and with hundreds of suppliers that happens every week. The difference is part of the wider OCR vs intelligent document processing question, and this is the practical side of it.
How template-based capture works, and breaks
A zone per field, per layout
Total here, invoice number there, lines in this table. Someone sets it up for each supplier, tests it, and maintains it.
The first layout change
The supplier moves the total to the next page or adds a column. The zone reads the wrong value or nothing. Usually nobody notices until the figure is already in the ERP.
The onboarding queue
Every new supplier or customer waits for a template before their documents can be processed. In a growing company that queue never empties.
What template-free changes in the office
New suppliers work on day one
A supplier you have never bought from sends its first invoice. It is read, the supplier is identified, and the lines are matched. No setup ticket.
Layout changes stop mattering
The same invoice in a new design is still an invoice with the same fields. Nothing to fix.
Multi-language and multi-format
English, Hebrew, German, PDF, scan, photo. Supplier invoice capture across a real supplier base needs this, not a template library.
Mixed document types in one mailbox
An invoice, a delivery note and a packing list in the same thread. The system tells them apart and routes each to its flow.
What template-free does not mean
It does not mean no rules
You still decide what to check and who decides on exceptions. The rules are about the process, not about where the total sits on the page.
It does not mean no ERP knowledge
Identifying the supplier and matching lines needs the ERP master data and the open POs. Template-free reading plus a direct ERP connection is the combination that works, and it is why intelligent document processing for freight forwarders with thousands of senders is possible at all.
How it works with DOConvert
DOConvert is the AI layer for the ERP. It connects directly to Priority through the DOConvert Priority connector, which is bi-directional, and to Oracle Fusion Cloud ERP and Infor M3, with no middleware and no template per supplier. Here is a first invoice from a new supplier.
The invoice arrives
The sender is unknown to DOConvert. The document is still recognised as a supplier invoice, and the supplier is identified from the document and matched to the ERP supplier record.
The PO is read from the ERP
Open purchase orders for that supplier are pulled through the connector. Lines are compared, item by item.
Exceptions stop, the rest is entered
A price difference waits for the buyer with a reason. The matched lines are entered as a native purchase invoice. The same applies to customer orders from PDF and email from a new customer.
Nothing was configured for that supplier
Not before the first invoice, not after. Avi Rafalson, CEO of DOConvert, wrote about the model choices behind this in Generalist vs specialist.
Who it fits
AP teams with hundreds of suppliers and a steady flow of new ones.
Order desks receiving POs from many customers, each in its own format.
Freight forwarders and importers handling documents from senders they have never seen.
IT managers who have maintained a template library and do not want another one.
Questions and answers
Does template-free mean the system guesses?
No. It understands the fields from the document itself and then checks them against the ERP record. A field it cannot read with confidence stops for a person instead of being guessed.
What happens with a very unusual document?
It is read like any other. If the supplier cannot be identified or the lines cannot be matched, the document stops with a reason rather than being entered wrong.
Is any setup needed at all?
The setup is about your process, which mailbox, which ERP, which checks, who decides. Not about suppliers or layouts.
How long does implementation take?
A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers.
Want to see it on your own documents? Book a Demo or Get Started