How I turn a messy deposit dump into a clean client deposit tracker
A Stripe CSV, three Venmo screenshots, a PayPal export with different column names, a bank deposit slip PDF, and a Slack note that says “can you track what clients paid?” are not a deposit system. They are how unapplied cash and “which invoice did this cover? questions hide until someone asks why AR and the bank do not match.
Here is the workflow I use when someone dumps messy client deposits on me and wants one clean deposit tracker sheet: every inbound payment listed, matched (or flagged), and easy to hand back — without me pretending to be their bookkeeper or CPA.
What “good enough” looks like
- Every row has a date received, client, amount, method, and source
- Applied-to invoice/job is filled when known; remaining unapplied is explicit, not implied
- Partial deposits and overpayments sit as numbers, not buried in notes only
- Duplicates from bank + processor of the same payment are flagged, not double-counted
- Open questions (who paid, which job, refund pending) are listed once so the handoff is honest
- Period totals (by client, by method, unapplied sum) are easy to skim
Intake checklist
- The dump (Stripe/PayPal/Venmo exports, bank deposit CSVs, payment screenshots, prior AR or invoice lists)
- Period that matters (month, quarter, custom range)
- Any invoice/job list they already use (or “match what you can, flag the rest”)
- Who the sheet is for (them, a bookkeeper, an AR handoff)
- What “done” means (clean deposit tracker, optional unapplied 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 deposit hygiene and labeling so their books stay clearer, not accounting, audit, or tax advice.
The pass order that saves time
- Gather sources — list every export, screenshot batch, and statement; note date range and who sent it.
- Normalize columns — map into: date received, client, amount, method, applied-to invoice/job, remaining unapplied, source, notes.
- Dedupe lightly — same date+amount+client from bank and processor → flag; do not invent merges without a rule.
- Match when clear — link to invoice/job only when the dump or their list makes it obvious; park unknowns as “ask.”
- Flag gaps — unknown payer, missing invoice ref, partial/overpay, possible refund → notes, not silent guesses.
- Hand back — the deposit tracker (+ short unapplied / ask list if useful); no bookkeeping filing, no “how to book this” language.
Columns that usually work
| Column | What goes here |
|---|---|
| Date received | When the payment hit the processor or bank |
| Client | Who paid (cleaned name if the dump is messy) |
| Amount | Deposit amount (note currency if mixed) |
| Method | Stripe, PayPal, Venmo, ACH, check, cash, other |
| Applied-to invoice/job | Invoice #, job name, or “unassigned” |
| Remaining unapplied | Amount not yet tied to an invoice/job (0 if fully applied) |
| Source | Which CSV, statement, or screenshot batch the line came from |
| Notes | Duplicate suspect, partial/overpay, “needs client confirm,” refund pending |
Soft CTA
If you want this done for you as a one-off: I turn a deposit dump into a client deposit tracker sheet in about 24 hours.
Product: https://brittanybonds.gumroad.com/l/depositsheet
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 deposits and open invoices are easier to reconcile.
Top comments (0)