Receipts die in photo albums. Use a form so US employees and UK staff submit a reimbursement ask with amount, currency (USD or GBP), date, and what the spend was—then finance can request the receipt image through the process you already trust.
Do not mix with the public contact form.
Those extra fields are required for this page.
Travel, meals, software, other—in copied HTML.
Match to receipts, then reimburse via payroll or bank file.
An expense report is a request to be paid back for a business cost already incurred: travel, client meals, software on a personal card. US teams talk about expense reports and IRS accountable plans. UK teams talk about expense claims, P11D risk, and HMRC subsistence rules. The form captures the claim header: who, how much, which currency, and why.
It is not Expensify. Line-item OCR and mileage IRS/HMRC rates stay in specialist tools if you have them.
An amount without currency is how $40 and £40 get mixed in one column.
Card numbers, CVV, and bank account details for reimbursement should not be collected here if payroll already has the account. Receipt files can use a URL field you add, or a follow-up email.
Brex, Navan, and Sage exist. Founders still get iMessage photos of till receipts.
Unlisted URL. Notifications to finance@.
Use it when policy, mileage, and cards must be enforced.
Month-end becomes archaeology.
UK SMEs still do this. Type the header here and staple later if policy demands originals.
Publish the form under the expense policy. State mileage rates and alcohol rules in copy; the form will not enforce them.
If you have US and UK entities, the currency select is the split. VAT versus sales-tax recovery is a finance decision after the row exists.
Add a file or URL field on the form, or ask finance to reply with an upload link. Do not put card PAN data in the description.
No.
Explain in policy copy. The amount field still needs a number.
Put miles and rate in the details textarea or add number fields later.