Expenses: prove you bought a sandwich, in triplicate, within thirty days

Most explanations of expense claims stop at the point where it starts to matter. This one carries on.

The audit is the customer, not the employee

Expense systems are designed so that a tax authority or an auditor can reconstruct every claim years later from documentary evidence. That requirement drives the receipt rules, the categorisation, the approval trail and the deadlines, all of which serve an external reader.

The employee who spent the money is not the audience for any of it, which is why the process feels indifferent to their experience. Understanding this makes the design comprehensible without making it enjoyable, and it explains why complaints about it never change anything. The rules also differ by jurisdiction, which is why multinational organisations run the strictest version everywhere rather than several versions.

Small claims cost more to process than they are worth

A claim requires an employee to submit, a manager to approve and a finance team to check, and each of those steps has a real cost in time. For a small amount the total administrative cost routinely exceeds the value being reimbursed, which is a well-known finding in finance operations.

Per diem allowances exist precisely to avoid this, replacing receipts with a fixed daily figure that requires no documentation at all. Where tax rules permit them, per diems are cheaper for everyone and are used less than they could be because they feel imprecise. Raising the receipt threshold is the other standard fix, and it is usually blocked by a preference for uniformity over arithmetic.

The employee is financing the company

An employee paying for travel personally and waiting weeks for reimbursement is extending an interest-free loan to their employer. For a large trip that can be a substantial sum, and it falls hardest on the people least able to carry it. Company cards, advances and direct billing all solve this and all require somebody to accept a fraud control risk.

The risk is real and is generally much smaller than the equity problem it creates, which is a trade rarely stated in those terms. Asking for a card or an advance for a large trip is entirely reasonable, and the answer tells you what the organisation prioritises.

Policies grow after incidents and never shrink

A new rule is usually written in response to a specific event, applied to everybody, and never revisited once the event is forgotten. The result is a policy document that is an archaeological record of past incidents rather than a coherent set of principles. Because removing a rule requires somebody to accept responsibility if the incident recurs, the ratchet only turns one way.

This is the same accumulation problem that produces packaging layers, compliance modules and consent banners, and it has the same fix.

Periodic expiry with active renewal works here as it does everywhere else, and is just as rarely implemented.

The photograph is now the receipt

Most tax authorities now accept digital images of receipts, which removed the shoebox and did not remove the deadline. Photographing a receipt at the moment of payment takes a few seconds and eliminates the single largest cause of unclaimed expenses. Thermal receipt paper fades, sometimes within months, which means the paper original is frequently worse evidence than the photograph.

On hold for the fourth time, filing the image into a single folder as you go converts the monthly claim from an archaeology project into a five-minute task. This is genuinely the whole trick, and almost everybody learns it only after losing a claim to a faded till roll.

Practices change, and a company that does this today may have quietly stopped by the time you read it.

Getting paid without the argument

Read the policy once, particularly the deadline, the receipt threshold and the categories, because those three cover most rejections. Submit weekly rather than monthly, since a small regular task is both faster and less likely to hit a deadline. Write a one-line business purpose on every claim, because that is the field auditors read and the one most often left blank.

Somewhere in the release notes, keep the images even after reimbursement, as queries can arrive long after the claim was settled. And for anything large, ask about a card or an advance beforehand rather than complaining about the wait afterwards.

The takeaway

Photograph it at the till and submit weekly. That is the entire method.

The fix is usually trivial, which is the most annoying part.