What it means
A manager uses a company card for travel, software and client meals, and at month end finance sees a bank statement but not necessarily what each charge was for. Reconciliation connects the external charges with the company's records, so collect the complete card statement or feed, including every card and account, not just transactions with uploaded receipts.
Missing evidence should remain visible as an exception. Match transaction details by comparing amount, date, merchant and currency with the expense record, remembering that a card settlement date may differ from the purchase date.
Attach support, because invoices, itemised receipts and booking confirmations answer different questions and a card slip alone may not identify what was bought. Ask for business purpose too, since a meal receipt may show food and a total but not the client meeting or participants.
Code accounts and projects, because the same supplier may provide different types of expense and the cardholder or reviewer should assign the correct ledger account, tax treatment and cost centre. Zoho's corporate-card reconciliation guide describes matching statements, receipts and accounting records, then resolving exceptions, and Corpay's guide also distinguishes transaction matching from policy review and month-end close.
Both are practical vendor guidance rather than binding accounting standards, so a company should adapt the process to its cards, systems and audit needs. Reconcile totals: the opening balance plus charges, fees and other adjustments less payments and credits should explain the closing balance, and a complete set of coded expenses alone may not match the statement.
An illustrative statement check is opening balance plus charges minus credits and payments. If opening is $2,000, charges $5,000, credits $300 and payment $4,000, closing is $2,700, but confirm statement treatment of fees and foreign exchange.
Check refunds, since a hotel reversal or returned purchase should link to the original charge and an unassigned credit may hide an overstated expense. Handle foreign currency by recording the card issuer's billed amount and conversion separately when needed, because the receipt's local-currency amount may not equal the ledger charge.
Investigate duplicate submissions, where a worker uploads one receipt twice or the card feed and a manual expense report both create an expense, by comparing identifiers before posting. Separate roles: a cardholder explains the purchase, while an independent reviewer checks evidence and policy, and the same person should not approve all their own exceptions.
Do not equate a missing receipt with fraud; ask for a replacement invoice or documented explanation, then apply policy, and report suspicious or unauthorised charges to the issuer promptly under the card terms so that a dispute window is not missed. Document each exception with who reviewed it, the explanation and the correction.
In practice
Real-world examples.
Example
Finance matches a hotel card charge of $480 with an itemised invoice and the trip purpose recorded in the expense report. The charge is coded to the travel account and the right project.
Example
A returned purchase is linked to its refund credit on the next statement, so the original expense is reduced instead of left overstated. The reviewer also codes the card's annual fee as a separate line because it has no receipt.
Example
A recurring $40 software charge is questioned after its project closes. The reviewer identifies the owner, confirms the subscription is no longer needed and asks for it to be cancelled.
Formula
Calculation
Illustrative closing balance = opening balance + charges - credits - payments. $2,000 + $5,000 - $300 - $4,000 = $2,700, before other statement adjustments.
Late-payment charges and annual card fees are real statement items even without a purchase receipt, so code them separately. If the statement above also carries a $50 annual fee, the closing balance becomes $2,700 + $50 = $2,750, and the reconciliation should show that fee as its own coded line.Case study
Seen in the real world.
This entirely fictional example follows Meridian Works. Finance found a software charge without a receipt for three months. The cardholder identified an unused trial that had become a subscription, and the team cancelled it under its vendor process. Meridian recorded the prior charges and updated its review steps.
The example illustrates an exception review, not a fraud finding. Meridian also confirmed that its card clearing account was zero or explained at close, and it began listing unmatched charges, missing receipts and unresolved credits by owner and age. It watched for patterns such as repeated split transactions just under approval limits, treating a pattern as a signal to investigate and not as proof of misconduct. A clean dashboard that hid exceptions would not have counted as a successful reconciliation.
Watch out
Common mistakes.
- Treating receipt upload as proof that the expense was business-approved.
- Ignoring refunds, fees and foreign-exchange differences in the statement total.
- Closing the ledger while unexplained card charges remain hidden.
Questions
People also ask.
What is corporate card reconciliation?
Matching card statement items to expense evidence and ledger entries, then reviewing exceptions.
How often is it done?
Many teams complete a statement reconciliation monthly and review transactions more often as risk warrants.
Why does it matter?
It helps find coding errors, missing records, unwanted subscriptions and suspicious charges.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%