Small business outsourcing workflow guide
Write a daily supplier invoice exception queue for a small-business assistant
An exception queue that separates a missing purchase order, a price mismatch, and a duplicate invoice before anything reaches the payment run.

Start with the invoices that cannot move
A daily exception queue should contain only the invoices that cannot move through the normal process, not every invoice the assistant touched. Define the normal path first: a matching purchase order, a received note, and a price within tolerance. An invoice that meets all three moves on without a queue entry. The exception queue is for the remainder, and its purpose is to make the reason for the stop visible.
Write the queue entry with the supplier, the invoice number, the amount, the age, and the specific exception. A row that says needs review tells the owner nothing and invites a second review later. Use a short list of reasons such as no purchase order, price mismatch, quantity mismatch, duplicate, missing bank details, or unclear approval. The reason should point to the evidence that resolves it.
Keep the queue in the same tool as the payment run so an invoice cannot be paid from one view while it waits in another. If the accounting system cannot hold the queue, use a shared sheet with a link back to the invoice. Do not let the queue live only in an inbox. An inbox hides the age of the item and makes it easy to miss.
Separate the exception types by owner
A missing purchase order belongs to the person who bought the item, while a price mismatch may belong to the buyer or the supplier. Give each exception type a named resolver and a target response time. A queue that routes every item to the owner trains the assistant to stop thinking and the owner to become a bottleneck. The routing rule should be visible beside the queue.
For a duplicate, the resolver checks whether the earlier invoice was paid and whether the new one is a credit or a reissue. For a bank-detail change, the resolver follows a callback rule and never accepts the new number from the invoice alone. The assistant can gather evidence but should not approve a change that moves money. Make that boundary explicit in the queue instructions.
Give the assistant a safe action for each row
The assistant should always have a next action, even when the answer is wait. For a missing purchase order, the action is to request the order number from the buyer with a template that names the invoice. For a price mismatch, the action is to attach the quote and the order line. For a duplicate, the action is to link the prior payment. A row with no action becomes a silent parking lot.
Set a rule for how many times the assistant may chase the same item before escalating. Two follow-ups on separate days is a common limit. Record the date of each attempt and the channel used. When the limit is reached, move the item to the owner with the evidence collected. The escalation should not restart the investigation.
Protect the payment run with a cut-off
Publish a daily cut-off after which an unresolved exception waits for the next run. The cut-off should be early enough that the assistant can complete the queue and the owner can review it before payments are released. Do not let a late invoice create pressure to skip the check. The schedule is part of the control, not an inconvenience.
Before each run, reconcile the number of exceptions opened, resolved, and carried forward. A queue that grows without explanation may point to a supplier sending bad data or a buyer who stopped providing orders. Show the count by reason so the pattern is visible. A single total hides the difference between a duplicate problem and a missing-order problem.
Keep evidence and access under control
The assistant needs read access to invoices and purchase orders, but not the ability to change bank details or release a payment. Use a named account and record who granted each permission. Keep the evidence in the queue row rather than in a personal folder. A reviewer should be able to open the invoice, the order, and the receiving note from one place.
Redact personal data when an invoice includes a home address or a personal phone number. Share only the fields the resolver needs. If a supplier sends a statement with other customers' data, do not forward it. Record the incident and ask the supplier for a clean copy. The queue should not become a channel for unnecessary personal data.
Review the queue weekly for root causes
At the end of the week, group the exceptions by supplier and by reason. A supplier that repeatedly sends invoices without the order number may need a template or a reminder. A buyer who never raises orders may need a simpler request path. The weekly review should choose one fix and name the owner. Counting the same problem every week without a fix is not a control.
Track the time each exception waits and the share resolved before the cut-off. Compare the result with the previous week and with the volume of invoices processed. If the queue is small but the wait is long, the problem is routing. If the queue is large but the wait is short, the normal process may be too strict. Adjust one variable and measure again.
Share the weekly summary with the buyer and the owner in one place. A short table by reason is easier to act on than a list of individual invoices. Ask each resolver which item they could have prevented and record the answer. The next week should test one prevention step, not a broader policy rewrite.
Sources and next steps
- U.S. Small Business Administration, manage your business
- U.S. Government Accountability Office, internal control standards
- Association of Certified Fraud Examiners, fraud resources
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.