Accounting
Financial Management
Spend Management
Travel and Expense Management
Corporate Card Reconciliation: Receipts, Coding and Close
Last updated: October 8, 2026 · Independent guide · We do not sell rankings or coverage.
Corporate card reconciliation is the monthly process of proving that every charge on the card issuer’s statement has a receipt and business purpose, is coded to the right general ledger account, and that the card liability in your GL agrees to the statement balance. For a mid-sized US company it runs in seven stages, from setting the cutoff to clearing exceptions, and most of the delay comes from missing receipts and late coding rather than from the balance check itself.
The corporate card reconciliation process in seven stages
- Set the cycle and cutoff. Align the card statement close date with your month-end and decide how you will accrue charges that fall between them.
- Capture receipts and business purpose. Cardholders attach documentary evidence and a reason for each charge within a set number of days.
- Code each transaction. Assign the GL account and dimensions (department, class, location, project), and flag prepaids, fixed assets and personal charges.
- Review and approve. A manager approves the spend and finance reviews policy exceptions.
- Post to the general ledger. Approved transactions post as expense debits against a card liability account.
- Reconcile the statement to the GL. Agree the card liability balance to the statement ending balance and explain every reconciling item.
- Resolve exceptions and sign off. Dispute errors with the issuer, recover personal charges, and have a reviewer sign the reconciliation.
How we researched this
We reviewed the vendor guides that rank for this topic (DATABASICS, Volopay, Paylocity, Hyperbots); none cites the IRS substantiation rules or lists prices. We then checked IRS Publication 463, the accountable plan regulation in the eCFR, QuickBooks Online, NetSuite, Ramp, Brex and Expensify documentation, and the Ramp, Brex, BILL and Navan pricing pages on October 8, 2026.
Who does what: stage table
This RACI-style summary assumes a controller, an expense team and a staff accountant. Smaller teams combine roles, but the preparer and reviewer of the final reconciliation should differ.
| Stage | Responsible | Accountable / approves | Key output |
|---|---|---|---|
| 1. Cycle and cutoff | Staff accountant | Controller | Close calendar, accrual of unposted charges |
| 2. Receipts and purpose | Cardholder | Cardholder’s manager | Receipt attached to each transaction |
| 3. Coding | Cardholder or expense team | Staff accountant | GL account and dimensions per line |
| 4. Review and approval | Manager | Expense or AP lead | Approved report, exception log |
| 5. Posting | Expense team or sync | Staff accountant | Expense entries against card liability |
| 6. Statement-to-GL reconciliation | Staff accountant | Controller | Signed reconciliation with reconciling items |
| 7. Exceptions and sign-off | Expense team | Controller | Disputes filed, personal charges recovered |
Stage 1: Set the cycle and cutoff
The controller owns the calendar. Inputs are the statement close date and your close calendar. If the statement closes on the 25th, charges from the 26th to month-end belong in the current period but will not appear on the statement you reconcile, so you need a rule for them.
The usual control is to accrue charges that have posted to the card platform but not yet to the GL, using the platform’s transaction export as support. What goes wrong: teams reconcile to the statement and leave several days of spend out of the month.
Stage 2: Capture receipts and business purpose
The cardholder is responsible, and the input is the card transaction itself. The output is a receipt and a short business purpose attached to that transaction. The deadline you set should reflect IRS rules, because those rules decide whether the arrangement counts as an accountable plan.
IRS Publication 463 says documentary evidence such as receipts is not required for an expense, other than lodging, of less than $75, and that adequate evidence shows the amount, date, place and essential character of the expense (IRS Publication 463, April 30, 2026). A lodging charge needs a receipt at any amount.
Timing matters too. Under the fixed date safe harbor in Treasury Regulation 1.62-2(g), an expense substantiated within 60 days after it is paid or incurred, and excess amounts returned within 120 days, are treated as occurring within a reasonable period (eCFR, 26 CFR 1.62-2). Publication 463 adds that nonaccountable plan reimbursements are reported as pay.
What goes wrong: late receipts, vague purposes such as “meeting”, and hotel folios without itemized charges.
Stage 3: Code each transaction
Coding is done by the cardholder or the expense team and checked by a staff accountant. The input is the receipt plus your chart of accounts and dimension list. The output is a GL account, department, class or location, and project where relevant, on every line.
Three coding decisions cause most rework. Annual software subscriptions charged to a card are often prepaid assets, not period expense, and belong on your prepaid expense amortization schedule. Equipment above your capitalization threshold goes to fixed assets. Personal charges go to an employee receivable, not to an expense account.
Controls that work: merchant category defaults that pre-fill the GL account, locked dimension lists so cardholders cannot invent values, and a rule that anything over a set amount is reviewed by accounting before posting.
Stage 4: Review and approve
The cardholder’s manager approves business need, and the expense or AP lead reviews policy exceptions such as split transactions, alcohol, weekend spend or merchants on a blocked list. The output is an approved transaction set and an exception log.
The key control is that nobody approves their own spend, including executives, whose charges should go to the CFO or audit committee chair. What goes wrong: managers approve in bulk without opening receipts.
Stage 5: Post to the general ledger
Posting is done by the expense team or by an automated sync from the card platform, and checked by a staff accountant. The input is approved, coded transactions. The output is entries that debit expense (or prepaid, fixed assets or employee receivable) and credit a corporate card liability account. The table below shows the standard entries.
| Account | Debit | Credit | Note |
|---|---|---|---|
| Travel, meals, software and other expense accounts | Charge amount | By department, class and project | |
| Corporate card liability | Charge amount | One account per card program | |
| Employee receivable | Personal charge | Cleared when the employee repays | |
| Corporate card liability / Cash | Payment to issuer | Payment to issuer | Debit liability, credit cash |
Platforms differ in how they post. Expensify, for example, documents that with daily settlement the amount moves to a clearing account and then to a liability account when the expense is exported, while monthly settlement moves the amount straight from checking to the liability account (Expensify Help, no date shown). A clearing account is one more balance to reconcile.
Stage 6: Reconcile the statement to the GL
A staff accountant prepares and the controller reviews. The inputs are the issuer statement, the card liability account detail and the card platform’s transaction report. The output is a signed reconciliation where the statement ending balance, plus or minus listed reconciling items, equals the GL balance.
In QuickBooks Online you enter the statement ending balance and ending date, check off transactions, and finish only when the difference is $0.00 (Intuit, August 5, 2026). NetSuite handles bank and credit card statements through its Match Bank Data and Reconcile Account Statement pages (Oracle NetSuite, no date shown).
Illustrative example (constructed numbers). Your statement closes on September 30 with an ending balance of $48,920. The GL card liability shows $47,310. You find $1,450 of approved transactions not yet synced from the card platform, a $260 charge posted twice in the GL, and a $420 personal charge that was coded to employee receivable but never posted. The reconciliation reads: GL $47,310 plus $1,450 unsynced plus $420 unposted personal charge minus $260 duplicate equals $48,920. You book the three corrections and the difference becomes zero.
What goes wrong: unexplained differences carried forward as “timing” and reconciliations that are prepared but never reviewed.
Stage 7: Resolve exceptions and sign off
The expense team works the exceptions and the controller signs off. Inputs are the exception log, missing-receipt list and unmatched items from Stage 6. Outputs are disputes filed with the issuer, personal charges recovered through payroll deduction or repayment, missing-receipt affidavits where policy allows them, and a dated reviewer sign-off.
A common control is to suspend a card when receipts are outstanding past the deadline. Card exceptions also feed your wider close, so tie them to the same calendar you use for accounting close automation.
Metrics to track
Track these monthly by department. Set targets from a few months of baseline data.
- Receipt compliance rate: transactions with a receipt attached divided by transactions requiring one.
- Days to substantiate: average days from transaction date to receipt and purpose, compared with your internal deadline and the IRS 60-day safe harbor.
- Coding accuracy: share of lines reclassified by accounting after posting.
- Unreconciled difference: statement balance minus GL balance before adjustments, and its age.
- Card program days in close: business days from period end to signed card reconciliation.
How software supports each stage
Accounting systems such as QuickBooks Online and NetSuite cover Stages 5 and 6 natively: a card liability account, statement matching and a reconciliation report. They do little for receipt capture, coding at the point of spend or approvals, which is where spend management platforms come in. For wider automation, see our guide to AI general ledger automation.
For Stage 2, Brex documents receipt capture by app, SMS, email forwarding and integrations, and says it verifies a receipt when two of date, amount and merchant match; it also says only receipts less than two months old match automatically (Brex, no date shown). For Stage 6, Ramp documents a NetSuite reconciliation report that compares Ramp records with NetSuite and flags mismatches, records not synced, records missing on either side and period shifts (Ramp, no date shown).
The table below lists published prices for card and spend platforms that publish them. Each issues its own card, so the price assumes you move your card program. SAP Concur and Emburse were left out because we could not confirm published US prices.
| Vendor and plan | Published price (checked October 8, 2026) | Relevant inclusions | Limitation to check |
|---|---|---|---|
| Ramp Free | $0 per user per month | Auto-receipt collection and matching, QuickBooks Online and Xero | NetSuite and Sage Intacct listed under Plus |
| Ramp Plus | $15 per user per month plus a platform fee based on team size | NetSuite and Sage Intacct, AI coding, multi-entity | Platform fee amount not shown on the plan card |
| Brex Essentials | $0 per user per month | Accounting integrations, auto-generated receipts, up to two entities | Customizable ERP integrations listed under Premium |
| Brex Premium | $12 per user per month | Advanced receipt data extraction, custom ERP integrations, multi-entity | Billing terms not stated |
| BILL Spend & Expense | $0 per user per month | Corporate cards, budgets, expense tracking | Credit lines of $1,000 to $5M subject to approval |
| Navan Business | Expense free for first 5 users, then $15 per expensing user per month | Travel and expense in one platform | For companies up to 300 employees; larger ones need a quote |
Sources for the table: Ramp pricing, Brex pricing, BILL pricing and Navan pricing, all with no date shown on the page. For a wider look at policy rules inside these tools, see our article on AI expense management software.
Related guides
- General Ledger Reconciliation: Steps, Frequency and Review
- Month-End Close Checklist Template (2026)
- Accrued Expenses Journal Entry: Examples and Reversals
Frequently asked questions
How often should corporate cards be reconciled?
At least monthly, as part of the close, with the statement-to-GL reconciliation signed by a reviewer. High-volume programs often code and approve weekly so that month-end only handles exceptions. Receipt collection should run continuously against a deadline shorter than the IRS 60-day safe harbor.
Does the IRS require a receipt for every corporate card charge?
No. IRS Publication 463 says documentary evidence is not needed for expenses other than lodging of less than $75, though you still need a record of amount, date, place and business purpose. Lodging needs a receipt at any amount.
What account do corporate card charges post to?
Each charge debits the relevant expense, prepaid, fixed asset or employee receivable account and credits a corporate card liability account. Payments to the issuer debit the liability and credit cash. Some platforms also use a clearing account, which then needs its own reconciliation.
What happens if an employee puts a personal charge on the corporate card?
Code it to an employee receivable, not to expense, and recover it through repayment or a payroll deduction your policy allows.
Do I need a separate spend management platform if I use NetSuite or QuickBooks Online?
Not for the balance reconciliation, which both systems handle natively. A spend platform helps when receipt capture, coding at the point of spend and approvals are the bottleneck, which is common once you have more than a few dozen cardholders.
Sources
- IRS, Publication 463, Travel, Gift, and Car Expenses (for 2025 returns), April 30, 2026. irs.gov
- eCFR, 26 CFR 1.62-2, Reimbursements and other expense allowance arrangements, last amended July 26, 2016, checked October 8, 2026. ecfr.gov
- Intuit, Reconcile an account in QuickBooks Online, August 5, 2026. quickbooks.intuit.com
- Oracle NetSuite, Reconciling Bank and Credit Card Statements, no date shown. docs.oracle.com
- Expensify, Expensify Card Reconciliation (vendor documentation), no date shown. help.expensify.com
- Brex, Receipts for expenses (vendor documentation), no date shown. brex.com
- Ramp, NetSuite integration: Reconciliation report (vendor documentation), no date shown. support.ramp.com
- Ramp, Pricing, no date shown, checked October 8, 2026. ramp.com
- Brex, Pricing, no date shown, checked October 8, 2026. brex.com
- BILL, Pricing, no date shown, checked October 8, 2026. bill.com
- Navan, Pricing, no date shown, checked October 8, 2026. navan.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
