Corporate Card Reconciliation

Corporate Card Reconciliation is the process of matching every corporate credit card transaction to the correct general ledger expense account, verifying receipts and business purpose, and resolving discrepancies before the statement closes. The work is matching each card transaction to a coded expense and a receipt, so the bottleneck is usually employee submission rather than the accounting.

Category: Expense Management SoftwareBest Expense Management Software

Month-end close includes reconciling 140 corporate cards. Thirty percent of cardholders haven't submitted receipts for the period. Finance has the transaction data from the card program, but not the GL coding and receipt documentation needed to post the expenses. Each missing receipt is an open item on the close checklist. Corporate card reconciliation is the process of matching transactions from the company's card program to receipts, business justifications, and GL codes, then posting the validated expenses to the accounting system. Unlike expense reports, where the employee starts the entry, card reconciliation starts with a known transaction: the card was swiped, the charge is on the statement, and the company has already paid for it. The employee's job is to document and code what was already spent. Corporate cards cut reimbursement processing for finance but create a different problem: the spending has happened whether or not the documentation exists. An unreconciled card transaction is more than an open item. It is a cost already incurred that can't be properly posted or categorized until the cardholder does their part.

How corporate card reconciliation works

Corporate card reconciliation usually follows a set cycle. The card program feeds transaction data to the expense management platform, either in real time or daily or weekly. Cardholders get notifications to review their transactions, attach receipts, add a business purpose, and assign GL coding (cost center, account, project). Once a cardholder submits, the manager reviews and approves. Finance then does a final review of coding accuracy and posts approved transactions to the ERP. The process usually breaks down in the middle: cardholders who submit late, or without receipts, block everything downstream. Finance can see the transaction on the card statement but can't post it without the documentation. When that affects a material number of transactions at close, finance has to choose: post with estimated coding and fix it later (creating cleanup work), accrue and wait for documentation (delaying close), or push the transaction to the next period (understating the current period). None of them is good. The root cause is almost always that card reconciliation is treated as the cardholder's personal admin task instead of a finance process with enforced deadlines.

Card feed data vs manual entry

Card feed quality matters before reconciliation even starts. A direct card program integration, where transaction data flows automatically into the expense platform, removes manual entry errors and keeps the transaction amount, merchant, and date accurate. Manual or CSV-based imports bring data quality issues (wrong amounts, duplicate entries, missing transactions) that cause reconciliation problems later. Even with a clean feed, transaction data alone isn't enough to post to the general ledger. A card statement shows a merchant name and an amount. It doesn't show the cost center, the account code, or the business purpose. That information comes from the cardholder, and without it finance can't post to the correct accounts. Merchant category codes (MCCs) from the card network give a general spend category. They can pre-fill account code suggestions or flag transactions that look inconsistent with the cardholder's role, but MCC-based coding isn't granular enough to replace cardholder judgment. The most accurate reconciliations happen when cardholders code as they spend, not in a batch at month-end. Expense platforms that surface transactions in real time and prompt coding within a few days consistently produce more accurate GL coding than those where cardholders reconcile 30 days of transactions at once.

How platforms handle it

The demo for corporate card reconciliation usually shows the clean path: the transaction appears, the cardholder codes it, uploads a receipt, and submits, the manager approves, and the ERP sync posts it. The scenarios worth testing are the exception paths. When a cardholder is on leave and their transactions aren't being reconciled, is there a delegate or admin override? When a transaction is a personal charge, can the cardholder flag it for repayment to the company, and does the platform track that liability? When the receipt doesn't match the transaction amount (common with tips or currency conversion), does the system flag the discrepancy or let it through? Also check close-readiness reporting: can finance see, by cardholder, which transactions are unreconciled, unsubmitted, or unapproved as of a given date? That view lets finance chase the right people at the right time instead of comparing card statements by hand at close.

Questions to ask

Does the card program feed transactions directly into the expense platform in real-time, or does it require manual or scheduled CSV imports?
Can cardholders submit receipts and coding on a rolling basis throughout the month, or does the platform only open a reconciliation window at period-end?
How does the platform handle transactions with missing receipts: soft flag, hard block, or escalation to a second approver?
Is there a delegate or administrative override for cardholders who are unavailable at close, and what is the audit trail for those overrides?
Can finance view a real-time reconciliation status dashboard by cardholder, showing unsubmitted, unapproved, and pending-sync transactions?
How are personal charges on corporate cards handled? Does the platform track the cardholder's repayment liability, or is that managed outside the system?

Common mistakes

The first mistake is letting cardholders submit receipts without coding guidance. When cardholders pick GL account codes and cost centers from an unrestricted list, they often code to the wrong account: meals to office supplies, software subscriptions to equipment, client entertainment to internal meetings. Finance then fixes the coding during review, which adds time to the cycle. The fix is to limit the coding options for each cardholder based on role and cost center, and to use merchant category codes to pre-suggest the most likely account. Judgment calls still happen, but the list of options shrinks and the default points to the correct code. The second mistake is treating card statement reconciliation as a month-end task instead of a continuous process. When 30 days of transactions land in a cardholder's queue on the last day of the period, quality drops: receipts go missing, business purposes get vague, and coding errors increase. Set a policy that transactions must be reconciled within a defined window (five to seven business days from the transaction date is common) and configure the expense platform to send reminders when transactions age past it.

Comparing expense tools

Expense tools separate on whether policy is enforced at the point of spend or checked afterwards by whoever reviews the report. Once corporate card reconciliation is settled as a requirement, read the Expense Management Software category guide for how the market splits, then weigh the Airbase profile against the Tipalti profile on that requirement rather than on the feature list. Our Airbase pricing breakdown records what the vendor publishes and what is quote-based. The Tipalti against Airbase comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the expense management savings calculator so the business case is written down before a vendor writes it for you.

Corporate Card Reconciliation questions

How is corporate card reconciliation different from an expense report?

An expense report documents out-of-pocket spending and creates a reimbursement obligation: the company owes the employee money. Corporate card reconciliation documents spending that has already happened on a company-funded card. The money is already spent, and the task is to add coding and documentation. Expense reports require finance to validate a claim and issue payment. Card reconciliations require finance to validate documentation for a cost that's already in the system. Some expense management platforms handle both in the same interface, but the underlying financial flow is different.

What happens to the GL when a corporate card transaction isn't reconciled by close?

The accounting treatment depends on how the card program is set up. In a corporate liability model, card transactions flow to a clearing or suspense account when the statement arrives and move to the correct expense account when reconciled. Unreconciled transactions sit in the clearing account at close, so the cost is on the balance sheet, not the P&L, until coding is complete. In a personal liability model (less common), the cardholder pays the card and submits for reimbursement, so unreconciled transactions aren't on the books at all until an expense report is submitted.

How should finance handle a cardholder who consistently fails to reconcile on time?

Escalate in stages. First, automated reminders triggered by transaction age. Second, a notice to the cardholder's manager when transactions are still unreconciled past the close deadline. Third, a card suspension process for repeat non-compliance; most corporate card programs let finance or HR temporarily suspend a card without closing the account. The consequence has to be real and applied consistently. A policy that says 'submit within 30 days' with no enforcement teaches employees that the deadline is optional.

Expense Policy Compliance, Expense Report, and Mileage Reimbursement come up in the same workflow as corporate card reconciliation, and the rest of the expense tools cluster is indexed in the finance operations glossary.