An accounts payable invoice processing SOP turns every incoming invoice into the same controlled journey: captured, matched, approved by the right authority, paid once, and filed with a clean audit trail. It is the control document that stops duplicate payments, keeps auditors satisfied, and makes month-end close predictable.
Every SOP generated by WorkProcedures follows the structure that auditors, regulators, and experienced operators actually expect. For a finance & accounting procedure like this one, that means:
A clear statement of why this accounts payable invoice processing procedure exists and what business / safety / compliance outcome it delivers.
Which people, equipment, locations, and conditions this SOP applies to — essential for finance & accounting operations where scope creep creates risk.
Certifications, PPE, tools, forms, and approvals that must be in place before starting the procedure.
Clear, sequential instructions that are unambiguous enough for a new hire to follow on their first shift. No interpretive language.
Industry-specific callouts — for Finance & Accounting, that typically includes relevant regulatory references (OSHA, ISO, FDA, or sector-specific).
Who last updated the SOP and when — critical for proving currency during audits.
Route all invoices to a single intake point (a dedicated AP mailbox or scanning tool). Record supplier, invoice number, date, amounts and tax on the day of receipt — late capture is the root cause of most missed early-payment discounts.
Match the invoice against the purchase order and the goods-received note. Quantities, unit prices and totals must agree within your stated tolerance (commonly 1–2% or a fixed small amount) before the invoice can advance.
Define which spend categories may legitimately arrive without a PO (utilities, rent, subscriptions), who assigns the GL code and cost centre, and who must approve. Everything else without a PO gets queried, not processed.
Approvals follow a documented authority matrix — by amount, department and spend type — with named delegates for absence. The SOP should state maximum turnaround times so invoices don't age in inboxes.
Price or quantity mismatches, missing POs and disputed goods go into a defined exception queue with an owner and an SLA, never into a personal 'pending' folder.
Fixed payment-run schedule (e.g. weekly), a review of the proposed payment file by someone who didn't prepare it, and dual authorisation for release. Urgent out-of-cycle payments need their own elevated approval.
Changes to supplier bank details are verified by calling a known contact on a number already on file — never one from the change request itself. This single step defeats most payment-diversion fraud.
Paid invoices are filed with their match evidence and approval trail. The AP ledger reconciles to supplier statements monthly, and unmatched receipts and aged credits are reviewed at close.
Statements are summaries, not source documents. Paying from them is how duplicates and fraudulent line items slip through — the SOP should permit payment only against matched invoices.
Define the duplicate check explicitly (same supplier + invoice number, and same amount + date within a window). Systems catch exact duplicates; your SOP has to catch the near-duplicates.
In small teams one AP clerk often does everything. If headcount can't provide separation, add compensating controls: owner review of the payment run and a monthly supplier-master change report.
Un-owned exceptions become aged liabilities and supplier disputes. Give the exception queue an owner, an SLA and a weekly review.
Comparing the supplier invoice against the purchase order and the goods-received note before approving payment. All three must agree within tolerance, proving you were billed for what you ordered and actually received.
A written duplicate rule (supplier + invoice number as the primary key, plus a near-match check on amount and date), one single intake channel so copies don't enter twice, and paying only against matched invoices — never statements.
Six years in the UK per HMRC requirements; seven years is the common standard in the US. Keep the match evidence and approvals with the invoice — the invoice alone doesn't prove the control operated.
There's no universal number — what matters is that the authority matrix is written, current, and enforced by the workflow. A common small-business pattern: line manager to £1k, department head to £10k, finance director above.
Most free SOP templates online are generic Word docs — you fill in the blanks yourself, which means 2–3 hours of research, writing, and formatting per procedure. WorkProcedures' AI SOP generator gives you a finished first draft, grounded in real finance & accounting procedures, in under two minutes.
Popular procedures in the finance & accounting industry — generate any of these free on the WorkProcedures platform.