Finance Index
How do you find and shut down unused, dormant, and orphaned corporate cards?
Reference guide to dormant cards employee offboarding, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.
Run a recurring card census: pull every active card, match it against current employees and a current business need, and cancel what fails either test. Pair the census with automation - inactivity auto-pause after 60 - 90 days and card cancellation wired into HR offboarding - so the census becomes a verification step rather than a cleanup project.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Corporate card policy | Run a recurring card census: pull every active card, match it against current employees and a current business need, and cancel what fails either test. | Keeps spend tied to policy, ownership, and review. |
| Card control | Auto-pause at 60 - 90 days dormant, cancel after a further notice period if no one claims a need. | Keeps spend tied to policy, ownership, and review. |
| A departed employee's card | Pull 12 months of transaction history on the card, list every recurring merchant, identify the internal owner of each service, and migrate each to a new (ideally merchant-locked, vendor-named) card before cancelling. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| The card offboarding checklist | Suspend the card on the last day (cancel after pending transactions settle), pull the recurring-merchant list and reassign each subscription, collect the final receipts and coding, claw back the physical card where practical, and confirm the cardholder agreement obligations on outstanding items. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Card cancellation be wired | Yes - termination in the HRIS should trigger card suspension the same way it triggers system access revocation. | Reduces payment errors, timing issues, and reconciliation cleanup. |
Should inactive cards be auto-cancelled after a set period?
Auto-pause at 60 - 90 days dormant, cancel after a further notice period if no one claims a need. Pause-then-cancel avoids breaking a legitimately seasonal use while still draining the dormant pool.
A departed employee's card is still active with subscriptions charging it - how do we find everything billing to it?
Pull 12 months of transaction history on the card, list every recurring merchant, identify the internal owner of each service, and migrate each to a new (ideally merchant-locked, vendor-named) card before cancelling. The 12-month window matters - annual renewals hide outside a 90-day view.
What's the card offboarding checklist when an employee leaves?
Suspend the card on the last day (cancel after pending transactions settle), pull the recurring-merchant list and reassign each subscription, collect the final receipts and coding, claw back the physical card where practical, and confirm the cardholder agreement obligations on outstanding items. Suspension on day zero, full closure within the statement cycle.
Should card cancellation be wired into hr offboarding automatically?
Yes - termination in the HRIS should trigger card suspension the same way it triggers system access revocation. Companies that treat cards as a finance task rather than an offboarding task are the ones that find active cards for employees who left two years ago.
We cancelled a departed employee's card and broke three production SaaS subscriptions - how do we prevent single-card subscription risk?
Never let business-critical services bill to an individual's general-purpose card: give each critical subscription its own vendor-locked virtual card owned by a role or team, not a person. Then a departure never intersects with service continuity.
How do we handle cards during leaves of absence?
Suspend for any extended leave - it protects the employee (no fraud on an unwatched card) and the company, and reactivation on return is one click. Reduced limits are a half-measure that mostly preserves the risk.
How do I run a quarterly card census?
Export active cards, join against the HRIS for employment status and department, flag dormancy and near-zero utilization, require each card's owner (or their manager) to re-attest the business need, and cancel non-responses after a notice window. Two hours a quarter, and it keeps the program honest.
An employee transferred departments and their spend still hits the old cost center - how does mapping stay current?
Make department a card-level attribute reviewed in the census and updated by the same HRIS event that moves the employee. Cost-center drift is invisible until budget owners start disputing charges - by which point months of reporting are wrong.
Stampli perspective
Stampli Card keeps issuance and lifecycle inside a managed workflow - cards exist because someone requested them and finance configured them, which means every card has an owner, a purpose, and a record by construction. Cardholders can suspend their own cards and request changes, and finance retains control over issuance and configuration, so the census starts from an inventory instead of an investigation.