Buy First, Ask Later Isn't Control: Pre-Approve in Slack

Someone needs a tool by Thursday. The approval DM sits unread. They buy it on a personal card, submit an expense claim two weeks later, and finance learns about the spend when the reimbursement request — or the vendor invoice — shows up.

That pattern has a name: unauthorized employee spending, also called maverick spend. It is any purchase that skips the company's required approval process. Controllers who study it keep saying the same thing: it is usually a process problem, not a people problem (ProcureDesk, May 16, 2026).

This post is for Slack-first teams that already book in QuickBooks or Xero. Day-of headlines in this niche were thin, so the guidance below is grounded in current purchase-request and maverick-spend playbooks rather than a single news item.

Reimbursement is not purchase approval

Glencoyne draws the line cleanly: procurement is requesting, approving, and committing company funds before the buy; expensing is reimbursing someone for a purchase they already made (Glencoyne, Oct 5, 2025). Both matter. They are not substitutes.

Stampli's purchase-request guidance is blunt about timing: requests should be required before the purchase as policy. After-the-fact requests are retroactive paperwork — they document spend but control nothing. Reserve ratification for genuine emergencies, and review those exceptions (Stampli).

If your only "approval" step is signing an expense claim after the card has already cleared, you have a reimbursement workflow. You do not have spend control.

Why "ask later" wins when the process is slow or fuzzy

ProcureDesk lists the usual reasons employees bypass intake (ProcureDesk, May 16, 2026):

• Nobody wrote down that a purchase request is required.
• Approvals take days while the work needs something this week.
• Email or DM approvals leave no queue, no budget check, and no enforcement if the buyer does not wait.

Warning signs look familiar to anyone who closes books in QuickBooks or Xero: invoices with no matching approval or PO, department heads charging personal cards and expensing later, employees emailing vendors directly, month-end numbers that do not match forecasts, and no named approver when someone asks who said yes (ProcureDesk, May 16, 2026).

Corporate cards help with visibility after the swipe. They do not, by themselves, create a pre-commit decision or a purchase record finance can match an invoice against (ProcureDesk, May 16, 2026). Approval-first teams still need the Slack decision before money moves — whether the eventual payment is a vendor bill, a company card, or a reimbursement.

Put the front door in Slack — and make it faster than a DM

You do not need an enterprise procurement suite on day one. Glencoyne's "1-Hour Fix" is still the right starting move for small teams: a dedicated channel such as #purchase-requests, a short template, and a published materiality threshold so people know when a request is required (Glencoyne, Jun 7, 2025).

A useful request captures what Stampli treats as required for spend control: requester, department, description of the need, estimated amount, need-by date, and vendor if known (Stampli). For Slack-first teams that book in QuickBooks or Xero, add:

• One-time vs recurring / renewal
• How it will be paid (vendor bill, company card, or — only if allowed — personal card then reimbursement)
• Suggested GL / class / tracking category
• Quote or link attached when you have one

Stampli's adoption advice matches what actually works in chat tools: make the structured path faster than the freeform message (under two minutes), redirect every out-of-band ask to it without exception, and give requesters status they can see without pinging finance (Stampli). If "can I buy X?" DMs are still accepted as the real process, the form will lose.

Keep an express lane — inside the process, not around it

True emergencies happen. The mistake is inventing a second, undocumented path every time someone is in a hurry.

Stampli recommends building the express lane inside the same intake: an urgent flag with faster nudges, a delegated emergency approver for low thresholds, and a documented after-the-fact ratification path that is rare, logged, and reviewed monthly. If "emergencies" are frequent, that is an approval-speed problem, not an emergency problem (Stampli).

Practical SLA targets from the same playbook: routine requests in 1–3 business days end to end, same-day for low-dollar, and anything beyond a week trains people to go around the process (Stampli). Pair that with the threshold habits you already use for Slack-first teams so small buys move fast and large or new-vendor buys get the right eyes.

Enforce the exception at reimbursement and at AP

Policy only sticks when finance's downstream rules match it.

No approval, no reimbursement (above your threshold). Personal-card buys that skipped the Slack request should not clear as a normal expense claim. Route them through the ratification path: itemized receipt, business purpose, manager sign-off, and a logged exception. Repeat offenders escalate to the manager — not as theater, but so the path of least resistance becomes the purchase channel (ProcureDesk, May 16, 2026).

No matching approval / PO, no payment for vendor invoices. ProcureDesk calls this the single most powerful rule in an unauthorized-spend policy: send the invoice back until a retroactive request is approved. Enforce it consistently, including for senior staff (ProcureDesk, May 16, 2026).

Tax substantiation for reimbursements is a separate layer. U.S. employers who reimburse under an accountable plan still need employees to adequately account for business expenses (and return excesses) so the reimbursement stays off wages — see IRS Publication 463. That protects tax treatment. It does not replace the pre-purchase decision your Slack channel is supposed to capture.

When the claim is legitimate and approved, close the loop the same way you would for any other approved spend: vendor or employee payable in QuickBooks or Xero, coding that matches what the approver saw, receipt attached, and a link to the Slack approval on the bill or expense.

What to put in place this week

1. Publish a one-page rule: above $X (or for any new vendor / new subscription), buy only after a Slack purchase request is approved. Reimbursement without that approval is an exception path, not the default.
2. Stand up #purchase-requests (or reuse your existing purchase channel) with the field list above. Stop treating freeform DMs as sufficient.
3. Name same-day or next-day approvers for low-dollar requests so urgency does not force personal cards.
4. Add two finance rules: no reimbursement without prior approval (or logged ratification), and no vendor payment without a matching approved request or PO.
5. Once a month, review every ratification and every "bought it already" claim. If the pile is growing, fix approval speed or thresholds — not the exception form.

BuyFlow is built for the pre-commit half of this: purchase approvals in Slack that sync into QuickBooks or Xero, so "we already bought it" stops being how finance first hears about spend.