Centrally Billed Account (CBA)
Centrally Billed Account (CBA) — Key Takeaways
- A centrally billed account consolidates eligible charges on an account that the organization pays, instead of assigning the bill to an individual employee.
- Central billing consolidates payment, but reconciliation still depends on booking details such as the traveler, trip, cost center, and booking reference.
- A CBA is a billing arrangement; it isn’t the same thing as an individually billed account, corporate card, or virtual card.
- The right setup depends on which expenses belong in the central flow, who is liable, and whether finance receives enough data to allocate and audit each charge.
- Navan can connect booking, payment, and expense context.
A centrally billed account (CBA) is a company-level card or account whose eligible charges are paid by the organization rather than an individual employee. In corporate travel, it can support centrally arranged transportation or other travel bookings. Confirm expense coverage, payment terms, and liability with the provider.[1][3]
How does a centrally billed account work?
Eligible purchases are charged to the central account rather than an individual employee account, and the organization pays the central bill under its program terms.
The U.S. Department of Commerce’s 2021 Travel Policy Handbook provides one clearly defined example: its CBA is issued to a bureau or operating unit for official transportation arranged through a travel management center, and the government pays the bank directly. That public-sector definition is useful for understanding the billing model, but it shouldn’t be treated as the rule for every commercial program.[1]
What information makes a CBA reconcilable?
Finance needs enough context to connect each charge to its booking and accounting records. When evaluating a program, ask whether it supplies:
- Traveler or employee ID
- Booking or trip reference
- Cost center or project code
Mastercard says its CTA reconciliation matches enhanced travel data with financial data. ICICI Bank says its enhanced data can connect booking and card-spend details with employee ID, cost center, project code, or trip reference.[2][3] Those fields can support a reconciliation process.
Consider a hypothetical example. A travel team books an $840 flight for Jane Smith. If the booking record carries her employee ID, trip reference, and Sales EMEA cost center, finance has clear fields for matching and allocation. The example illustrates the data flow; it doesn’t prescribe fields for every CBA.
If a required field is missing, finance can leave the charge unallocated and route it to the team that owns account review under the organization’s process.
CBA vs. IBA, corporate card, and virtual card
These terms describe different combinations of billing, account ownership, and payment form.
Term | Account or billing model | Typical use | Question to confirm |
|---|---|---|---|
Centrally billed account (CBA) | Company-level account paid by the organization | Centrally arranged travel | Which charges are eligible, and what detail accompanies them? |
Individually billed account (IBA) | Account issued to an employee | Employee-managed travel-related purchases within the program | Who receives the bill, who pays it, and who is liable under the agreement? |
Corporate card in ICICI Bank’s comparison | Card issued to an individual employee | Business travel and expense purchases in that example | Which controls, limits, and repayment process apply? |
Virtual account in Mastercard’s CTA example | Digital account access; no plastic is required in this implementation | A central travel account housed at a travel agency for multiple travelers | How does the specific provider structure access and settlement? |
The Commerce handbook distinguishes a CBA issued to an operating unit from an IBA issued to an employee. ICICI Bank similarly contrasts its company-level CTA Card with corporate credit cards issued to individual employees.[1][3] Mastercard’s CTA implementation primarily runs on a virtual account, showing that a central account doesn’t necessarily require plastic.[2]
When should an organization use a centrally billed account?
A CBA may be a practical fit when:
- Travel is booked through an approved channel or travel management company.
- The organization, not the traveler, should receive and pay the consolidated bill.
- Finance can receive enough booking and accounting data to allocate each charge.
- A team owns account review and exceptions.
Central billing is a weaker fit when purchases occur across unconnected channels, finance lacks allocation data, or nobody owns exceptions. Before adoption, test a sample account export against the organization’s travel expense management process: Can finance identify the traveler, business purpose, and accounting code without manual detective work?
The agreement should also state who is liable, which expenses are permitted, and how disputed charges are handled.
How does Navan complement a centrally billed account?
For an organization evaluating central billing, the relevant question is whether its travel, payment, and expense records can stay connected.
Navan Payments supports within-policy travel booking, categorizes spend using employee roles and custom fields, and matches payment data with booking and invoice information. Those capabilities can provide business context for finance.
Evaluate the complete flow: booking, policy controls, payment, data passed to finance, and exceptions. Learn more about expense management.
Frequently Asked Questions About Centrally Billed Accounts