Small business outsourcing workflow guide
Write a reimbursement request path a small-business assistant can follow
A reimbursement path that captures the receipt, the business purpose, and the approval before a small expense turns into a month-end argument.

Define which expenses qualify
Write a short list of expenses the business will reimburse without a prior approval, such as postage, local transport, or a customer coffee meeting under a set amount. Name the categories that always need approval, including equipment, software, and travel. A clear list keeps the assistant from guessing at the boundary. The list should fit on one page and use the words the team already uses.
State what the business will not reimburse, such as personal subscriptions or a fine. A short exclusion list prevents a difficult conversation later. Review the categories when the business changes tooling or adds a service. An outdated list produces requests that nobody can classify.
Capture the receipt and the business purpose
Require a receipt or a comparable record for every request, including a photo of a paper receipt taken at the time of purchase. Ask for the date, the vendor, the amount, and one sentence about the business purpose. The purpose should name the customer, the project, or the internal event it supports. A receipt without a purpose is a number that cannot be defended later.
For a purchase made online, keep the confirmation email and the invoice together. For a cash purchase, record who received the money and where the purchase was made. The assistant should check that the amount on the receipt matches the amount requested. A mismatch is a question for the requester, not a reason to adjust the record silently.
Set approval limits before the purchase
Give the assistant a table that shows who may approve which amount. A routine expense under a small threshold may need only the assistant's check and the owner's weekly review. A larger amount should need approval before the purchase, not after. The table should name a backup approver for the owner's absence.
Record the approval in the same request rather than in a separate email. The approver should see the receipt, the purpose, and the amount before deciding. If the purchase was already made without approval, the request should say so and explain why. Hiding the sequence makes a small control problem look like a trust problem.
Give missing receipts a clear path
Create a short missing-receipt form that records the date, the amount, the vendor, and why the receipt is unavailable. Require a second person to confirm the purchase before the request can proceed. Set a limit on how many missing-receipt requests one person may submit in a month. The path should be possible but visibly unusual.
Do not let the assistant approve a missing-receipt request alone, even for a small amount. The exception path exists to keep the record honest, not to make the process easier to bypass. Record the outcome and keep it with the reimbursement file. A repeated missing receipt is a signal to change how purchases are made.
Keep personal and business spending apart
Ask the assistant to use a business card or a dedicated account whenever one is available. When a personal card is used, require the request to state that fact and the reason. Never mix a personal expense and a business expense in one request. A clean separation makes the month-end review faster and the tax record clearer.
Record the payment method on every request and reconcile it against the statement. The assistant should flag a business charge that appears on a personal statement and a personal charge that appears on the business account. Both are easier to fix in the same week than at the end of the quarter. The goal is a record that matches the bank, not a perfect story.
Track the request until it is paid
Give every request a number and a status: submitted, approved, scheduled, paid, or returned. The assistant should update the status at each step and tell the requester when the payment is scheduled. A request that is approved but never paid is still open. The queue should show the age of every unpaid item.
Set a payment day and a cut-off for adding requests to that run. A request that misses the cut-off should get the next date rather than an exception. Record the payment reference so the requester can match it to their account. The assistant should close the request only after the payment is confirmed.
Close the month with a reconciliation
At month end, compare the reimbursement log with the bank and card statements. Look for a payment with no request, a request with no payment, and a duplicate payment. The assistant can prepare the comparison, but the owner should review the exceptions. A reconciliation that only totals the log does not prove the money moved correctly.
Record the closing date and the person who reviewed the exceptions. Keep the log with the receipts for the period the business retains its records. If a category grows quickly, review whether the approval limit still fits the spending. The month-end close is the moment to fix the rule, not just the entry.
Audit a sample each quarter
Each quarter, pull a small sample of paid requests and check that each one has a receipt, a purpose, and an approval that matches the amount. Include one missing-receipt request in the sample. Record what the sample found and what changed as a result. A sample of ten is enough to show whether the path is working.
Ask the assistant which step causes the most back-and-forth and remove one unnecessary field. Keep the fields that support the receipt, the purpose, and the approval. A form that grows after every audit becomes a form people avoid. The quarterly review should make the next request easier to file correctly.
Sources and next steps
- IRS, recordkeeping for small businesses
- U.S. Small Business Administration, manage your business
- U.S. Government Accountability Office, internal control standards
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.
Related guides
Set a daily opening check for an assistant-run support desk
A short opening routine that proves the overnight queue, the phone, and the day's promises are covered before the first customer arrives.
Build a damaged-order photo checklist for a support assistant
A photo checklist that gives a support assistant the right evidence for a damaged-order claim before the packaging disappears.