Accounts payable is the money your business owes to the people it buys from, and the accounts payable process is everything that happens between a supplier deciding to bill you and that bill being paid, recorded, and closed. Written out, it sounds like one task. In practice it is seven, they are usually done by different people, and most of the delay and most of the errors happen in the handoffs between them.
This guide walks the whole cycle in order. It is written for small businesses doing their own books and for bookkeeping and accounting firms running the process on behalf of clients, because the steps are the same and only the ownership changes. Where a step works differently in QuickBooks Online and Xero, we say how.
One thing worth settling early, because it shapes everything below: the accounts payable process is not a payment process with some paperwork attached. Paying is a single step near the end. The work sits in the steps before it, where a document has to be found, checked against what was actually ordered and received, coded to the right account, and approved by someone with the authority to commit the money. A business that speeds up only the payment step has not fixed anything.
What is the accounts payable process?
The accounts payable process is the sequence a business follows to turn a supplier's invoice into a recorded, approved, and paid obligation. It runs from the moment a purchase is authorized through invoice receipt, verification against what was ordered and delivered, coding to the right expense account, approval, payment, and the filing of the record so the period can be closed. Each step exists to make sure the business pays the right supplier, the right amount, once.
Accounts payable covers money you owe; accounts receivable covers money owed to you.
The distinction matters more than it looks, because software names blur it constantly. A product described as "invoicing software" is usually about the invoices you send to customers, which is accounts receivable. A product described as "invoice processing" or "AP automation" is usually about the invoices you receive, which is accounts payable. The two jobs share a word and almost nothing else, and buying the wrong one is a common and expensive mistake. Our guide to invoice automation software covers that distinction in detail.
The other thing worth naming up front is who the process is for. In a business large enough to have an AP clerk, the steps below are one person's job description. In a business of ten people, they are scattered: the owner authorizes the purchase, whoever opens the mail finds the invoice, the bookkeeper codes it, and the owner pays it from a banking app two weeks later, possibly without knowing whether it was already paid. Nothing in that is unusual. It is simply the same seven steps with no one holding them together, which is why small businesses tend to feel the pain of this process as "surprise bills" and "I think we paid that twice" rather than as a process problem at all.
For an accounting firm, there is a third shape: the steps happen across many client files at once, with the firm doing the coding and the client doing the approving, and the hardest part is not any individual step but collecting the documents from clients in the first place.
The accounts payable process, step by step
Seven steps, in the order they happen. Not every business runs all seven formally. A two-person company with no purchase orders skips straight from step two to step four. But every business runs them informally, and the ones they skip are usually where the errors come from.
1. The purchase is authorized
Before anything is bought, someone decides it should be. In a business with a formal process this produces a purchase order: a numbered document sent to the supplier that says what is being bought, how many, at what price, and on what terms. In a business without one, it produces an email, a phone call, or nothing at all.
The purchase order matters later, at the verification step, because it is the only record of what the price was supposed to be. Without it, an invoice can only be checked against someone's memory of the conversation. That is workable when one person buys everything and knows every supplier. It stops being workable the moment a second person can commit the company's money.
This is also the step where spend controls actually live. Approval thresholds ("anything over $2,000 needs a second signature"), preferred-supplier rules, and budget checks all belong here, before the commitment is made, not at the approval step after the goods have already been delivered and the supplier is expecting payment. Approving an invoice is not really a decision; by then the business is already legally on the hook. The real decision was made when someone said yes to the purchase.
Small businesses can get most of the benefit without adopting purchase orders wholesale. Deciding that a named person authorizes anything above a threshold, and that the authorization goes in writing somewhere findable, covers the majority of the risk. The formality of a numbered PO document earns its keep when volume rises or when the people buying are not the people paying.
2. The invoice arrives
The supplier bills you. In practice this means the invoice lands in an inbox as a PDF attachment, arrives on paper, or waits in a supplier portal for someone to log in and fetch it. Most businesses receive invoices by all three routes at once, which is the first real problem in the cycle: there is no single place where the bills are.
An invoice that has arrived but has not been recorded is invisible. It is not in the books, so it does not appear in what the business owes, does not get included in a cash-flow view, and cannot be paid on time except by accident. The gap between "the invoice arrived" and "the invoice is in the accounting system" is where late-payment fees, duplicate payments, and month-end surprises are manufactured. It is also, for most small businesses, the longest gap in the whole process: an invoice can sit in someone's personal inbox for two weeks with nobody aware it exists.
This is why the intake step deserves more attention than it usually gets. The goal is a single destination that every invoice reaches regardless of how it was sent, so that "have we received it" and "is it recorded" become the same question. A shared mailbox that everything is forwarded to is the simplest version. A connected inbox that is watched automatically is a stronger one, because it removes the human step of remembering to forward. Our guide to getting invoices out of Gmail and into QuickBooks covers that path specifically, and receipt automation for bookkeepers covers the equivalent problem for receipts, where the money has already moved.
Whatever the mechanism, the test is the same. If someone asks "what do we owe right now," the answer should come from the accounting system, not from four people checking their email.
3. The invoice is checked against the order
This is the verification step, and it is where the control in accounts payable actually sits. The question is whether the invoice matches reality: is this a real supplier, did we order this, did it arrive, and is the price what we agreed?
Where purchase orders exist, this is done by matching documents. Two-way matching compares the invoice against the purchase order: same supplier, same items, same prices. Three-way matching adds a third document, the goods receipt or delivery note, so that quantity delivered is checked as well as quantity ordered and billed. Three-way matching is the standard control for businesses that buy physical goods, because it is the only one of the three that catches a supplier billing for twelve units when ten arrived.
Businesses that buy mostly services, such as software subscriptions, contractors and professional fees, often cannot do three-way matching at all, because there is no delivery to receive. For them the equivalent control is a named person confirming the work happened, which is a judgment rather than a document comparison.
Without purchase orders, verification still happens; it just happens in someone's head. The practical substitute is a short, explicit check: is this supplier one we actually use, does the amount look like what we normally pay them, and has this invoice number come through before? That last question is the duplicate check, and it catches the single most common AP error. The same invoice arriving twice is routine: once emailed directly by the supplier, once forwarded by a colleague who wanted to be helpful. A business without a duplicate check will eventually pay both.
4. The invoice is coded
Coding means deciding which accounts the invoice belongs to and recording it in the books as a bill: the supplier, the date, the due date implied by the payment terms, the amounts, the tax, and the expense account each line should hit.
Three things go wrong here often enough to be worth naming. The first is supplier duplication: coding a bill to "Acme Supplies Ltd" when the books already contain "Acme Supplies," leaving one supplier's history split across two records so that neither shows what was really spent. The second is inconsistent account coding, where the same monthly software charge lands in three different expense accounts across a year, making the comparison to last year meaningless. The third is tax treatment, which is the one most likely to need an accountant rather than a rule.
Consistency matters more than perfection. An expense coded to a defensible account every single month tells you something useful; the same expense scattered across several accounts tells you nothing, even if each individual choice was arguable. This is the strongest argument for pinning routine suppliers to a default account and letting only genuine exceptions be decided case by case.
In both QuickBooks Online and Xero, a recorded bill becomes a payable with a due date and shows up in what the business owes. The two systems differ in vocabulary more than substance: Xero calls the supplier a contact, QuickBooks calls it a vendor, and QuickBooks additionally supports assigning transactions to projects, which Xero handles through tracking categories. If you are running the process for clients across both systems, the coding step is the one where the two feel most different day to day, even though what is being recorded is the same.
5. The invoice is approved
Approval is the point where someone with authority confirms the business will pay. In a small business this is frequently the owner, looking at a list once a week. In a larger one it is a routed workflow: the invoice goes to the budget holder for the department that ordered it, then above a threshold to a second approver.
A good invoice approval workflow has three properties, and most bad ones fail the same way. First, it is explicit about who approves what, so nothing waits in a queue nobody owns. Second, it has a documented threshold, so routine small invoices do not consume the same attention as significant ones. Third, it leaves a record of who approved and when, which is what makes the control meaningful after the fact.
The common failure is an approval step that exists on paper but is performed as a formality: a batch of forty invoices approved in one click, weeks after the goods arrived, by someone who has no way of knowing whether any of them are wrong. That is not a control, and it carries a real cost, because the approver's time is spent without buying any assurance. If approval cannot be meaningful for every invoice, it is better to approve by exception than to spread the same attention so thin it stops functioning. Set clear rules for what flows through untouched, and reserve genuine attention for what falls outside them.
This is also where invoice approval and purchase authorization get confused. By the time an invoice is approved, the money is already owed. Approval at this stage is confirming the invoice is correct and should be paid, not deciding whether the purchase was a good idea. If you find yourself wanting to reject invoices at this step, the problem is at step one.
6. The invoice is scheduled and paid
An approved bill has a due date derived from the supplier's payment terms: net 30 from the invoice date, due on receipt, or whatever was agreed. Scheduling means deciding when within that window to actually pay, and paying means executing it.
Most businesses benefit from paying in batches on a fixed rhythm rather than paying each invoice as it is approved. A weekly payment run means one deliberate session where cash is considered as a whole, instead of a stream of individual payments made whenever someone gets around to it. It also makes the cash position knowable a week ahead, which is the difference between managing payments and reacting to them.
Paying too early is a real cost, and an underrated one. Settling a net-30 invoice on day two hands the business's cash to the supplier twenty-eight days sooner than agreed, for no benefit, unless the supplier offers an early-payment discount worth taking. Paying late is the more obvious cost: late fees, interest, and the supplier relationship. The point of scheduling is to sit deliberately between the two rather than landing on either by accident.
Once the payment is made it must be recorded against the bill, which clears the payable. A payment that leaves the bank without being matched to the bill it settles produces the worst of both worlds: the books still show the amount as owed, and the cash is gone. Whatever else is automated, this is one of the reconciliation points a person should check.
DocStreamAI does not pay suppliers and does not schedule payments. It stops at a coded, recorded bill in QuickBooks Online or Xero; the payment itself happens in your accounting system or your bank, and this step stays where it is.
7. The record is filed and the period is closed
The last step is the one people think of as filing, and it is really about evidence. Every recorded bill should be traceable back to the document it came from, because that is what an accountant, an auditor, or a tax authority will ask for, sometimes years later.
Attaching the source document to the transaction in the accounting system is the simplest way to achieve this, and both QuickBooks Online and Xero support it. The alternative, a folder of PDFs organized by supplier and separate from the books, works right up until the person who understood the folder structure leaves.
At period end, accounts payable feeds the close in two ways. Unpaid bills are a liability and appear as what the business owes, so any invoice that arrived and was never recorded understates that figure and overstates the period's profit. And expenses need to land in the period they belong to, which is why invoices received after month end for goods delivered before it are the perennial close problem. The review-and-close job is covered from the software side in our guide to automated bookkeeping software.
The practical habit that makes this step painless is doing it continuously rather than at the end. A business that codes and files invoices as they arrive has already finished this step by the time the month closes. A business that leaves it for month end does the entire cycle at once, under time pressure, for every invoice, which is exactly when documents go missing.
What does a good accounts payable process flow look like?
A good accounts payable process flow has one intake point, a verification step that includes a duplicate check, consistent coding, an approval rule that distinguishes routine invoices from significant ones, a scheduled payment run rather than ad-hoc payments, and source documents attached to the records they support. The shape matters less than the fact that each step has a named owner and nothing waits in a place nobody checks.
Most process failures are handoff failures, not step failures.
It is worth being concrete about the three common shapes, because advice written for one is often useless for another.
The small business doing its own books. One or two people do everything. There are no purchase orders and no approval routing, because the person approving is the person who bought the thing. The binding constraint is time and the main risks are invoices that are never recorded at all and duplicate payments. The highest-value changes here are a single intake point and a duplicate check, not workflow software, which solves a coordination problem this business does not have.
The business with a bookkeeper. Someone else does the coding, which introduces the first real handoff: the bookkeeper cannot code what they have not been sent. The characteristic failure is a monthly scramble in which the bookkeeper chases documents for transactions they can see but cannot explain. The highest-value change is making intake automatic so documents arrive without anyone remembering to forward them.
The firm running AP for clients. The steps happen across many client files, the firm codes and the client approves, and the hardest part is collection. A firm's version of this process lives or dies on whether documents arrive from clients without weekly chasing, which is why AI tools for accountants and bookkeepers tend to be judged on intake rather than on their ledger features.
In all three, the steps are identical. What changes is which handoff breaks first.
What are accounts payable best practices?
The practices that matter most are: one intake point for every invoice regardless of how it arrives, a duplicate check before payment, supplier records kept clean so history is not split across near-identical names, consistent account coding with defaults for routine suppliers, an approval threshold that reserves real attention for significant invoices, a scheduled payment run instead of ad-hoc payments, and source documents attached to their transactions. Most are free. None requires software.
Do the cheap ones first; they remove more errors than automation does.
That last point is worth dwelling on, because the order is usually wrong. Automating a process with no duplicate check produces duplicates faster. Automating coding when supplier records are split across three spellings produces confidently miscoded bills. The sequence that works is to fix the process, then automate the parts that are repetitive and well-defined, then measure.
A few practices deserve more than a line:
- Keep supplier records clean. Merge near-duplicates, use the supplier's legal name consistently, and make sure new suppliers are added deliberately rather than created by accident during coding. Almost every "our reports are wrong" complaint traces back here.
- Separate who approves from who pays. In any business with more than two people in finance, the person approving an invoice should not be the person executing the payment. This is the single most effective fraud control in accounts payable, and it costs nothing.
- Verify supplier bank detail changes out of band. An email saying a supplier's bank details have changed is the most common invoice fraud in existence. Confirm it by phoning a number you already had, never a number in the email.
- Record the bill when it arrives, not when it is paid. This is what makes the payables figure mean anything, and it is the habit that most reliably separates businesses that know their cash position from businesses that guess.
- Review what is outstanding weekly. A short, regular look at unpaid bills catches missing documents and approaching due dates while both are still cheap to fix.
None of these is sophisticated. All of them are more valuable than the software decision, and a business that adopts them will get more out of automation later.
Where does automation actually help?
Automation helps most at the two steps that are high-volume, repetitive, and rule-shaped: getting invoices from wherever they arrive into the accounting system, and coding them consistently once they are there. Those two steps are most of the clock time in a typical small-business AP process and almost none of the judgment. Verification of unusual invoices, approval, and the decision of when to pay all involve judgment that software cannot supply, and automating them mostly moves the work rather than removing it.
Intake and coding are where the hours are; the rest is where the decisions are.
This is worth being precise about, because "AP automation" is sold as though it compresses the whole cycle evenly, and it does not. Look at the seven steps again and ask which are repetitive:
- Step 1, authorization is a decision. Software can enforce a threshold once someone has set it, but the judgment is human.
- Step 2, intake is pure repetition. Finding the attachment, downloading it, and filing it has no judgment in it at all, and it is the single largest time sink in most small-business AP.
- Step 3, verification splits. The duplicate check and the match against a purchase order are mechanical and automate well. Deciding what to do about a genuine discrepancy does not.
- Step 4, coding is largely repetition with occasional judgment. The same twenty suppliers each month are routine; a new supplier or an unusual purchase is not.
- Step 5, approval is a decision, and automating it usually means automating the routing rather than the approving.
- Step 6, payment is execution, and it is already automated by banking systems for most businesses.
- Step 7, filing and close partly automates: attaching documents can be automatic, while judgments about which period an expense belongs to cannot.
So the realistic claim for automation in accounts payable is that it removes the retyping in steps two and four, and makes the mechanical parts of step three reliable rather than dependent on someone remembering. That is a substantial gain, because those are the steps with the most volume. It is not the same as an automated accounts payable process, and vendors that imply otherwise are describing a business without exceptions, which does not exist. Our guide to what invoice automation is walks through that pipeline in more depth, and best automated bookkeeping software covers how the category as a whole is shaped.
Where DocStreamAI fits
DocStreamAI is built for steps two and four, and it is honest about stopping there. It watches connected Gmail and Outlook inboxes and provides a per-organization forwarding address, so invoices and receipts that arrive by email reach one place without anyone remembering to forward them. It reads each document with AI, pulling the supplier, dates, line items, totals, and tax, and it runs a duplicate check before anything is submitted, so the same invoice arriving twice by two routes is recognized rather than booked again.
For coding, it matches each document against the vendors and categories already in your QuickBooks Online or Xero account rather than keeping a separate supplier list, which is what keeps the near-duplicate supplier problem from being automated into existence. A vendor can be pinned to a specific expense category and funding account so it is coded the same way every time, or left to the AI. Payment terms are resolved into a due date, and the result is a bill drafted in your accounting system.
What it does not do is equally important for anyone reading this as a buying guide. It does not raise purchase orders, does not perform two-way or three-way matching against a PO, does not route invoices between multiple approvers, and does not pay anyone. Approval in DocStreamAI is a review gate rather than a routing workflow: you can require manual approval for everything, let documents submit automatically, or set it per vendor so trusted suppliers flow through while everything else waits. Documents uploaded directly always get one human confirmation before they can be submitted.
If your process is held up by approval routing across departments or by PO matching, that is a different category of product and this is not it. If it is held up by invoices sitting in inboxes and by someone retyping the same six fields several hundred times a month, that is the problem it was built for. You can see the mechanics step by step for QuickBooks Online and for Xero.
How long should the accounts payable process take?
There is no universal benchmark worth quoting, because the honest answer depends on whether the business uses purchase orders, how many people approve, and how invoices arrive. The more useful measure is the gap between the invoice date and the date the bill was recorded in the accounting system. That gap is entirely under your control, involves no judgment, and is the part of the cycle that automation genuinely compresses. If it is measured in weeks, the process has an intake problem, whatever else is true.
Measure recording lag before measuring anything else.
Two other numbers are worth watching once recording lag is under control. The first is the share of invoices that need an exception: a correction, a chase, or a conversation. If nine invoices in ten pass through untouched, automating the routine ones is clearly worthwhile. If half need attention, the process has a supplier or data problem that automation will not fix and may obscure. The second is duplicate payments caught versus duplicate payments made, which is the only direct measure of whether the verification step is doing its job.
Resist the temptation to measure cost per invoice. It is the headline metric in vendor marketing because it can be made to move, and for a small business it mostly reflects how the overhead was allocated rather than anything about the process.
The honest bottom line
The accounts payable process is seven steps, and most businesses do not have a process problem across all seven. They have one broken handoff, usually between the invoice arriving and the invoice being recorded, and everything downstream inherits it. Fixing that one gap resolves more than any other change available, and none of it requires buying anything: a single intake point, a duplicate check, and bills recorded when they arrive rather than when they are paid.
Once that is true, automation is worth considering, and it is worth considering narrowly. The steps that automate well are intake and coding. The steps that do not are the ones where someone decides something. A product that claims to automate the whole cycle is either describing a business with no exceptions, or quietly relying on a person to handle them without saying so.
If your invoices arrive by email and the bottleneck is that they sit there, DocStreamAI watches the inbox and drafts the coded bill in QuickBooks Online or Xero. If your bottleneck is approval routing or purchase-order matching, look at a dedicated AP platform instead. That is a real category, and it is not the one we are in.