To prepare a reimbursement claim with an AI assistant, paste the relevant card statement rows, mark which ones were for work, note which have receipts, and ask for a claim table with a one-line note per entry and a subtotal. Your company's policy, not the assistant, decides what is claimable. The assistant organises; finance decides.
Start from the statement and the policy
Read your company's expense policy first, because limits and rules differ. Then mask card and account numbers, and paste only date, merchant and amount. Add two columns by hand: Work, Personal or Unsure, and Receipt Yes or No.
Ask finance about the deadline for submitting claims and the format they prefer. A claim in the wrong format can easily be returned, and no prompt will fix a missed deadline.
A two-day client visit, in numbers
Here is a hypothetical claim.
| Day | Item | Amount (₹) | Receipt |
|---|---|---|---|
| 1 | Train to client city | 1,850 | Yes |
| 1 | Cab to hotel | 420 | No |
| 1 | Hotel | 4,200 | Yes |
| 1 | Dinner | 680 | Yes |
| 2 | Breakfast | 300 | No |
| 2 | Cab to client office | 350 | No |
| 2 | Lunch with client | 1,450 | Yes |
| 2 | Train back | 1,850 | Yes |
That is ₹11,100 in all. Entries with receipts come to ₹10,030 and entries without to ₹1,070, which together give ₹11,100.
The receipt-less ₹1,070 is about 9.6% of the claim, since 1,070 divided by 11,100 is 0.096. Knowing the size of that gap tells you how much attention it deserves.
Prompt 1: pull out the work rows
Prompt: "Here are my card statement rows for the 10th and 11th. Mark each as Work, Personal or Unsure based on the merchant and my trip notes: client visit in another city, one night in a hotel. Do not decide anything about company policy. For Unsure rows, ask me a question."
A souvenir or an airport shop purchase should land in Personal. Ask the assistant to leave personal rows out of the table completely.
Mixed bills are common, such as a hotel bill that includes a personal item. Ask the assistant to split the line only if the bill itself shows the parts. Never estimate a share and call it exact.
Prompt 2: build the claim table
Ask also for a one-paragraph cover note in plain language: where you went, why, and the number of days. Keep it factual. Finance teams read many claims, and a clear cover note gets yours understood quickly.
Prompt: "Make a claim table with Date, Description, Amount and a short note for each line, such as the purpose of the trip or which meeting it relates to. Add a subtotal for lines with a receipt and a separate subtotal for lines without one. Show the arithmetic."
What should I double-check before I submit?
- Dates and amounts on every line against the statement.
- That each amount is the amount you paid, not a rounded one.
- That no personal item is mixed in with a work line.
- That the totals on the claim match the sum of its lines.
- That the note on each line would make sense to someone who was not on the trip.
Where can the records live?
Keep claim documents together by trip. SpendixAI keeps receipts attached to their transactions and lets you pick the account, such as a card, before importing a statement, so the supporting papers stay with each line. CSV export gives you a table to adapt.
After you submit
Note the claim date and amount in your records, then watch for the matching credit so you know it arrived. If the amount paid differs from what you submitted, ask finance for the line-wise reason and update your table.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

