Invoice processing in accounts payable is everything that happens to a supplier invoice between arrival and payment. The invoice is received, its data captured, checked for errors and duplicates, matched to a PO when there is one, coded to the right accounts, and approved. Any exceptions are fixed, then the invoice is scheduled and paid, and the record is reconciled and filed.
Invoice processing is the work itself. Invoice automation is software that handles the repetitive parts of that work.
What Is Invoice Processing in Accounts Payable?
Invoice processing is the invoice-level core of accounts payable. Its job is to make sure every supplier invoice is real, correct, approved by the right person, recorded in the right accounts, and paid on agreed terms, with no duplicates.
It's a narrower topic than the full accounts payable process, which also includes purchasing, receiving, and month-end work. This guide zooms in on the invoice itself.
What to Check on Every Supplier Invoice
Before anything else, AP needs to know what a good invoice looks like. Here's a sample invoice with the fields that matter most:
The Invoice Processing Workflow at a Glance
| Stage | What happens | Common issue |
|---|---|---|
| 1. Receipt | Invoice enters AP | Invoice sent to the wrong person and lost |
| 2. Capture | Data is entered or extracted | Wrong amount or invoice number |
| 3. Validation | Details and duplicates are checked | Duplicate or incomplete invoice |
| 4. Matching | Invoice is compared with PO and receipt | Quantity or price mismatch |
| 5. Coding | Accounting fields are assigned | Wrong GL account or cost center |
| 6. Approval | An authorized person reviews it | Approval delay |
| 7. Exceptions | Problems are resolved | Price, tax, or missing-document issues |
| 8. Payment | Invoice is scheduled and paid | Missed due date or discount |
| 9. Reconciliation | Records are updated and checked | Unmatched payment |
| 10. Archive | Documents are retained | Missing audit trail |
How Invoice Processing Works, Stage by Stage
1Receipt
Invoices arrive by email, supplier portal, e-invoicing or EDI, or mail. The best setup routes them all to one AP-controlled inbox or portal, so nothing sits in a manager's personal email. Paper invoices are scanned on arrival.
2Capture
Key data is entered or extracted: supplier, invoice number, invoice date, due date, PO number, line items, tax, and total. Many teams use OCR or AI-based extraction to read PDFs, then a person checks the fields the software is unsure about.
3Validation
AP confirms the invoice is complete and legitimate: a known supplier with matching remit-to details, a unique invoice number, correct math and tax, and valid terms. Duplicate checks look for the same supplier, number, and amount, and also near-duplicates like "INV-1042" vs "1042".
4Matching
If there's a PO, the invoice is compared with it (two-way) and with the receiving report (three-way). Non-PO invoices skip this step and go through owner review instead. See matching and tolerances below.
5Coding
The invoice gets its accounting details: GL account, and where relevant, department, cost center, project, and tax treatment. PO invoices often inherit coding from the PO. Non-PO invoices are usually coded by AP or the budget owner. Depending on the company, coding happens before approval or during it.
6Approval
The invoice goes to whoever is authorized under company policy, often based on amount, department, or budget owner, with higher amounts needing more senior sign-off. Thresholds vary widely, so they should be written down and enforced consistently. Learn how approval fits within the invoice workflow.
7Exception handling
Any invoice that fails validation, matching, or approval is held while the problem is fixed. More on this below.
8Payment
Approved invoices are scheduled based on terms and cash plans, then paid by ACH, check, card, or wire, usually in a regular payment run.
9Recording and reconciliation
The invoice was recorded as a liability (debit expense or inventory, credit accounts payable). When it's paid, AP is debited and cash credited. The payment is later matched to bank records and supplier statements during accounts payable reconciliation.
10Archive
The invoice, PO, receipt, approval history, and payment proof are stored together. Auditors use this trail to confirm who approved what and when, and AP uses it to answer supplier questions quickly.
Validation vs Matching vs Coding
These three checks are easy to blur together, but each answers a different question:
| Check | Question it answers | Compares against |
|---|---|---|
| Validation | Is this a real, complete, correct, unique invoice? | The invoice itself, the supplier record, and past invoices |
| Matching | Did we order and receive what we're being billed for? | The PO and receiving report |
| Coding | Where does this cost belong in the books? | The chart of accounts and budgets |
PO Invoices vs Non-PO Invoices
Not every invoice has a purchase order. Utilities, rent, subscriptions, legal fees, and one-off services often don't. Those invoices need a separate path:
| PO invoice | Non-PO invoice | |
|---|---|---|
| Proof it was authorized | The approved PO | Contract, budget, or owner confirmation |
| Main check | Two-way or three-way match | Budget owner review |
| Coding | Usually from the PO | Assigned by AP or the owner |
| Supporting documents | PO and receiving report | Contract, statement of work, or receipt confirmation |
| Main risk | Price or quantity differences | Paying for something nobody authorized |
Two-Way vs Three-Way Matching, and Tolerances
| Method | Compares | Often used for |
|---|---|---|
| Two-way | PO and invoice | Services, or purchases without a receiving step |
| Three-way | PO, receiving report, and invoice | Physical goods where receipt matters |
Tolerances are small differences a company allows before an invoice is flagged, such as minor freight charges or rounding. They're usually set as a percentage, a dollar amount, or both.
| PO amount | Invoice amount | Difference | Result |
|---|---|---|---|
| $1,000 | $1,012 | $12 (1.2%) | Within tolerance, moves on |
| $1,000 | $1,030 | $30 (3%) | Over 2%, flagged |
| $10,000 | $10,090 | $90 (0.9%) | Over $50, flagged |
How Invoice Exceptions Get Resolved
| Exception | Usual fix | Usual owner |
|---|---|---|
| Missing PO | Buyer confirms the purchase, or invoice moves to the non-PO path | Procurement or requester |
| Price mismatch | Corrected invoice or approved price change | Procurement and supplier |
| Quantity mismatch | Credit memo or updated receipt | Receiving and supplier |
| Duplicate invoice | Reject and notify supplier | AP |
| Tax error | Corrected invoice from supplier | AP and supplier |
| Missing approval | Reroute or escalate | Approver or their manager |
| Changed bank details | Verify by phone with a known contact before paying | AP and supplier master owner |
See where these loops sit in the full workflow on our accounts payable process flow chart.
Credit Memos and Debit Memos
A credit memo is a document from the supplier that reduces what you owe, usually for returns, damaged goods, overbilling, or an agreed discount. It's recorded against the supplier and applied to an open invoice, or held for a future one.
A debit memo is a document you create to tell the supplier you're reducing what you'll pay, for example for a short shipment. Many companies then ask the supplier to issue a matching credit memo so both sides agree.
| Account | Debit | Credit |
|---|---|---|
| Accounts Payable | $200 | |
| Inventory (or the original expense account) | $200 |
Approved Doesn't Mean Paid
Four separate things happen after the invoice clears its checks, and they're often done by different people on different days:
| Step | What it means |
|---|---|
| Approval | An authorized person confirms the invoice is valid to pay |
| Payment scheduling | Finance picks the pay date based on terms, discounts, and cash |
| Payment execution | Treasury or AP actually releases the money |
| Payment reconciliation | The payment is matched to the bank and closes the invoice |
An invoice approved on Day 5 might not be paid until Day 30 if the terms are Net 30. That's normal, and it's how businesses manage cash.
Who Touches an Invoice?
| Role | Part in invoice processing |
|---|---|
| AP clerk or specialist | Receipt, capture, validation, matching, coding, exceptions |
| Requester | Confirms goods or services were received |
| Budget owner | Approves non-PO invoices and confirms coding |
| Procurement | Resolves PO and pricing questions |
| Finance manager or controller | Approves larger invoices and owns policy |
| Treasury or payments team | Schedules and releases payment |
Common Invoice Processing Challenges
- Lost invoices sent to individuals instead of AP
- Manual typing that leads to wrong amounts or numbers
- Near-duplicate invoices that slip past basic checks
- Slow approvals that cause late payments and lost discounts
- Non-PO invoices with no clear owner
- No visibility into where each invoice stands
- Fake "bank change" requests targeting AP
Invoice Automation: What It Does and Doesn't Do
Invoice automation software handles repetitive work so AP can focus on exceptions. Results depend on how clean your invoices are, how your workflow is designed, and how many exceptions you get.
Automation can help with
- Capturing invoices from email or upload
- Extracting data with OCR or AI
- Flagging likely duplicates
- Suggesting coding
- Routing approvals by rules
- Tracking status and keeping an audit trail
It doesn't replace
- Resolving exceptions
- Approval decisions
- Supplier disputes
- Chasing missing documents
- Judgment on unusual invoices
- Accounting decisions
When should you automate invoice processing?
It's usually worth a look when invoice volume keeps growing, approvals depend on email, invoices are hard to find, duplicates have slipped through, or the team spends much of its week typing data and chasing sign-offs. Read more about automated invoice processing.
How this works in Quick Payable
As one example of a product-specific setup: Quick Payable runs inside Salesforce. Invoices come in by email or upload, AI OCR extracts the fields, and duplicates are flagged and rejected. Approvals route to an assigned approver and escalate to their manager above that person's monetary limit. Suppliers can submit invoices and check status through a vendor portal, and every action is recorded on the invoice. Ask in a demo how PO matching and payment steps would work with your setup.
See How Invoice Processing Works in Salesforce
Book a free Quick Payable demo to see invoice capture, approvals, and AP tracking in Salesforce, using a few of your own invoices. 15-day free trial, no credit card required.
Best Practices for Invoice Processing
- Send every invoice to one AP inbox or portal, and tell suppliers in writing
- Ask suppliers to put the PO number on every invoice
- Validate before routing for approval, so approvers only see clean invoices
- Write down coding rules and approval limits
- Give non-PO invoices a named budget owner
- Set clear matching tolerances and review them yearly
- Give each exception type an owner and a deadline
- Verify bank detail changes by phone, every time
- Track processing time and exception rate monthly
Conclusion
Good invoice processing comes down to a few habits: get every invoice into one place, check it before anyone approves it, match it when there's a PO and get owner sign-off when there isn't, and fix exceptions quickly. When the volume makes those habits hard to keep up by hand, that's the point where automation is worth exploring.
Frequently Asked Questions
It is the set of steps AP follows to receive, capture, validate, match, code, approve, pay, record, and file a supplier invoice, so every invoice is correct, authorized, and paid on agreed terms.
Common steps are receipt, data capture, validation, matching to the PO and receipt, coding, approval, exception handling, payment, recording and reconciliation, and archiving.
Invoice processing is the work of handling an invoice from receipt to payment. Invoice automation is software that performs the repetitive parts of that work, such as data extraction, duplicate checks, and approval routing.
Invoice coding assigns accounting details to an invoice, such as the GL account, department, cost center, project, and tax treatment, so the cost is recorded in the right place.
Validate it, confirm it with the budget owner or against a contract, code it to the right accounts, attach supporting documents, and route it for approval under your non-PO policy before payment.
A matching tolerance is a small allowed difference between the invoice and the PO, set as a percentage, a dollar amount, or both, below which the invoice can proceed without being flagged.
The invoice is held, the reason is identified, and the owner fixes it through a corrected invoice, a credit memo, an updated receipt, or an approved variance. It is then revalidated before payment.
Not usually. After approval, the invoice is scheduled based on its payment terms and the company's payment runs, then paid and later reconciled to bank records.
Shyam Agarwal is a technology professional with 12+ years of experience in Salesforce consulting, development, and administration. He writes about accounts payable, AP automation, and Salesforce, drawing on his experience delivering scalable technology solutions that support business needs and improve operational efficiency.