Invoice processing automation template
This template turns an incoming invoice into a checked, structured record. It reads the fields, validates them, shows anything doubtful to a clerk and writes a draft bill only after confirmation.
Last reviewed 7 October 2026
Designed
No template covers invoice processing. The Marketplace listings Invoice extraction workflow and Invoice extraction → ERP are samples, with nothing seeded behind them. The steps are the shape you would build in Studio.
No template covers this job yet. The steps below are the shape we would build and the shape you can build in Studio yourself.
What this template does
Invoice processing is the front half of payables, usually owned by a clerk or an accounts assistant. The job is data quality. Every invoice arrives as a PDF, a scan, an email body or a photo, and someone has to turn it into fields that a ledger can trust.
Typing is where it goes wrong. A digit is transposed, a tax line is dropped, a multi-page invoice is entered as two. Fixed templates per supplier help until a layout changes. This flow reads the document, checks the arithmetic and the required fields, and puts only doubtful records in front of a person, beside the original. Approval and payment are a separate job, covered on the accounts payable template.
The workflow, step by step
Steps marked as approval gates pause the run until a named person approves. Nothing after a gate runs before that decision, and the decision is recorded.
- 01
Capture the document
The workflow collects invoices from the mailbox, a shared folder or an upload form. Multi-invoice PDFs are split by page ranges, and each document is stored unchanged with its source and arrival time. The next step receives one file per invoice. - 02
Read the text
For PDFs that carry text the workflow extracts it directly. For scans and photos it calls a document reading service. The output is raw text with page and position information, kept beside the file. The next step receives the text and the original. - 03
Extract the fields
A model maps the text to your schema: supplier, invoice number, dates, currency, lines, tax and totals. Each field is marked found, missing or uncertain. Because the model reads meaning rather than positions, a new supplier layout does not need a new template. The next step receives the structured record. - 04
Validate the record
Code steps check the arithmetic, so that lines add up to the subtotal and the tax matches the rate. They check that required fields are present, that dates are plausible and that the currency code is one you accept. Failures are written onto the record as reasons. Passing records carry a clean flag. - 05
Confirm before posting
A named clerk sees each flagged record beside the original document, with the failed check highlighted. They correct the field and confirm, or reject the document. Clean records can skip this pause if you decide so, but your first weeks of running are better with every record confirmed.Approval gate: a named person approves before the next step runs. - 06
Write the draft and archive
Confirmed records are written to the accounting system as draft bills, never as posted ones, or exported as a spreadsheet for upload. The original, the extracted record and every correction are stored together under one reference, which the draft carries.
What it can do, cannot do, needs approval for, and records
Can
- Collect invoices from a mailbox, a folder or a form
- Extract fields from PDFs, scans and photos
- Check arithmetic, required fields, dates and currency
- Write a draft bill after a clerk confirms
Cannot
- Post a bill as final
- Approve or pay an invoice
- Treat an uncertain field as certain
- Edit the original document
Requires approval
- Every flagged record, by the named clerk
- Rejection of a document, with a reason
- Any change to the validation rules, by the process owner
Records
- The original document and where it came from
- Extracted text and the structured record
- Which checks failed, and which field was corrected
- The clerk, the decision and the time
What the library holds for this job
| Asset | Type | Covers | Role in this flow |
|---|---|---|---|
| Invoice extraction workflow | Marketplace sample listing | Sample listing, no template behind it | A sample listing described as OCR, extract, validate and post to ERP. No template is seeded behind it, and this page does not quote its cost. |
| Invoice extraction → ERP | Marketplace sample listing | Sample listing, no template behind it | A second sample listing for the same job in the Document category. Also nothing seeded. |
| Extract Key Information from Text | Prompt | Used inside the flow | A starting prompt for pulling named fields out of free text. |
| Mindee | Integration | Used inside the flow | A document reading service that can be called for the field extraction step. |
Integrations this flow uses
- Mindee: A document reading service for scans and photos.
- ReadPdf: Extracts text from PDFs that already contain it.
- QuickBooks: A target for draft bills, if it is your ledger.
The full list of tools Studio connects to is on the integrations page.
What you supply, and what this page does not cover
- You supply the target schema, the validation rules, the currencies you accept and the people who confirm records.
- Reading quality depends on the document. Poor scans and handwriting will produce uncertain fields, and the clerk gate exists for them. This page quotes no accuracy figure.
- Approving and paying invoices is a separate workflow. See the accounts payable template.
- Tax rules, e-invoicing formats and retention periods differ by country and are not covered here.
Common questions
- How is this different from OCR?
- OCR turns an image into text. This flow goes on to map the text to fields, check the arithmetic and required values, and show doubtful records to a person. A model reads the meaning of the page, so a changed supplier layout does not need a new template for that supplier.
- Do I have to confirm every invoice?
- It is your choice. The design lets clean records skip the clerk and sends only flagged ones. In the first weeks we would confirm every record, so you can see how often the extraction is wrong on your own documents before you relax the rule.
- Does it work with scanned or photographed invoices?
- Yes, by calling a document reading service for the text, and then using a model to read fields. Quality depends on the image. A skewed photo or a faded scan gives more uncertain fields, which the workflow marks and passes to the clerk rather than guessing.
- Where does the draft bill go?
- To the accounting system you connect, as a draft, or into a spreadsheet for upload. Making the bill final, approving it and paying it are separate steps owned by people, and the accounts payable template shows one way to arrange them.