Invoice Processing: Steps, Cost per Invoice and How to Improve It

Every business that buys from suppliers processes invoices. For a sole trader it might be a handful a month, paid from a banking app; for a mid-sized company it might be thousands, flowing through an AP team, approval chains and an ERP. The steps are fundamentally the same, and so are the problems: invoices lost in inboxes, waiting for approval, keyed with errors, paid twice or paid late.

This guide walks through the invoice processing workflow step by step, explains how to calculate what it costs you, describes the controls that prevent expensive mistakes, and sets out practical ways to make the process faster and more reliable. It applies whether you process invoices manually, with accounting software or with dedicated AP automation.

What invoice processing covers

Invoice processing sits within accounts payable, between procurement (which orders) and treasury (which pays). It starts when an invoice arrives and ends when the invoice is paid and archived. For the wider context of AP, see what is accounts payable.

The invoice processing workflow

Step 1: Receive

Invoices arrive by email, post, supplier portals, e-invoicing networks and occasionally by hand. Best practice is a single intake channel, typically a dedicated AP email address or the AP system's inbox, communicated to all suppliers. Invoices sent to individual employees are a leading cause of late payment and missed early payment discounts.

For paper invoices, scan on arrival so everything downstream is digital, and ask paper-only suppliers to switch to email or e-invoicing.

Step 2: Capture

The invoice's data must get into the system: supplier, invoice number, dates, PO number, currency, net amount, tax, total, bank details and, where needed, line items. Options:

• Manual keying: slow and error-prone at volume.
• Extraction from PDFs and scans using OCR and AI. See invoice data extraction.
• Structured e-invoices, which arrive as data and need no extraction. See e-invoicing.
• Supplier portals, where suppliers enter or upload invoices themselves.

Step 3: Validate

Before going further, check the invoice is legitimate and complete:

• The supplier exists in the master file and is active.
• The invoice number has not been processed before (duplicate check).
• Required fields are present: tax numbers, dates, totals.
• Arithmetic is correct: lines plus tax equal the total.
• Tax treatment is correct for the supplier and goods.
• Bank details on the invoice match the supplier master file. Any difference is a red flag for payment fraud.
• The invoice is addressed to the correct legal entity.

Step 4: Code

Assign the invoice to general ledger accounts, cost centres, projects or departments, and tax codes. For PO invoices, coding is usually inherited from the PO. For non-PO invoices, coding comes from supplier defaults, rules or the approver.

Step 5: Match

For PO-backed invoices, compare with the purchase order and goods receipt. See three-way matching for line-level matching and tolerances.

Step 6: Approve

Invoices that match within tolerance may be approved automatically. Non-PO invoices and exceptions need approval according to an approval matrix, typically based on amount, cost centre and category. Good approval workflows:

• Route automatically to the right approver.
• Show the invoice image and coding.
• Set deadlines and send reminders.
• Allow delegation during absence.
• Record who approved what and when.

Step 7: Post

The approved invoice is posted to the ledger, creating an accounts payable liability and recording the expense or asset. In accrual accounting this should happen in the period the goods or services were received; invoices arriving after month-end for prior-period supplies may need accruals.

Step 8: Pay

Approved invoices are scheduled for payment according to terms. Payment runs, typically weekly or twice weekly, group invoices by supplier and due date. Consider:

• Paying on the due date, not early, unless there is a discount.
• Taking early payment discounts when worthwhile.
• Sending remittance advices so suppliers can apply payments.
• Dual authorization of payment runs.

Step 9: Archive and reconcile

Store the invoice with its approval trail, linked to the ledger entry and payment. Then reconcile:

• The bank statement to confirm payments cleared as expected. See how to reconcile a bank statement.
• Supplier statements to catch missing invoices, unapplied credits and duplicates.

Worked example: tracing one invoice through the process

A facilities company receives an invoice from its cleaning contractor for March services, 3,600 plus 20% tax, total 4,320.

1. Receive: the contractor emails the PDF to the AP mailbox on 2 April.
2. Capture: extraction reads supplier, invoice number CL-2291, dates, net, tax and total, and the PO number for the annual cleaning contract.
3. Validate: the supplier is active, CL-2291 has not been seen before, the arithmetic is correct, and the bank details match the master file.
4. Code: the PO carries the cost centre and the cleaning expense account.
5. Match: it is a service PO, so two-way matching applies. The contract allows 3,600 per month; the invoice matches.
6. Approve: the facilities manager confirms the service was delivered in March through a one-click approval on 3 April.
7. Post: the invoice is posted to March, because the service was received in March, before the 5 April cut-off.
8. Pay: terms are 30 days from invoice date, so it is scheduled in the payment run nearest the due date, 1 May.
9. Archive and reconcile: the payment appears on the May bank statement and is matched to the invoice; the PDF, approval record and payment are linked in the system.

The whole internal process took two days of elapsed time and a few minutes of human effort. A missing PO number or a bank detail mismatch would have stopped it at step 3, which is exactly where such problems should be caught.

Calculating your cost per invoice

Published figures for the "average cost to process an invoice" vary widely, depend heavily on who was surveyed and how costs were counted, and often cannot be traced to a clear methodology. Your own number is more useful. Calculate it like this:

Cost per invoice = (staff cost + system cost + overheads + error cost) ÷ invoices processed

Component	How to estimate
Staff cost	Hours spent on AP tasks × loaded hourly cost, including approvers' time
System cost	Annual cost of AP software, scanning, storage, share of ERP
Overheads	Postage, printing, office space if material
Error cost	Duplicate and overpayments not recovered, late fees, lost discounts
Invoices processed	Count for the same period

Worked example

A company processes 18,000 invoices a year.

• Three AP clerks spend 85% of their time on invoices: 3 × 1,700 hours × 0.85 = 4,335 hours. At a loaded cost of 32 per hour: 138,720.
• Approvers spend an estimated 4 minutes per invoice: 18,000 × 4 ÷ 60 = 1,200 hours at 55: 66,000.
• Software and scanning: 24,000.
• Lost early payment discounts and late fees: 9,500.
• Duplicate payments not recovered: 3,200.

Total: 138,720 + 66,000 + 24,000 + 9,500 + 3,200 = 241,420. Cost per invoice: 241,420 ÷ 18,000 ≈ 13.41.

The breakdown is more useful than the headline: approver time and lost discounts together cost about 75,500, about 31% of the total, which suggests faster approvals would pay off as much as faster capture.

How many invoices can one person process?

Throughput depends on invoice complexity, the share of PO vs non-PO invoices, exception rates, system quality and how much of capture is automated. A clerk keying multi-line invoices manually processes far fewer per day than one reviewing exceptions from an automated system. Rather than relying on benchmarks, measure: count invoices processed and hours spent for a few weeks, and track how the figure changes as you improve the process.

Where the time actually goes

In most AP teams, a minority of invoices consume the majority of effort. Typical time sinks:

• Chasing approvals, especially for non-PO invoices.
• Exceptions: price and quantity mismatches, missing PO numbers.
• Supplier queries: "When will we be paid?"
• Manual keying of line items.
• Duplicates and corrections.
• Month-end accruals for invoices not yet received.

Tag exceptions by cause for a month and you will usually find two or three causes accounting for most of them, each with a fixable root.

Controls that matter most

Risk	Control
Payment to fraudster after fake "change of bank details" request	Verify any bank detail change by phone to a known number; dual approval of master data changes
Duplicate payment	System duplicate checks on supplier + invoice number + amount; supplier statement reconciliation
Fictitious supplier	Supplier onboarding checks; segregation between supplier setup and payment
Overbilling	PO matching with tolerances
Unauthorized spend	Approval matrix; POs for defined categories
Payment errors	Dual authorization of payment runs; bank reconciliation

Business email compromise, where fraudsters impersonate suppliers or executives to redirect payments, is one of the most damaging risks for AP teams. The bank detail verification control is simple and highly effective.

Designing an approval matrix

Approvals are often the slowest part of invoice processing, and a clear matrix is the fix. An example for a mid-sized company:

Invoice type	Amount	Approver
PO invoice matched within tolerance	Any	Automatic (PO was approved)
PO invoice with exception	Any	Requester, then buyer for price issues
Non-PO invoice	Up to 1,000	Budget holder
Non-PO invoice	1,000 to 10,000	Budget holder and department head
Non-PO invoice	Over 10,000	Department head and finance director
Recurring contract invoice	Within contract value	AP, checked against contract schedule

Principles behind a good matrix:

• Approve once. If a PO was approved, a matching invoice should not need a second approval.
• Match authority to risk. Low-value invoices should not wait for senior managers.
• No self-approval. People should not approve invoices from suppliers they set up or for purchases that benefit them.
• Deadlines and escalation. An invoice waiting more than a few days escalates automatically.
• Delegation. Approvers on leave delegate to a named colleague with equivalent authority.

Review the matrix annually and when the organisation changes.

Month-end, accruals and cut-off

Invoice processing does not stop at month-end, but the books must close. Common practices:

• Cut-off date for posting invoices to the closing month, typically a few working days after month-end.
• Accruals for goods and services received but not yet invoiced, from goods received not invoiced reports, open POs and managers' estimates.
• Reversal of accruals at the start of the next month, when the actual invoices are posted.
• Review of unapproved invoices relating to the closing month, so material ones are accrued.

Fast invoice capture makes month-end more accurate, because fewer invoices are sitting unprocessed in inboxes when the books close. See our month-end close checklist.

Communicating with suppliers

Many AP hours go on answering supplier queries. Reduce them by:

• Publishing invoicing requirements: where to send invoices, what they must include (PO number, legal entity name, tax details), and payment terms.
• Sending remittance advices automatically with each payment.
• Offering a supplier portal or a status lookup, where volume justifies it.
• Rejecting incomplete invoices quickly, with a clear reason, rather than letting them sit.
• Being consistent about payment days, so suppliers know when to expect money.

Good communication shortens the payment cycle and strengthens supplier relationships, which can matter when negotiating prices or securing supply.

Small business invoice processing

Small businesses can follow the same steps with lighter tools:

1. Have suppliers send invoices to one email address, forwarded to your accounting software's document inbox.
2. Let the software extract the details and create a draft bill.
3. Check it, code it and approve it, which may be the owner's job.
4. Pay through online banking or the software's payment feature on the due date.
5. Match the payment when it appears in the bank feed or imported statement, and reconcile monthly.

If bank feeds are missing for some periods, convert PDF bank statements with a bank statement converter and import them so payments can be matched to bills.

Improving invoice processing: a practical roadmap

1. Centralize intake in one channel.
2. Clean supplier master data: remove duplicates, verify bank details.
3. Define an approval matrix and set approval deadlines.
4. Automate capture with extraction or e-invoicing.
5. Introduce PO matching for the categories where it matters.
6. Tag and fix exception causes monthly.
7. Schedule payment runs and take worthwhile discounts.
8. Reconcile bank and supplier statements monthly.
9. Measure cost per invoice, cycle time and exception rate quarterly.

See accounts payable automation for tools that support these steps.

Key performance indicators

KPI	Definition
Cost per invoice	Total AP processing cost ÷ invoices
Cycle time	Days from receipt to approval (or to payment)
First-pass rate	Share of invoices processed without exceptions
Exception rate	Share of invoices with exceptions, by cause
On-time payment rate	Share paid by the due date
Discount capture rate	Discounts taken ÷ discounts available
Duplicate payment rate	Duplicates found ÷ invoices paid
Invoices per FTE	Throughput per full-time AP employee

Common pitfalls

• Multiple intake channels, so invoices go missing.
• Keying everything manually when capture could be automated.
• No duplicate checks beyond human memory.
• Approvals stuck with busy managers.
• Paying everything immediately, harming cash flow, or paying late, harming supplier relationships.
• Ignoring bank detail changes as a fraud vector.
• Not reconciling bank and supplier statements.

Frequently asked questions

What are the steps of invoice processing?

Receive the invoice, capture its data, validate it, code it to accounts, match it to purchase orders and receipts where applicable, approve it, post it to the ledger, pay it according to terms, and archive it while reconciling payments.

How much does it cost to process an invoice?

It varies widely by organisation. Calculate your own cost by adding staff time (including approvers), systems, overheads and error costs, then dividing by the number of invoices processed. The breakdown shows where improvements will pay off most.

How can I process invoices faster?

Centralize intake, automate data capture, clean supplier master data, use clear approval rules with deadlines, match PO invoices automatically and fix the root causes of exceptions.

What is the difference between invoice processing and accounts payable?

Invoice processing is the workflow for handling individual supplier invoices. Accounts payable is the broader function and ledger, including supplier management, payments, reconciliations and reporting.

Who should approve supplier invoices?

The budget holder or person responsible for the purchase, according to an approval matrix based on amount and category. Invoices matched to an approved purchase order often need no further approval. Nobody should approve invoices relating to suppliers they created or purchases that benefit them personally.

Should invoices be paid as soon as they are approved?

Usually not. Paying on the due date keeps cash in the business longer without harming the supplier relationship. The exception is when an early payment discount is worth more than the cost of paying early.

How do I prevent duplicate invoice payments?

Use system checks on supplier, invoice number, date and amount, require unique invoice numbers, reconcile supplier statements regularly and review payments before each payment run.

Summary

Invoice processing turns supplier invoices into accurate, approved and timely payments through nine steps: receive, capture, validate, code, match, approve, post, pay and archive. Measure your own cost per invoice and where time goes, put strong controls on bank details and duplicates, automate capture and clean matches, and attack exception causes.

Close the loop by reconciling payments: StatementPilot converts bank statements into spreadsheets or import files so every invoice payment can be matched.