Learn · Accounts payable
Invoice processing: how the AP workflow actually works
Learn the invoice-processing workflow, including two-way and three-way matching, approvals, bottlenecks, automation, duplicate controls, and reconciliation.
On this page
In short
How does invoice processing work?
Invoice processing is the accounts-payable workflow that turns a supplier bill into a controlled payment and accounting record. AP receives the invoice, validates required fields, checks for duplicates, matches it to an order and receipt when applicable, resolves exceptions, obtains approval, posts the liability, schedules payment, releases funds, and reconciles the result.
The AP workflow from inbox to ledger
The exact system varies, but a defensible workflow preserves the same evidence and decision points.
Receive and timestamp
Capture the invoice through a controlled channel, preserve the original, and record when it arrived. FAR 32.905 requires the designated billing office to annotate the actual receipt date, illustrating why the start of the payment clock must be observable.
Validate the invoice
Confirm supplier identity, invoice number and date, buyer entity, order or contract reference, description, quantities, prices, tax treatment, currency, total, terms, and exception contact. Return a defective invoice with a precise reason instead of leaving it in a silent queue.
Check supplier master and duplicates
Compare the invoice against supplier identity, verified payment instructions, prior invoice numbers, amounts, dates, orders, and service periods. A duplicate check should flag near matches, not only identical strings.
Match authorization and receipt
For ordered spend, compare the invoice to the purchase order and, where required, the goods receipt or service acceptance. Investigate differences beyond approved tolerances before payment.
Route the exception or approval
Send the invoice to the budget owner, buyer, receiver, tax reviewer, or security owner that can answer the specific question. Record the decision, not just a forwarded email.
Post and schedule
Create the payable with the right entity, supplier, account, department, project, tax, currency, invoice date, due date, and payment terms. Schedule according to approved terms and cash policy.
Release and reconcile
Require payment authority distinct from preparation where practicable. Then reconcile the payment instruction, bank debit, settlement status, payable clearing, and any fee, withholding, credit, or return.
Two-way and three-way matching explained
Match the documents the purchase actually produced
| Feature | Non-PO reviewInvoice plus approval | Two-way matchPO plus invoice | Three-way matchPO plus receipt plus invoice |
|---|---|---|---|
| Primary evidence | Contract, business purpose, service evidence, approver | Authorized quantity and price versus billed quantity and price | Authorized, received, and billed quantities and prices |
| Useful for | Rent, utilities, subscriptions, professional services | Spend ordered without formal receiving | Physical goods or measured delivery |
| Potential exception | Missing owner or unclear service period | Price or quantity exceeds PO | Receipt missing or quantity differs |
| What it cannot prove alone | Whether coding and tax are correct | Whether delivery occurred | Whether supplier and bank details are genuine |
Oracle’s procurement documentation defines two-way as purchase-order and invoice quantities matching within tolerance, and three-way as purchase-order, receipt, and invoice quantities matching within tolerance.
The receiving record is not paperwork for its own sake. GAO identified matching the type and quantity received to the order or contract, plus preventing duplicate and early payment, as essential controls when payment is authorized without a traditional vendor invoice. FAR 32.905 likewise requires receiving or other authorization documentation for invoice payments in its scope. For services, define what acceptance evidence replaces a warehouse receipt.
A tolerance is an exception rule, not permission to overpay casually. In a configured matching system, it determines whether a documented variance blocks the match. The organization must decide which field, amount, percentage, supplier, and category qualify. A price variance, quantity variance, tax difference, or freight line may need different ownership even when the total difference is small.
Why invoices get stuck
| Bottleneck | Root question | Operational fix |
|---|---|---|
| No order reference | Who authorized this spend? | Require an owner and documented exception path |
| Missing receipt | Did goods or services arrive? | Make receiving easy and assign it before delivery |
| Price or quantity mismatch | Which record is wrong? | Route to buyer or receiver with all three documents |
| Wrong legal entity | Who contracted and owes? | Validate buyer identity at vendor onboarding |
| Unclear tax | Is the tax treatment supported? | Send structured fields and evidence to tax review |
| Approval drift | Who has authority now? | Maintain role-based rules and backups |
| Duplicate suspicion | Was this obligation already paid? | Search normalized supplier, amount, date, and order data |
| Bank-detail change | Is the destination genuine? | Pause and verify through a known independent channel |
What invoice-processing software actually automates
Automation begins with data quality. The European Commission defines an eInvoice as structured data that allows automatic electronic processing and says it can be imported into AP without manual entry. It distinguishes that from a PDF, which removes paper but still presents visual data that generally must be read and entered. OCR can extract a PDF, but extraction confidence and validation remain controls.
Automate the clerical work, retain accountable decisions
| Feature | Good automation targetRepeatable rule | Human or governed decisionBusiness judgment |
|---|---|---|
| Intake | Capture channel, timestamp, file, structured fields | Confirm an unusual or damaged document |
| Validation | Required fields, totals, tax math, duplicates | Resolve ambiguous or unsupported content |
| Matching | Compare PO, receipt, invoice within tolerance | Decide whether a variance is acceptable |
| Routing | Send by entity, owner, amount, category | Approve business purpose and authority |
| Payment | Build due-date queue and payment proposal | Verify changed destination and authorize release |
| Audit | Preserve event log and attached evidence | Review override patterns and control failures |
GAO guidance calls for separation of purchasing, receiving, accounting, and disbursing duties where practicable, plus duplicate controls in automated systems.
A practical invoice-processing control list
- Give suppliers one documented intake route and reject invoices sent only to individual employees.
- Maintain a unique invoice record before approval so forwarding and resubmission cannot create a second payable.
- Require an order, contract, or named non-PO owner before accounting can post the liability.
- Capture receipt or service acceptance separately from invoice approval.
- Make every hold show a reason, owner, next action, and age.
- Separate supplier creation, bank-detail verification, invoice approval, payment preparation, and release where team size permits.
- Report overrides, duplicates caught after payment, late approvals, return rates, and unmatched credits to improve the process.
- Reconcile paid invoices to the bank and ledger, including fees, withholding, credits, and rejected transfers.
Invoice-processing questions
What is the difference between invoice processing and invoice approval?
Processing is the entire receipt-to-reconciliation workflow. Approval is one decision within it: an authorized person accepts the business purpose, coding, amount, and exception resolution before payment.
What is two-way invoice matching?
It compares the invoice with the purchase order, normally testing billed quantity and price against ordered quantity and price within defined tolerances. It does not prove receipt.
What is three-way invoice matching?
It adds the receiving record to the purchase order and invoice. The organization verifies that what was ordered, what was received, and what was billed agree within policy before payment.
How should services be matched when there is no goods receipt?
Define service-acceptance evidence in advance, such as a milestone approval, timesheet, deliverable sign-off, or usage record, and link it to the contract, period, and invoice.
Is a PDF invoice an eInvoice?
Not under the European Commission definition used here. A structured eInvoice contains machine-readable data for automatic processing. A PDF is digital but generally remains a visual document unless data is extracted and validated.
Should AP automatically pay invoices that match?
Only if the organization has explicitly designed that control for the spend type and risk. Matching does not authenticate a new bank account, prove tax treatment, or replace payment authorization and cash controls.
How do you prevent duplicate invoice payments?
Create one intake record, normalize supplier and invoice identifiers, compare amount, date, order, service period, and prior payments, restrict overrides, mark paid documents, and review near-match alerts. GAO guidance calls for both procedural and automated duplicate controls.
Sources
External links open in a new tab.
- Payment documentation and process, FAR 32.905 — Acquisition.gov
- Match approval level options — Oracle
- Vendor’s invoice — US Government Accountability Office
- Policy and Procedures Manual, Title 7 — US Government Accountability Office
- What is eInvoicing? — European Commission
- Invoice data extraction — Microsoft Learn
- Business Email Compromise — Federal Bureau of Investigation
Written by
Glide Editorial
Research desk
Glide Editorial covers cross-border money, stablecoin rails, travel finance, and living abroad. Guides are researched for practical accuracy and updated when rails, fees, or regulations change.
- Published
- Last reviewed
Glide · Borderless banking
Moving money across borders?
Hold crypto and 80+ currencies in one account, convert close to the mid-market rate, and pay out on local rails instead of paying the wire tax. Solo, or with multisig for teams.
- Currencies
- 80+
- Spend anywhere
- Visa card
- Registered with
- FINTRAC · Canada