Expense receipt reimbursement check
Check one employee expense claim and its receipt against a small company's expense policy: approve, ask for missing receipt details, needs manager approval, personal or not reimbursable, possible duplicate, or unreadable, so founders and finance stop rechecking every receipt by hand.
F@fLimits to keep in mind
This only labels the claim. It does not pay, reject or change anything in your accounting or expense tool.
Tax rules for receipts differ by country; check with your accountant what a valid receipt must show.
Receipt text read from photos can contain errors; check the image before declining a claim.
Problem
Small companies reimburse team expenses from photos of receipts sent in chat or email. Founders and part-time bookkeepers recheck every claim by hand, miss receipts without a date or tax details, approve personal items or the same receipt twice, and slow down honest claims while they chase the few that need a question or a manager's sign-off.
Goal
Label each claim so clean ones are paid quickly, claims with missing receipt details go back to the employee with a clear ask, over-limit or unusual items go to a manager, personal or non-reimbursable items are declined politely, possible duplicates are checked, and unreadable receipts are resubmitted, with a human deciding anything uncertain.
Input / state
One expense claim with the text read from its receipt, the employee's note, and the relevant parts of the company expense policy.
- receipt_text
- Text read from the receipt or invoice (merchant, date, items, totals, tax, payment method), or a note that the image is blurry or cut off.
- claim_details
- What the employee entered: amount, currency, date, category, business purpose, project or client, and attendees for meals.
- policy_excerpt
- The company rules that apply, such as spending limits per category, what needs pre-approval, what is never reimbursed, and required receipt details.
- recent_claims
- Optional: this employee's recent claims (date, merchant, amount) to spot repeats.
Decision question
reimbursement_decisionWhat should happen with this expense claim? Use approve when the receipt matches the claim, has the required details, has a clear business purpose and fits the policy. Use missing_details when the receipt or claim lacks something the policy requires but the expense looks fine. Use needs_manager_approval when the expense is allowed in principle but is over a limit, unusual, or needs missing pre-approval. Use not_reimbursable when the item is personal or banned by the policy. Use possible_duplicate when it seems to repeat an earlier claim. Use unreadable when the receipt is not legible.
Options
approveReceipt and claim match on amount, date and merchant, required details are present, the business purpose is clear, and the expense is within policy limits.missing_detailsThe expense looks legitimate but something required is missing or does not match, such as an itemized receipt, date, tax details, business purpose, attendees for a meal, or the claimed amount differs from the receipt.needs_manager_approvalThe expense is allowed in principle but goes over a policy limit, is an unusual or large purchase, or needs pre-approval (for example travel, equipment, software) that the claim does not show.not_reimbursableThe item is personal or excluded by the policy, such as alcohol where banned, fines, personal shopping, family members' costs, or upgrades the policy does not cover.possible_duplicateThe same receipt or the same merchant, date and amount already appears in recent claims, or the claim looks split to stay under a limit.unreadableThe receipt is too blurry, cut off, faded or in a form where the merchant, date or total cannot be read.
Allowed outcomes
Decided in your code from the answer and its confidence. Thresholds are yours to set and test.
- Finance person decidesConfidence is below your threshold, the policy does not cover the item, or the input is not an expense claim.
- Approve for paymentChoice is approve and confidence meets your threshold.
- Ask employee for missing detailsChoice is missing_details and confidence meets your threshold.
- Send to manager for approvalChoice is needs_manager_approval and confidence meets your threshold.
- Decline politely with the policy reasonChoice is not_reimbursable and confidence meets your threshold.
- Check against earlier claimsChoice is possible_duplicate and confidence meets your threshold.
- Ask for a clearer receiptChoice is unreadable and confidence meets your threshold.
Example scenarios
Predefined demonstrations. No model is called; the outcome shown is an illustrative judgment.
Example state
{
"receipt_text": "Trattoria Roma, 2026-11-12, 2x pasta, 2x sparkling water, subtotal 42.00, VAT 8.40, total 50.40 EUR, Visa ****4417",
"claim_details": "50.40 EUR, 2026-11-12, Meals, lunch with Acme Ltd about the Q1 renewal, attendees: me and Jane Doe (Acme)",
"recent_claims": "2026-11-03 Train ticket 34.00 EUR",
"policy_excerpt": "Client meals up to 60 EUR per person with attendees listed. Itemized receipt with VAT required. No alcohol."
}Outcome
IllustrativeChoice is approve and confidence meets your threshold.
Why
Itemized receipt matches the claim, attendees and purpose are given, and it is under the per-person limit.
Using it well
- Judge against policy_excerpt only; if the policy says nothing about an item, do not invent a rule, use needs_review.
- Compare the receipt total, currency and date with the claim; a small difference from tips or currency conversion explained in the note is fine, an unexplained difference is missing_details.
- A card slip that shows only a total is missing_details when the policy requires an itemized receipt.
- If one claim mixes allowed and excluded items (for example dinner plus alcohol where alcohol is banned), choose missing_details and ask for a corrected amount instead of declining the whole claim.
- Two or more claims at the same merchant on the same day that each sit just under a limit suggest splitting: use possible_duplicate.
- Over-limit but clearly business-related spending is needs_manager_approval, not not_reimbursable.
- If the input is not an expense claim (for example a supplier invoice to pay or a sales receipt), use needs_review.
- Never accuse the employee of fraud; describe what does not match and what is needed.
Request definition
POST https://api.typesafe.ai/v1/systemone{
"model": "jev-latest",
"state": {
"receipt_text": "<receipt_text>",
"claim_details": "<claim_details>",
"policy_excerpt": "<policy_excerpt>",
"recent_claims": "<recent_claims>"
},
"questions": {
"reimbursement_decision": {
"type": "choice",
"instructions": "What should happen with this expense claim? Use approve when the receipt matches the claim, has the required details, has a clear business purpose and fits the policy. Use missing_details when the receipt or claim lacks something the policy requires but the expense looks fine. Use needs_manager_approval when the expense is allowed in principle but is over a limit, unusual, or needs missing pre-approval. Use not_reimbursable when the item is personal or banned by the policy. Use possible_duplicate when it seems to repeat an earlier claim. Use unreadable when the receipt is not legible.",
"criteria": {
"approve": "Receipt and claim match on amount, date and merchant, required details are present, the business purpose is clear, and the expense is within policy limits.",
"missing_details": "The expense looks legitimate but something required is missing or does not match, such as an itemized receipt, date, tax details, business purpose, attendees for a meal, or the claimed amount differs from the receipt.",
"needs_manager_approval": "The expense is allowed in principle but goes over a policy limit, is an unusual or large purchase, or needs pre-approval (for example travel, equipment, software) that the claim does not show.",
"not_reimbursable": "The item is personal or excluded by the policy, such as alcohol where banned, fines, personal shopping, family members' costs, or upgrades the policy does not cover.",
"possible_duplicate": "The same receipt or the same merchant, date and amount already appears in recent claims, or the claim looks split to stay under a limit.",
"unreadable": "The receipt is too blurry, cut off, faded or in a form where the merchant, date or total cannot be read."
}
}
}
}Request shape from the System One API reference; a Kev server accepts the same body. Replace the placeholder state with your data. Requests need your own API key or server.
Version History
Initial version