An invoice processing SOP (standard operating procedure) is the written routine your team follows to take a supplier invoice from arrival to payment and filing, with a named owner and a clear rule at every step. The seven-step outline below is a starting structure, not a required page count: receive, verify, code, approve, pay, record and archive.

This page covers invoices you receive and pay (accounts payable). If you need an SOP for creating and sending invoices to your own customers, use the invoicing and billing SOP guide instead.

The 7-step invoice processing SOP

Step What happens Typical owner Done when
1. Receive Invoices from approved channels (AP inbox, supplier portal or scanned mail) enter one controlled queue with the date received AP clerk Invoice is in the queue with a received date
2. Verify Check required fields (supplier, invoice number, date, amounts, tax, PO number), look for duplicates, and for PO invoices run a three-way match against the purchase order and receiving report AP clerk Fields complete and documents agree, or invoice moved to exceptions
3. Code Assign the GL account, department or class and project, then prepare the draft bill in the accounting system AP clerk or bookkeeper Draft coded; posting/payment authorization still required
4. Approve The budget owner approves within their written dollar limit; non-PO invoices always need an approver Budget owner Approval recorded in the system or on the invoice
5. Pay Approved bills go into the scheduled payment run (ACH, check or card); a second person releases the payment Payment releaser Payment sent on the scheduled date
6. Record Apply the payment to the bill and reconcile the payment run to the bank statement Bookkeeper Bill shows paid; bank reconciles
7. Archive File the invoice, approval and proof of payment together in the agreed location AP clerk Record findable by supplier and invoice number

Anything that fails step 2 or 4 goes to a named exception owner with a time limit, not back into a general inbox.

If invoices still arrive on paper, add one line to step 1 saying who scans them and where the scan is saved, so every invoice enters the queue as a digital file. Our document scanner picks for a paperless small office compare scanners built for that job. For one AP desk scanning a small daily stack, the compact Epson DS-C330 (20-page feeder, USB) is the pick there; if scans should land straight in a shared network folder or SharePoint, the Brother ADS-3350W lists both as destinations.

Sample invoice processing SOP template

Use this outline as the skeleton. Each heading is a section of the finished SOP.

SOP ID and title:   FIN-003 Process supplier invoices
Version and dates:  v1.0, effective [date], next review [date]
Owner / approver:   [AP lead] / [finance manager or business owner]

1. Purpose          Pay valid supplier invoices accurately and on time
2. Scope            All supplier invoices. Excludes payroll, employee
                    expense claims and customer billing
3. Roles            AP clerk, budget owner (approver), payment releaser,
                    reviewer
4. Inputs           Invoice, purchase order, receiving report,
                    supplier master record
5. Procedure        Steps 1-7 above: owner, rule and time limit for each
6. Approval limits  Table of amount bands and the approver for each
7. Exceptions       Price or quantity mismatch, missing PO, duplicate,
                    disputed amount, supplier bank-detail change
8. Controls         Three-way match, duplicate check, separate approval
                    and payment roles, call-back on bank-detail changes
9. Records          Storage location, file naming, retention period
10. Revision history Date, version, what changed, approved by

File the finished SOP under a stable ID in your shared drive; the SOP folder structure guide shows a simple layout and naming convention.

Controls to write into the SOP

  • Distinguish capture from authorization. Step 3 captures and codes a draft; it does not authorize posting or payment. Define where approval must occur in your accounting system and prevent an unapproved draft from entering a payment run. The outline’s approval step must agree with the actual posting controls.
  • Three-way match for PO purchases. Compare quantities, unit prices and terms on the purchase order, the receiving report and the supplier invoice; release the invoice only when the match meets documented tolerances or an authorized exception is recorded. Specify how partial receipts, freight, tax and non-PO invoices are handled rather than requiring every amount to be identical.
  • Separate duties. The person who approves an invoice should not also release the payment. AccountingCoach points out that small companies without enough staff to separate these duties carry a greater risk of theft. If one person must do both, add a compensating check, such as the owner reviewing every payment run before it is released.
  • Verify bank-detail changes through a second channel. The FBI’s Internet Crime Complaint Center advises using secondary channels or two-factor authentication to verify requests to change account information, a common business email compromise tactic. Write in that AP calls the supplier on a number already on file, never one in the request.
  • Keep the records long enough. The IRS lists invoices among the supporting documents a business should keep, and says to keep records that support items on a tax return until the period of limitations runs out: generally 3 years, 7 years for a bad-debt deduction, and longer in some situations. Check with your accountant, and whether insurers or lenders need them longer, before setting the retention line in section 9.

One SOP or several?

Use one SOP when all invoices follow the same approval chain and accounting system. Split it when PO-backed invoices, non-PO invoices and credit memos follow different controls.

Situation SOP shape Must include
Solo operator or very small team Checklist linked to the applicable controls The 7 steps, one approver, a backup
Small office with one approver Checklist plus approval table Backup approver, payment-run cutoff, escalation path
PO-backed purchasing Core SOP with a match step Three-way match, receiving proof, discrepancy handling
Multiple entities or shared AP Core SOP plus exception guide Entity coding, tax treatment, storage location, sign-off rules

Keep purchasing policy and supplier onboarding in their own documents. Mixing them in makes it unclear whether the next step is an AP action, a procurement rule or a supplier setup task.

Common mistakes

  • Hiding approval limits in prose instead of a table of amounts and roles.
  • Leaving disputed amounts and mismatches without a named owner.
  • Ignoring payment-run timing, so approved invoices still pay late.
  • Letting one person enter, approve and pay with no review.
  • Using screenshots as the source of truth with no version date.

A weak step reads: “AP processes invoices after manager approval.” A usable one reads: “AP checks the required fields, routes non-PO invoices to the budget owner, enters approved invoices in the accounting system and includes them in the Friday payment run.” The second version tells a new hire what to do without a follow-up question.

Frequently Asked Questions

What does SOP mean for invoices?

SOP stands for standard operating procedure. An invoice SOP is the written, step-by-step process a business follows to receive, check, approve, pay and file supplier invoices, so every invoice is handled the same way no matter who is processing it.

Is invoice processing the same as invoicing?

No. Invoice processing usually means handling bills you receive from suppliers (accounts payable). Invoicing or billing means creating and sending invoices to your customers (accounts receivable). They need separate SOPs because the owners, controls and systems differ.

How long should an invoice processing SOP be?

Use enough detail to define the actual controls; there is no universal one-to-three-page limit. Add an appendix or exception guide once the process has several approval paths, PO matching or entity-specific coding rules.

Should PO and non-PO invoices share one SOP?

Only when the controls are the same. If PO invoices need a three-way match and non-PO invoices follow a different approval chain, write them as separate branches or separate documents.

Who should write the SOP?

One process owner should draft it, then the people in AP, finance and operations who touch the invoice should review their handoffs. The final version needs one accountable owner.

How often should it be updated?

Update it whenever approval limits, payment methods, accounting software, supplier master ownership or tax setup change, and review it on a fixed schedule, such as quarterly while the process is new.

Sources

This guide is desk research, not hands-on testing.