Card programs · July 19, 2026
Corporate card reconciliation: a step-by-step process for finance teams
Corporate card reconciliation means matching every charge on the card statement to a receipt and the correct general ledger account, then confirming the statement total agrees with your books. Done monthly, it catches missing receipts, miscoded expenses, policy violations, and the occasional bad charge before they harden into the financial record. The math is trivial. The real work is chasing documentation and deciding what each charge actually was.
Most finance teams treat reconciliation as a month-end chore that arrives all at once, a pile of transactions with no receipts and no memory attached. It does not have to be that painful. The process below is the same one whether you run five cards or five hundred; what changes with scale is how much of it you automate and how early you start. The goal is a close that is fast, a ledger you trust, and no surprises hiding in the card feed.
What is corporate card reconciliation?
Corporate card reconciliation is the process of matching every charge on a company card statement to a receipt and the right general ledger account, then confirming the statement total agrees with what was recorded in your books. It verifies that each transaction is real, business-related, correctly coded, and backed by documentation. Most teams do it once a month, aligned with the card billing cycle and the month-end close. When it is done well, the payoff is accurate books, clean audits, and unauthorized spend caught while it is still small.
The reconciliation process, step by step
Six steps, in order. The first two are mechanical and increasingly automated. The middle two are where judgment lives. The last two are the close itself.
Swipe the table sideways to compare all columns.
| Step | What you do | What you are checking for |
|---|---|---|
| 1. Gather the statement | Pull the closing statement and the raw transaction export for the period | A complete list of every charge, credit, and fee |
| 2. Import into the ledger | Load the transactions into your accounting system or reconciliation tool | Every charge landed, nothing dropped or duplicated on import |
| 3. Match receipts | Attach a receipt to each charge and chase the ones that are missing | Documentation for every line, amounts that agree with the receipt |
| 4. Code and review | Assign each charge to a GL account and cost center, and review for policy | Right category, right department, no personal or out-of-policy spend |
| 5. Confirm the total | Check that the coded transactions sum to the statement balance | The books and the statement agree to the penny |
| 6. Post and file | Post the journal entries and archive receipts with an audit trail | A closed, documented record you can hand an auditor |
How do you reconcile a corporate credit card?
Pull the statement, import the transactions into your accounting system, then match each charge to a receipt and assign it to a general ledger account and cost center. Flag anything without a receipt or that breaks policy and chase the cardholder for it. Finally confirm the total of the coded transactions equals the statement balance, and post the entries. The work is the matching and the chasing, not the math. If your accounting tool cannot ingest the bank's raw export cleanly, it is worth taking a minute to turn the statement CSV into a QuickBooks-ready file so step two stops being a copy-and-paste job every month.
How often should you reconcile corporate credit cards?
Monthly is standard because it lines up with the card billing cycle and the close. Teams with high transaction volume or many cardholders should reconcile weekly so receipts get chased while people still remember the purchase and backlogs never build. Waiting a full quarter is the common mistake: by then receipts are lost, memories are gone, and a bad charge has been sitting on the books unnoticed. The right cadence is the one that keeps the pile small enough that no single reconciliation feels like an event.
What breaks reconciliation, and how to prevent it
Almost every painful close traces back to the same handful of causes. Missing receipts are the biggest: a charge with no documentation cannot be verified, and the longer you wait to ask for it, the less likely you are to get it. Miscoded charges are next, where a real expense lands in the wrong account and quietly distorts a department's numbers. Then come the genuine problems, a duplicate charge, a subscription that renewed at a higher price, a personal purchase on a company card, all of which look like ordinary transactions until someone looks closely.
The fix for all three is the same: shorten the gap between the charge and the review. Require a receipt at the point of purchase rather than at month-end. Standardize your coding so the same merchant always maps to the same account. And do not let the card feed sit untouched for three weeks, because the transactions you never look at are exactly the ones that turn into write-offs. Reconciliation is a control, and a control that only runs once a quarter is barely a control at all.
Can corporate card reconciliation be automated?
The mechanical parts can. Software can import the card feed, suggest the general ledger coding, match receipts captured by photo, and flag missing documentation automatically, which removes most of the manual data entry. What still needs a human is judgment: deciding whether a charge is legitimate, whether the coding is right, and what to do about a policy violation. Automation shrinks the work, it does not remove the review. The teams that close fastest are the ones that let the tooling do the matching and spend their own time only on the exceptions.
The problem reconciliation cannot solve on its own
Reconciliation is a look backward. However tight your process, it runs after the money has moved, which means it is a great way to record what happened and a poor way to prevent it. If a card was used for a five-figure purchase nobody approved, reconciliation is where you find out, and by then the charge has cleared and the review is a matter of clawing money back rather than catching it in flight. That lag is structural: a monthly reconciliation can only be as fast as the month.
Closing that gap is a different job from reconciliation, and the two work best together. Real-time corporate card monitoring reads the transactions as they post and raises a flag when a charge breaks a limit, a budget, or a pattern, so a questionable purchase gets a same-day conversation instead of a month-end surprise. Pair that with budget alerts by team and category and you see spend drifting toward a limit before it crosses one, not after. One honest caveat: monitoring tells you, it cannot decline a charge on a card it did not issue. What it buys is the first hour instead of the fourth week, which is the difference between a quiet word and a write-off. Reconciliation still happens at month-end, but it stops being where you learn about the bad charges for the first time. If personal charges are your specific worry, the same signals power anomaly detection on the cards you already carry, and it is worth writing the rules down first with a corporate card policy template.