When a corporate card outlives the job it was issued for

The most common failure is a card that stays live after its holder leaves or changes role. It starts when cancellation depends on someone remembering. It is spotted through charges nobody can approve. It is fixed by tying deactivation to the HR record and checking active cards against it.

How it starts

Card issuing usually gets careful design. There is a request form, an approver, a credit limit tied to grade, and a policy the holder signs. Cancellation gets far less attention. In many organisations it sits on an offboarding checklist owned by the line manager, who is also handling handover, equipment returns and a replacement hire.

The card administrator often hears about a departure late, informally, or not at all. HR systems record the leaving date. The card issuer's portal knows nothing about it. Nothing connects the two unless a person makes the connection.

Subscriptions make it worse. A departing employee may have put software licences, travel memberships or supplier accounts on the card. Those keep billing whether anyone is watching or not.

The role change version

Leavers are the obvious case. Internal movers are the quieter one, and often the more expensive. Someone moves from a sales role with a high travel limit into a desk job. The card stays, the limit stays, and the new manager has no idea the card exists. Approval routing may still point to the old manager, who signs off expenses for a person no longer in the team.

Policy usually says limits should match the role. Practice rarely revisits limits once set. The "Approve/Change credit limits" step tends to fire only when someone asks for more, never when they need less.

How it gets spotted

Detection is usually accidental. A statement line arrives for a cardholder whose expense report never comes. The reconciliation team chases it and learns the person left some time ago. Or a manager receives an approval request for a name they do not recognise.

Other signals are worth watching for:

• Unreconciled transactions clustering under a small set of cardholders
• Recurring charges from the same merchant with no matching receipt
• Cards with no activity at all, which often belong to people who have gone
• Approval chains that route to managers outside the cardholder's current department

The most reliable check is a straight comparison. Pull the list of active cards from the issuer and match it against current employees and their present cost centres. Every mismatch is either a leaver, a mover, or a data error, and each needs a different response.

Fixing the open accounts

Cancel the card first, then investigate. Delaying deactivation while working out whether charges were legitimate only lets the exposure grow.

Next, sort the post-departure charges. Some will be genuine business costs, such as a subscription the team still uses. Those need a new owner and a new payment method. Others will be disputable with the issuer. When the issuer accepts a dispute, record the credit against the original charge so the ledger and the statement agree. Where a former employee made personal purchases, the amount becomes a debt owed by that individual. Contact them, agree the balance, and record any adjustment when terms are settled or written off. Keep the correspondence, because recovery disputes depend on it.

For movers, reset the limit to match the new role and repoint approvals to the current manager. Ask whether the card is still needed at all.

Fixing the cause

The lasting fix is to make cancellation an event, not a memory. When HR records a leaving date or a transfer, that record should notify the card administrator automatically, or trigger the change directly through the issuer's interface where one exists. A manager's checklist can stay as a backup. It should not be the control.

Alongside that, run the active card list against the HR record on a regular cycle. Assign the review to someone outside the card administration team so the person checking is not marking their own work.

Policy needs a small amendment too. State that limits are reviewed on any role change, not only on request. State who owns recurring charges when a cardholder leaves. Without that line, subscriptions drift.

Finally, decide how unused cards are handled. A card with no spend over an agreed period should be flagged for deactivation unless its holder justifies keeping it.

Questions to ask the people who run it

The documented process and the lived one often differ. These questions tend to surface the gap:

• When someone leaves, how does the card administrator actually find out? Who tells them, and through what channel?
• Has a card ever been found active for a former employee? How was it discovered?
• What happens to subscriptions on a leaver's card? Who decides whether they continue?
• When a person moves teams, does anyone look at their card limit or approver?
• Who reconciles the active card list against the employee list, and when did it last happen?
• Are there cards held by contractors or temporary staff who sit outside the main HR system?
• When the issuer refunds a disputed charge, who records it and where?
• How are amounts owed by former employees chased, and who signs off on writing them off?

Listen especially for workarounds. A shared spreadsheet of leavers, a monthly email from a friendly HR contact, or a manager who always remembers: each one points to where the formal control is missing.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.