Skip to article
Automation Voice Agent Creative Blog Request a call Contact us
Automation

Invoice Processing Automation: Workflow, Checks and Exceptions

A practical guide to automating supplier invoices: how the workflow runs, which checks stop a bad posting, and who owns each exception.

Illustration: supplier invoices leave an inbox tray, pass through three checks (reading, rules, matching) and reach the accounting ledger, while one flagged invoice goes to a person at a desk for review.
On this page

Invoice processing automation uses software to move a supplier invoice from arrival to a posted accounting record. It reads the fields, checks them against your records, routes the approval and writes the result to your accounting system. People handle the exceptions, and paying the invoice stays a separate, controlled step.

A hypothetical example: a supplier emails invoice INV-2048 for 12 units at USD 40 each. The purchase order says 12; the goods receipt says 10. Software can read every field correctly and still must not post this invoice. The right result is a review task that shows the two-unit gap to the person who owns receiving. The exception section follows this invoice through.

This guide is for finance and operations leads whose team still re-keys invoices and chases approvals by email. It gives you a workflow map, an exception-owner table and a pilot checklist to use with your team or a vendor.

What invoice processing automation covers (and what it doesn't)

It's easy to treat "invoice automation" as one tool. In practice it's four different jobs, and each one fails in a different way:

The four jobs inside invoice automation
JobWhat it doesTypical failure
Extraction (OCR or document AI)Reads fields from a PDF or image: supplier, invoice number, dates, line items, totalsA field is misread or missing
Workflow rulesValidates the data, checks for duplicates, matches records and routes the invoiceA rule is wrong, too strict or too loose
Accounting postingWrites the approved bill or invoice into your accounting system or ERPThe write fails, or its result is unknown
Payment authorizationReleases money to the supplier under your payment controlsShould stay a separate, governed process

Extraction services can return structured data from an invoice. For example, Amazon Textract's invoice and receipt analysis documents fields such as invoice date, invoice number, item prices, total amount and payment terms. But extraction only tells you what the document says. It doesn't tell you whether the invoice is valid, expected or approved. That's the workflow's job.

Scope note: this article covers incoming supplier invoices (accounts payable). It doesn't cover sending invoices to your customers or subscription billing.

Map the workflow before you choose tools

Before comparing software, write down how invoices actually reach you and where they need to end up. Six questions cover most of it:

  1. Intake: Do invoices arrive as emailed PDFs, scans, supplier portal uploads or structured electronic invoices? Each may need a different intake method. A structured e-invoice doesn't need OCR at all.
  2. Supplier record: Where is your trusted list of suppliers and their details kept, and who is allowed to change it?
  3. Purchasing records: Which invoices relate to a purchase order (PO), and where are POs and goods receipts recorded?
  4. Destination: Which accounting system receives the approved record, and how (API, import file, manual entry)?
  5. Approvers: Who approves what, and at which amounts or cost centers?
  6. Exception owner: When something doesn't check out, who is responsible for resolving it, and how quickly?

If the last question has no clear answer today, automation will move invoices faster into a queue nobody owns.

How invoices arrive, and what has to be read

A finance team rarely receives invoices one way. In the same week, the AP inbox may hold text PDFs, a scanned invoice, a phone photo of a delivery-day invoice, a file downloaded from a supplier portal and a structured e-invoice. Each channel needs a different intake step. The workflow should still produce one invoice record with the same fields, whatever the source.

From several intake channels to one invoice record

  • Emailed PDFText PDFs can be read directly; scanned PDFs need OCR
  • Paper scan or phone photoOCR plus an image-quality check
  • Supplier portalDownload step, then the PDF path
  • Structured e‑invoiceMap fields from the file; no OCR
  • EDI or file feedMap fields; validate the format

Intake: keep the original file, log the channel and identify the supplier

Read or map: extract fields from images and PDFs, or map them from structured files

One invoice record

  • Supplier and tax ID
  • Invoice number
  • Invoice and due dates
  • Currency
  • PO reference
  • Line items
  • Tax
  • Total

Each value keeps a link to its source, and extracted values keep their confidence.

Original MVO illustration. Channels and fields are typical examples; your suppliers and accounting system decide the exact list.
Intake channels and what each one needs
ChannelWhat arrivesIntake stepWatch out for
Emailed PDFA PDF attached to an email, sometimes several per messageSplit attachments, store the original, read text or run OCRStatements and reminders mixed in with invoices
Paper scan or phone photoAn image of a printed invoiceOCR, with an image-quality check firstSkewed, cropped or blurred images; handwriting
Supplier portalA file you download after logging inA scheduled or manual download, then the PDF pathPortal credentials and a download nobody owns
Structured e-invoiceA machine-readable invoice file (for example UBL XML)Validate the file and map its fieldsValid format doesn't mean the invoice is expected or correct
EDI or file feedBatches from larger suppliers or a procurement systemFormat validation and field mappingOne broken batch can hold many invoices

Extraction services are built for this mix. Microsoft's prebuilt invoice model documentation, for example, says invoices can arrive as phone-captured images, scanned documents and digital PDFs. It also lists key values the model returns, such as customer name, billing address, due date and amount due.

Structured e-invoices skip the reading step. In the EU, Directive 2014/55/EU led to the European e-invoicing standard EN 16931, and the Peppol BIS Billing 3.0 specification takes its element names from that standard. When a supplier sends a file like this, the workflow maps fields from the file instead of reading an image. It still runs every business check described below.

Fields the workflow needs, and the check that uses each one
FieldUsed forIf it's wrong or missing
Supplier name and tax IDMatching the invoice to the trusted supplier recordThe invoice can't be matched to a known supplier
Invoice numberDuplicate detection and the audit trailDuplicates slip through, or a correct invoice is flagged
Invoice date and due datePeriod, payment terms and approval deadlinesWrong accounting period or late payment
CurrencyTotals, tolerances and postingAmounts are compared in the wrong unit
PO referenceTwo-way or three-way matchingA PO invoice drops into the non-PO path
Line items (description, quantity, unit price)Price and quantity matchingPartial deliveries and price changes go unnoticed
Tax and totalArithmetic checks and postingThe posted amount doesn't match the document

Extraction quality is a separate topic, and the right OCR approach depends on your documents. For the workflow, the rule is simple: an uncertain or missing required field stops the invoice and goes to a person, with the source image beside the extracted value.

How an invoice moves through the system

Each stage should produce a clear output, and each stage needs a defined reason to stop.

Stages, outputs and stop conditions
StageOutput when it passesWhat stops processing
1. Receive and identifyOriginal file stored; supplier identifiedUnknown sender or unreadable file
2. Extract (if needed)Structured fields linked to the source documentRequired field missing or uncertain
3. ValidateFields pass business checks (totals add up, dates and tax fields make sense)A check fails
4. Check for duplicatesNo likely earlier copy foundA possible duplicate is found
5. Match (PO invoices)Invoice agrees with PO and, where required, receipt, within agreed tolerancesPrice or quantity mismatch
6. ApproveApproval recorded by the right person under company policyApproval rejected or overdue
7. Post and reconcileAccounting record created and its ID stored with the audit trailWrite fails or its result is unknown

Platforms that support this kind of process tend to treat extraction, review and approval as separate building blocks. SAP's invoice processing and approval tutorial mission, for instance, combines forms for entering or reviewing information, automated data extraction and an approval flow. Whatever you use, keep those pieces distinct, so a reading error never turns into an approval.

Validation checks and matching

Correct extraction tells you what the invoice says. Checks decide whether you should accept it. Most checks are deterministic: either they pass or they don't. A few depend on tolerances that finance sets. Some need judgment, and those should go to a person.

Common checks, what they compare and what a failure looks like
CheckComparesHypothetical failureType
Required fieldsEvery field the posting needs is presentNo invoice number on a scanned invoiceDeterministic
ArithmeticLines, subtotal, tax and totalLines add up to USD 600 plus USD 60 tax, but the stated total is USD 690Deterministic
Supplier recordInvoice supplier and tax ID against the trusted supplier recordTax ID doesn't match; supplier is inactiveDeterministic
Bank detailsPayment details on the invoice against the supplier recordNew account number printed on the invoiceAlways a person
DuplicateSupplier, invoice number, amount and date against earlier invoicesINV-2048 and INV 2048 for the same amountNeeds judgment
Two-way matchInvoice lines against PO linesUnit price USD 41 against a PO price of USD 40Tolerance
Three-way matchInvoice, PO and goods receiptInvoice for 12 units, receipt for 10Tolerance

Two checks worked through

Matching rules vary by organization. In Microsoft Dynamics 365 Finance, for example, matching policies let a company match invoices to purchase order lines (two-way matching) or to both purchase order lines and product receipt lines (three-way matching), with price tolerances it defines. Not every invoice has a PO, so a workflow also needs a separate path for non-PO invoices.

Duplicates are rarely exact copies. A reissued invoice may come back as "INV 2048" instead of "INV-2048", with a new date. Compare supplier, invoice number, amount and date, and normalize the invoice number before comparing it. Treat a match as a signal for review, not proof. Tune the rule during the pilot so it flags real risks without burying reviewers in false alarms.

Approval routing: who approves what

Routing decides which person sees a checked invoice and when. The usual keys are amount, cost center or department, supplier and exception type. Write these rules down before you automate them. Software can follow a rule exactly. It can't fix a rule nobody agreed on.

Three approval patterns, and the decisions that always reach a person

Checked invoice → routing rules (amount, cost center, supplier, exception type)

Sequential

  1. Budget owner
  2. Finance manager

Hypothetical A USD 25,000 marketing invoice. The finance manager sees the budget owner's decision first.

Parallel

  • Budget owner, Sales
  • Budget owner, Support

Hypothetical A software invoice split between two departments. Both approve, and neither waits for the other.

Escalation

  1. Approver
  2. Named backup after 2 business days
  3. AP lead decides

Hypothetical The approver is on leave. The invoice moves on instead of waiting.

May need no extra invoice approval

PO-matched within tolerance, known supplier, under the limit, if your policy says the PO approval covers it

Always a person

Bank-detail change · mismatch beyond tolerance · possible duplicate · non-PO invoice above the limit · unknown accounting write

Original MVO illustration. The amounts, roles and two-day limit are hypothetical; your approval policy sets the real ones.

Sequential, parallel and escalation

Workflow tools describe these patterns in similar terms. Microsoft's Power Automate documentation gives the example of a sequential approval policy that requires pre-approval for invoices over $1,000 before the finance department can approve them. In a parallel approval, several people must approve, and each approval is independent of the others. Dynamics 365 Finance lets an approval step set a time limit and an escalation path. An overdue document moves to the next person on the path, and if nobody responds, the system takes the end action you chose.

Choosing an approval pattern
PatternUse it whenHypothetical caseRisk if misused
Single approverOne person owns the budget and the amount is within their limitUSD 800 office supplies, cost center owner approvesOne person can approve their own spending without a check
SequentialThe second approver needs the first decision as contextUSD 25,000 campaign invoice: budget owner, then finance managerSlow if each step has no time limit
ParallelIndependent owners must each agreeSoftware cost split across Sales and SupportOne approver can be skipped if the rule treats either approval as enough
EscalationAn approval can stall because of leave or workloadNo response in 2 business days goes to a named backupEscalating to someone without authority for the amount

Write the approval matrix down

An approval matrix is a one-page table that the workflow follows. Here is the shape of one. The thresholds and roles are invented for illustration.

Hypothetical approval matrix (your thresholds and roles will differ)
Invoice type and amountApprover(s)PatternIf no response
PO-matched, within toleranceCovered by the PO approval, if policy says soNone extraNot applicable
Non-PO, under USD 5,000Budget ownerSingleNamed backup after 2 business days
Non-PO, USD 5,000 to 25,000Budget owner, then finance managerSequentialBackup, then AP lead
Cost shared by two departmentsBoth budget ownersParallelEach owner's backup
Supplier bank-detail changeSupplier-record owner, through an independent checkSeparate controlNever auto-approved by escalation

Before you switch routing on, test four things. Every queue has a named owner, not a shared mailbox. Every threshold is written down. Every exception type has a destination. Every escalation has a time limit that finance agreed.

Design the exception path before the happy path

It is tempting to start by connecting the case where everything is correct. The harder and more valuable work is deciding what happens when something isn't.

Hypothetical invoice
INV-2048 from a fictional supplier
12 units × USD 40
USD 480 before tax
  • PassRequired fields read: supplier, invoice number, date, lines and total
  • PassNo earlier copy of this invoice found
  • PassPurchase order: 12 units at USD 40
  • StopGoods receipt: 10 units, a two-unit difference

Result: not posted. A review task goes to the receiving owner with the invoice, PO, receipt and the difference.

Illustration of a fictional invoice. The checks are examples; your own rules decide what stops an invoice.

The flow, step by step

  1. Receive the invoice and keep the original file
  2. Identify the supplier and capture the fields
  3. Check required fields and business rules If a check fails: review queue, with a reason and an owner
  4. Check for a possible duplicate If it looks like a duplicate: review queue
  5. Match or code the invoice

    PO invoices are checked against the PO and receipt under policy. Non-PO invoices go to coding and budget-owner review.

    If PO, receipt and invoice don't match within approved tolerances: review queue
  6. Get approval under company policy
  7. Write the approved record to the accounting system

    If posting is confirmed: store the record ID and audit evidence.

    If posting isn't confirmed or is unknown: check the destination before any retry; unresolved cases go to review
  8. Resolve and re-enter

    Items resolved in review re-enter at the checks, keeping their earlier evidence. They don't repeat approvals or writes that already happened.

View the same flow as a diagram
Flowchart of the eight steps listed above: an invoice moves from receipt through field checks, duplicate check, PO matching or non-PO coding, approval and accounting posting, and every failed check routes to a review queue.
Conceptual flow, not a specification. Open the diagram full size.

Your systems may use different states, and payment release stays a separate, governed process.

Who owns each exception

Exception owners and release conditions
ConditionWhat the reviewer should seeSuggested ownerReleased when
Missing or uncertain required fieldSource document with the extracted value highlightedAP reviewerValue corrected or confirmed, with a record of who did it
Totals don't reconcileLine items, totals and the failed ruleAP reviewerDiscrepancy explained or corrected
Possible duplicateThe candidate records and the fields that matchedAP reviewerDuplicate decision recorded explicitly
Received quantity differs from invoiceInvoice, PO and received quantityReceiving or purchasing ownerResolution documented under finance policy
Non-PO invoiceCoding, purpose and approverBudget owner and APRequired review and approval complete
Supplier bank details changedThe change request and the current trusted supplier recordAuthorized supplier-record ownerChange verified through your approved independent process
Accounting write result unknownRequest reference, time and destination lookup resultIntegration support ownerDestination checked before any retry

When the accounting write times out

Imagine the accounting system's API times out right after the workflow submits an approved invoice. This is a hypothetical case. A timeout doesn't prove the write failed. A blind retry can create the very duplicate the earlier checks were built to stop. A safer sequence:

  1. Record the request reference and the time, and mark the invoice "write result unknown".
  2. Look the invoice up in the destination by your stored reference, or by supplier and invoice number.
  3. If the record exists, store its ID and mark the invoice posted. If it doesn't, retry using the API's duplicate protection, if it offers one.
  4. If the result is still unclear, send it to the integration owner's queue. Don't keep retrying.

Some accounting APIs offer duplicate protection for retries. Xero's idempotent requests guide, for example, describes an Idempotency-Key header for POST, PUT and PATCH requests. A repeated request with the same key returns the cached response instead of being processed again. Keys are stored for 6 minutes, so they cover quick retries, not a check the next morning. After repeated errors, the guide says to make a GET request to check whether the resource was already created.

These are design recommendations. They don't by themselves guarantee fraud prevention, compliance or correct accounting.

Use what you have, integrate, or build custom?

Start with what you already pay for. Many accounting and AP tools include capture, approval routing or matching features. Check those first.

Three ways to get there
OptionFits whenWatch out for
Existing featuresYour tools cover your intake channels, approval rules and exceptions with acceptable manual effortWorkarounds that live in someone's inbox
IntegrationThe gap is a handoff between systems that both support it, such as approved invoices moving from an AP tool into your ERPWho monitors the connection, and what happens on an unknown write
Custom softwareYour rules are complex, a key system has no suitable connector, or reviewers need a screen built around the evidence in the exception tableOwnership, maintenance and support after launch

Compare the total operating burden, not just the build cost. That means access and permissions, maintenance when a supplier changes format or a system updates its API, monitoring, and who supports it when something breaks.

Pilot with real invoices before you go live

A pilot should prove the workflow handles your messy cases, not just clean ones. Include:

  • several suppliers with different invoice layouts;
  • poor-quality scans and phone photos, if you receive them;
  • non-PO invoices, credit notes and partial deliveries;
  • a deliberate duplicate.
Hypothetical pilot sample of 100 recent invoices
GroupCountWhat it tests
PO invoices that should pass40Straight-through path and posting
PO invoices with known mismatches20Price and quantity tolerances, receiving owner queue
Non-PO invoices15Coding and approval routing
Poor scans and phone photos10Required-field stops and the review screen
Credit notes5Sign handling and matching to the original invoice
Deliberate duplicates5Duplicate rule and false-alarm rate
New supplier formats5Supplier identification and field mapping

Agree acceptance criteria with finance before you start. Run early postings in a test environment or as drafts that need confirmation, and verify what each connected system actually supports.

Extraction tools often attach a confidence score to each field, and teams use these to decide what goes to a person. Microsoft's transparency note for Document Intelligence describes customers calibrating their own thresholds to route content either to straight-through processing or to human review. Thresholds depend on your documents and your tolerance for errors, so set them from your pilot data rather than a generic number. A high confidence score means the text was probably read correctly. It doesn't mean the invoice is legitimate or should be paid.

Pilot exit questions

  • Can reviewers find the source evidence for every flagged invoice?
  • Does an unexpected or failed write stop safely, without a blind retry?
  • Can support check and resolve an accounting timeout?
  • Are permissions limited to each person's assigned tasks?
  • Can the team export the audit trail?
  • Is there a named owner and a written recovery procedure?

What to measure, and who owns it

Define each measure before you collect data, and record a baseline from your current process so comparisons are fair.

Pilot measures and how to define them
MeasureHow to define itWatch out for
Human touch timeStaff minutes spent per invoice, including exceptionsIt's not the same as waiting time
Elapsed timeFrom receipt to confirmed accounting recordState whether weekends and approval waits count
Field accuracyCorrect required fields ÷ required fields reviewedAccurate fields don't mean a correct invoice
Straight-through rateEligible invoices that reach the agreed endpoint with no human touch ÷ eligible invoicesDefine "eligible" and the endpoint; it isn't the same as auto-paid
Exception rate and ageFlagged invoices ÷ total, and time unresolved, by reasonA low rate alone doesn't prove quality
Posting integrityAccounting records reconciled to authorized source invoicesCheck for duplicates, missing records and unknown writes
Operating costSoftware, review time, support and maintenance for the periodSaved minutes don't automatically become cash savings

Give the workflow a named owner after launch. Supplier formats change, approval rules change and APIs change. Someone has to watch the exception queue and decide when a rule needs updating.

Sources

Official documentation and guidance, checked 5 November 2026. Product documentation shows that product's documented behavior, not every system's.

Back to top