The true statement about an individually billed account (IBA) is that it is a corporate travel account in which the traveler—not the company—holds the payment liability and receives the card statement, while the organization still books, tracks, and reports the spend. Liability, statement delivery, and reconciliation ownership all sit with the individual cardholder, even though the travel policy and data feeds belong to the company. That split is the defining feature, and nearly every other true statement about IBAs follows from it.
This explainer goes deeper than a glossary entry. It covers how the liability chain actually works, why corporate card programs split into IBA and centrally billed variants, where the model breaks at scale, and what thresholds practitioners use to decide. Numbers appear where mechanism or widely published industry practice supports them. Where the evidence base is thin—vendor surveys, for instance—the limits are stated rather than papered over.
Liability Mechanics Inside an IBA
An IBA is best understood as a three-party contract. The card issuer extends credit to the employee. The employer signs a separate commercial agreement that defines spend policy, data sharing, and sometimes a corporate guarantee. The travel management company or expense platform sits between them, ingesting transaction feeds for reporting. The employee's personal credit line carries the balance; the employer's obligation is policy-based reimbursement, not card repayment.
That structure explains the two-step flow. The issuer bills the employee directly, typically at the same cycle as a consumer card. The employee then files an expense report, and the company reimburses through payroll or accounts payable. Two settlements occur where a centrally billed account (CBA) has one. Each step adds latency and a failure point: a missing receipt stalls reimbursement, and a stalled reimbursement strains the traveler.
The mechanism matters because it changes who absorbs risk. If the company-issued card is lost and fraud occurs before the freeze, the issuer's zero-liability policy generally protects the cardholder—but the float and the dispute paperwork land on the employee. In a CBA, those burdens sit with the program administrator. Here is the plain version: in an IBA, the employee is the bank's customer and the company is the auditor.
Corporate card programs grew from this base. Early iterations in the 1980s were essentially consumer cards issued under corporate agreements, with individual liability as the default because issuers had no clean way to underwrite a whole company's travel spend. Central billing emerged later as issuers built corporate liability products. The IBA is therefore not a legacy quirk; it is the original architecture, and many programs still choose it deliberately.
Quantified Context: Where IBAs Fit in Corporate Spend
Industry benchmarks place individually billed cards as the dominant model among mid-market US travel programs, with central billing more common at the largest enterprises. The reason is underwriting capacity: a 500-employee company rarely wants to post collateral or accept joint liability for USD 40,000 in monthly air spend, so individual liability keeps the issuer's exposure diversified across employees.
The float economics are concrete. An IBA traveler typically waits 30 to 60 days from swipe to reimbursement, depending on the company's expense cycle. A CBA program can settle at roughly 30 days with no employee involvement. Over a year, that difference compounds into thousands of dollars of employee-borne float per frequent traveler—a real cost that rarely appears in program comparisons.
Policy compliance data also diverge. Programs with individual liability often report higher out-of-policy booking rates, because the traveler perceives the card as personal and the reimbursement as the company's problem. Central billing tends to show tighter compliance, since the company holds the card and can block merchant categories. Neither pattern is universal; both appear in published program surveys, which rely on self-reporting and should be read as directional.
Edge Cases Where the Model Breaks
The first edge case is termination. When an employee leaves, an IBA card's balance does not automatically transfer to the company. The departing employee remains liable to the issuer for charges made before cancellation, and the company's reimbursement obligation survives the exit only if policy and local law say so. Programs that fail to cancel cards at offboarding accumulate stranded balances, and reconciliation becomes a collections problem.
The second is disputed charges. In an IBA, the cardholder must dispute fraudulent or erroneous charges directly with the issuer, often within a fixed window. The company can support the dispute with booking records but cannot file it. A CBA administrator can file centrally and net the result against the program account.
The third is credit access. An employee with a thin credit file may not qualify for the corporate card at all. Programs then issue a personal-liability card with a low limit, or the traveler pays out of pocket and seeks reimbursement. That gap disproportionately affects junior staff—a fairness problem that shows up in retention data more than in finance reports.
Warning: an IBA card left active after an employee resigns creates a personal-liability balance the company may not be able to reimburse. Warning: reimbursing an IBA charge before the issuer posts it can create duplicate-payment risk if the charge is later reversed. Warning: commingling personal and business spend on an IBA card complicates audits and can void policy protections. Warning: assuming the company's corporate agreement shields the employee from issuer collections is a common and costly error.
Misconceptions That Survive in Program Docs
The most persistent misconception is that IBA and CBA differ only in who pays the bill. They differ in who holds legal liability to the issuer, who can dispute charges, whose credit is underwritten, and who owns cancellation at offboarding. Finance teams that treat the models as a payment preference miss the contractual layer, and that lapse surfaces during audits.
A second misconception holds that IBAs are inherently less compliant. The compliance gap is real in survey data but is a function of program design, not the billing model itself. A well-built IBA with pre-trip approval, merchant category controls, and automated receipt capture performs comparably to central billing. The model sets the liability default; it does not set the control environment.
A third is that individual liability means the company has no exposure. In practice, most IBA programs include a corporate guarantee or a reimbursement policy that creates indirect exposure. The traveler is liable to the bank; the company is liable to the traveler. That chain is exactly what auditors test.
Comparison: IBA Against Alternative Billing Models
| Feature | Individually billed (IBA) | Centrally billed (CBA) | Hybrid / corporate liability |
|---|---|---|---|
| Liability to issuer | Employee | Company | Company or shared |
| Statement recipient | Employee | Program administrator | Company |
| Dispute filing | Cardholder | Administrator | Administrator or cardholder |
| Credit underwriting | Individual employee | Corporate entity | Corporate entity |
| Offboarding risk | Card must be cancelled per employee | Single account closure | Per-card controls |
| Typical fit | Mid-market, distributed teams | Large enterprise, high spend | Programs migrating between models |
The hybrid row deserves a note. Many issuers now offer corporate-liability cards with individual reporting, which blurs the categories. When a vendor claims an IBA "with corporate backing," read the cardholder agreement, not the marketing sheet. The liability clause is the answer.
Timeline: Lifecycle of an IBA Transaction
| Stage | Typical timing | What happens |
|---|---|---|
| Authorization | Day 0 | Issuer approves against employee's credit line |
| Posting | 1 to 3 days | Transaction settles to employee statement |
| Statement | Monthly cycle | Employee receives bill; company sees feed |
| Expense report | 3 to 30 days | Traveler submits receipts and coding |
| Reimbursement | 7 to 30 days after report | Company pays employee via payroll or A/P |
| Dispute window | Up to 60 days from statement | Cardholder files with issuer if needed |
| Charge-off risk | About 180 days past due | Unpaid IBA balance can affect employee credit |
The reconciliation of these timings matters. A program that reimburses in 7 days but whose issuer bills in 30 days effectively gives the employee a short credit buffer. A program that reimburses in 30 days forces the employee to float the balance for a full cycle. Finance teams should align reimbursement timing to the issuer cycle, not to payroll convenience.
Practical Actions and Thresholds
Program selection usually comes down to a few explicit tests. Run them before choosing a model, and rerun them annually.
If monthly travel spend exceeds roughly USD 50,000 and the company can post collateral or accept corporate liability, evaluate CBA first. If more than 30 percent of travelers have thin credit files, an IBA-only program will fail; plan for a hybrid or a prepaid alternative. Set offboarding cancellation within 24 hours of termination notice, and reconcile final statements within one billing cycle. Align reimbursement timing to within 14 days of the issuer statement date to limit employee float. Require receipt capture at booking, not at reimbursement, to cut dispute volume in half. Audit liability clauses annually; issuers change terms, and the cardholder agreement, not the program summary, governs.
These thresholds are operational rules of thumb drawn from published program guidance and practice, not regulatory mandates. Treat them as starting points for your own cost model.
Limits of What Can Be Concluded
The evidence base for billing-model comparisons is thinner than vendor content suggests. Most published benchmarks come from industry surveys with self-selected samples, and card issuer program terms vary by country and contract. Specific figures for compliance rates, float costs, and dispute volumes should be verified against your own issuer agreement and expense data before any program decision. Mechanisms described here are stable; the numbers around them are not.
This article is general educational information about corporate billing models, not a legal, tax, financial, or insurance opinion. Cardholder agreements, reimbursement policy, and employment law vary by jurisdiction. Consult a qualified local professional—and your issuer's contract terms—before making program decisions.