Reimbursement forms: the fields that get a claim approved first time

Reimbursement forms exist to move a claim from a person to the accounts in one pass. When they fail, it is almost never because the expense was wrong — it is because the form did not collect what the approver or the bookkeeper needed, so the claim goes back, waits, and gets resubmitted a week later with the same amount and one extra line.

The fix is designing the form around what happens after it is submitted, not around what feels tidy on screen.

The nine fields

• Name and — if you pay by transfer — the payment details you actually use, collected once rather than per claim where possible.
• Date of the expense, separate from the date of submission.
• Amount and currency, with the currency as a choice list rather than free text.
• Category, as a choice list matching your accounting categories exactly.
• Business purpose, one line, required. This is the field that satisfies an auditor and the one people skip if it is optional.
• Related client, project or cost centre, from a list where you have one.
• Payment method used — personal card, cash, company card — because company-card spend usually must not be reimbursed again.
• Receipt upload, required, with a note about legibility.
• A declaration that the expense was incurred for business purposes and has not been claimed before.

Make the category a fixed list, never free text. "Travel", "travel expenses", "Taxi" and "transport" in the same column mean someone re-categorises every claim by hand at month end — the single most common source of avoidable bookkeeping work.

Design decisions that reduce rejections

1. Split multi-item claims into one row per expense rather than one blob per trip, so each line can be categorised and approved.
2. Validate the amount format and require the receipt file before submission — a missing attachment is the top reason claims bounce.
3. Use branching: mileage claims need distance and route, not a receipt; foreign spend needs the rate or card amount.
4. Show the policy limits next to the fields they apply to, at the moment of entry, instead of in a document nobody opens.
5. Confirm on submission with a copy of what was submitted, so the claimant has a record without chasing.
6. Route the response somewhere with an owner: an inbox with a name attached, not a shared address.

Ettex Forms covers that shape directly: a drag-and-drop builder from question blocks, logic and branching so mileage and foreign-currency claims ask their own questions, choice, scale, date and file-upload question types for the receipt, multi-step sections with progress, validation for required fields and formats, custom themes, and publishing by link or embedded on an internal page. Submissions land in a searchable, timestamped response inbox with a live summary, the team can review and process them together, and everything exports to CSV or XLS — which is how the approved claims reach the books without retyping.

After the form

A reimbursement form is only half a process. Decide who approves at what amount, on what rhythm they approve, and when payments run — and publish all three. A perfectly designed form attached to an unpredictable payment cycle still produces the same complaint.

Retention matters too: the claim and its receipt are financial records, keep them for the period your jurisdiction requires, and delete the personal payment details you no longer need rather than carrying them indefinitely.

Good reimbursement forms are designed backwards from the books. Fixed categories, a required purpose, a required receipt — and a payment cycle that makes filling the form worth it.