Information only. This site is a reference project. We do not provide account access, financial services, card applications, payments, credit decisions or official support, and we never ask for account or financial credentials.
Where cards sit in the finance function
A card program is not a payments project. It is the front end of the accounting process, and how well it is designed determines how much of the month-end close is automatic.
The reason is a data problem. At the moment a card is authorised, the system knows four things: an amount, a merchant descriptor, a timestamp and a merchant category code. Everything a controller needs beyond that — business purpose, project, cost centre, tax treatment, a receipt — does not exist yet and has to be attached afterwards.
So the whole discipline reduces to one question: how much of that enrichment happens by rule, and how much lands on a human being. Card structure is the largest single lever on the answer, which is why the corporate card guide and this one are two halves of the same subject.
- Spend management
- Deciding and constraining what may be spent, before and during the transaction.
- Expense management
- Documenting, categorising and reconciling what was spent, after the transaction.
- Enrichment
- Adding the context a raw transaction lacks: purpose, project, cost centre, receipt.
- Reconciliation
- Matching each transaction to documentation and to the correct ledger entry.
- Close
- The point at which a period’s records are complete and no longer changing.
How Expense Management Works
Expense management is the sequence between a posted transaction and a closed accounting entry. It is the same five stages in every company, whether they are performed by software or by someone with a shoebox of receipts.
-
Capture
The transaction posts with amount, merchant and timestamp. Nothing here required human involvement.
-
Enrich
Category, cost centre, project and business purpose are added — ideally by rule, based on the card or the merchant.
-
Document
A receipt or invoice is attached, either forwarded by the spender or matched automatically.
-
Review
Exceptions and policy flags are examined by a person; compliant items pass through untouched.
-
Reconcile
The item is matched to the ledger and the period is closed.
Stages two and three are where all the cost is. Stage one is free, stage five is mostly mechanical, and stage four should touch only a minority of items. If a finance team is spending its month on enrichment and chasing documents, the fix is almost never a better process — it is a change upstream so the data arrives with more context attached.
| Stage | Manual by default? | What removes the manual work |
|---|---|---|
| Capture | No | Nothing needed — this is automatic |
| Enrich | Yes, heavily | Purpose-scoped cards and coding rules |
| Document | Yes, heavily | Automatic receipt matching and clear thresholds |
| Review | Partly | Prevention at authorisation, so fewer exceptions exist |
| Reconcile | Partly | Direct integration with the accounting system |
A structural framework. Which capabilities exist in any given tool must be established from that provider.
The cluster pages go further on each stage: expense management for the overview, business expenses for categorisation, and expense automation for what automation reliably does and does not remove.
How Businesses Manage Employee Expenses
There are two fundamentally different models, and most companies run both without ever articulating the difference. Naming it clarifies a surprising number of arguments.
Reimbursement model
- The employee pays with their own money first
- They submit a claim with documentation
- Finance reviews, approves and pays it back
- Control is entirely retrospective
- The employee carries the cash-flow cost
Company-paid model
- The employee spends on a company card
- Policy is applied at authorisation
- Documentation is attached to an existing transaction
- Control is preventive plus evidential
- The company carries the cash-flow cost
The company-paid model is better on almost every axis that matters — earlier control, better data, no personal cash-flow burden — and it is not free. It requires enough cards for everyone who needs one, which means issuance has to be cheap, and it requires documentation to be collected from people who have already got what they wanted.
Reimbursement does not disappear, though. It remains the right mechanism for genuine edge cases: a purchase made before a card existed, mileage, or a situation where a personal card was the only option. The mistake is running reimbursement as the default because issuing cards feels harder than approving claims. That trade is almost always the wrong way round. See employee spending and employee cards.
- A documentation threshold that is the same for everyone, leadership included
- A submission route that works from a phone at the moment of purchase
- Categories few enough that a non-finance person picks the right one
- A stated turnaround for reimbursements that are genuinely necessary
- Exceptions recorded with a reason, so patterns become visible
Business Spend Management Guide
Spend management and expense management are constantly used as synonyms, and they are not. The distinction is temporal and it is the organising idea of this whole site: spend management acts before and during the transaction, expense management acts after it.
| Dimension | Spend management | Expense management |
|---|---|---|
| Timing | Before and during the transaction | After the transaction |
| Core question | Should this be allowed? | What was this, and where does it post? |
| Primary tools | Limits, category rules, budgets, approvals | Coding rules, receipt matching, review, reconciliation |
| Owner in practice | Finance plus team owners | Finance and accounting |
| Failure symptom | Spending nobody authorised | A close that takes weeks |
| Main lever | Card and control design | Data quality arriving from upstream |
The framework this site is organised around. Terminology varies across the industry and vendors often use both words for the same product.
The practical value of separating them is diagnostic. If out-of-policy purchases keep happening, that is a spend management problem and no amount of better reconciliation will fix it — see the spending controls guide. If purchases are all legitimate but the close is painful, that is an expense management problem, and tightening limits will annoy people without helping. Most companies attack the wrong one first.
The two clusters on this site follow that split exactly: spend management for the preventive half, including budgets and card limits, and expense management for the downstream half.
The monthly close with a card program
A well-designed program makes the close boring, which is the highest compliment available in finance operations. The goal is that most items require no attention at all.
Most items pass untouched
Coded by rule, documented automatically, within policy. Nobody looks at them individually.
A small exception queue
Missing receipts, policy flags and unusual amounts — a list short enough to work through in one sitting.
No archaeology
Nothing requires asking a colleague what a charge was for, because the card already says.
A fixed cut-off
A stated date after which the period stops changing, so the numbers can be relied on.
Everything in that list is determined upstream. You cannot make a close boring by working harder at the end of the month; you make it boring by deciding, months earlier, that each card would map to a purpose and each rule would encode a written policy. That is the argument for treating card design as a finance decision rather than an operational one — the point finance teams develops further.
This project is independent and non-commercial. It provides no accounting, bookkeeping, tax or legal advice, holds no financial data, and is not affiliated with any provider discussed. Treatment of any specific expense is a question for a qualified adviser.
FAQ
Frequently asked questions
What is the difference between spend management and expense management?
Timing. Spend management acts before and during the transaction — limits, category rules, budgets, approvals. Expense management acts after it — coding, documentation, review, reconciliation. The words are often used interchangeably in marketing, which is why diagnosing a problem as one or the other is genuinely useful.
Why does the monthly close take so long?
Almost always because transactions arrive without enough context and someone has to add it. If a charge needs a person to identify the vendor, the purpose and the cost centre, that cost is paid on every line, every month. The fix is upstream: purpose-scoped cards and coding rules, not a faster reviewer.
Is reimbursement always worse than a company card?
Not always, but it should be the exception rather than the default. Reimbursement moves control to after the money has moved and puts the cash-flow burden on the employee. It remains appropriate for genuine edge cases such as a purchase made before a card existed.
How much of expense management can be automated?
Capture is automatic by nature; coding and receipt matching can be substantially automated by rule; review and judgement cannot. Automation reduces volume rather than eliminating the function. The expense automation page is more specific about where the boundary usually falls.
Who should own the card program in a company?
Whoever owns the monthly close, because they bear the consequences of poor upstream design. In smaller companies this is often a founder or an operations lead; as a finance function forms it typically moves to a controller. What matters is that one named person owns limits, exceptions and review.
Does this guide give accounting or tax advice?
No. This is an independent editorial project explaining how card, spend and expense workflows are structured. It gives no accounting, tax or legal advice and makes no claims about how any specific expense should be treated. For that, use a qualified adviser.
Sources and reference basis
- Reference General reference material on card transaction data fields and merchant category classification.
- Practice Commonly documented finance-operations workflows: transaction enrichment, receipt matching, exception review and period close.
- Framework Standard internal-control literature on preventive versus detective controls and segregation of duties.
- Method Our methodology explains how these guides are researched and our fact-checking policy how claims are verified and corrected.