Building Purchase Approval Workflows in QuickBooks

QuickBooks Online has purchase orders. What it mostly doesn't have is approvals — the kind where a request gets checked against a budget before anyone commits money. QBO Advanced ships approval workflows for bills and POs. Every tier below gives you an honor system and a Slack message.

So most companies run the informal version: someone asks in a thread, someone thumbs-up it, someone buys the thing, and a bill arrives six weeks later that finance has never seen. That's not a control. It's a rumor with an invoice attached.

Know what you're actually building

A real purchasing flow has six stages, each a place data gets created or lost. Skip the first and approval becomes a formality performed after the money is gone.

1. Request. Who wants what, why, how much, which budget line.
2. Approve. Routed by amount, department, and category.
3. PO issued. A number the vendor references on their invoice.
4. Receive. Someone confirms the goods or work arrived.
5. Bill. Matched to the PO, not typed fresh.
6. Pay. Only against an approved, received, matched bill.

Thresholds people can live with

The fastest way to kill a workflow is to make everything need sign-off. Approve by exception. Under $250 on an approved vendor in a budgeted category needs nobody. $250 to $2,500 goes to the department head. Above that, add finance.

Then build the escape hatches: a delegate for every approver, auto-escalation at 48 hours. Workflows die from vacations more than disagreement.

An approval step nobody can complete in under a minute is a step people will route around.

Where the workflow actually lives

• QBO Advanced. Native, auditable, no extra system. Fine for amount-based routing.
• Ramp or Approve.com. Spend requests tied to card issuance and budget checks at request time, synced back to QuickBooks.
• Custom. A form, a rules engine in Make or n8n, and the QuickBooks API creating the PO once approval clears. We build this when routing depends on project, entity, or vendor risk, not amount alone.

Whatever you pick, the approval record lands on the PO in QuickBooks. Slack is not an audit trail.

Close it with a three-way match

PO, receipt, and bill agree, or the bill stops. That one rule catches price creep, quantity padding, and duplicate invoices — before payment, not during next year's cleanup.

Approval before the spend is a control. Approval after it is a memo.

We build routing that matches how your company really buys — see Workflow Automation, plus Team Enablement Sessions to make it stick.