The expense claim as a records problem

You submitted a claim in February, it was approved in March, and something was paid in April. Now someone wants to know what the £212 was. The receipts went with the claim, the claim lives in a system you no longer have an account for, and you have a bank credit with no breakdown.

An expense claim looks like an admin task. It is actually a records transaction, and the awkward feature is that your records leave your possession partway through it.

Three artefacts, not one

The claim process generates several distinct things and people habitually keep only the first.

The underlying records. The receipts and invoices for what was actually bought. These establish the spend and — if annotated — the reason for it.

The claim itself. What you asserted: which items, which amounts, which dates, under which category or project, submitted when. This is a document in its own right, and it is the only place the grouping exists. The receipts don’t know they were part of a claim.

The settlement. What was actually paid, when, and by which route. Usually a single bank credit, frequently for an amount that isn’t the total you claimed.

Those three answer different questions, and the third minus the second is where every reimbursement argument lives.

Why the claim goes wrong specifically

The originals leave. Depending on the arrangement, you hand over paper, or upload images and then bin the paper because it felt processed. Either way, the copy you can reach is now the copy in someone else’s system, and that copy is subject to their retention, their account lifecycle, and their decision to change platforms.

Your own record loses its reason. The reason for the spend was often written into the claim — the project code, the client, the trip — rather than onto the receipt. So your copy of the receipt is a bare amount again, exactly the failure described in what makes a receipt useful later. The reason went into the system with the claim and stayed there.

Approval takes longer than the paper lasts. A claim can sit for weeks. A thermal slip photographed on day one is fine; a thermal slip waiting in a wallet for the approval cycle to finish may not be — see where paper survives.

Partial settlement splits one receipt in two. A line is queried and dropped, or a portion is treated differently. Now one receipt corresponds partly to money you received and partly to money you didn’t, and nothing in your files records the split unless you wrote it down.

Grouping is invisible afterwards. Claims are grouped by trip, month or project. Your files are grouped by date or vendor. Reconciling one bank credit of £212 against nine receipts across two months, months later, is an unpleasant afternoon that a copy of the submitted claim would have made a two-minute job.

The practice

Capture before you submit, always. The image you keep is taken before the paper goes anywhere, and it is yours regardless of what happens to the claim. This is the whole of the discipline; everything else is refinement.

Keep a copy of the submission, not just the receipts. A screenshot, an export, a confirmation email, or a line typed into a file: date submitted, items, total, reference. It costs seconds and it is the artefact nobody keeps.

Write the reason onto your copy, not only into the form. The project, the client, the trip. The form’s version is not accessible to you later.

Record the settlement against the claim reference. When money arrives, note which claim it settled and whether the amount matched. A short running list of claim reference, claimed, paid, and date closes the loop; without it, unmatched shortfalls are simply never noticed.

Never let the claim system be your archive. It belongs to someone else, and access ends when the relationship does — see records you don’t actually hold.

Keep or bin

KEEP OR BIN — a reimbursement cycle

  · Your own image of each receipt, taken
    before submission
                    → KEEP. The only copy whose
                      lifetime you control.

  · Copy of the submitted claim
                    → KEEP. The only artefact holding
                      the grouping and the stated
                      reason.

  · Note of what was actually paid, against
    the claim reference
                    → KEEP. Closes the loop; makes a
                      shortfall visible.

  · The approval email on its own
                    → NOT A RECEIPT. It establishes a
                      decision, not a purchase and
                      not a payment.

  · Bank credit line for the reimbursement
                    → NOT A RECEIPT either. Payment
                      evidence, with no breakdown of
                      what it settled.

  · Duplicate photos of the same slip from
    three angles
                    → BIN all but the legible one.

  · Whether a claimant or the payer must
    retain the original, and for how long
                    → ASK LOCALLY. Splits by
                      jurisdiction, by arrangement,
                      and by who is claiming what.

If you are the one being claimed against

The same structure inverts if you receive claims — a contractor invoicing you with expenses attached, or a small team submitting their own.

You need the underlying records, the claim that grouped them, and your own record of what you paid, for exactly the reasons above. The additional problem is that the underlying records were created for someone else’s filing system, arrive named however they arrived, and are frequently images of variable quality. Renaming on receipt is the only thing that stops a year of these becoming unsearchable; finding it again covers the naming, and the two-container approach in an inbox and an archive is what stops incoming claims piling up in an email thread.

One more thing worth knowing: a claim submitted to you is a record you now hold about someone else. It carries their partial card numbers, their travel, sometimes their address. That has handling implications independent of any tax question — what a receipt reveals covers what is actually on these documents.

What this doesn’t settle

Who is required to keep the original, whether a photograph is an acceptable substitute for it, what categories a claim must use, whether reimbursed expenses are treated differently from directly incurred ones, and how long any party must hold any of it.

Those are rules — set by tax authorities, and by the arrangement between the parties — and they vary by jurisdiction and situation. Ask your tax authority or an adviser. What this page settles is narrower and entirely within your control: at the point where your records go into someone else’s system, you should still have your own.