Where corporate credit card management breaks down

Corporate card programmes usually break where responsibility passes between HR, line managers, the card provider and accounts payable. The costliest failures are cards left active after people leave, limit changes granted outside policy, and merchant credits that never get matched. Each one leaves a trace in statements and approval records.

Policy that cannot be applied

Most card policies are written once and then interpreted differently by every approver. Limits get set by job grade on paper. In practice, they are set by whoever shouts loudest. When the policy lacks a clear owner, exceptions pile up quietly until audit finds them.

The giveaway is inconsistency. Look at cardholders in similar roles and compare their limits and merchant category blocks. Wide variation with no recorded reason means the policy is decorative. Another sign: approvers asking finance what the rule is before every decision.

Requests and ordering

The request stage fails at the handoff between the manager who approves and the administrator who places the order with the bank. Forms arrive missing a cost centre or a signed cardholder agreement. The administrator chases. The new starter waits and borrows a colleague's card meanwhile.

That borrowing is the real damage. It breaks the link between cardholder and spend, and nobody reverses it once the new card arrives. Check for requests returned for missing information, and for charges on a card that fall outside the holder's normal pattern while a colleague's order sits pending.

Ordering also breaks when the card provider's portal and the internal request system hold different data. Names, addresses and default cost codes drift apart. Statements then land on the wrong ledger account and need manual recoding.

Limit changes

Temporary increases are where control slips most. Someone travels for a conference, gets a higher limit approved by email, and the limit never comes back down. The approval lives in an inbox. The provider portal shows only the current figure.

To detect this, compare current limits on the provider side against the last approved limit in the internal record. Any card whose limit exceeds its approval, or whose approval cannot be found, is evidence. Repeated increase requests from the same cardholder suggest the base limit is wrong for the role.

Statements, disputes and credits

Account maintenance is where rework concentrates. Cardholders submit receipts late, code expenses to whatever looks closest, or skip the explanation entirely. Approvers sign off batches without opening them.

Disputes create a separate mess. A cardholder raises a disputed charge with the bank, the bank issues a provisional credit, and the original charge has already been coded and approved. When the credit posts, nobody links it back. The ledger ends up with an expense and an unexplained credit sitting in different accounts. Merchant refunds behave the same way.

Unmatched credits on the card clearing account are the clearest signal. So is a clearing account that never quite reaches zero after reconciliation, or one that only balances after a manual journal labelled as a correction.

Cancellation when people leave or move

This is the handoff most programmes get wrong. HR processes a leaver. Nobody tells the card administrator, or the message arrives after the last working day. The card stays live. Recurring subscriptions keep charging it.

Internal transfers are worse because nothing triggers at all. A buyer moves into a non-purchasing role and keeps a high limit with broad merchant access.

Compare the active card list against the current HR roster and job titles. Cards held by leavers, or spend posted after a termination date, show the handoff has failed. Recurring charges with no owner to approve them point the same way.

Workarounds that become the process

Watch for the shared departmental card. It usually starts as a fix for slow ordering and ends as a card nobody personally answers for. Also watch for split transactions, where a purchase over the single transaction limit gets broken into smaller charges at the same merchant on the same date. That pattern means either the limit is too low or someone is avoiding procurement. Both need fixing, and they need different fixes.

Another common workaround is finance staff recoding cardholder submissions themselves to hit the close. It keeps the books clean while hiding the fact that coding guidance has failed.

Questions to ask the people who run it

The documented process and the lived one diverge here more than most. Ask these directly:

• When someone leaves, how does the card administrator actually find out?
• Where are temporary limit approvals kept, and who reverses them?
• Which cards are used by more than one person?
• What happens to a refund or dispute credit after it posts?
• How often do approvers send a statement back, and why?
• Who fixes miscoded transactions before close, and does the cardholder ever hear about it?
• Are there cards the administrator would cancel tomorrow if allowed?
• What do new starters use to pay for things before their card arrives?

The answers to the last two questions often reveal more about control gaps than any policy review.

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.