What is an expense report?

Why the evidence matters as much as the amount

An expense report exists to let somebody other than the spender decide whether the cost was a business cost. That decision needs three things per line: what was bought, when, and for what purpose. The purpose is the part most templates leave out, and it is the one that makes an approval possible without a conversation. Client dinner is not a purpose; dinner with two people from the Adelaide project during the implementation visit is. For tax records the organisation generally needs the supplier's document rather than a bank statement line, because the statement shows a payment and not what was supplied. That is also why a photograph of a receipt is fine and a screenshot of a card transaction usually is not.

Where the rules should be written down

Most expense disputes come from rules that exist only in the approver's head. Whether alcohol is claimable. Whether a taxi home after nine is. What the accommodation ceiling is in each city. Whether a meal on a day trip counts. Whether personal travel attached to a business trip changes the flight claim. Each of those is easy to answer in one line in a policy and expensive to litigate case by case. The policy should also say what happens when somebody spends outside it, since the honest answer in most organisations is that it is approved anyway with a note, and pretending otherwise just teaches people to describe things vaguely.

GST, project codes and the reason finance cares

The report is a source document for two separate purposes: paying the person back and getting the accounting right. Those want different things. The claimant wants a total; the accounting wants each line split by category, tax treatment and the project or cost centre it belongs to. Where the organisation is registered for GST, the credit can generally only be claimed with a valid tax invoice, which is why the receipt quality question is a financial one rather than a bureaucratic one. Splitting a report across projects at the line level costs the claimant almost nothing at submission time and saves a reconstruction later, so a project column is worth having even in a small business.

Common failure patterns

Reports submitted quarterly, which produce a large claim, faded receipts and a cash flow surprise for the claimant. Approvers who tick everything, which turns the control into paperwork. A category list with thirty entries, which guarantees inconsistent coding. And the pattern of an employee carrying business costs on a personal card for months because the reimbursement is slow, which is a fairness problem before it is a process problem. Setting a submission window, a payment turnaround and a short category list solves most of it. Where volumes are high, a company card with a matching workflow removes the personal money question entirely, at the cost of needing tighter reconciliation.

Building the report as a document

An expense report is a tabular one or two page document, so the core is a table with date, description, purpose, category, amount and tax columns. Tables are one of the forty five component types, and keeping the table to six columns keeps it printable. A key values block carries the claimant, the period and the total in one of four layouts. One signature block party is one signer, so a claimant declaration plus a manager approval needs two parties with a signing order. No cover is added, since covers are never used on a document under three pages or on anything that functions as a receipt.

Client rechargeable expenses change the rules

When an expense will be billed on to a client, the report has to satisfy a second reader who has no relationship with the person who spent the money. That usually means a stricter evidence standard than the internal policy asks for, since a client can and will query a line with a vague description. Three habits prevent most of the arguments. Record the client's own reference or matter number on the line rather than only the internal project code, so the recharge can be matched without a lookup. Keep rechargeable and internal costs on separate lines even when they were paid in one transaction, because splitting a shared taxi fare after the fact is tedious. And check the engagement terms before spending, since many contracts cap categories such as accommodation or exclude them entirely, and an unapproved cost becomes the supplier's cost rather than the client's.

Questions people ask