Best way to set up a purchase order approval process for a small business
Use one request route, approval limits by amount, a backup approver, and separate approving, receiving and paying roles. Adapt it for a tiny team.
Smalt AI team ·
Give every purchase one request route, check it against budget, and send it to an approver whose authority matches the amount. Name a backup approver and a path for urgent requests. Where you can, keep approving, receiving and paying with different people, and if your team is too small for that, add a second person’s review where the risk is highest.
Set up the request and approval route
Intuit’s guidance on the procure-to-pay process (page undated, read 2026-11-16) describes the sequence: a request goes to approvers after a budget check. It also says approval thresholds can vary by amount, department, location or expense type. Start with the simplest version of that.
- Pick one intake route. A form, a shared inbox or a request type in your accounting software. Purchases that arrive by chat message and hallway conversation tend to skip approval. List what every request carries: supplier, items, price, delivery date and budget line.
- Check budget first. The approver should know whether the money exists before judging the purchase.
- Set approval limits. Amount is the usual starting point; add department or expense type later.
- Name a backup approver. Intuit recommends naming backups, so a purchase does not wait because one person is away.
- Define an urgent path. Intuit’s same guidance suggests an escalation route for urgent requests, and separate paths for routine purchases and exceptions. Write down who can approve out of hours.
- Issue the PO only after approval. The PO number then becomes the reference everything else is matched to.
| Request tier | Who approves | Evidence needed |
|---|---|---|
| Up to your amount | Team lead | Budget check on the request |
| Above your amount | Owner | Budget check and a PO |
| Above your second amount | Two people | Budget check, a PO and both sign-offs |
The amounts are blanks for you to fill in. The tiers and evidence are our illustration, not a standard.
Here is a hypothetical walk-through, ours and not a real company. In a 12-person firm, the team lead approves up to $500 and the owner approves anything above. A designer requests a $320 monitor. The budget line has room, so the team lead approves and a PO is issued. Reception confirms the monitor arrived, and the $320 invoice matches the PO and the receipt, so payment is released.
If you are a one-person business, our suggestion is to approve your own purchases but write the request down first, then review any bank-detail changes a week later.
Separate the roles that can be separated
Intuit’s page says to keep purchase approval, receipt, invoice approval and payment release with different people. The usual name for this is segregation of duties: different people for asking, approving, receiving and paying. The University of Arizona’s Finance office, quoting the COSO framework (May 2013), says it is considered when designing control activities. Where it is not practical, management selects alternative controls.
A small business can use those alternatives. CPABC’s primer on internal controls (January 2025) says controls should fit the organisation, and that a two-employee company may not be able to fully segregate duties. Its suggested fixes include having another person review changes to master files such as bank details, and requiring supporting documentation. The primer has no purchase-order-specific guidance, so applying it to POs is our reading.
Start with one rule: the person who requests a purchase does not approve it. For a team of three or four, our suggestion is to add two more:
- Whoever receives the goods confirms receipt against the PO.
- The owner or a second person releases payment and glances at anything that does not match.
Match the PO, the receipt and the invoice before paying
Intuit describes a three-way match: compare the PO, the receiving record and the invoice before you pay. For a small business this can be a short checklist per invoice: same supplier, same quantity as received, price within what was approved. Anything that fails goes back to the approver rather than being paid and fixed later.
Intuit also advises verifying vendor bank-detail changes independently. Call a number you already hold, not one in the announcing email.
Use software to enforce it
If you use QuickBooks Online Advanced, Intuit’s help page on workflows (updated 5 August 2026) describes the setup: pick a record type, define conditions, then choose Do this > Request Approval. Approver groups can have up to 5 approvers, with a minimum number required, and approval can happen by email. It applies to QuickBooks Online Advanced and Intuit Enterprise Suite.
Purchase orders appear among the template categories, but the page does not explicitly confirm that Request Approval works on POs. Check Settings > Manage workflows > Templates in your account before you plan around it. A spreadsheet with a sign-off column is a legitimate start.
Doing it with an AI coworker
Smalt can take over the checking around the process, not the approving. Upload a month of supplier invoices as a .zip and ask your AI coworker to reconcile them against your PO sheet in Excel, with each exception linked to its invoice. It can also draft a reminder email to a slow approver; emails wait for your approval before anything is sent.
What to check before you rely on it
A backup approver nobody told is a backup in name only. Manual handling is common: Intuit’s 2026 Late Payments Report, cited on Intuit’s procure-to-pay page, found nearly 3 in 4 surveyed small and mid-sized businesses have not fully automated bill management and payment. This is Intuit’s own survey and shows no sample size, so treat it as a sign, not a precise figure.
Controls help, but the evidence is general. The ACFE’s Occupational Fraud 2026 report (read 2026-11) analysed 2,402 usable cases from 10,276 survey responses across 143 countries. It found that organisations with anti-fraud controls tend to have lower losses and faster detection. That is an association across many organisations, not a guarantee for yours.
Some checks only a person can do: whether your limits still match how the business buys, whether urgent-path purchases are reviewed afterwards, and whether one person can still request, approve and pay in an edge case, such as an owner buying for themselves. Lenders, grant funders or local requirements can also set rules on who may approve spending, so check those before you fix your limits.
Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.