Invoice Processing at a Glance

What is incoming invoice processing?

Incoming invoice processing refers to the activities involved in receiving, recording, validating, approving, posting, preparing for payment and retaining supplier invoices. It forms the operational core of the accounts payable function, where each supplier invoice becomes a recorded liability with a named owner and a due date.

Every supplier invoice connects a set of business records that need to stay aligned, including:

• Supplier identity and payment details
• Purchase orders and goods received notes (where applicable)
• Contracts or service confirmations
• Accounting codes and cost centres
• Approval decisions
• Payment and reconciliation records
• Shared accounts payable inboxes
• Supplier portals
• PDF email attachments
• Electronic invoice formats such as Peppol, BIS and UBL
• Scanned or paper invoices from smaller suppliers

Invoices may arrive through a variety of channels, including:

Regardless of how it arrives, every supplier invoice should follow the same controlled invoice workflow for validation, approval and posting. The outcome is a correctly coded record with the appropriate VAT treatment, ready for payment and reconciliation, with all supporting documentation retained in line with legal and organisational requirements.

What effective invoice processing delivers

• Payment of supplier invoices that are valid and authorised
• Visibility of liabilities and the cash needed to settle them
• Accurate accounting, VAT treatment and month-end reporting
• Lower risk of duplicate payments and processing errors
• Fewer late-payment fees and fewer missed early-settlement discounts
• Named approval owners and a visible list of outstanding actions
• Faster resolution of discrepancies with suppliers and purchasing
• More predictable supplier communication about payment status
• Approval evidence that can be produced for audits and internal reviews
• Consistent control across distributed and hybrid finance teams

How incoming invoice processing works

1. Receive and capture the invoice

Every invoice arrives at one collection point. Invoice processing software captures the supplier name and identifier, invoice number and date, payment terms, currency, the net, VAT and gross amounts, and the purchase order or contract reference.

OCR reads text from scans and PDFs. Intelligent Document Processing (IDP) goes further, identifying the document type and extracting fields without anyone keying them. Where extraction confidence scores below a set threshold, the invoice goes to a person to check.

Read more on invoice data capture.

2. Validate invoice data

Validation checks completeness and accuracy before an invoice travels any further. The checks cover supplier details, invoice number and date, VAT information, calculations and totals, payment terms, currency, possible duplicates, and any change to supplier or bank details since the last payment.

Anything missing, inconsistent or suspicious goes down a review path with a named owner instead of continuing into approval.

Read more on invoice validation.

3. Match and code the invoice

At this stage, invoice matching compares the invoice against the purchasing record. PO and non-PO invoices diverge here: a PO invoice is checked against the purchase order and, for goods, the goods received note. A non-PO invoice has no purchasing record to check against and depends instead on coding, supporting evidence and the person who owns the spend.

Coding assigns the general ledger account, cost centre, project, department and tax code. Tolerances decide what passes automatically, and any invoices that fall outside tolerance, or that have no matching order at all, are routed to whoever can resolve the issue.

Read our guide to three-way matching.

4. Review and approve the invoice

The invoice approval process routes each invoice by value, supplier, cost centre, department, purchase order status or exception type. Approvers see the invoice and its supporting records together, so they can judge the charge without asking accounts payable (AP) to forward anything.

Approval limits determine who can authorise different amounts, while reminders, delegated approvers and escalations help prevent invoices from sitting in someone's inbox. Every approval, rejection and comment is recorded, creating a clear audit trail.

Read more on the invoice approval workflow.

5. Post and prepare the invoice for payment

Approved invoice data transfers to your ERP or accounting platform. Before posting, the accounting code, VAT treatment, payment terms and due date are validated, and the invoice enters the appropriate payment run.

The original invoice, supporting evidence, approval history and the accounting entry remain linked, so each can be accessed from the others. The payment is executed through BACS or Faster Payments using your banking or payment platform.

6. Reconcile and retain the records

Reconciliation confirms that the invoice, the payment and the accounting entry agree. It also resolves the cases where they do not, such as short payments, overpayments, credit notes, unapplied payments and unmatched bank transactions.

Once reconciliation is complete, the invoice and its supporting records are retained together so they can be retrieved whenever they're needed for audits, queries or compliance. Access controls determine who can view them, while retention policies ensure records are kept for the required period before review or disposal.

Read more on invoice reconciliation.

Where invoice processing typically breaks down

Fragmented invoice intake

Anything sent to an individual employee is invisible to AP until that person forwards it, which can take days. The volume of documents arriving across personal mailboxes, post trays and portals also makes it impossible to say how many invoices are in progress at any moment.

Missing supplier or purchase order references

An invoice without a usable PO number or supplier identifier cannot be matched automatically, so it drops out of the flow at the first check. This often happens when goods or services are ordered without a purchase order being raised, leaving nothing to match the invoice against.

Repeated manual data entry

The same invoice details get keyed more than once when the AP system, ERP and a spreadsheet each need the data. This introduces transposition errors that often go unnoticed until reconciliation, long after they could have been corrected at source.

Inaccessible supporting documents

Approvers who cannot see the delivery note or the contract alongside the invoice either approve without checking or delay while they ask for it. In either case, the approval process becomes less effective and takes longer than it should.

Undefined coding and approval ownership

When coding responsibilities and approval ownership are unclear, invoices can spend days being passed between teams while the right approver is identified. Non-PO invoices are particularly affected because there is no purchase order to indicate who requested or authorised the purchase.

Delayed matching and exception resolution

Exceptions accumulate when nobody is responsible for reviewing them each day. A pricing variance that could have been resolved when the invoice arrived often requires significantly more investigation if it isn't identified until weeks later.

Limited invoice-status visibility

When accounts payable teams can't see where an invoice has reached, answering supplier queries becomes slow and time-consuming. At month end, the lack of visibility also makes it harder to produce accurate accruals, because invoices still awaiting approval have yet to reach the ledger.

Duplicate invoices and supplier-data risks

Duplicate invoices can arise when a supplier resends an invoice or statement, or when the same document enters the process through more than one channel. Without automated checks against details such as the supplier, invoice number and amount, duplicate payments become much more likely and can be time-consuming to recover.

How automation and AI support the invoice process

Capturing and classifying invoices

Invoice processing software collects invoices from every channel, identifies the document type and the supplier, extracts header and line-item data, and creates the metadata the later stages rely on. Artificial intelligence (AI) and machine learning models improve extraction accuracy as they see more of your supplier documents. Where the extraction scores below the accepted threshold, the invoice routes to a person rather than continuing on uncertain data.

Read more on invoice data capture and AI in invoice processing.

Validating and matching information

Required field checks, VAT and calculation checks, duplicate detection, and validation against supplier master data all take place before the invoice reaches an approver. Where purchase orders and goods received notes are available, automated invoice matching applies your defined tolerances, allowing minor variances through while flagging material discrepancies for review. The result is a shorter queue of invoices needing attention.

Read more on invoice validation and three-way matching.

Routing approvals and exceptions

Invoices are routed automatically to the right approver based on factors such as value, supplier, cost centre or invoice type. Reminders, escalations and delegated approvers help prevent approvals from stalling when someone is unavailable or an approval is overdue.

Supporting documents are available alongside the invoice, allowing approvers to make informed decisions, while every approval, rejection and comment is recorded in a complete audit trail.

Read more on the invoice approval process.

Connecting AP and finance systems

Integrating your invoice software with your ERP, accounting and procurement systems reduces duplicate data entry and keeps records consistent across your finance systems. Where direct integration isn't possible, RPA can bridge the gap by transferring data between applications.

Supporting human review

Human review remains an important part of invoice processing. By presenting the invoice alongside supplier history, purchase orders and approval records, reviewers can resolve exceptions more efficiently. Validation rules, confidence thresholds and review workflows ensure only suitable invoices are processed automatically.

For more, see AI in accounts payable.

UK controls, compliance and record keeping

Invoice processing in the UK is shaped by a range of legal and regulatory requirements. HMRC requires VAT records to be retained for six years and, under Making Tax Digital (MTD), maintained digitally with a digital link between the original transaction and the VAT return. That means invoice data must move reliably between your document management and accounting systems, not simply be stored.

A valid VAT invoice must include key information such as the supplier's VAT number, invoice number, date, description of the supply, and the net, VAT and gross amounts. Capturing this information consistently supports accurate VAT treatment and reporting.

Strong financial controls also depend on a clear audit trail. Invoices should remain linked to purchase orders, goods received notes, contracts, approvals and payment records, with every validation, coding change, approval and exception recorded. Segregation of duties is equally important, ensuring that the person raising a purchase order is not also the person approving the related invoice.

Invoices often contain personal and financial information, so access should be controlled in line with UK GDPR and the Data Protection Act 2018. Retention policies ensure records are kept for the required period before secure disposal, while business continuity arrangements mean invoices remain accessible even after system failures or cyber incidents.

Read more on retention periods and document archiving.

How organisations improve incoming invoice processing 

Standardising invoice intake

Give suppliers a single route for submitting invoices, whether that's a dedicated accounts payable inbox or a supplier portal, and make your requirements clear from the outset. Specify the information every invoice must include, such as a purchase order number, the correct legal entity and any agreed reference. Once received, invoices should follow the same process regardless of whether they arrive as PDFs, structured electronic documents or scanned copies.

Improving supplier and purchasing data

Clean, consistent supplier and purchasing data is essential for effective invoice processing. Duplicate supplier records, outdated information and inconsistent coding all reduce match rates and increase manual work. Defining when purchase orders are required also increases the proportion of invoices that can be matched automatically.

Defining validation and exception rules

Establish the checks every invoice must pass, the matching tolerances that apply, how duplicates are identified and how changes to supplier bank details are verified. Every type of exception should have a clear owner and an escalation path for higher-risk cases.

Assigning approval ownership

Define approval authority by value, department, cost centre or spend type, together with rules for delegated approvers and temporary cover. Clear ownership reduces delays, eliminates unnecessary follow-ups and gives approval workflows consistent rules.

Connecting systems and records

Integrating procurement, ERP, accounting and document management systems ensures invoice data and processing status remain consistent across your finance function. Everyone involved can see the status of any invoice without email chasing or phone calls.

Measuring and improving performance

Monitor metrics such as invoice cycle time, approval time, exception rate, first-pass match rate, duplicate rate, on-time payment rate and supplier query volume. These measures highlight where delays occur, helping you prioritise improvements and measure the impact of any changes before rolling them out more widely.