Read summarized version with
Most teams can describe their invoice processing steps. They just describe them differently depending on who you ask.
I’ve watched it play out more than once. Ask the person who’s done AP for five years and you get one version. Ask whoever’s covering for them this week and you get a shorter version that’s slightly wrong. Ask the person who left last quarter and, well, you can’t. That last one is usually how the whole conversation gets started.
I’m Yuval, founder and CEO of Glitter AI. I’m not an accountant. I do spend a lot of time around finance and operations teams whose entire invoice management process lives inside one person’s head, though, and the fix nearly always begins the same way: write the steps down in the order they actually happen.
So here’s that order. Think of this as the companion piece to my longer invoice processing guide, which gets into the why and the manual-versus-automated tradeoffs. This one is the how. The exact steps, in sequence, and what each should look like when it’s working.
Teach your co-workers or customers how to get stuff done – in seconds.
The invoice processing steps, in order
There are eight. Smaller teams collapse a couple of them. Larger teams split a couple further. The sequence itself doesn’t change. Each step is there because the one before it can fail, and skipping a step is exactly how that failure ends up reaching your bank account.
Step 1: Receive the invoice into one place
The first step is intake. The only rule that really matters here is one front door.
Invoices show up by email, by vendor portal, by EDI, and as the occasional paper copy somebody has to scan. If each of those lands somewhere different, you don’t have an invoice process. You have several. Route everything into a single dedicated AP inbox or queue.
What good looks like: every incoming invoice hits the same destination within minutes of arriving, and nothing depends on a specific person watching their personal inbox.
How it breaks: an invoice sits in someone’s email while they’re on vacation, the vendor calls 60 days later, and now it’s a late fee and an awkward call.
Step 2: Capture the invoice data
Now you pull the structured data off the document: vendor, invoice number, invoice date, line items, amounts, tax, PO number, payment terms.
Done by hand, this is someone reading the PDF and typing into QuickBooks, Sage, or your ERP. Slow work, and it’s where most keying errors come from. Automated capture uses OCR to pre-fill those fields so a human reviews instead of retypes. The step itself doesn’t go away, though. It just changes who does the typing.
What good looks like: the invoice number and total are captured exactly as they appear on the document, because the next steps depend on those two values being right.
Step 3: Validate the invoice
Before the invoice goes anywhere, check it on its own merits. Is the arithmetic right? Is this a duplicate of something you already entered or paid? Is the vendor real and already set up in your system? Do the payment terms match what you actually agreed to?
This is your first fraud and error control, and it happens to be the cheapest one you have. A duplicate caught here costs nothing. That same duplicate caught after payment costs you a recovery effort and an uncomfortable explanation. The FBI’s Internet Crime Complaint Center found that business email compromise schemes - where attackers impersonate vendors to reroute payments - generated over $3 billion in reported losses in 2025, making validation a genuine fraud control, not just a bookkeeping step.
What good looks like: duplicates and math errors are caught and flagged before the invoice is ever routed for matching or approval.
Teach your co-workers or customers how to get stuff done – in seconds.
Step 4: Match the invoice
Validation checks the invoice against itself. Matching checks it against reality, meaning against what you ordered and what you actually received.
For PO-backed invoices that means reconciling the invoice, PO, and receipt together: the invoice, the purchase order, and the goods receipt all have to agree on quantity and price. For non-PO invoices like utilities, rent, or services, you fall back to a two-way match or a direct approver who can confirm the spend was real.
What good looks like: invoices that match cleanly flow straight through, and only the genuine mismatches stop for a human to look at. If everything stops for a human, your matching tolerances are too tight.
Step 5: Code the invoice
Now assign the accounting: the GL account, cost center, department, project, and any tax handling. This is the step that decides whether your financial reports mean anything at all later on.
Coding is also the easiest step to quietly skip, because a miscoded invoice still gets paid. Nobody calls you about it. You find out at month-end, when a budget owner asks why their numbers look wrong. Getting this right is a big part of why a written accounts payable process matters more than it first appears.
What good looks like: recurring vendors have default coding so the common case is automatic, and only the exceptions need a judgment call.
Step 6: Route for approval
The invoice goes to whoever has the authority to approve that spend, usually decided by amount, department, or budget owner. The mechanics here, the thresholds and the routing rules, are worth designing on purpose rather than by accident. I went deep on that in the invoice approval workflow post.
The two failure modes here are opposites, and both are bad. Too loose, and spend gets approved by people who shouldn’t be approving it. Too rigid, and every invoice waits on one overloaded manager while the rest of the process stalls behind them.
What good looks like: the right approver gets the invoice automatically, there’s a defined path when they’re out, and approvals have a deadline that someone actually watches.
Step 7: Pay the invoice
Approved invoices get scheduled and paid by ACH, check, card, or wire, with the timing picked to hit terms without paying early for no reason. Then you confirm the payment cleared and mark the invoice paid in the system.
The control that matters here is separation. The person who can approve an invoice should not also be the person who can release the payment. That one division stops a large share of internal fraud.
What good looks like: payment status is reflected in the system the same day it happens, so the invoice can’t accidentally be paid twice.
Step 8: Archive for audit
The last step is the one everyone treats as optional right up until an auditor asks for an invoice from fourteen months ago. Store the invoice, the PO, the receipt, the approval record, and the payment confirmation together, somewhere searchable.
What good looks like: pulling the full history of any past invoice takes a search, not an archaeology project.
A quick invoice processing checklist
If you want the steps as something you can tape next to a monitor:
- Receive - one intake point for every invoice
- Capture - pull vendor, number, amounts, PO, terms
- Validate - math, duplicates, vendor, terms
- Match - invoice vs. PO vs. receipt
- Code - GL account, cost center, project, tax
- Route - send to the right approver, with a backup
- Pay - schedule, pay, confirm, mark paid
- Archive - store everything together, searchable
Teach your co-workers or customers how to get stuff done – in seconds.
The step that’s actually missing
Here’s what I keep running into. Teams do all eight of these steps correctly. The process works. And it’s still fragile, because the steps only live in the head of the person doing them.
That’s the real missing step: documenting the process so it survives the person leaving. Not a stale PDF nobody opens. A walkthrough of the real screens and the real clicks, in your real system, that a new hire can follow without booking time with the one person who knows.
This is the part Glitter AI exists for. You run through your invoice process once, the way you’d do it anyway, and it captures every step, screen, and click into a guide you can hand to anyone. The eight steps above stop being tribal knowledge and turn into something you can onboard against. Same idea as a well-built standard operating procedure for accounts payable, minus the part where someone has to sit down and write it from scratch.
Final thought
The order of the invoice processing steps isn’t the hard part. Most teams get the sequence right on instinct. What breaks is everything around it: the step that lives in one person’s inbox, the coding nobody checks, the approver with no backup, the archive that’s really just a folder named “misc.” Ardent Partners benchmarks show the average AP organization takes 9.2 days and spends $9.40 to process each invoice - and top performers reduce both figures by more than two-thirds by having every step written down and followed consistently.
Get the eight steps written down in order, spell out what good looks like at each one, and document it where the work actually happens. That’s the difference between a process that survives a resignation and one that walks out the door with it.
Frequently Asked Questions
What are the steps in invoice processing?
The standard invoice processing steps, in order, are: receive the invoice, capture its data, validate it, match it against the PO and receipt, code it to the right accounts, route it for approval, pay it, and archive it for audit. Smaller teams may combine a few steps, but the sequence stays the same.
How many steps are in the invoice processing workflow?
Most AP teams run eight core steps: receipt, capture, validation, matching, coding, approval routing, payment, and archive. Some guides describe it as five to seven steps by merging validation with matching or coding with approval, but the underlying work is the same.
What is the first step in invoice processing?
The first step is receiving the invoice into a single intake point, such as a dedicated AP email address or vendor portal. Centralizing receipt prevents invoices from getting stuck in individual inboxes, which is the most common cause of late payments.
What is the difference between invoice validation and invoice matching?
Validation checks the invoice against itself: correct math, no duplicates, a legitimate vendor, and agreed terms. Matching checks it against reality by comparing it to the purchase order and goods receipt. You do validation first, then matching.
What is three-way matching in invoice processing?
Three-way matching compares the invoice, the purchase order, and the goods receipt to confirm quantity and price agree before payment. It is the main control that stops you from paying for goods you did not order or did not receive.
Why is invoice coding an important step?
Coding assigns the GL account, cost center, and project to each invoice, which is what makes financial reports accurate. A miscoded invoice still gets paid, so errors stay invisible until month-end, making this a quiet but high-impact step.
Who should approve invoices in the approval step?
Invoices should route to the person with spending authority for that amount and department, usually a budget owner or manager. There should always be a defined backup approver so the process does not stall when someone is unavailable.
How can I make invoice processing steps faster?
Centralize intake, automate data capture with OCR, set sensible matching tolerances so clean invoices flow straight through, apply default coding for recurring vendors, and route approvals automatically with deadlines. Most delay comes from steps waiting on a person, not from the steps themselves.
What happens if you skip a step in invoice processing?
Each step controls a specific failure: skipping validation lets duplicates through, skipping matching pays for goods you did not receive, skipping coding corrupts your reports, and skipping archive fails audits. The steps are sequential because each one depends on the one before it being done right.
How do you document invoice processing steps so they survive turnover?
Capture the actual screens and clicks in your real system as a step-by-step guide, not a static document nobody opens. Tools like Glitter AI record the process once as you do it normally and turn it into a guide any new hire can follow without shadowing the current owner.
