Corporate cards or reimbursements: choosing a spend model

Every dollar an employee spends on the company's behalf leaves the building one of two ways: on a card the company owns, or out of an employee's own pocket to be paid back later. That single choice — who fronts the money — quietly decides how much control you keep, how fast your team can move, and how much cleanup lands on whoever closes your books at month end.

Two models, one real trade-off

A corporate card is a company-owned card issued to an employee. The company is on the hook for the balance, and spending shows up in your accounting software the moment it happens. A reimbursement works the other way: the employee pays with their own card or cash, submits an expense report, and you pay them back after someone approves it.

The trade-off is speed versus control, and it never fully goes away. Cards let people buy what they need without asking, which is fast but means money moves before anyone reviews it. Reimbursements put a human approval in front of every dollar, which is tighter but slower — and they ask your team to lend the company money in the meantime.

Corporate cards move fast, but only with guardrails

Handing someone a company card removes friction. Marketing can top up ad spend at 9 p.m. without a Slack message, and no one is floating $2,000 on a personal card waiting to be paid back. The risk is the flip side of that speed: money leaves before you see it, so the controls have to sit on the card itself, not on an approval step after the fact.

Modern card platforms let you set those controls per card. A card without limits is not a convenience — it is an unreviewed checkbook. At minimum, put these guardrails in place before you issue a single card:

• Per-card monthly limits sized to the role, not the company balance
• Category locks so an ads card cannot buy electronics or gift cards
• Mandatory receipt capture, with the card frozen if receipts go missing
• A named owner on every card — no shared or anonymous cards
• Monthly reconciliation against the statement, every card, every month

Reimbursements give you control at a cost

Reimbursements flip the timing. The employee spends first, submits a report with receipts, and you review before any money moves. Nothing leaves the company until a person has looked at it, which is the tightest control you can have. That is genuinely valuable for spend you want to scrutinize — a $1,900 conference ticket, a client dinner, a one-off equipment purchase.

The cost is real, though, and it is not only slower processing. Your employee is now a short-term lender to the company. Someone who fronts $340 for a flight and waits three weeks to be paid back notices. Do that a few times to a junior employee and you have a morale problem, not just an accounting one. Reimbursements work best when they are the exception, not the daily path.

The hybrid most teams actually run

In practice, most small companies stop choosing and split the difference. The people who buy often — and the recurring bills that hit every month — go on cards. Everyone else uses reimbursement for the occasional out-of-pocket expense.

The dividing line is frequency. If a person or a cost shows up more than a couple of times a month, a card with a sane limit saves everyone time. If it is rare or unpredictable, reimbursement keeps you from issuing a card that sits unused eleven months a year. A clean version looks like this: your two or three frequent buyers get category-locked cards, every subscription lives on one dedicated card, and the rest of the team expenses the occasional taxi or lunch.

What each model does to your books

The two models create very different bookkeeping. Card spend arrives through a bank feed — an automatic import of every transaction — so the work is categorizing charges and matching receipts to charges that are already there. Reimbursements arrive as expense reports you approve and then pay, which means an extra step: booking the liability and cutting the payment, often through payroll.

Here is a concrete month. You have a 12-person team. Four people buy regularly, so they carry category-locked cards: marketing spends $4,200 against a $6,000 limit, operations spends $1,800, and two others spend $600 combined — roughly 45 card transactions that flow in through the feed and get categorized in about an hour. Separately, three employees submit reimbursements: $180 for supplies, $340 for a flight, and $95 for a client lunch, totaling $615 across three reports that each need review, approval, and a payout run.

Notice the shape. The $6,600 of card spend is far larger but nearly hands-off at close, because the feed already captured it. The $615 of reimbursements is small money but carries most of the manual work — and the flight buyer waited two pay cycles to see their $340 back. That is the pattern to design around: use cards to absorb volume, and reserve reimbursement for the low-frequency spend that genuinely deserves a second look.

As a rule of thumb keyed to size: under five people, reimbursements plus one shared subscription card are usually enough. From five to roughly twenty, move your frequent buyers onto individual cards with limits and keep reimbursement for the rest. Past twenty, you want a real card platform with automated receipt capture and per-card rules, because manual policing stops scaling right about there.