The pre-apply checklist I use so a deposit tracker still matches what hit the bank

Mid-period honesty is necessary. Pre-apply is different. The morning you decide "I will apply / reconcile / send this sheet today" is when a Stripe+bank double-count is still sitting in the totals, a refund still looking like cash, an Applied row with no invoice, a missing payer quietly deleted so the sheet looks complete, last month's deposit still hitchhiking into this period, and a raw Slack dump quietly hitchhiking into the share.

I am a freelancer admin helper. I turn messy deposit dumps into a clean client deposit tracker. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, or accounting advice. It is the checklist I run the week I am about to treat the sheet as cash truth (the final pass before anyone applies, reconciles, or sends it) so double-counts, refunded-as-cash rows, applied theater, missing-payer ghosts, and period blur do not become the bank story.

This is complementary to my earlier posts — not a rewrite. For the full messy deposit dump → clean client deposit tracker workflow, see How I turn a messy deposit dump into a clean client deposit tracker. For the mid-period honesty pass while dumps are still arriving, see The mid-period checklist I use so a deposit tracker stays honest. This third pass is the pre-apply check: mid-period honesty is not enough once someone else will treat the sheet as done.

What "honest enough to apply" looks like

• Cash filter shows real money that hit the bank — not theater, duplicates, or refunds dressed as deposits
• Applied vs pending vs refunded are still separated — nothing looks settled that is still unclear
• Every complete-looking row has a source (processor export, bank slip, PayPal CSV) — "I remember it" is not a source
• Each amount has a client + method from a named list or Needs-confirm — orphan labels do not ship as ready
• Missing invoice/job refs and unknown payers are visible and named — not silently deleted so the sheet looks tidy
• Period that matters is named on the sheet — older noise stays out or flagged
• Raw dump artifacts (CSV leftovers, unfinished notes, named complainers) are out of the share view
• You can answer "what cash landed this period, by client?" without reconstructing six exports

If the only apply plan you have is a sticky labeled "mark all applied?" pre-apply honesty has already slipped.

The pre-apply checklist (run it before anyone hits apply / reconcile / send)

Use this against the near-final client deposit tracker and the live artifacts (Stripe/PayPal/Venmo exports, bank deposit slips, invoice list, prior sheets) before anyone treats the sheet as this period's cash truth.

1. Kill double-count before the sheet leaves

• [ ] Same date+client+amount twice (processor + bank, or Venmo + bank) → still flagged double-count — not silently summed in cash totals
• [ ] Duplicate paste across CSV + Slack + Notion is one row or one labeled duplicate — not two deposits
• [ ] Soft "I think they paid twice" folklore is Needs-confirm or cut — vibe is not cash
• [ ] Currency mixes are labeled — do not silently sum USD + "local" into one client total
• [ ] Skim test: sorting by amount shows one deposit per payment, not a museum of doubles

2. Separate refunded / pending from applied before anyone trusts Cash

• [ ] Status is applied / pending / refunded / ask — not mood words or a single Applied checkbox for everything
• [ ] Refunded rows stay in a separate filter so they do not inflate cash totals
• [ ] Ask rows name what is blocking a call — not "waiting on stuff"
• [ ] Applied rows have a client + invoice/job ref a human could skim — "misc" is not a client
• [ ] Skim test: you can answer "what cash do we actually have this period?" without reconstructing six exports

3. Lock sources, clients, and the period

• [ ] Each amount has a source note (which export, which bank slip) — orphan amounts without a source are Needs-confirm
• [ ] Clients match a named list or are marked Needs-confirm — floating labels that look unique are folklore
• [ ] Period that matters is named (this month, this quarter, custom) — older noise stays out or flagged
• [ ] Exports from six weeks ago are labeled window unverified until the period is confirmed — pretty columns do not renew stale dumps
• [ ] Skim test: sorting by client shows a real cash list for this period, not a museum of March deposits from three years ago

4. Catch missing-payer ghosts and applied theater

• [ ] Rows marked applied that still need an invoice move back to ask or pending
• [ ] Fake greens (all Applied, no ask section) get a forced missing-ref pass before the sheet ships
• [ ] Applied theater ("matched" for everything) is broken into real invoice refs or Needs-confirm
• [ ] Threads titled "quick deposit note" without a usable amount are labeled artifact thin
• [ ] Skim test: missing-ref filter shows real gaps, not theater

5. Honesty tripwires (before you treat the sheet as apply-ready)

• [ ] You did not promote vibes to "all applied" because the Applied column looked empty of red
• [ ] Refunds buried in a wall of chat paste are lifted — not left under a cash headline
• [ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready" because the sheet looked sparse
• [ ] Raw dump artifacts (unfinished CSV paste, named complainers, draft notes) are out of the share view
• [ ] Skim test: a stranger can answer "what landed this period, by client?" from the sheet alone

Soft CTA

If you have a messy deposit dump and want a clean client deposit tracker in 24 hours: depositsheet on Gumroad ($12). Code ADMIN12 for $2 off. Full shop: brittanybonds.gumroad.com. Catalog mirror: brittany-bonds.github.io.

Not a CPA. Not financial, tax, legal, or accounting advice — just admin cleanup so the cash story matches what actually hit the bank.