Corporate Credit Cards: What Each Role Knows and Where It Breaks

Cardholders know why a charge happened. Managers know whether it should have. The card administrator knows what the bank has been told. HR knows who is leaving. Accounting knows what is still unreconciled. Trouble starts wherever one of these facts needs to reach another role and depends on someone remembering to pass it on.

Who holds which piece

The cardholder is the only person who knows the business purpose of a transaction. They also know whether a charge was personal, whether the card is still in their wallet, and whether next month brings a trade show that will blow through their limit. Most of this lives in their head until a statement deadline forces it out.

The approving manager knows the budget and what the person is really doing in their role. That second point matters. A manager often knows about a promotion, a transfer or a resignation weeks before any system does. What they rarely see is the transaction detail. Many approve a statement as a single block, trusting that someone else checked the receipts.

The program administrator sits closest to the bank. They know every card's limit, which merchant categories are blocked, which requests are waiting, and which cards were ordered but never activated. They do not know when someone changes jobs unless told.

HR owns the leaver and transfer records. It usually has no idea who holds a card.

Accounting knows coding rules, the open liability to the issuer, which transactions are unmatched at month end, and which cardholders are chronically late. It cannot judge whether a purchase was sensible, only whether it was documented.

The issuing bank sees spend in real time. It knows about declines, fraud holds and disputes before anyone inside the business does.

Where the gaps bite

Departures

This is the classic failure. HR processes an exit. Nobody tells the card administrator. The card stays live, sometimes with a recurring subscription still billing to it, and the first anyone hears is a charge with no owner. Cancellation in the bank portal is easy. Knowing it needs doing is the hard part.

Temporary limit increases

A cardholder asks for more headroom for one trip. The administrator raises it. The request said temporary, but no date was set and no one owns the reversal. Months later the high limit is still there and has quietly become the norm for that role.

Declines

The bank declines a card at a hotel desk or a supplier checkout. The cardholder knows instantly. The administrator finds out when an angry message arrives. Whether the decline came from a limit, a blocked category or a fraud rule is visible only in the bank's system, so the first conversation is often guesswork.

Personal charges

When a cardholder admits a personal charge, it becomes money the employee owes the business. Accounting records it. The manager assumes accounting will chase it. Accounting assumes payroll will deduct it. Payroll was never told. Small amounts like this age into a receivable that nobody is collecting, and writing it off later requires an approval nobody planned for.

Policy drift

Finance writes the policy and sets approval limits without much sight of what cardholders actually buy. Cardholders then work around it. Splitting a purchase to stay under a single transaction limit is the common pattern. The bank data shows it plainly, yet accounting, which reviews coding, may never look for it.

Questions to ask the people who run it

Documented procedure and daily practice tend to drift apart in this process. These questions surface the difference.

• When someone leaves, how does the card administrator find out? Who told them last time?
• How many people can raise a limit in the bank portal, and does every change have a written request behind it?
• When a temporary increase is granted, who puts it back, and how do they remember?
• What does a manager actually look at before approving a statement?
• If a cardholder never submits receipts, what happens next, and who does it?
• Where does a personal charge go once it is flagged? Has anyone ever been asked to repay one?
• Who sees decline and fraud alerts from the bank, and how quickly do they reach the cardholder?
• Are there cards in the bank's records that nobody internally can match to a person?
• Which suppliers get paid on cards that procurement thinks are under contract?
• When the policy changed last, did cardholders hear about it from finance or from a colleague?

Ask the card administrator and a few cardholders separately. Their answers to the same question often disagree, and the disagreement is where the redesign work lives.

Before changing anything

Map the handoffs before the steps. Most failures here are not a broken task but a fact sitting with the wrong role. A leaver feed from HR to the administrator, an end date on every limit change, and a named owner for employee repayments each close a specific gap. Tooling that pulls bank data into accounting faster helps, but it cannot supply business purpose. Only the cardholder has that, and the process has to ask them for it while they still remember.

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.