Expense Reimbursement Policy for Small Businesses: The One Page That Ends Receipt Archaeology

The three questions every claim answers, the seven lines that fit on one page, the monthly flow that keeps the books fast, and the five traps that turn reimbursements into a second payroll.

Every small business runs two payment systems and only controls one of them. The company pays suppliers through the supplier payment terms you negotiated; employees pay for the company out of their own pockets, on their own terms, and hand you the bill at month-end. Unmanaged, that second system produces three familiar failures: the shoebox of receipts someone reconciles at midnight, the employee who has quietly been lending the company $400 for six weeks, and the duplicate claim nobody catches because no one is sure what was already paid. None of it is fraud in the main — it is what happens when the rules live in the owner's head instead of on a page. This is that page: seven lines, three questions, twenty minutes to write and ten minutes a month to run. It feeds straight into the month-end close, and its approval ladder borrows from the standing orders template — pre-agreed limits so small decisions never queue for you.

1. The three questions every claim answers

A claim that can't answer all three in one line doesn't get rejected — it gets a question. But the questions are the same every time, so the policy writes them down once:

Three yeses, paid with the next run. One no, one question. The point is not suspicion; it is that every claim is legible to the bookkeeper without a conversation with the person who spent the money.

2. The seven lines — the whole policy, printable on one page

  1. Card-first. The company card is the default for anything business-related. A personal card is the exception, used when the card won't work — not a second payment system with rewards points.
  2. Pre-approval threshold: $150. Under it, buy and claim. Over it, one line of approval before the spend ("Kestrel Foods — $310 saw stand"). The threshold is a speed limit, not a prohibition.
  3. Submit within 7 days. Claims older than the window roll to the next batch — not refused, just not urgent. The window is what keeps claims attached to the month they happened in.
  4. Proof: receipt above $10. A photo of the receipt attached to the claim is a receipt. No receipt: the declaration form — what, when, why — once a month per person, capped at $50. The cap is what keeps the exception an exception.
  5. Categories, named. Yes: travel to jobs, tools and materials, client meals (client named), software. Never: parking fines, personal upgrades, the commute. If a category isn't listed, that's a question, not a no.
  6. Mileage at the ATO cents-per-kilometre rate (reviewed each July), logged as date, job, kilometres — a note in the truck is fine.
  7. No self-approval. The owner's own claims are approved by the bookkeeper. The rule that keeps the policy honest is the one that applies to the person who wrote it.

Payment timing closes the loop: approved claims are paid with the next pay run — weekly or fortnightly, whatever the payroll already does. Ten business days is the outside edge; past that, the policy quietly turns employees into lenders, and lenders start keeping the receipts as hostages.

3. The monthly flow — ten minutes, feeding the close

Once a month, before the month-end close opens the books: claims in by the 1st, each one answering the three questions, proof attached, categories checked, then paid with the next run. The bookkeeper's reconciliation is then arithmetic — match claims to card feed, pay the batch — instead of archaeology. Card-first is what makes it cheap: every company-card transaction already has a record; the claim is a label ("Kestrel Foods, materials"), not a reconstruction.

4. The five traps

5. Worked example — the electrical contractor's 3.1 hours

A twelve-person electrical contractor: nine field techs on personal cards, $23,400 a year in reimbursed spend, and a month-end ritual the office manager called "receipt archaeology" — 3.1 hours matching paper to memory. The year before had produced $4,100 of unreceipted spend and two duplicate claims worth $310, found by luck in a bank statement, not by the system. The owner wrote the seven lines on one page on a Sunday; the only purchases were the card-first switch and a photo-of-receipt habit. One quarter later: month-end reconciliation down to 40 minutes, unreceipted spend at $0 (the declaration form used three times, all under the $50 cap), duplicate claims zero, and the card's transaction feed doing the matching the shoebox used to do. The owner: "I thought a policy was for companies with HR departments. It turns out it's for companies with shoeboxes."

Kits

Every page ships with a kit block — the paid tools behind the free advice:

Related: the supplier payment terms checklist is the paying side of the same spend — this policy is the employee-spend side, and the two together are the company's real outgoings; the month-end close is where the claims batch reconciles — card-first keeps that hour short; the standing orders template is the same idea applied to decisions — pre-agreed thresholds so small ones never queue; and the overdue invoice letters are what the other side of your ledger owes you while you're being prompt about theirs.

Related: the purchase order process is the over-threshold sibling of the expense policy — card-first under the line, a numbered promise before the order above it.