AP approval workflows for teams of one to five

Most advice about AP approval workflows assumes a department: a clerk who enters, a manager who approves, a controller who reviews. At a small business the “department” is one to five people, sometimes one person wearing all three hats. That doesn't make approval pointless — it makes the design different. The goal at this size isn't bureaucracy; it's making sure no dollar leaves without a second look, even when there's barely a second person.

Why bother at this size

Three failure modes hit small teams hardest, precisely because no one is checking: the duplicate paymentnobody catches for months, the vendor price creep nobody notices because the same person enters and pays, and the fraudulent invoice that looks routine. None of these need a big team to prevent. They need a moment, on purpose, between “this arrived” and “this got paid.”

The workflow that fits

Keep it to rules everyone can hold in their head:

• A threshold, not a committee.Below a set amount (say $500), one person's review is enough. Above it, a second set of eyes — the owner, a partner, the fractional CFO — before payment, not after.
• New vendors always get reviewed. First invoice from any vendor is approved by someone senior, whatever the amount. This single rule blocks most invoice fraud.
• Separate entering from paying.Even with two people, the one who enters the bill shouldn't be the one who releases the payment. With one person, the separation is in time: enter today, pay from a reviewed batch on a set day each week.
• Pay on schedule, not on arrival.A weekly payment run turns approval into one sitting instead of a constant trickle, and makes the “urgent” invoice — the classic fraud pressure tactic — stand out.

The one-person shop

If you're solo, you can't separate duties, but you can separate moments. Enter bills as they arrive; never pay in the same sitting. Once a week, open the batch and review it cold: new vendors, amounts against last month, anything twice. The gap between entry and payment is where your own errors become visible to you.

Where automation fits

Notice what the workflow above actually asks of a person: read each invoice, code it, compare it to history, and queue it for a decision. Everything except the decision is mechanical. An automated intake pipelinedoes the reading and coding on arrival, runs the checks — duplicate, math, new vendor, out-of-pattern amount — and presents a queue where each item is either clean or flagged with a reason. The approval moment stays exactly where it belongs, with a person; it just starts from “review this” instead of “type this.” For a team of one to five, that's the difference between a workflow you designed and one you actually follow in a busy week.