- Employee cards make spend attributable at the moment it happens, not weeks later in a claim.
- Role templates keep issuance consistent and fast as headcount grows.
- Limits should reflect the job, not seniority — most roles need far less than people assume.
- Offboarding must include card termination, or dormant cards accumulate.
- Policy works best when it is short, specific and enforced by the system rather than by managers.
Why issue cards at all
The alternative to employee cards is reimbursement, and reimbursement has an uncomfortable property: the employee finances the company until the claim is paid. For junior staff and anyone travelling frequently, that is a genuine hardship and a recurring source of friction.
Cards also fix an information problem. A reimbursement claim tells you what happened after the decision was made. A card transaction tells you at the moment it happens, tagged to a person, team and category.
A workable issuance model
Define roles, not people
Three or four templates usually cover a whole company: individual contributor, manager, traveller, and a purchasing role for people who buy on behalf of others.
Set limits from actual spend
Look at what the role genuinely spends in a normal month and set the ceiling a little above it. Limits set from seniority tend to be several times too high.
Issue during onboarding
Make card issuance part of the joining checklist so it happens once, consistently, with the right template applied.
Terminate during offboarding
Card termination belongs on the leaving checklist next to laptop return and account deactivation.
Example role templates
Illustrative structure — the categories and thresholds should reflect your own policy, not ours.
| Template | Typical categories | Control emphasis |
|---|---|---|
| Individual contributor | Software, small equipment, occasional meals | Modest ceiling, receipt rule above a small threshold |
| Manager | Team meals, recruiting, small vendor purchases | Higher ceiling, approval routing above a threshold |
| Frequent traveller | Flights, hotels, ground transport, meals | Travel categories open, non-travel categories restricted |
| Purchasing role | Vendors, subscriptions, contractors | Virtual cards per vendor, tight merchant locking |
Policy that people actually follow
Long expense policies fail for a simple reason: nobody reads them, so the rules live only in the reviewer's head. A short policy that the system enforces is more effective than a comprehensive one that it does not.
The best structure we have seen is one page: what you can buy without asking, what needs approval, what is never reimbursable, and what to do when something goes wrong.
- State the receipt threshold once, clearly, and enforce it automatically.
- Name the categories that always need approval rather than listing everything that does not.
- Say explicitly what happens with a personal purchase made by mistake — it will happen.
- Give one place to ask questions, so ambiguity does not become precedent.
Offboarding and dormant cards
Dormant cards are the most common control weakness in otherwise well-run programmes. They accumulate quietly: someone leaves, their card is never terminated, and it remains capable of authorising spend indefinitely.
Two habits fix it permanently. First, put card termination on the offboarding checklist alongside account deactivation. Second, run a quarterly review of cards with no activity and close anything without a clear owner.
- Terminate rather than freeze when someone leaves, so the card cannot be reactivated by mistake.
- Reassign any vendor-locked virtual cards the person owned before terminating their access.
- Check for pending authorisations that will settle after termination.
- Review zero-activity cards quarterly and close them by default.
Frequently asked questions
Everyone who needs to spend on the company's behalf should, with a limit sized to their role. Withholding cards from people who then pay out of pocket transfers a cash-flow burden onto individuals and delays visibility for finance.
Base it on what the role actually spends in a normal month rather than on seniority. Most individual contributor roles need far less than expected, and limits are trivial to raise when a genuine need appears.
Authorisations already placed generally still settle. Confirm the exact behaviour with the provider, and check for pending items as part of offboarding.
Delegated administration allows this within a ceiling set by finance. Whether it is available, and how granular the delegation is, varies between programmes — see the corporate card administration section.
Decide the process in advance and write it into the policy: usually flag it immediately, mark it as personal in the expense tool, and repay through payroll or a direct transfer. Ambiguity here is what makes small mistakes into awkward conversations.
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.
- Visa — commercial payment solutions Network-level background on commercial card products and data levels.
- Consumer Financial Protection Bureau — credit card resources Background on card terminology, billing cycles and consumer-vs-commercial distinctions.
- IRS Publication 463 — travel, gift and car expenses Used for statements about expense substantiation and record keeping in the United States.