- The goal is a complete, correctly coded record for every transaction with no manual data entry.
- Receipt capture at the moment of purchase is the single highest-leverage change.
- Automatic coding rules handle recurring merchants; humans handle the exceptions.
- Review should be exception-based, not line-by-line.
- Substantiation requirements come from tax and audit rules, not from the software.
What expense management covers
Expense management is everything that happens between a transaction occurring and that transaction being correctly represented in the general ledger. It includes documentation, categorisation, policy checking, approval where required, and export.
The traditional version of this process was built around reimbursement: an employee spends, files a report, waits for approval and receives money back. Card-led expense management inverts it. The company has already paid; the process now exists to attach context to a payment that has already happened.
The four-stage pipeline
Capture
The transaction arrives with merchant, amount, cardholder and timestamp. A receipt is attached by photo, email forward or automatic merchant integration.
Code
The transaction is assigned a category, cost centre, tax treatment and any project or client attribution. Rules handle recurring merchants automatically.
Review
Exceptions surface for human judgement: missing documentation, policy breaches, unusual amounts or new merchants.
Export
Coded, documented transactions move into the general ledger in the structure the accounting system expects.
Receipt capture is where programmes succeed or fail
Everything downstream depends on documentation arriving. If receipts show up three weeks late, coding is guesswork, review is archaeology, and close slips.
The practical fix is to reduce the employee's obligation to a single action taken at the moment of purchase, and to remove the obligation entirely wherever a merchant integration or a below-threshold rule allows it.
- Prompt at the moment of the transaction, not at month-end.
- Accept a photo, an email forward or a messaging reply — whatever is fastest for the person.
- Integrate the top recurring merchants so their receipts arrive automatically.
- Set a sensible de-minimis threshold and stop chasing documentation below it.
Coding rules and the chart of accounts
Coding is where accounting policy meets daily reality. A well-structured chart of accounts with a small number of clear categories is coded accurately by everyone; a sprawling one is coded inconsistently by everyone, including the finance team.
Recurring merchants should be coded by rule, not by hand. Once a vendor has been categorised correctly twice, the third transaction should require no human decision at all.
- Keep the category list short enough that a non-accountant can choose correctly.
- Map recurring vendors to accounts once and let the rule handle the rest.
- Attach cost centre from the cardholder's team by default, overridable when needed.
- Handle tax treatment by rule where jurisdictional logic is stable.
Exception-based review
Reviewing every line does not scale and does not catch more. Reviewing exceptions does both.
| Exception | Why it matters | Typical action |
|---|---|---|
| Missing receipt above threshold | Substantiation and audit evidence | Automated reminder, then escalation to the manager |
| New merchant | Could be a genuine new vendor or a mistake | One-time review, then a coding rule |
| Out-of-policy category | Policy enforcement without blocking everything | Reviewer decision with a written note |
| Amount well above the cardholder's norm | Detects errors and duplicates as much as misuse | Confirm with the cardholder |
| Possible duplicate | Double-charged vendors are common | Check before it reaches the ledger |
Audit evidence and substantiation
Expense records serve two audiences beyond your own reporting: tax authorities and auditors. Both want to see that a business purpose was documented and that the amount is supported.
Requirements differ by jurisdiction and by the nature of the expense — entertainment and travel are usually scrutinised more closely than software. Build the documentation habit around the strictest category you have rather than the easiest.
United States guidance on substantiation is set out in IRS Publication 463. Requirements elsewhere differ; check local rules.
The handoff to accounting
The export is the moment of truth. If categories, cost centres and tax codes map cleanly, close is fast. If they need manual repair each month, everything upstream has been wasted effort.
Agree the mapping with whoever owns the ledger before the programme goes live, and test it with a real period rather than a sample.
See the accounting reference for how mapping and sync behaviour usually work.
Frequently asked questions
In a card-led model, largely not. The company has already paid, so the remaining task is attaching a receipt and confirming coding. Formal expense reports persist mainly for genuine out-of-pocket spending, which should be a small minority of transactions.
Pick a level where chasing documentation costs more than the risk it mitigates, and check it against your local tax rules, which may impose their own thresholds for particular categories.
Retention periods are set by tax and company law in each jurisdiction and commonly run to several years. Confirm the rules that apply to your entity rather than relying on a software default.
No. It feeds the general ledger; it does not replace it. See accounting for where the boundary sits.
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.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.