Small business outsourcing workflow guide

Build a simple invoice exception log for a small business

An invoice exception log that shows what did not match, who owns the fix, and when the supplier or customer was told.

Define what counts as an exception

An invoice exception is any invoice that cannot be paid on the normal path. That includes a missing purchase order, a price that differs from the quote, a duplicate charge, or a delivery that was never confirmed. Write the list before the assistant starts reviewing invoices. A clear definition keeps the log from becoming a place for every question.

Separate a supplier error from an internal error. A supplier invoice with the wrong address is different from an internal approval that was never recorded. The log should show the type so the owner can fix the right process. The assistant can identify the mismatch but should not decide who is at fault.

Capture the invoice and the source

For each exception, record the invoice number, the supplier, the amount, the date, and the source document. Link the purchase order, the quote, or the delivery note that the invoice should match. If the source is missing, say so rather than marking the invoice approved. A log without the source cannot support a decision.

Use one row per exception and keep the original invoice unchanged. Do not edit the supplier's document to match the internal record. If the supplier sends a corrected invoice, add it as a revision and keep the earlier one. The history shows what changed and why.

Name the owner and the next action

Every exception needs an owner and a next action, such as request a credit, obtain the missing purchase order, or confirm delivery. Write the action as a verb and a specific object. Name the person who will do it and the date it should be done. An exception without an owner will stay open until someone asks about it.

If the action depends on the supplier, record the contact and the date the request was sent. If it depends on an internal approver, record the approval needed. The owner should be able to see which side is holding the case. That distinction prevents the assistant from chasing the wrong person.

Set a review cadence

Review the exception log weekly, not only at month end. A small mismatch caught early is easier to fix than a pile of invoices at the payment run. Check the age of each open item and the number of items waiting on the same supplier. The weekly review should take less time than reconstructing the month later.

At month end, compare the log with the payment run. Confirm that no excepted invoice was paid without a decision and that no approved invoice was left out. Record the comparison and the person who checked it. The log is only useful if it changes what gets paid.

Keep the log small

A log with too many columns will not be maintained. Keep the invoice, the supplier, the amount, the mismatch, the owner, the next action, and the date. Move detailed notes to the invoice record if needed. The log should be readable in one screen and sortable by age.

Use a small set of reason codes so the owner can see patterns. Examples include missing order, price mismatch, duplicate, and delivery not confirmed. Do not create a new code for every case. A stable set makes the monthly review faster and the trend more reliable.

Close with evidence

Close an exception only when the corrected invoice, credit note, or approval is attached. A status change without evidence is not a close. Record the person who confirmed the resolution and the date. If the supplier agrees to a credit, keep the written confirmation.

If the exception is resolved by paying a different amount, record the approved amount and the approver. Do not let the payment run silently override the invoice. The log should match the payment record. A mismatch at that point is a new exception, not a closed one.

Keep the log in the accounting system or a shared sheet the bookkeeper can access. A personal spreadsheet creates a second source of truth. If the business uses a shared inbox, route the supplier reply to the same row. The log should be the place where the next person looks first.

Review the causes each quarter

Once a quarter, group the exceptions by reason and supplier. Ask whether the same supplier keeps sending the same error and whether the internal process keeps missing the same step. A repeated cause is a process problem, not a one-off. Choose one change and assign an owner.

Tell the supplier or the internal team about the change and the expected effect. Check the next month's log to see whether the cause fell. If it did not, the change may have addressed the symptom rather than the source. The review should end with a decision the business can test.

An exception log should show the payment status as well as the review status. An invoice can be reviewed and still unpaid, or paid and still unresolved. Record both so the owner does not assume a closed review means the payment is complete. The two states answer different questions.

Sources and next steps

Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.

Related guides

Free role planning call

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to prepare a practical Philippines staffing conversation.

Contact Us