A refunds and credits tracker that finds the money that came back
Nearly everyone tracks money going out. The negative lines on the statement — returns, cancellations, chargebacks, billing corrections — are the ones that quietly never get reconciled.
Quick answer: What does a refunds and credits tracker do?
A refunds and credits tracker keeps the money that came back to you from being ignored, so your expense totals are net rather than gross. It has to do four things: separate credits from expenses instead of dumping them into one column, match a credit back to the purchase it reverses, keep internal noise like autopay and statement payments out of the way, and leave your totals net. ExpenseBot is an expense tracking app that pulls refunds and credits from an uploaded credit card statement into a separate Credits & Refunds queue — they are never added as new expenses — and each one you add becomes a negative expense row on your Expenses sheet, never Income.
✓ 60-day free trial • ✓ No credit card • ✓ Your data stays in your Google Drive
Refunds are the line everyone skips — and they make your books wrong in one direction
You expensed a $312 flight in March. In April you cancelled it and the airline put the money back on your card. Your expense sheet still says you spent $312. Nothing in an ordinary expense tracker will tell you otherwise, because nothing was wrong at the moment you recorded it.
That is the shape of the problem: the error arrives after the entry was correct. And it always biases the same way — expenses overstated, never understated. It is an accuracy problem, and the point of fixing it is that your books say what actually happened.
Credits arrive in four shapes. It is worth recognising which one you have, because they are not interchangeable:
| Type | What it is | Where ExpenseBot puts it | Changes your expense total? |
|---|---|---|---|
| Merchant refund / return | The merchant gave money back — a return, a cancellation, a price adjustment. | Credits & Refunds queue, for you to review. | Yes, once you add it — as a negative expense row. |
| Chargeback | A disputed charge reversed by the card issuer. | Credits & Refunds queue, same as a refund. | Yes, once you add it. |
| Statement credit / billing correction | An adjustment applied by the issuer or merchant rather than a return. | Credits & Refunds queue. | Yes, once you add it. |
| Card payment / autopay | You paying your own card bill. Money moving between your own accounts. | Nowhere — filtered out automatically and never shown. | No. It is neither an expense nor a refund. |
That last row is the one tools most often get wrong. A card payment looks like a large credit on the statement, and treating it as one produces a spectacular, obviously-wrong number that then has to be found and undone by hand.
What a refunds and credits tracker actually has to do
Four jobs. This is a checklist you can hold any tool to, including this one — if a tool does the first three and fails the fourth, your totals are still wrong.
- Separate credits from expenses rather than dumping both into one column where a negative number is easy to miss and easy to mis-sign.
- Match a credit back to the purchase it reverses, so you can see which expense was undone rather than just that some money returned.
- Keep internal noise out of the way — paying your own card is not a refund and should never reach your review queue.
- Leave the totals net, not gross, so the number you report is what you actually spent after everything that came back.
How ExpenseBot separates credits from expenses
When you upload a credit card statement, refunds and credits are pulled into a separate Credits & Refunds queue. They are never added as new expenses — an unreviewed credit cannot silently move your numbers in either direction.
You reach it from your dashboard: open Review expenses, choose Match card activity, and when a card check has found unresolved credits a Credits & Refunds button appears with the count on it. Each credit gets its own decision — Add to Spreadsheet or Ignore.
Internal card payments — autopay and statement payments — are filtered out automatically and never shown, so the queue contains decisions worth making rather than a wall of transfers between your own accounts.
Matching a credit to the purchase it reverses
When ExpenseBot can verify that the same refund is already represented by an exact offset row, it keeps that row's receipt identity with the decision instead of adding a second credit — so you get one coherent record of the reversal rather than two competing ones.
What it deliberately will not do
A similar merchant name, by itself, is not treated as proof that two rows are related. That refusal is a feature rather than a gap. A credit sitting unmatched in a queue is visible and takes thirty seconds to resolve; a wrong automatic match is invisible, and you only find it when a total disagrees with reality months later.
To connect them yourself, expand the credit in Review expenses and choose Link to purchase. This is worth stating plainly because readers reasonably assume linking edits numbers: it does not. Linking adds the explanation and a supporting report reference, and both amounts stay exactly as they were — including for partial credits, where the purchase and the smaller credit each keep their own value.
The same charge on two statements
Statements overlap at the month boundary. A charge made on December 31 can post in both the December and the January statement, and importing both would count it twice. ExpenseBot matches on merchant name + amount + date within ±1 day and suppresses the repeat.
That is one half of a larger topic. Receipt-level duplicates — the same receipt submitted twice, and the more costly fear of resubmitting a receipt that failed — are covered on the duplicate expense detection page.
Where the durable record lives
The Credits & Refunds history is retained for a limited period. Your main Expenses sheet is the durable record — the queue is a working surface, the sheet is what you keep.
Added credits are negative expense rows, and are never treated as Income.
If you work with an accountant or bookkeeper, that is the sentence they need — it is the difference between a refund that correctly reduces an expense category and a refund that wrongly inflates your revenue. Reports then calculate net spend from those signed rows:
| Row | Description | Amount |
|---|---|---|
| Expense | Airline ticket, March | +312.00 |
| Credit | Airline refund, April | −312.00 |
| Report total | Net spend on that ticket | 0.00 |
The condition that surprises people: a full or partial credit reduces the matching category, tag and report total when both the purchase and the credit are in the report's scope. In the example above, a March-only report shows +312 and an April-only report shows −312. Neither is broken — each is answering a question about its own period. You see the net only in a report whose range covers both.
Refunding a customer is the other direction
Everything above is about money a merchant put back on your card, which reduces an expense. Money you gave back to a client is the opposite: an income reversal, not a card credit, and it is recorded differently. If that is what you are looking for, our answer on refunding a customer payment covers it — this page deliberately does not, because conflating the two is how a refund ends up on the wrong side of the books.
Frequently Asked Questions
Does ExpenseBot count a refund as income?
No. A credit you add is written as a negative expense row on your Expenses sheet, never as Income. That keeps your expense total net of the refund instead of inflating your income — which is the distinction an accountant will look for first.
Why didn't my refund reduce my report total?
A credit reduces the matching category, tag and report total only when both the original purchase and the credit fall inside that report's scope. If the purchase was in one report period and the refund landed in the next, each report shows its own side, and neither is wrong — they are answering different questions.
The same charge shows up on two of my statements. Will it be counted twice?
No. ExpenseBot matches merchant name, amount and date within ±1 day across statements and suppresses the duplicate, so a December 31 charge that posts in both the December and January statement is only counted once.
Are my credit card autopay payments treated as refunds?
No. Internal card payments — autopay and statement payments — are filtered out automatically and never appear in Credits & Refunds. Paying your own card moves money between your own accounts; it is neither an expense nor a refund, and showing it would just add noise to the queue.
What's the difference between a card credit and refunding a customer?
A card credit is money a merchant put back on your card, and it reduces an expense. Refunding a customer is money you sent back to a client, which is an income reversal. They move in opposite directions and are recorded differently, so it is worth being sure which one you have before recording it.
Does linking a credit to a purchase change the amounts?
No. Link to purchase records the explanation and a supporting report reference. Both the purchase amount and the credit amount stay exactly as they were, including for partial credits — linking explains the relationship, it does not rewrite either row.
How does ExpenseBot decide a credit belongs to a particular purchase?
It links a credit to a purchase when it can verify that an exact offset row already represents that refund, and in that case it keeps that row's receipt identity with the decision rather than adding a second credit. It will not treat a similar merchant name on its own as proof that two rows are related — that refusal is deliberate, because a wrong automatic match is harder to notice and undo than an unmatched credit sitting in the queue.
Start catching your credits
Connect Gmail so receipts land automatically, then upload a card statement — the Credits & Refunds queue populates from the statement import, and you decide what each one is.
✓ No credit card • ✓ Autopay filtered out automatically • ✓ Your data stays in your Google Drive