The before-you-share checklist I use so a payables sheet still matches what is open

A payables sheet can look batch-ready while its story is already wrong: a phantom bill is added for a tidy open total; the same vendor+invoice from email + portal + PDF is counted three times; a silent partial is still left at the full Open amount; a paid or credited ghost still greens the due-in-7-days slice; a disputed or “on hold” row is buried so it looks ready to pay; a guessed “about next Friday somehow” is locked as Net-30 fact; a superseded INV_FINAL_v2 still travels next to v3; or open asks are scattered as footnotes nobody will find at handoff.

Before-you-share is different from a mid-open cleanup. This is the pass I run when the sheet is about to leave my hands and someone else may treat every row as what is still owed.

I am Brittany Bonds, a freelancer admin helper. I turn a pile of vendor bills into a clean accounts-payable sheet. I am not a CPA, bookkeeper, lawyer, or tax advisor, and this is not financial, tax, legal, or accounting advice. It is an administrative proof-checking routine, not a recommendation about what anyone should pay, dispute, credit, or schedule.

This complements How I turn a pile of vendor bills into an accounts-payable sheet and The mid-open checklist I use so a payables sheet stays honest. Those live posts cover the first-pass workflow and the mid-open honesty cleanup. This third pass is the pre-share evidence check — not a rewrite of either.

What “honest enough to share” looks like

• Every open row and open remainder maps to a PDF/email/portal crumb, bank memo, credit note, or a labeled ask — nothing invented for a tidy payment-batch preview.
• Soft guesses (“about next Friday somehow,” “usual Net-30”) stay soft; hard due dates and open amounts only appear when a source supports them.
• Same-bill duplicates across email + portal + PDF stay merged or labeled duplicate — they are not three open bills.
• Silent partials name original amount vs remaining open — they are not left at the full Open total.
• Paid or credited-to-zero ghosts are flipped off Open — they do not still green the due-in-7-days slice.
• Disputed / on-hold rows stay out of ready-to-pay filters until status says otherwise.
• Superseded or zombie bill versions are labeled superseded / stale or removed from the share view.
• Open asks are listed once — not scattered as footnotes nobody will find at handoff.
• An emoji reaction or vague “pay when you can” is not treated as a locked batch unless the sheet states what was confirmed.

If the only share instruction is “send the clean payables sheet,” pre-share honesty has already slipped.

The before-you-send checklist

Use this against the near-final sheet and live evidence: the original vendor-bill dump (PDFs, email forwards, portal screenshots, stale AP exports, Slack “pay when you can” pings), prior open-AP sheet if any, and the mid-open scratch trail. The goal is not to make every cell complete. The goal is to make uncertainty visible before the sheet becomes someone else’s payment-batch source of truth.

1. Freeze open rows to what is still owed

• [ ] Every open row maps to a source crumb, screenshot, export, or a labeled ask — no orphan row gets a confident “this is the batch” look.
• [ ] Phantom bills, template filler, and “bonus” vendors that never appeared in the dump stay out or labeled proposed / ask — polish is not permission.
• [ ] Duplicate bills under two (or three) phrasings — email + portal + PDF of the same vendor+invoice — are merged or marked duplicate — one bill is not three open slots because it looked tidy three times.
• [ ] Vendor naming stays close to the source; a polished synonym may not be the same entity or the same invoice.
• [ ] Reimbursements (money you are owed) stay out of vendor AP — mixing them in is a rewrite, not a cleanup.
• [ ] Skim test: a reader can point from each open row back to a source, or see that it still needs confirmation.

An invented open row is not automatically useless. It is a proposal. The misleading part is leaving it dressed as what is already owed for this pay-batch window.

2. Keep amount, open remainder, and due-date strength-honest

• [ ] Soft notes (“about next Friday somehow,” “usual Net-30,” “roughly the same as last time”) stay soft — they are not upgraded to hard due dates or open amounts for neatness.
• [ ] Hard amounts keep an invoice line, portal balance, credit note, date, or confirmer when available — silence is not consent.
• [ ] Partial rows name original amount and remaining open — “partial” alone is not a balance, and silent partials must not stay at the full Open total.
• [ ] Missing due date or amount stays ask — a blank cell that looks batch-ready is worse than a visible unknown.
• [ ] Currency and tax/shipping inclusion stay labeled; converting vibes into a tidy open total without a note is a rewrite, not a cleanup.
• [ ] Totals never invent missing dollars or dates — blanks stay ask.
• [ ] Skim test: a reader can tell which open lines are locked, which are soft, and which still need confirmation.

This is a consistency check, not cash strategy or accounting advice. I am recording what the dump disclosed, not deciding what anyone must pay or when.

3. Separate ready-to-pay from paid ghosts, disputes, and holds — and list open asks once

• [ ] Status vocabulary is named (to pay / scheduled / paid / disputed / on hold / missing info / ask) — not blank cells that look batch-ready.
• [ ] Evidence for paid (portal confirm, bank memo, receipt match) sits in notes or source — “I think we paid that” alone is not paid.
• [ ] Paid or credited-to-zero bills are flipped off Open — they do not still green the due-in-7-days slice because the PDF is still in the dump.
• [ ] Disputed / on-hold bills stay out of ready-to-pay filters until status says otherwise — burial in a thread is not a status.
• [ ] Approver (who can say yes on their side) is named or unowned — folklore that “they’ll pay when they can” is not ownership.
• [ ] Open asks (missing due date, no invoice #, vendor alias, currency unclear, conflicting portal vs PDF) are listed once in a visible place — not scattered as footnotes nobody will find at handoff.
• [ ] Skim test: a reader can say what is ready to pay, what is paid/credited, what is disputed/hold, and what still needs confirmation without reopening Slack.

A paid ghost can be useful archive context. The misleading part is leaving it dressed as this window’s share-ready open total.

4. Retire zombie and stale bill versions before they travel

• [ ] Superseded bill versions (INV_FINAL_v2 still looking live next to v3, or an older PDF next to a portal reissue) are labeled superseded or removed from the share view — they do not still inflate Open.
• [ ] Walked-back, credited, canceled, out-of-window, or wrong-entity bills are labeled stale or stay-off — they do not still green the batch list.
• [ ] When email, portal, and PDF disagree, keep the conflict visible as recheck — do not pick the easier amount or due date because it fits the template.
• [ ] Capture or last-checked date exists for material open totals — “I cleaned this last week” is not a freshness rule.
• [ ] Raw scratch, rejected options, and unresolved conflicts stay in the evidence trail but out of the clean share view.
• [ ] Skim test: a reader can tell whether each line describes the current dump, an older bill version, or something still needing confirmation.

A zombie bill version is historical context. The misleading part is leaving it dressed as this window’s share-ready open AP.

5. Challenge the Slack “pay when you can”

• [ ] Replace “pay when you can” / “looks fine” folklore with the exact vendors, open remainders, due dates, or status that were confirmed, parked, or never named on the sheet.
• [ ] An emoji reaction, “lgtm,” or vague thumbs-up is labeled by what it covered — it does not silently rewrite open totals, due dates, or paid status.
• [ ] If Slack approved a different version than the sheet you are about to send, stop and reconcile — do not ship the prettier draft under the older reaction.
• [ ] Make the share ask specific — confirm this vendor, this open remainder, this due date, this disputed flag, this superseded version — instead of asking for another vague “pay when you can.”
• [ ] Leave a visible needs confirmation marker where sharing would otherwise create a false record of agreement.
• [ ] Final skim: I can answer “what source supports this line, what still needs confirmation, and what did Slack actually cover?” for every share-ready row.

If a row fails one of these checks, I would rather send a visible needs confirmation label than make the payables sheet look complete by guessing.

Soft CTA

If you have a pile of vendor bills and want it organized into a clean accounts-payable sheet, payablesheet on Gumroad is $12. Code ADMIN12 takes $2 off. Browse the full shop or the catalog mirror on GitHub Pages.

Not a CPA. Not financial, tax, legal, or accounting advice — just an admin checklist for keeping a shared payables sheet tied to what is still open.