Why group expenses by category?

Finance teams post expenses to ledger accounts by category — travel, meals, accommodation, software, and so on. Grouping the claim by category lets them code it quickly and lets managers see where spend is going. This tool subtotals each category and shows the grand total.

Do I need a receipt for every expense?

Most company policies and tax authorities require a receipt for reimbursable expenses, often above a small threshold. The report includes a receipt-attached flag per line so missing receipts are obvious before submission. A claim with unflagged receipts is usually sent back.

What counts as a valid business purpose?

A specific reason that ties the expense to company work — 'client lunch with Nordic Retail', 'taxi to supplier site', 'annual design-tool licence'. Vague entries like 'food' or 'travel' get queried. The clearer the purpose, the faster the approval.

Can I claim expenses in different currencies?

Yes — pick the currency the expense was incurred in. For a mixed-currency trip, most companies want the original amount plus the converted home-currency value at the day's rate. This builder records the amount and currency; add the converted figure in the purpose note if your policy needs it.

How is the grand total calculated?

The grand total is the sum of every line amount in the report, regardless of category. Category subtotals break that figure down so approvers can sanity-check each type of spend. The line amounts are summed exactly, so part-amounts like 12.49 are never rounded away.

What is the Expense Report Builder?

Generate an expense report with date, merchant, category, amount, currency, and business purpose for each line, plus a receipt-attached flag. Totals by category and grand total, and exports a printable claim. It runs free in your browser on Gera Tools, with nothing uploaded.

Expense Report Builder

Name: Expense Report Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

A reimbursement claim that gets approved first time

Expense reports are rejected for a handful of predictable reasons: missing receipts, vague business purposes, inconsistent categories, and foreign-currency amounts without conversions. This builder removes all of them. Every line requires a date, merchant, category, amount, stated business purpose, and a receipt flag — and the report subtotals each category so finance can post it to the ledger without manual sorting.

What each field does

Field	Why it matters
Date	Ties the expense to the correct accounting period and matches receipt dates
Merchant	Identifies who was paid; must match the receipt
Category	Determines which ledger account finance posts to (travel, meals, software, etc.)
Amount and currency	The actual spend in the original transaction currency
Business purpose	The field approvers read most carefully — must be specific
Receipt flag	Confirms the receipt exists and will be submitted with the claim

The business purpose field is where claims fail or pass

“Lunch” fails. “Meals” fails. “Coffee” fails. These tell the approver nothing they can verify or justify to an auditor.

Write: what was purchased, why, and who was involved if relevant. For example:

“Client lunch with Nordex Digital, discussing Q3 proposal” (not “Lunch”)
“Taxi from London Bridge to supplier site, Holborn (7am meeting)” (not “Travel”)
“Annual Figma subscription, design team licence” (not “Software”)
“Hotel, Manchester, annual team offsite 14–15 June” (not “Accommodation”)

A specific purpose that survives a tax audit is what distinguishes a claim that moves through approval in one pass from one that generates three emails and a delay.

The calculation

Line amount      = the amount you enter
Category total   = Σ line amounts in that category
Grand total      = Σ all line amounts
Receipts missing = count of lines with the receipt flag off

The output lists every expense with a [✓] or [ ] receipt marker. If any lines are missing receipts, the report flags them at the top so you fix them before submission rather than after rejection.

Handling foreign currencies

Record the original amount and currency the expense was incurred in. Most finance teams require:

The original amount (e.g., USD 85.00)
The home-currency equivalent at the day’s rate (e.g., GBP 67.50 at the rate on the date of the expense)
The source of the rate (bank statement, card statement, or published rate)

Add the converted figure and rate source in the business purpose field if your policy requires it. Never convert using a current exchange rate for a past expense — use the rate at the date of spend.

Tips for clean submissions

Consistent category names: if you write “Meals”, always write “Meals” — not “Food” or “Dining” on other lines. Inconsistent naming breaks the subtotals and makes manual sorting necessary.
Sequential report references: a claim reference like “EXP-2026-47” makes it uniquely traceable in finance systems and easy to reference in approval email threads.
Attach receipts in the same order as the report lines: numbered to match, so an approver can cross-reference in seconds.
Submit within your policy window: most companies specify 30 or 60 days from the expense date. Claims outside that window often require additional sign-off.