Credit card reconciliation is the process of proving that every transaction reported by a card issuer is complete, supported, correctly coded, and recorded in the general ledger. For a corporate card programme, that means comparing the issuer statement or transaction feed with cardholder submissions, receipts, expense reports, accounting entries, payments, refunds, and credits.
This is broader than collecting receipts. A receipt supports a purchase, but it does not prove that the complete issuer balance has been recorded or that the card liability or clearing account agrees. Credit card reconciliation closes that control gap.
What records are compared?
| Record | What it establishes | Typical owner |
|---|---|---|
| Issuer statement or card feed | The complete transaction population, statement balance, fees, credits, and payments | Treasury or finance operations |
| Cardholder submission | Business purpose, cost centre, project, attendee, or other policy information | Cardholder and manager |
| Receipt or invoice | Vendor, date, amount, tax, currency, and evidence of the purchase | Cardholder or AP team |
| Expense platform | Approval status, policy checks, allocations, and export history | Expense administration |
| General ledger | Expense, tax, asset, liability, clearing-account, entity, and currency postings | Accounting |
| Bank payment | Settlement of the issuer balance and any timing difference between payment and posting | Treasury |
Credit card reconciliation process
- Fix the population and period. Obtain the final issuer statement or a complete transaction extract for every active card. Confirm the statement dates, account numbers, cardholders, opening balance, closing balance, and payment activity before matching individual lines.
- Load transactions without losing issuer identifiers. Preserve transaction IDs, authorization dates, posting dates, original currency, billed currency, merchant details, cardholder, fees, refunds, and credits. These fields make later duplicates and timing differences easier to investigate.
- Match supporting documents. Link each purchase to the submitted receipt or invoice and cardholder explanation. The document amount may differ from the billed amount when tax, gratuity, foreign exchange, or a partial refund is involved, so amount-only matching is not sufficient.
- Validate approval and policy. Confirm business purpose, permitted spend, required manager approval, split allocations, and treatment of any personal or out-of-policy item. The reconciliation should record the exception without inventing a justification on the cardholder's behalf.
- Verify the accounting entry. Check entity, GL account, cost centre, project, tax treatment, currency, and posting period. A fully documented transaction can still be wrong if it was charged to the wrong entity or account.
- Reconcile the control account. Prove that the opening card liability or clearing balance, plus current-period charges and fees, less payments and credits, equals the closing balance. List every reconciling item rather than forcing the ledger to agree.
- Resolve, age, and certify. Assign an owner and due date to missing evidence, coding corrections, disputed charges, and feed failures. A preparer completes the work; an authorized reviewer challenges old or material items and records approval.
Worked reconciliation example
Consider a month-end statement with an illustrative closing balance of 25,300. The ledger initially shows 24,650. The 650 difference should not be posted to a miscellaneous expense merely to make the accounts agree. Investigation may show a 400 annual card fee that was not exported from the expense platform and a 250 refund that appeared in the card feed after the accounting export. Once both items are supported and posted to the appropriate accounts, the ledger and statement agree.
The important output is not only a zero difference. The workpaper should preserve the statement, transaction-level matching, the fee and refund evidence, the correcting entries, preparer and reviewer actions, and the final account balance. Amounts and account names in this example are illustrative; the correct treatment follows the organisation's accounting policy and chart of accounts.
Common credit card reconciliation exceptions
| Exception | What to investigate | Controlled resolution |
|---|---|---|
| Missing receipt | Cardholder, merchant record, duplicate document, and policy deadline | Collect evidence or follow the approved missing-document process; do not fabricate support |
| Statement line missing from the GL | Export failure, posting-period cutoff, rejected journal, or wrong entity | Post from verified issuer data with the correct account and period |
| GL line missing from the statement | Duplicate posting, pending authorization, wrong card account, or timing | Reverse a confirmed duplicate or carry a documented timing item |
| Foreign-currency difference | Original amount, issuer rate, billed amount, fees, and posting currency | Record the supported billed amount and any separately identified fee or exchange difference |
| Refund or chargeback | Original purchase, issuer reference, merchant correspondence, and period | Link the credit to the original expense or disputed item and clear the open amount |
| Personal or out-of-policy charge | Cardholder explanation, policy, approval, and recovery status | Route through the approved recovery and escalation process |
| Duplicate transaction | Issuer IDs, authorization and posting dates, merchant, amount, and reversal status | Dispute a genuine duplicate; do not reverse a valid clearing or payment line |
| Incorrect GL coding | Business purpose, entity, cost centre, project, tax, and capital-versus-expense treatment | Prepare a supported reclassification with approval |
Statement date, posting date, and month-end cutoff
The issuer's statement cycle may not align with the accounting month. A transaction can be authorized in one period, posted by the issuer in the next, and exported to the ledger later still. The reconciliation policy should state which date drives accounting cutoff and how unbilled or pending activity is treated. The objective is consistent application and a clear explanation of genuine timing items, not automatic use of whichever date makes the account balance.
Credit card reconciliation versus receipt reconciliation
Receipt reconciliation asks whether a transaction has valid source documentation and whether the document agrees with the claim. Credit card reconciliation starts with the issuer's complete balance and proves that every charge, credit, fee, and payment has been supported and recorded. Receipt matching is one control within the wider card-account reconciliation.
Operating the process at scale
A multi-entity programme may include many issuers, statement cycles, currencies, cardholders, and accounting systems. Standardized transaction IDs, controlled mappings, exception codes, and aging rules allow the team to separate clean matches from items requiring judgment. Automation can assemble the population, match evidence, identify missing postings, and route exceptions, while authorized people retain approval over policy decisions and correcting entries.
Aetherix runs these exception and control-account workflows as part of managed reconciliation operations. See how related coding breaks are handled in the guide toGL coding errors, or review the scope of ledger reconciliation services.
Frequently asked questions
What is the purpose of credit card reconciliation?
It proves that the complete issuer balance is supported and accurately recorded, while exposing missing documents, unposted items, coding errors, policy exceptions, and unresolved credits or disputes.
How often should corporate credit cards be reconciled?
The control account should be reconciled for each reporting close and each issuer statement. High-volume programmes may match transactions and chase missing support throughout the cycle rather than waiting until month-end.
Who should review a credit card reconciliation?
An authorized reviewer who did not prepare the work should verify completeness, challenge old or unusual exceptions, and confirm that corrections and policy escalations have appropriate support.