Finance Index
What is card drift?
Reference guide to card drift, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.
Card drift is the gradual migration of invoice-able spend onto corporate cards - purchases that should flow through requisitions, vendor records, and AP instead happening as card swipes. The money gets spent either way; what drifts away is everything attached to the invoice path: approval before commitment, negotiated pricing, contract linkage, PO matching, vendor compliance records, and a coherent audit trail. Card drift is how a company's spend controls erode without a single control ever being removed.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Card drift | Card drift is the gradual migration of invoice-able spend onto corporate cards - purchases that should flow through requisitions, vendor records, and AP instead happening as card swipes. | Keeps vendor records and payment decisions reliable. |
| Card control | The incentives all point one direction. | Keeps spend tied to policy, ownership, and review. |
| What exactly do you | Five things, in order of expense: (1) **Approval before commitment** - the card authorizes after the decision is irreversible; an invoice approval happens before money is owed. | Keeps spend tied to policy, ownership, and review. |
| This drift | Apply the counterfactual test: *would this purchase have produced an invoice five years ago?* Recurring software charged monthly to a card, a contractor paid by card, a five-figure equipment purchase swiped at point of sale. | Keeps evidence clear and reduces control risk. |
| Card drift undermine procurement | Every drifted purchase is maverick spend: it bypasses preferred vendors and negotiated contracts (contract leakage), fragments volume that could have earned pricing leverage, and never touches the intake where procurement could have consolidated, negotiated, or declined it. | Keeps vendor records and payment decisions reliable. |
Why does spend migrate from invoices to cards over time?
The incentives all point one direction. For the employee, the card is instant and the requisition is a form; nothing in the moment rewards choosing the slower path. For the card provider, more card volume means more interchange revenue, so the product is engineered to make swiping ever easier - higher limits, instant issuance, "no approvals needed." For the vendor, card-on-file means frictionless recurring revenue. Even finance contributes: when the AP or procurement intake is slow, the card becomes the documented workaround, then the undocumented norm. Drift isn't deviance - it's rational behavior inside a system whose frictions are arranged backwards.
What exactly do you lose when a purchase happens on a card instead of through AP?
Five things, in order of expense: (1) Approval before commitment - the card authorizes after the decision is irreversible; an invoice approval happens before money is owed. (2) Contract and pricing context - card purchases routinely bypass negotiated rates and create contracts (auto-renewing subscriptions) nobody reviewed. (3) The vendor record - no W-9, no banking verification, no insurance certificate, no compliance trail. (4) Matching - there is no PO and often no invoice to match against, so overbilling detection drops to whatever the cardholder notices. (5) The audit trail - a merchant descriptor and a receipt photo, versus an invoice with approvals, coding, and history.
Is this drift or just modernization - how do you tell?
Apply the counterfactual test: *would this purchase have produced an invoice five years ago?* Recurring software charged monthly to a card, a contractor paid by card, a five-figure equipment purchase swiped at point of sale - those would have been invoices, and the card didn't remove the need for the controls, it just skipped them. Genuinely card-native spend - travel, meals, incidental supplies - was never invoice-able and isn't drift. Modernization changes the payment rail while keeping the process; drift abandons the process and calls it speed.
How does card drift undermine procurement specifically?
Every drifted purchase is maverick spend: it bypasses preferred vendors and negotiated contracts (contract leakage), fragments volume that could have earned pricing leverage, and never touches the intake where procurement could have consolidated, negotiated, or declined it. Procurement can't manage spend it only discovers on a statement.
Is card drift inevitable with a modern card program?
No - but it's the default outcome of programs designed to maximize card volume. Programs resist drift when cards are issued against requests rather than as standing capacity, when limits are sized to need rather than generosity, and when the invoice path is fast enough that the card isn't the rational workaround.
What's the relationship between card drift and shadow it / shadow spend?
Unsanctioned SaaS is the leading edge of drift: software is the easiest category to buy by card, the most likely to auto-renew, and the most likely to carry security and data implications nobody assessed. A card statement full of unrecognized software merchants is shadow IT's accounting signature.
Our AP invoice volume is flat while card volume doubled in two years - growth or leakage?
Decompose it: if card growth is concentrated in invoice-capable merchants (software, services, equipment, vendors who also appear in your AP master), it's leakage; if it's travel, meals, and field spend scaling with headcount, it's growth. Flat AP against doubled card spend in a growing company usually means both - and the leakage share is worth auditing before it compounds.
Stampli perspective
Stampli's position is that spend management should manage spend, not encourage it - and that a credit limit isn't a budget. Stampli Card is built into the P2P workflow rather than beside it: AP Cards are issued from approved purchase requests with pre-set controls and pre-coded GLs, so card-fulfilled spend keeps the approval, the coding, and the audit trail that drift normally deletes. The card becomes a payment method inside the process instead of an exit from it.