The week-of close checklist I use so a receipt spreadsheet still matches the month

Mid-month cleanup is necessary. A week-of close is different. This is the pass I run when someone is about to rely on the receipt spreadsheet for a reimbursement send, a bookkeeping handoff, a tax folder drop, or a simple “are we caught up for the month?” conversation. At that point, a dual date is not a harmless note, a personal lunch still looking business is not a rounding error, and a Slack message saying “I think we’re caught up” cannot quietly turn an incomplete dump into a closed month.

I am a freelancer admin helper. I turn a month of receipt photos into a clean spreadsheet. I am not a CPA, bookkeeper, tax advisor, or auditor — and this is not financial, tax, legal, or accounting advice. It is a practical spreadsheet and close checklist for keeping stated facts, photo evidence, and unresolved questions separate.

This is complementary to my earlier posts, not a rewrite. For the full receipt-photo dump → clean spreadsheet workflow, see How I turn a month of receipt photos into a clean spreadsheet. For the mid-month pass while dumps are still arriving, see The mid-month checklist I use so a receipt spreadsheet stays honest. This third pass starts with the close boundary and the intended handoff: what can the sheet honestly say this week?

What “honest enough for a week-of close” looks like

• The month boundary and as-of date are explicit — not an old export wearing a current-looking filename
• One receipt maps to one row, with date, vendor, amount, and currency confirmed, missing, or marked ask — not two conflicting photos silently merged into one total
• Personal purchases cannot masquerade as business just because they sat in the same camera roll
• Tips sit with the base fare (or ask) — floating tip screenshots are not a second expense
• Category is stable enough to hand off — mid-sheet drift and “software somehow” folklore are labeled, not averaged
• Slack recollections are labeled folklore or needs recheck unless the photo or a source supports them
• A reader can tell what was photo-backed, what was estimate-only, and what still needs confirmation without reconstructing a message thread

If the only close evidence is a message titled “I think we’re caught up,” the week-of pass has already slipped.

The week-of close checklist (run it before anyone treats the sheet as truth)

Use this against the near-final spreadsheet and the live artifacts: the camera roll, Drive folder, email forwards, screenshots, bank-app captures, prior month export, and reimbursement notes. The point is not to make every row green. The point is to make every row legible.

1. Set the close boundary before you trust the total

• [ ] Write the month (or date range), timezone rule if travel mattered, and what “included” means for this close
• [ ] Keep older months and prior exports as sources, not as current truth — superseded rows are labeled prior or recheck
• [ ] List dumps that were not reviewed — a late email forward or a second phone’s camera roll should not disappear into a blank cell
• [ ] Skim test: you can answer “as of when, for which cards/accounts, under what include rule?” without opening Slack

2. Match each receipt to one row

• [ ] Use date, vendor, amount, and a short description to match the photo — not only a vague label such as “lunch”
• [ ] If two photos show the same receipt, keep one as duplicate and do not double-count the total
• [ ] If one photo could map to two rows, do not invent a second expense just because the sheet has room
• [ ] Record an amount only when it was readable on the receipt or supported by a source — never fill a blank with a remembered round number
• [ ] Separate tip-only screenshots from the base fare when the close rule needs both; otherwise state why they stay grouped
• [ ] Skim test: every included receipt has one row, and every unresolved match is visible from that row

A dual date or dual amount is not a formatting problem. It may be a timezone shift, a refunded charge, a tip added later, or two visits collapsed into one photo. The sheet can say date conflict — needs photo recheck and still be useful. It cannot honestly say “closed” while leaving both values active.

3. Keep personal bleed out of the business total

• [ ] Flag personal, mixed, or unknown purchases with an explicit status — do not leave them looking reimbursable because the camera roll was messy
• [ ] If a receipt was already client-reimbursed or paid on a different card, mark it stay-off for this close rather than counting it twice
• [ ] “Probably business” and “I usually expense that” stay ask or folklore — they are not categories
• [ ] Skim test: the business total does not include a row the evidence says was personal, reimbursed elsewhere, or unknown

4. Pin tips, currency, and category before the handoff

• [ ] Tips sit on the same row as the base fare, or are labeled ask / n/a — floating tip screenshots are not a second vendor
• [ ] Currency is named once per row (USD / other / ask) — mixed currencies without a note are not one month total
• [ ] Category uses one stable vocabulary for the close — mid-sheet renames and “software somehow” folklore stay in notes as ask
• [ ] Do not average two categories into a tidy label because the sheet looked sparse of red
• [ ] Skim test: sorting by category and currency does not invent a cleaner story than the receipts support

5. Reconcile the close without letting Slack rewrite it

• [ ] Mark each row as photo-backed, source-backed, estimate, duplicate, personal, out-of-range, or ask using a small, consistent vocabulary
• [ ] Put the evidence for a material amount in Source or Notes: receipt photo, email forward, bank capture, or named document
• [ ] Label “I think we’re caught up,” “that was about forty,” and similar messages as folklore unless a later check supports them
• [ ] Resolve duplicate sightings and stale totals before updating the month total
• [ ] Do not use a Slack reaction, a green cell, or an unchallenged old export as a substitute for a close result
• [ ] Skim test: someone reviewing the sheet can distinguish photo-backed spend from remembered spend in under a minute

6. Honesty tripwires (before you treat the month as closed)

• [ ] You did not promote vibes to “caught up” because the sheet looked tidy
• [ ] Incomplete rows stay ask — not silently promoted to closed because the week felt busy
• [ ] Raw dump artifacts (unlabeled screenshots, named complainers, draft notes, secret card digits) are out of the share view
• [ ] Skim test: a stranger can answer “what is still missing, which rows are soft, and what total is honest for this month?” from the spreadsheet alone

Soft CTA

If you have a month of receipt photos and want a clean spreadsheet in 24 hours: wxbclt on Gumroad ($15). 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 month-close line still matches what the receipts support.