Mid-schedule honesty is necessary. Week-of due is different. The morning you decide "this installment is due and I will invoice / chase / treat next-due as cash truth" is when mid-month and on-delivery are still sitting where a calendar date should be, the amounts still do not add to the contract, a deposit already paid is still double-counting as installment #1, paid / due / waived / disputed is still blank, and a Slack "I think we're fine" is still rewriting the next-due line.
I am a freelancer admin helper. I turn messy payment-schedule dumps into a clean installment tracker. I am not a CPA, bookkeeper, lawyer, or tax advisor — and this is not financial, tax, legal, collections, or accounting advice. It is the checklist I run before anyone treats next-due as this week's cash truth (the final pass before an invoice, remittance ask, or "are we current?" conversation) so date fog, amount drift, deposit overlap, status silence, and Slack folklore do not become the due story.
This is complementary to my earlier posts — not a rewrite. For the full messy payment-schedule dump → clean installment tracker workflow, see How I turn a messy payment-schedule dump into a clean installment tracker. For the mid-schedule honesty pass while dumps are still arriving, see The mid-schedule checklist I use so an installment tracker stays honest. This third pass is the week-of due check: mid-schedule honesty is not enough once someone else will treat next-due as done.
What "honest enough for week-of due" looks like
- Every due-soon row has a real calendar date — not mid-month / on-delivery / net-30 still pretending to be a date
- Installment amounts still add to the contract (or the gap is labeled ask) — not "close enough" before you invoice
- Deposits already paid are linked or marked — not double-counted as installment #1 this week
- Status is paid / due / waived / disputed / ask — not blank vibes
- Payer / client names are normalized — not three ghost payers for one job
- You can answer "what is due this week, by whom, for how much?" without reconstructing Slack and a PDF
If the only due plan you have is a calendar ping titled "balance??," week-of due honesty has already slipped.
The week-of due checklist (run it before anyone invoices or chases)
Use this against the near-final installment tracker and the live artifacts (PDF plan, prior invoices, deposit receipts, Slack "half then somehow," calendar reminders) before anyone treats next-due as this week's cash truth.
1. Kill date fog before the chase starts
- [ ] Mid-month / on-delivery / net-30-after-invoice rows due this week are mapped to one calendar date or labeled ask — not mixed as if they were the same kind of due
- [ ] One as-of / "due through" note sits at the top — not three conflicting "this Friday" notes
- [ ] Rows still showing last month's due when the plan moved are labeled date drift until recalced
- [ ] Skim test: you can answer "what is due this week?" without opening Slack
2. Lock amounts, deposits, and status before anyone invoices
- [ ] Installment amounts for this job still add to the contract (or the gap is ask) — not silently rounded because the invoice looked nicer
- [ ] Deposits already paid are linked or marked paid — not sitting as installment #1 again
- [ ] Status is paid / due / waived / disputed / ask — blank rows stay Needs-confirm, not silently "due"
- [ ] Skim test: you can answer "what is still owed vs already paid?" without reconstructing three PDFs
3. Normalize payers, sources, and folklore
- [ ] Each complete-looking row has a source (PDF plan, invoice, Slack confirmation) — orphan due amounts without a source are Needs-confirm
- [ ] Payer / client name drift is normalized with aliases in notes — not three ghost payers
- [ ] Slack "I think we're fine" / "they said next week" folklore is in notes as folklore — not rewritten as the next-due date
- [ ] Skim test: sorting by due date shows one clear line per installment, not a museum of duplicates
4. Honesty tripwires (before you treat next-due as chase-ready)
- [ ] You did not promote vibes to "all current" because the sheet looked sparse of red
- [ ] Incomplete sections stay Needs-confirm — not silently promoted to "ready to invoice" because the week felt busy
- [ ] Raw dump artifacts (unfinished PDF paste, named complainers, draft notes) are out of the chase view
- [ ] Skim test: a stranger can answer "what is due this week, by whom, for how much?" from the sheet alone
Soft CTA
If you have a messy payment-schedule dump and want a clean installment tracker in 24 hours: installmentsheet 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, collections, or accounting advice — just admin cleanup so the due story matches what is owed.
Top comments (0)