Don't Chase Receipts at Close: Attach Proof When You Approve in Slack

A Slack ✅ on a purchase feels finished. Month-end is when finance discovers it was not.

The charge is in the bank feed. The vendor name is fuzzy. Nobody has the invoice, the quote, or a photo of the receipt. Now the close slows down while someone reconstructs what should have been attached when the company said yes.

For Slack-first teams that book in QuickBooks Online or Xero, the fix is not a heroic chase in the last three days of the month. It is a simple rule earlier in the flow: no proof, no approval — or at least no booking until the proof is on the request.

Why missing docs show up at close, not at buy time

Cash Flow Desk's May 2026 guide on expenses without receipts is blunt about timing: by the time month-end starts, missing receipts have often been sitting unresolved for weeks. Their walkthrough covers reconstruction from card statements, employee attestation with manager sign-off, de minimis write-offs, and accruals when support is still incomplete (Cash Flow Desk).

Xero's expense-tracking guide pushes the same habit from the ledger side: record expenses as they occur, digitize receipts the same day, and match each receipt to the corresponding entry — not at month-end when details fade (Xero). Xero also notes that the IRS accepts legible digital copies of receipts for most tax purposes, and recommends keeping most expense records for at least three years from filing (employment-tax records longer) (Xero).

Senvora's small-business close checklist puts the operational cost in plain view: credit-card reconciliation means matching each transaction to a receipt or supporting document, and accruals fall apart when invoices never arrive on time (Senvora). If your close regularly stalls on undocumented card lines, you do not have a bookkeeping problem first — you have an intake problem.

Emburse's 2026 receipt best-practices guide adds the compliance frame: a card statement proves money moved; an itemized receipt (or invoice) is what substantiates what was bought and why it was business. They summarize IRS Publication 463's common documentary threshold — receipts generally expected for expenses of $75 or more, with lodging always needing a receipt — and stress that even under that threshold you still need contemporaneous records of amount, date, place, and business purpose (Emburse; IRS Publication 463 (2025)). Treat tax rules as a floor. Your internal control can — and for growing teams usually should — ask for proof sooner and on more purchases than the minimum deduction rules.

Approval without an attachment is only half a decision

Purchase approval answers: May we commit?
Documentation answers: What exactly did we commit to, and can finance book it?

When those questions live in different weeks, you get:

1. Bank feed first, story later — someone spent, Slack never saw a file, QBO/Xero gets a guess-coded expense.
2. Emoji yes, empty audit trail — an approver reacted in a DM with no quote, invoice PDF, or order confirmation to reopen later.
3. Close-time archaeology — finance pings five people to rebuild vendor, amount, tax, and purpose from memory and calendar invites.

That is the same failure mode as pre-approval and segregation of duties, just one step later: the decision happened in chat, but the evidence never joined the decision.

A practical "proof on the request" rule for Slack + QBO/Xero

You do not need an ERP receipt module. You need a channel habit and a short policy.

1. Define what counts as proof

Minimum attachment (pick what matches the buy):

Buy type	Acceptable proof on the Slack request
New software / SaaS	Quote, order form, or checkout screenshot with plan and price
Vendor invoice / bill pay	Vendor invoice PDF (or portal link + saved PDF)
One-off card spend already made (exception path)	Itemized receipt photo/PDF + business purpose
Recurring renewal	Prior invoice or renewal notice showing amount and term
Contractor / agency	Signed SOW or proposal with fee schedule

Cash Flow Desk's resolution paths are useful except when you treat them as the default: reconstruction and attestation are for exceptions, not for every mid-month purchase (Cash Flow Desk).

2. Put the file on the request before Approve

In #spend-requests (or your approvals channel), every request above your smallest threshold should include:

• Vendor name
• Amount (and currency)
• Business purpose (one sentence)
• Category / who owns the budget
• Attachment or durable link to the quote, invoice, or receipt

Approvers should reject incomplete requests the same way they reject over-budget ones. A yes without proof trains the team to create next month's close backlog.

3. Set a capture SLA measured in hours, not month-end

Xero's guidance is to digitize the same day (Xero). Cash Flow Desk reports that many companies target 48–72 hours after the transaction, with limited grace during close (Cash Flow Desk). Pick one SLA, publish it, and enforce it in Slack — not in a PDF handbook nobody opens.

Example one-liner: If the receipt is not on the thread within 48 hours of spend (or before Approve for pre-approved buys), the request stays Pending and will not be booked.

4. Book only from complete threads

When the bookkeeper creates the expense or bill in QuickBooks or Xero, they should open the Slack request and pull vendor, amount, purpose, and the attached file into the ledger attachment — not invent coding from the bank description alone. Xero's matching advice and Emburse's point about linking the GL entry to point-of-sale evidence are the same control in different words (Xero; Emburse).

5. Use a missing-receipt path that is louder than silence

For genuine losses, require a short affidavit: vendor, date, amount, purpose, why the original is missing, plus manager sign-off — the pattern Cash Flow Desk and Emburse both describe (Cash Flow Desk; Emburse). Cap how often someone can use it. Track exceptions monthly. If the same person files three missing-receipt forms in a quarter, fix behavior, not the form.

6. De minimis is a policy choice, not "no docs ever"

Many internal policies allow lighter documentation under $25–$75 for low-risk spend (Cash Flow Desk; Emburse). Write your number down. Lodging and anything you care about for tax or customer bill-back should still demand an itemized receipt. Under-$75 does not mean "approve in a DM with zero context."

What this is not

This is not a pitch to move every purchase onto a new corporate card so a card product can nag for receipts after the swipe. Card platforms are strong when your problem is card issuance and real-time spend controls. Many Slack-first QBO/Xero teams already buy on existing cards or ACH — their gap is decision + evidence before booking, not another payment rail.

It is also not bill approval inside the ledger. Bill approval checks an invoice after it arrives. Receipt-on-request is about the Slack commitment (or the exception path when someone already spent) so month-end is not the first time finance sees the file.

This week's checklist

1. Pin the rule in #spend-requests: Attach quote, invoice, or receipt before asking for Approve (or within 48 hours for true exceptions).
2. Add "attachment present?" to your approver's mental checklist — same weight as amount and budget owner.
3. Spot-check last month's card and bank lines in QBO/Xero: how many have no Slack thread with a file? Those are your close debt.
4. Publish a one-page missing-receipt form and a monthly exception count.
5. Tell the bookkeeper: do not book from bank description alone when a Slack request should exist.

Bottom line

Month-end does not create missing receipts. Slack approvals without attachments do. Require proof on the purchase request, sync the approved package into QuickBooks or Xero, and treat reconstruction as the exception path. Your close gets shorter because the evidence arrived when the company said yes — not three weeks later when someone is hunting a faded PDF.