- Spend management operates before the money moves; expense management operates after.
- Budgets are only useful if committed spend is visible, not just settled transactions.
- Approval workflows should be reserved for decisions that genuinely need judgement.
- Over-controlling produces workarounds, which are worse than the spend they prevent.
- The unit of control is usually the card, the budget or the vendor relationship.
What spend management means
Spend management is the set of rules and workflows that determine who can spend, on what, up to how much, and with whose agreement. In a modern stack these rules are enforced by the system that issues the cards, which means policy is applied automatically at the point of purchase.
It is worth separating this clearly from procurement, which manages vendor selection and contracting, and from expense management, which records outcomes. All three interlock, but conflating them produces process that satisfies nobody.
Who does what
| Discipline | Question it answers | Typical owner |
|---|---|---|
| Procurement | Should we buy from this vendor, on what terms? | Procurement or a functional lead |
| Spend management | Who may spend, how much, on what, with whose approval? | Finance |
| Expense management | What did we actually spend, coded how, with what evidence? | Finance operations |
| Accounting | How is this represented in the ledger and the accounts? | Controller |
Budgets that mean something
A budget that only reflects settled transactions is a rear-view mirror. By the time a department appears over budget, the commitments causing it were made weeks earlier.
Useful budgets include pending authorisations, scheduled payments and known recurring commitments — so the number a manager sees is what the team has actually committed, not what has cleared.
- Include pending card authorisations, not just settled ones.
- Include scheduled vendor payments from the payables queue.
- Roll recurring subscriptions forward automatically rather than re-forecasting them.
- Give the budget owner the ability to see the underlying transactions without asking finance.
Approval workflows without the bureaucracy
Every approval step costs someone's attention. A workflow that routes a €40 software purchase to a director trains that director to approve without reading, which destroys the control entirely.
Design approvals around materiality and risk. Route the purchases where a second opinion changes the outcome, and let the rest through with after-the-fact review.
- Set thresholds by cost centre rather than one company-wide number.
- Route new vendor relationships even when the amount is small — that is where risk concentrates.
- Give approvers enough context to decide in seconds, or they will not decide at all.
- Track approval latency; a slow workflow is a workflow people will route around.
Choosing the right control for the risk
Controls are not free. Each one adds friction somewhere, so match the mechanism to the actual exposure rather than applying the strongest available control everywhere.
- Recurring, known vendor — vendor-locked virtual card, no approval needed.
- One-off, unknown merchant — single-use card with a hard cap.
- High value, strategic — approval workflow plus procurement review.
- Routine, low value — per-card limit and after-the-fact review only.
Frequently asked questions
Spend management is preventive and operates before money moves: policy, budgets, limits, approvals. Expense management is recording and operates afterwards: receipts, coding, review, export. See expense management for the other half.
In a light form, yes. Two or three rules — a per-card limit, a virtual card per subscription, and an approval threshold — deliver most of the benefit and take an afternoon to set up.
Rarely. Hard-blocking a department mid-month usually creates an emergency rather than discipline. Most teams get better results from visible commitments and a conversation, with hard limits reserved for genuinely capped categories.
Finance normally owns the policy, but adoption depends on functional leaders agreeing it is workable. Policy written without operational input is the kind that gets routed around.
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- Brex — official website Primary source for current product names, availability and terms.
- Brex Support Center Official help documentation, including account access and card administration topics.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.
- IRS Publication 463 — travel, gift and car expenses Used for statements about expense substantiation and record keeping in the United States.