Accounts payable SOP that actually gets followed

I’ve seen hundreds of AP standard operating procedures. Most of them are 40-page documents that someone wrote three years ago, uploaded to SharePoint, and never opened again. The formatting is beautiful. The content is thorough. And absolutely nobody follows them.

That’s the uncomfortable reality of most finance SOPs. They exist to satisfy auditors, not to help the people doing the work.

In our experience with workflow automation, the AP teams that run smoothly don’t have better documents. They have better systems. The procedure is built into the workflow itself - you can’t skip steps because the system won’t let you. That’s a fundamentally different approach than hoping Karen in accounting remembers to check the three-way match before cutting a check.

Here’s what a practical accounts payable SOP looks like when it’s designed to be followed, not filed.

Invoice receipt through payment - the full cycle

The AP cycle has maybe seven steps that matter. Not forty-seven. Not a hundred sub-procedures with Roman numeral headings. Seven.

Step 1: Invoice arrives. Could be email, mail, EDI, vendor portal. Doesn’t matter how - what matters is that every invoice enters the same system immediately. No desk drawers. No email folders named “to process later.” The invoice gets logged with a timestamp the moment it shows up.

Step 2: Data capture and validation. Someone (or something - OCR tools are genuinely useful here) pulls the key fields: vendor name, invoice number, date, amount, line items, payment terms. Then you check - is this vendor in our system? Does the invoice number already exist? Are the payment terms what we agreed to?

Step 3: Match it. This is where the purchase order process connects to AP. You’re comparing three documents: the original PO, the receiving report showing what arrived, and the invoice requesting payment. More on this below - it’s critical enough to deserve its own section.

Step 4: Route for approval. Based on amount, department, expense type, or whatever your approval matrix says. A $200 office supply order probably doesn’t need the CFO’s signature. A $50,000 consulting engagement probably does.

Step 5: Approval or rejection. The approver confirms the expense is legitimate, the amount is correct, and the budget exists. If something’s wrong, it goes back - with a reason. Not just “rejected.” That tells nobody anything.

Step 6: Schedule payment. Approved invoices get queued for the next payment run based on their terms. Net 30 means net 30 - not net 45 because someone forgot. Early payment discounts (2/10 net 30) need to be flagged automatically. Missing a 2% discount on a $100,000 invoice is literally throwing away $2,000.

Step 7: Payment execution and recording. Cut the check, send the ACH, wire the funds. Then record it. GL coding happens here - and it needs to be right, because fixing GL entries after month-end close is everyone’s least favorite activity.

That’s it. Seven steps. The complexity isn’t in the steps themselves - it’s in making sure they happen consistently, every single time, for every single invoice.

Why segregation of duties isn’t bureaucratic nonsense

I get it. Segregation of duties sounds like something an auditor invented to create more work. It’s not.

Here’s the scenario without it: Sarah receives invoices, approves them, and processes payments. Sarah is a wonderful person. Sarah is also now capable of creating a fake vendor, submitting invoices from that vendor, approving those invoices, and paying herself. Nobody would ever know until the annual audit - if then.

The Association of Certified Fraud Examiners estimates that organizations lose 5% of revenue to fraud annually. AP is one of the most common targets because it’s where cash actually leaves the company.

Proper segregation means splitting AP into at least three roles:

The receiver. Opens mail, logs invoices, does initial data entry. Can’t approve payments. Can’t cut checks.

The approver. Reviews invoices against POs and budgets. Confirms legitimacy. Can’t enter invoices. Can’t process payments.

The processor. Executes approved payments. Can’t enter invoices. Can’t approve their own payment batches.

In smaller companies, I know what you’re thinking - we don’t have three people in AP. Fair. But you still need separation. Maybe the office manager receives invoices, the department head approves them, and the bookkeeper processes payments. The titles don’t matter. The separation does.

At Tallyfy, we’ve seen this play out repeatedly. When we talk with finance operations teams, the ones who’ve had fraud incidents almost always had one person controlling too many steps. It’s not that they hired dishonest people. It’s that they created an environment where dishonesty was easy and undetectable.

And this connects to something bigger - in the age of AI, defining processes matters more than ever. AI can accelerate invoice processing, flag anomalies, even suggest GL codes. But if your segregation of duties doesn’t exist in the workflow itself, AI just makes it faster to skip controls. The process definition has to come first.

3-way matching - the part everyone wants to skip

Three-way matching is the single most effective control in AP. It’s also the one that people constantly try to shortcut.

Here’s what you’re matching:

Document 1: The purchase order. What did we agree to buy? What quantity? At what price? From which vendor?

Document 2: The receiving report (or goods receipt). What did we actually receive? Was it the right quantity? The right quality? Did anything arrive damaged?

Document 3: The invoice. What’s the vendor charging us? Does the quantity match what we ordered AND received? Does the unit price match the PO?

When all three match - congratulations, process the payment. When they don’t? That’s where exception handling kicks in.

Common mismatches and what to do:

• Quantity variance. Invoice says 100 units, receiving report says 95. Don’t pay for 100. Contact the vendor about the shortage. Create a debit memo for the 5 missing units.
• Price variance. PO says $10/unit, invoice says $11/unit. This could be a legitimate price increase with proper notification, or it could be an error. Either way - don’t just pay it. Route it back to procurement.
• No PO exists. Someone ordered something without going through the purchase order process. This is maverick spending and it’s a bigger problem than one invoice. Flag it, find out who ordered it, and make sure there’s a conversation about why POs exist.

Some companies set tolerance thresholds. If the variance is under 2% or under $50, auto-approve it. That’s reasonable for small differences - nobody wants to hold up a $10,000 payment over a $3 rounding difference. But the threshold needs to be defined in the SOP, not left to individual judgment.

In discussions we’ve had about AP processes, the teams that skip 3-way matching always have the same justification: “It slows us down.” They’re right. It does. But accounts payable errors from duplicate payments alone cost businesses an average of $2,034 per incident. Matching prevents those errors. The “slowdown” is the control working.

Exception handling without the chaos

Here’s where most AP SOPs fall apart. They describe the happy path beautifully. Invoice arrives, matches perfectly, gets approved, gets paid. Done.

But maybe 20-30% of invoices won’t follow the happy path. And your SOP needs to handle those too, or your team will invent their own workarounds. Workarounds become habits. Habits become “how we do things.” And suddenly your carefully designed process has a dozen unofficial side doors.

The exceptions you need procedures for:

Missing PO invoices. These shouldn’t be paid without retroactive approval. The approver needs to confirm the goods/services were received and the expense is legitimate. Then either create a retroactive PO or document why a PO wasn’t required (some expense categories genuinely don’t need them - recurring utilities, for example).

Disputed invoices. When you disagree with a vendor about an amount, you need a clear escalation path. Who contacts the vendor? Within what timeframe? How is the dispute tracked? What happens if it’s not resolved within 30 days? Without answers to these questions, disputed invoices sit in limbo forever, damaging vendor relationships.

Rush payments. Every AP department gets the “I need this paid TODAY” request. Your SOP should define when rush payments are allowed, who can authorize them, and what controls can be abbreviated (hint: not all of them). If everything is a rush, nothing is.

Credit memos and returns. When a vendor issues a credit, it needs to be matched against the original invoice and applied before the next payment. This sounds obvious. In practice, credits get lost constantly - they arrive separately from invoices, in different formats, sometimes weeks later.

Building these exception paths into an approval process workflow is exactly the kind of problem that workflow software solves well. The system routes exceptions to the right person with the right context, tracks resolution time, and prevents invoices from disappearing into someone’s inbox.

Month-end close that doesn’t require overtime

Month-end close is the moment of truth for your AP SOP. If your team regularly works weekends at the end of every month, it’s not a staffing problem. It’s a process problem.

The AP-specific close tasks that need to happen:

Accruals. Any goods or services received but not yet invoiced need to be accrued. This means AP has to talk to receiving (or whoever logs deliveries) to find out what came in during the last few days of the month that hasn’t been invoiced yet. If this conversation happens on the 28th, it’s manageable. If it happens on the 5th of the next month - you’re already behind.

Cutoff procedures. Which invoices belong to this month and which belong to next month? The rule should be based on when goods/services were received, not when the invoice arrived. An invoice dated March 28 for services delivered in February belongs in February’s books. This sounds simple but creates genuine confusion when invoice dates, delivery dates, and receipt dates don’t align.

Reconciliation. The AP sub-ledger needs to match the GL. Every penny. If they don’t match, you need to find out why before close. Common culprits: invoices entered but not posted, payments processed but not recorded, manual journal entries that hit the AP account without going through the AP system.

Aging review. Pull your AP aging report. Anything over 60 days should have a documented reason. Anything over 90 days is probably a problem - either a dispute that’s been ignored, a payment that was made but not recorded, or a legitimate liability that’s been forgotten.

Vendor statement reconciliation. At least quarterly, compare your records against statements from your top 20 vendors by spend. Discrepancies reveal missed invoices, duplicate payments, and unapplied credits. I’d argue monthly for your top 5, but quarterly is the minimum.

The teams that close smoothly have one thing in common: they don’t save these tasks for month-end. Accruals are estimated weekly. Reconciliation happens continuously. Aging is reviewed every Friday. Month-end becomes a verification exercise instead of a discovery exercise. That’s a massive difference.

Feedback we’ve received from finance teams using Tallyfy suggests that when these recurring close tasks are built into a trackable workflow - with assignments, deadlines, and visibility - the panic disappears. It’s not magic. It’s just structure.

Making the SOP stick

The reason most SOPs get ignored is that they’re documents, not workflows. A PDF sitting in a folder requires someone to remember it exists, find it, read it, and then do what it says. That’s four failure points before anyone does actual work. The fix? Stop treating your AP SOP as a reference document. Treat it as an active workflow. Every invoice that enters the system should trigger a defined sequence of steps. Each step should be assigned to a specific role (not a specific person - people leave, roles don’t). Each step should have a deadline. And the whole thing should be visible to the AP manager, the controller, and anyone else who needs to know where things stand.

This is exactly why we built Tallyfy the way we did. Not to replace your AP SOP, but to make it executable. The procedure isn’t something you read - it’s something you do, step by step, with the system ensuring nothing gets skipped.

One thing I probably should’ve mentioned earlier - none of this works without buy-in from your AP team. If the people doing the work think the SOP is bureaucratic overhead designed by someone who’s never processed an invoice, they’ll find ways around it. Involve them in designing it. Let them tell you where the real bottlenecks are. They know things your process map doesn’t.

The best AP SOP isn’t the most thorough one. It’s the one that’s simple enough to follow every day, and built into a system that makes following it the path of least resistance.