Trupeer Blog
Ringkas
Picture an accounts payable team spread across three offices. One site checks for duplicate invoices before entry, another after. One escalates price variances to the buyer, another to the AP supervisor. Each team believes its way is the standard. The result is duplicate payments, invoices stuck on hold, unhappy suppliers and an audit trail nobody can explain. The fix is a single, standard AP invoice processing SOP that everyone follows.
An invoice processing SOP sets out exactly how invoices are received, checked, matched, approved, paid and filed, with the controls and exception handling built in. This guide explains what an AP invoice processing SOP should include, the standard workflow step by step, how to handle exceptions and controls, and how to standardise the SOP across teams and sites by building it from screen recordings with Trupeer.
What is an AP invoice processing SOP?
An AP invoice processing SOP is a standard operating procedure that defines how accounts payable handles supplier invoices from receipt to payment. It covers the steps, the people responsible, the system screens, the checks and approvals, and what to do when an invoice doesn't match. It's the core procedure in accounts payable process documentation, and it sits in the payment half of the procure to pay process flow.
Why standardise your AP invoice processing SOP?
Consistency across teams and sites: every clerk processes invoices the same way, whichever office or shift they work in.
Fewer errors: standard checks catch duplicates, miscoding and missing approvals before payment.
Stronger controls: approvals, segregation of duties and evidence are built into every invoice.
Faster onboarding: new clerks learn one documented way of working; see accounts payable training for new hires.
Easier audits: auditors test one process, not several local versions.
Better supplier relationships: predictable processing means invoices are paid on time.
Ready for change: a standard SOP is the starting point for automation, ERP projects and shared services; see the ERP go-live readiness checklist.
What should an AP invoice processing SOP include?
Every invoice processing SOP should contain these sections:
Document control: document ID, version, owner, approver, effective date and next review date.
Purpose and scope: which invoices it covers, such as PO and non-PO invoices, entities and currencies.
Roles and responsibilities: AP clerk, AP supervisor, buyers, budget holders and treasury.
Systems: the ERP or AP automation tool, the invoice inbox and the archive.
Procedure: numbered steps with screenshots, from receipt to filing.
Exception handling: what to do for each type of mismatch or missing information.
Controls: the checks that must happen and the evidence to keep.
Escalation: who to contact and when.
Related documents: approval limits, payment terms policy and vendor master procedures.
Start from the free SOP template so every section is in the same place.
The standard AP invoice processing workflow, step by step
Here's a standard AP invoice workflow you can adapt for your SOP.
Step 1: Receive the invoice
Invoices arrive by email, supplier portal, e-invoicing or post. All invoices go to one central AP inbox or capture tool, never to individual employees.
Step 2: Capture and log the invoice
Scan or import the invoice, capture the key data (supplier, invoice number, date, amount, tax, PO number) and log it in the ERP or AP system with a received date.
Step 3: Check for duplicates and validity
Check the supplier is active in the vendor master, the invoice is addressed to the right entity, the tax details are valid and the invoice hasn't already been entered under the same number, amount or date.
Step 4: Match PO invoices
For PO invoices, run a three-way match against the purchase order and goods receipt. Invoices within tolerance move to payment; those outside tolerance go on hold as exceptions.
Step 5: Route non-PO invoices for approval
For non-PO invoices, code the invoice to the right cost centre and general ledger account and route it to the budget holder for approval within their limit.
Step 6: Resolve exceptions
Investigate held invoices, contact the buyer, receiving team or supplier, and release, adjust or reject them according to the exception rules below.
Step 7: Post and schedule for payment
Post approved invoices and schedule them for payment based on payment terms, early payment discounts and the payment run calendar.
Step 8: File and retain
Store the invoice and its approval evidence in the archive, linked to the transaction, for the retention period your finance and tax rules require.
How should the SOP handle invoice exceptions?
Exceptions are where most errors and delays happen, so your SOP should spell out each one:
Exception | What to do | Who resolves |
|---|---|---|
Price variance above tolerance | Confirm the agreed price with the buyer; adjust the PO or request a credit note | Buyer and AP clerk |
Quantity variance or no goods receipt | Confirm delivery with receiving; post the receipt or hold the invoice | Receiving and AP clerk |
Missing or wrong PO number | Ask the requester or supplier for the correct PO | AP clerk |
Duplicate invoice | Reject and notify the supplier | AP clerk |
Supplier not on vendor master | Route to vendor master team for verified setup | Vendor master team |
Missing approval on non-PO invoice | Chase the budget holder, escalate after the agreed time | AP supervisor |
Set a time limit for each exception, after which it escalates to the AP supervisor.
Which controls should an invoice processing SOP include?
Duplicate invoice checks before posting.
Three-way match tolerances agreed with procurement and finance.
Approval limits for non-PO invoices and exception releases.
Segregation of duties between vendor setup, invoice entry and payment release; a RACI matrix makes these explicit.
Independent verification of any supplier bank detail change.
Audit evidence retained for every approval and exception release.
How do you create and standardise an AP invoice processing SOP with Trupeer?
Step 1: Agree the standard process
Bring AP leads from each team or site together, compare how each one processes invoices today, and agree one standard process, including the exceptions. Map it with the process flow template.
Step 2: Record the standard process
Have your most experienced clerk record each step in the ERP with Trupeer's AI screen recorder, narrating the checks and decisions. Auto-zoom and click detection highlight every field and action.
Step 3: Generate the SOP from the recording
Trupeer turns the recording into a step-by-step SOP with screenshots and a narrated video with the SOP creator or the free AI SOP generator. The AP lead reviews the draft rather than writing it from scratch.
Step 4: Add exceptions, controls and branding
Add the exception table, controls and escalation rules, and apply your brand kit so every SOP looks the same.
Step 5: Translate and distribute
Translate the SOP and video for every site, export in the formats your teams use, such as PDF, HTML, MP4 or SCORM for your LMS, and publish everything in a searchable knowledge base.
Step 6: Measure and improve
Use viewer analytics to see which steps people rewatch or skip, compare error rates and exceptions across sites, and update the SOP when the process or system changes; see how to update a training video without re-recording.
Standardising the AP invoice processing SOP across sites and shared services
When invoices are processed in several countries or in a shared services centre, standardisation matters even more:
One global core SOP, with documented local variants for tax, language or legal requirements.
One owner for the global SOP and a named owner for each local variant.
The same exception rules and tolerances everywhere, unless a local rule requires otherwise.
Translated SOPs and videos from the same source, so every language stays in step.
Shared metrics across sites, so differences in performance are visible.
See shared services SOP documentation at scale if invoice processing is moving to a provider.
Invoice processing KPIs to track
Invoice cycle time: days from receipt to approval for payment.
First-pass match rate: the share of PO invoices that match without exception.
Exception rate and resolution time.
Duplicate payment rate.
On-time payment rate.
Cost per invoice.
SOP compliance: the share of invoices processed following the standard steps, based on audit samples.
Common mistakes in AP invoice processing SOPs
Leaving out exceptions, so clerks improvise on the invoices that matter most.
Text-only SOPs with no screenshots or video, which are hard to follow in a complex ERP.
Several local versions instead of one standard with documented variants.
No owner or review date, so the SOP falls behind the system.
Controls in a separate document nobody reads alongside the steps.
SOPs nobody can find, stored in folders rather than a searchable knowledge base. If people ignore your SOPs, it's usually because they're too long, out of date or hard to find; see how to break SOPs into knowledge articles.
Get the free AP invoice processing SOP template
Start your invoice processing SOP with the free SOP template, and bring your AP SOPs together in a desk manual for each AP role. You can also generate an AP manual with the accounting manual generator. To turn your team's recordings into standard SOPs and videos, start free with Trupeer. Comparing tools?
Frequently asked questions
What is an AP invoice processing SOP?
It's a standard operating procedure that defines how accounts payable handles supplier invoices from receipt to payment, including the steps, roles, system screens, controls and exception handling.
What are the steps in AP invoice processing?
Receive the invoice, capture and log it, check for duplicates and validity, match PO invoices, route non-PO invoices for approval, resolve exceptions, post and schedule for payment, then file and retain the invoice and evidence.
What should an invoice processing SOP include?
Document control, purpose and scope, roles, systems, numbered steps with screenshots, exception handling, controls, escalation and related policies.
How do you standardise invoice processing across teams?
Agree one standard process with all teams, record it once, generate the SOP and video, add exceptions and controls, translate it for every site and publish it in one searchable knowledge base with one owner.
How do you handle invoice exceptions?
List each exception type in the SOP with what to do, who resolves it and a time limit, and escalate unresolved exceptions to the AP supervisor.
What controls belong in an AP invoice processing SOP?
Duplicate checks, three-way match tolerances, approval limits, segregation of duties, independent verification of bank detail changes and retained audit evidence.
How often should the invoice processing SOP be reviewed?
At least annually, and whenever the ERP, approval limits, tolerances or tax rules change, or an audit finding affects the process.
Can video SOPs improve invoice processing?
Yes. Short videos showing each step in the actual ERP help clerks follow the process correctly, especially in complex screens, and make onboarding faster across sites and languages.
