The month-end email nobody wants
Near month end, someone in finance sends a list around: twenty card transactions with no receipt, each with a date, an amount and a merchant name that looks nothing like the shop. People scroll through photos on their phones, dig through inboxes, and some just reply that they cannot find it.
Unreceipted spending then sits in a holding account. VAT cannot be reclaimed on it. The accountant asks about it at year end. And the same people are on the same list the next month.
The real reason receipts disappear
It is tempting to see this as a discipline problem. Mostly it is a timing problem. The moment someone is holding the receipt is the moment they pay. The moment they are asked for it is weeks later, stripped of context. By then the paper receipt went through the wash and the emailed one is buried.
Expense apps help if everybody uses them consistently. In practice some cardholders do and some do not, and the app has no way to nudge the ones who forget, at the right moment, in the channel they actually read.
What the gap costs
- VAT that could have been reclaimed is not, because there is no valid receipt.
- Finance staff spend the end of each month chasing instead of closing.
- Spending is coded to a vague 'sundry' account, so budgets by department are unreliable.
- At audit or year end, the accountant has questions that nobody can answer.
- Genuine misuse of a card is harder to spot when unexplained spending is normal.
How we build the receipt loop
- Watch card transactions as they clear, from the bank feed in Xero or QuickBooks or from the card provider's API.
- Identify the cardholder and send a short request the same day, in the channel they use: email, Microsoft Teams, Slack or WhatsApp through Twilio. The message names the merchant, amount and date.
- Accept a reply with a photo, a forwarded email or a PDF. We read the receipt with a document model, extracting merchant, date, total and VAT.
- Match the receipt to the transaction on amount, date and merchant, allowing for currency conversion and tips.
- Ask one short question where needed, such as which project or client the spend relates to, with the answer offered as buttons rather than free text.
- Attach the receipt to the transaction in the ledger, apply the coding, and gently remind anyone who has not replied after a set interval.
| Case | What the system does |
|---|---|
| Receipt matches cleanly | Attached and coded, no human step |
| Amount differs slightly | Checks for tip or currency, flags if it cannot explain the gap |
| No receipt exists | Cardholder confirms, and finance decides on treatment |
| Personal spend on company card | Routed to finance for recovery, never auto-posted |
What month end looks like after
Receipts arrive while people still have them in their hand. The month-end chase list becomes a handful of genuine exceptions rather than a group email. VAT on card spend is supported, and spend is coded to the right department because the question was asked when the answer was obvious.
Cardholders tend to prefer it too. A single message on the day, answered with a photo, is less irritating than a list of twenty mysteries at the end of the month. Finance gets to spend the close on reviewing numbers rather than on detective work, and the budget holders see their department's spending properly split rather than lumped under sundries.
It also makes unusual spending easier to notice. When nearly every transaction is receipted and explained within a day or two, the few that are not stand out, and a manager can ask about them while the details are still fresh.
Signs you need this
- A list of missing receipts goes round every month.
- Your holding or suspense account for card spend is never empty.
- Some cardholders use the expense app and some ignore it.
- The accountant asks about unreceipted spending at year end.