Card transactions without receipts pile up because nobody enjoys chasing colleagues. The agent finds every transaction with no receipt, reminds the cardholder on a fixed schedule, matches what they upload, and tells their manager when reminders run out. Consequences, such as suspending a card or treating spend as personal, stay with finance and the manager.
What is the process, and who owns it?
Company card spend arrives from the card feed before anyone has submitted evidence for it. Each transaction needs a receipt to support the expense, to recover sales tax where your rules allow, and to satisfy auditors. Missing receipts are usually forgetfulness, sometimes lost paper, occasionally spend that should not have happened.
The expenses or accounts payable lead owns the process and the reminder schedule. Line managers own their team's compliance. Finance and HR own consequences. The case for agents applying policy evenly while people judge exceptions is made in expense agents enforce policy consistently; people handle the exceptions. The wider finance position is in AI agents for finance: books you can audit.
How does the agent chase, step by step?
- Agent, depth 1: compares the card feed with the expense system. Every card transaction older than the grace period with no receipt attached becomes a gap. Evidence: the gap list with transaction references.
- Agent, depth 1: checks for reasons not to chase. Cardholder on leave, transaction under a no-receipt threshold, a refund that offsets the charge. Evidence: the reason recorded for each skipped item.
- Agent, depth 3: sends the first reminder to the cardholder: transaction, date, merchant, amount, and a one-click upload link. One message listing all their gaps, not one per transaction. Evidence: message sent, template version.
- Agent, depth 1: matches uploads. Amount, date and merchant on the receipt against the card line. A receipt is declared evidence from the employee; the card line is sealed. Evidence: the match result per receipt.
- Agent, depth 3: attaches matched receipts and closes the gap. Mismatches, such as a different amount, go back to the cardholder with the difference stated. Evidence: attachment and verdict.
- Agent, depth 3: sends follow-up reminders on the schedule the expenses lead set. Evidence: each reminder.
- Agent, depth 3: notifies the line manager when the schedule is exhausted, with the list of open gaps. Evidence: the notification.
- Person, expenses lead and manager: decide consequences. Accepting a lost-receipt declaration above the policy limit, treating spend as personal, suspending the card. Evidence: the decision and its reason.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Find gaps | Compares card feed and expense system | 1 | Nothing |
| Skip rules | Applies leave and threshold rules | 1 | Setting the rules |
| Remind | Sends grouped reminders | 3 | Changing the schedule |
| Match | Checks uploads against card lines | 1 | Nothing |
| Attach | Attaches matched receipts | 3 | Nothing |
| Escalate | Notifies the line manager | 3 | Nothing |
| Consequences | Prepares the case | 2 | Suspension, personal spend, declarations |
Why are reminders depth 3 when consequences are not?
A reminder costs the recipient a moment and can be ignored, corrected or apologised for. It is routine, internal and reversible. The schedule and wording are approved in advance, so the agent is applying a decision already taken.
Consequences affect a person's pay, their card and their standing with their manager. A suspended card can leave someone stranded on a business trip. Treating spend as personal may mean a deduction from salary, which raises employment questions. These need someone who can weigh the circumstances: the employee who lost a receipt on a long trip is not the same as the one with a pattern of unexplained spend.
What about lost receipts?
Most policies allow a lost-receipt declaration: the employee states what the expense was and why the receipt is missing. The agent can accept a declaration below a limit the expenses lead sets, at depth 3, and record it as declared evidence. Above the limit, or for a cardholder with several declarations in a period, it holds the declaration for the manager. Repeated declarations are a pattern worth a person's attention.
Which controls matter, and what evidence do they leave?
The card line is the authority. A receipt that does not match the card line does not close the gap. Evidence: match result on each attachment.
Grouped, scheduled reminders. Evidence: reminder count and timing per cardholder, against the schedule.
Skip rules applied and recorded. Evidence: the reason for every skipped gap.
Declaration limits. Evidence: declarations accepted at depth 3, with amounts, and those held.
No consequences by the agent. Evidence: refused verdicts on any card suspension or personal-spend posting.
What should you measure?
- Open gaps by age, overall and by team.
- Time from transaction to receipt attached.
- Receipts uploaded after the first reminder, against those that need follow-ups.
- Lost-receipt declarations by cardholder.
- Complaints from employees about reminders, which usually point to the schedule or wrong gaps.
How does this compare with chasing customers?
The mechanics resemble chasing overdue customer invoices: a list, a schedule, escalation. The relationship is different. Employees are colleagues, the amounts are small, and the aim is evidence, not money. Tone should be plain and brief, and escalation goes to a manager, not a collections process. The parallel question for customers is covered in can an AI agent chase overdue customer invoices.
Where does it usually go wrong?
One message per transaction. Frequent travellers receive dozens of reminders a week and start ignoring all of them. Group them.
Out-of-office replies are ignored. The agent keeps chasing someone on long leave. Read the leave calendar, or at least react to automatic replies.
Matches are too loose. A receipt for a similar amount at the same merchant on a different day is attached to the wrong transaction. Require date and amount to match within tight bounds.
Managers are copied too early. Copying the manager on the first reminder feels punitive and sours the process. Escalate only when the schedule runs out.
Questions people ask
Can the agent read receipts from photos?
Yes, it can extract merchant, date and amount from an image. Treat the extraction as declared evidence and keep the image attached for audit.
Should the agent chase receipts for small amounts?
Only above the threshold your policy sets. Chasing tiny amounts costs more than it recovers.
What if the cardholder has left the company?
The agent stops reminding them and sends the open gaps to the expenses lead, who decides how to close them.