How I turn a messy refund dump into a clean credits and refunds tracker

A Stripe refund CSV, three PayPal dispute emails, a Venmo “I sent it back” screenshot, a Google Sheet with half-filled credit memos, and a Slack thread that says “can you track what we owe clients?” are not a credits system. They are how double-refunds and forgotten store credit hide until a client asks why their balance is wrong.

Here is the workflow I use when someone dumps messy refunds and credits on me and wants one clean tracker sheet: every outbound credit listed, tied to an original sale when possible, and easy to hand back — without me pretending to be their bookkeeper or CPA.

What “good enough” looks like

• Every row has a date, client, amount, type (refund / store credit / chargeback / adjustment), and source
• Linked original invoice or payment is filled when known; orphans are flagged, not invented
• Partial refunds and remaining credit balances sit as numbers, not buried in notes only
• Duplicates from processor + bank of the same refund are flagged, not double-counted
• Open questions (who, which sale, still pending) are listed once so the handoff is honest
• Period totals (by client, by type, open credit sum) are easy to skim

Intake checklist

1. The dump (Stripe/PayPal refund exports, chargeback notices, credit memo drafts, bank lines, screenshots)
2. Period that matters (month, quarter, custom range)
3. Any invoice or original-payment list they already use (or “match what you can, flag the rest”)
4. Who the sheet is for (them, a bookkeeper, a client-facing balance handoff)
5. What “done” means (clean credits & refunds tracker, optional open-credit list, optional by-client totals)

I am a freelancer admin / spreadsheet helper. I do not give tax or financial advice, and I am not a CPA — this is refund and credit hygiene so their books stay clearer, not accounting, audit, or tax advice.

The pass order that saves time

1. Gather sources — list every export, notice, and screenshot batch; note date range and who sent it.
2. Normalize columns — map into: date, client, amount, type, linked invoice/payment, remaining credit, status, source, notes.
3. Dedupe lightly — same date+amount+client from bank and processor → flag; do not invent merges without a rule.
4. Match when clear — link to original invoice/payment only when the dump or their list makes it obvious; park unknowns as “ask.”
5. Flag gaps — unknown client, missing sale ref, partial/pending, possible double-refund → notes, not silent guesses.
6. Hand back — the credits & refunds tracker (+ short open-credit / ask list if useful); no bookkeeping filing, no “how to book this” language.

Columns that usually work

Column	What goes here
Date	When the refund/credit posted or was issued
Client	Who received the credit (cleaned name if the dump is messy)
Amount	Credit or refund amount (note currency if mixed)
Type	Full refund, partial refund, store credit, chargeback, courtesy adjustment, other
Linked invoice/payment	Original invoice #, payment ID, or “unassigned”
Remaining credit	Open balance still owed to the client (0 if fully paid out / used)
Status	Issued, pending, applied, disputed, canceled
Source	Which CSV, notice, or screenshot batch the line came from
Notes	Duplicate suspect, partial, “needs client confirm,” chargeback window

Soft CTA

If you want this done for you as a one-off: I turn a refund dump into a credits & refunds tracker sheet in about 24 hours.

Product: https://brittanybonds.gumroad.com/l/creditssheet

Shop: https://brittanybonds.gumroad.com/

Catalog mirror: https://brittany-bonds.github.io/

Code ADMIN12 for $2 off.

No fake CPA claims — spreadsheet cleanup so your refunds and open credits are easier to reconcile.