Expense Reimbursement Email: How to Claim

Expense claims are the one workplace email where being good at English means being boring: numbers exactly once, receipts matched, policy cited. Do it well and finance processes the claim in one pass; do it loosely and each missing detail costs a query cycle, and each cycle costs days. This guide builds the one-pass claim.

Why Claims Bounce

Claims bounce on four fixable causes: missing receipts, unlumped totals, no business purpose and wrong payment route, and each adds a query cycle that delays money by days. None of the four is a judgement about your spending; all four are process facts your email can supply before finance has to ask. The one-pass claim simply answers the four questions inside the first email. Finance queries are process, not suspicion; one-pass claims end them.

The One-Pass Claim Email

The claim email runs four blocks: a subject line with your name and month, an itemised table with dates and amounts, the receipts referenced by name and count, and the policy clause plus payment route.

1. Subject: Expense claim, Wei Ming, March 2026.
2. Table: five lines, one per receipt, exact amounts.
3. Receipts: five PDFs attached, named to match the table lines.
4. Policy and route: per the travel policy, section 4; reimburse to the DBS account on file.

Totals to the cent; rounding invites queries.

The Itemised Table

Each line carries date, description, business context, category and exact amount, because the table is what an approver approves and finance files, not the prose around it. Worked line: 4 Mar, client dinner, Meridian account renewal discussion, client entertainment, 118.40. The description names what; the context names why; the category maps to the policy's own vocabulary. One line per receipt; bundled lines create reimbursement ambiguity, and ambiguity is what queries are made of.

Receipts, References and Timing

Name receipts to match table lines, reference them by count in the email, and submit within the policy's claim window, because unmatched attachments are the top query trigger.

• Naming: Receipt-01-04Mar-dinner.pdf mirrors the table's first line.
• Count reference: five receipts attached, one per line, in order.
• Window: submit the week the expenses land, not quarter-end.

Photographs of paper receipts are acceptable where policy allows; legibility is the bar.

When a Claim Comes Back Queried

Answer the query in the same thread with exactly the missing item, no re-submission and no new claims mixed in, because clean threads close cycles in one reply. The reply is two lines: the item requested, attached and named, and a thanks that ends the cycle. A second query on the same line means a call, not a third email; somewhere the thread and reality have diverged, and voice fixes that faster than prose.

Transactional Writing as a Register

Claims, purchase requests and invoice queries share the transactional register, numbers exactly once, context one line, action stated, and small-group practice keeps it precise. The register is small and learnable, and it is exactly where second-language professionals gain the most from corrected drafts. iWorld Learning's Business English small-group classes mark transactional emails as core practice. Keep a sent claim as the template for the next cycle.

Frequently Asked Questions

Can I claim expenses paid on my personal card?

Where policy allows, yes; state the payment method in the table so finance routes the reimbursement rather than querying it.

How do I split a shared bill in a claim?

Claim only your share, note the split in the line description, and name whose receipt the original is, so finance does not reimburse the full amount twice.

What about foreign-currency expenses?

Attach the card statement line showing the SGD equivalent and claim that figure; the receipt proves the spend, the statement sets the amount.