Your corporate card statement just landed with 340 charges from 22 employees, and your month-end close is in four days. Somewhere in that list is a duplicate hotel charge, a software renewal nobody approved, three personal purchases, and a refund that posted without any reference to the original payment. Every one of them that you miss becomes either a lost deduction, a misstated expense, or an awkward conversation.
Corporate card reconciliation is the monthly discipline of matching each of those charges to a receipt, a business purpose, and the right account in your books — before the books close. Done well, it takes a few focused hours. Done late, it becomes a forensic dig through faded memories and expired card feeds. Here is a workflow that keeps it in the first category.
How Corporate Card Reconciliation Differs From Ordinary Card Reconciliation
Reconciling your own business credit card means matching one statement against your own memory. Corporate card reconciliation means matching many cardholders' charges against other people's memories, which decay fast. That difference shapes everything about the process:
- The cardholder knows what the charge was; you do not. A $412 charge from "SQ *METRO" means nothing to the bookkeeper but is instantly obvious to the employee who bought team lunch. Reconciliation has to route each charge back to its cardholder for identification.
- Every charge needs an owner, a receipt, and a code. Not just "matched to the statement" but attributed to a person, supported by documentation, and coded to the right expense account and department or project.
- Personal charges and refunds are first-class cases, not edge cases. With twenty people carrying your cards, accidental personal use will happen every few months, and vendor credits post constantly. The workflow must handle both routinely.
Think of it as expense-report review and bank reconciliation fused into one process: the statement proves the money moved, and the cardholder proves why.
The Monthly Workflow, Step by Step
Pick a fixed cadence and hold it. Many organizations require every transaction to be reconciled and approved within 30 days, with weekly reconciliation as the recommended habit. For a small business, a practical rhythm is: cardholders submit their charges weekly, and accounting reconciles the full statement once a month before close.
1. Pull Every Cardholder's Activity Into One Place
Start with the complete transaction feed: every charge, credit, fee, and adjustment for every card on the account, for the statement period. If your issuer offers a transaction feed into your accounting system, use it — manual CSV imports are where charges get silently dropped. Confirm the feed is complete by comparing its total against the statement total before you touch individual lines.
If an employee also paid for business items out of pocket and expects reimbursement, keep those on a separate expense-report track. Mixing reimbursements into card reconciliation is how charges get double-counted: once on the card feed, once on the reimbursement.
2. Collect a Receipt for Every Charge
Ask every cardholder to attach a receipt or invoice to each of their charges, plus a one-line business purpose: what was purchased and why. "Client dinner with Acme renewal team" is a business purpose; "dinner" is not.
The IRS recordkeeping rules are the floor here, not the ceiling. You generally need documentary evidence — receipts, canceled checks, or bills — showing the amount, date, place, and essential character of each expense. Documentary evidence is not strictly required for expenses under $75 except lodging, which always needs a receipt. But that exception only excuses the receipt; you still need a record of the amount, time, place, and business purpose. Most small businesses sensibly require receipts for everything, because a uniform rule is easier to enforce than a threshold, and card-issuer feeds already supply the amount and date.
Set a submission deadline with teeth. A common pattern: charges unsubmitted after 30 days trigger reminders, and accounts with long-unreconciled charges get suspended until the cardholder catches up. The point is not punishment; it is that a three-month-old charge is nearly unidentifiable, while a three-day-old one takes ten seconds.
3. Match, Verify, and Code Each Charge
For each line on the feed, confirm three things:
- It matches the receipt. Same vendor, same amount, same date (allowing a day or two for posting lag). Flag duplicates, split shipments billed separately, and foreign-currency charges where the posted amount differs from the receipt.
- It was appropriate. The purchase fits company policy and the cardholder's authority. A $2,000 software renewal on a card with a $500 single-purchase limit is a policy exception even if the software is legitimate.
- It carries the right coding. Verify the expense account, department, client, or project code. "Office supplies" versus "client-billable travel" is a coding decision the cardholder's one-line description should make obvious.
A supervisor or manager should then approve the coded charges — someone who can judge whether the spend was appropriate, not just whether the math ties. That second pair of eyes is the control that catches both honest miscoding and quiet misuse.
4. Handle Refunds and Credits Deliberately
Refunds are where reconciliation most often goes wrong, because a credit on the feed carries no pointer to the charge it reverses. A $189 credit from an airline could offset last month's ticket, a fee from March, or a charge on a different cardholder's card.
For each credit, find the original charge and net them against each other in the same expense account. Do not book vendor refunds as miscellaneous income: that overstates both your expenses and your revenue, and it misstates category totals your tax return and your management reports rely on. If a credit arrives a month after the original charge already closed, book it against the same account in the current period rather than reopening the prior month — and note the cross-period link so the next reviewer does not "find" the same credit twice.
Partial refunds deserve the same care. A hotel that refunds one night of a five-night stay, or a supplier that issues a short-shipment credit, should reduce the original expense line, not appear as a standalone windfall.
5. Flag Personal-Use Charges and Get Repaid
Sooner or later someone will put a personal purchase on a company card — usually by grabbing the wrong card at checkout. Treat it as a routine workflow, not a scandal, but treat it promptly:
- Book it as an employee receivable, not an expense. A personal charge is money the employee owes the company. Recording it to "Employee advances" or "Due from employees" keeps it out of your deductions and makes the outstanding balance visible.
- Collect repayment quickly. Common methods are a personal check from the employee or a payroll deduction. If you use payroll deduction, get written authorization from the employee first — several states restrict deductions from wages without consent, and a signed cardholder agreement at card issuance covers this cleanly.
- Do not let it linger. An unrepaid personal charge sitting in receivables for months invites exactly the wrong question in an audit: was this really a loan, or compensation that should have been on a W-2? Clear it within the same cycle whenever possible.
Deliberate misuse is a different matter and belongs in your card policy: define what happens on a first offense versus a pattern, who reviews it, and when card privileges are revoked. Having that written down before you need it is what separates a policy from a reaction.
6. Approve, Post, and Close
Once every line is matched, coded, credited, or flagged, route the package for final approval and post it to the general ledger. Then perform the control total check: the sum of posted charges minus credits, plus fees and interest, must equal the statement balance. If it does not, something was skipped or double-counted — find it now, not during the year-end close when the card feed for the period may no longer be adjustable.
File the package — statement, receipts, approvals — where it can be retrieved by period. Digital attachment to the accounting record beats a shared-drive folder, which beats a shoebox, but any retrievable system satisfies the requirement.
Why the Deadlines Are a Tax Issue, Not Just Tidiness
The reconciliation timetable connects directly to the IRS accountable plan rules, which are what keep employee expense handling tax-free. For reimbursements and allowances to stay non-taxable to the employee and deductible to you, the arrangement needs three things: a business connection for the expense, adequate substantiation by the employee, and the return of any excess amounts.
"Timely" has safe harbors worth building your deadlines around: substantiation within 60 days of the expense, and return of excess reimbursements within 120 days. Miss those windows systematically and the arrangement starts to look like a nonaccountable plan — at which point reimbursements become taxable wages subject to income tax withholding and payroll taxes. Your 30-day reconciliation rule is not bureaucratic zeal; it is the habit that keeps you comfortably inside the 60-day line with margin to chase stragglers.
The same logic applies to unrepaid personal charges. A personal purchase the company paid for and never collected is, economically, extra compensation. Prompt repayment keeps the books' story — a brief advance, repaid — matching reality.
Common Discrepancies and What They Usually Mean
- Missing receipts. The most common gap. Send the cardholder the charge details while memory is fresh, and keep a formal exception process — a signed missing-receipt affidavit stating amount, vendor, and business purpose — for the genuinely lost ones. An affidavit used twice a year is a control; one used twice a week is a hole.
- Duplicate charges. Pending authorizations that later post as a second line, or vendors that charge a deposit and then the full amount. Match against receipts before assuming fraud; most duplicates resolve to authorization holds or deposit-then-final billing.
- Charges in the wrong period. Statement cutoffs split travel arbitrarily — the hotel posts Tuesday, the rental car Thursday. Reconcile to the statement period for the card account, but code travel to the trip for management reporting so one trip's cost stays together.
- Foreign-currency differences. The receipt shows euros; the feed shows dollars plus a conversion fee. Book the converted amount to the expense and the fee to bank charges, and do not burn an hour reconciling half a percent of rate movement.
- Unidentified small charges. Subscriptions, app-store purchases, and domain renewals with cryptic descriptors. Maintain a shared register mapping descriptors to owners ("APL*ITUNES 855-xxx — design team's stock assets") so each month's mystery charges shrink.
- Credits with no matching charge. Refunds for purchases made before the current feed window, or goodwill credits. Research them rather than parking them in a suspense account indefinitely; a suspense balance that only grows is a write-off waiting to be discovered.
When a charge looks like a genuine vendor error — billed twice, wrong amount, services never rendered — contact the vendor first. Most billing errors resolve faster that way than through the issuer dispute process, which should be the backup when the vendor will not cooperate.
Controls That Prevent the Month-End Scramble
The cheapest reconciliation is the one with little to reconcile. A few controls, set once, remove most of the monthly pain:
- Issue cards with limits that match the job. Per-transaction and monthly caps, plus merchant-category restrictions where your issuer supports them, turn policy into plumbing. The card that cannot spend $3,000 at an electronics store never generates that exception report.
- Require receipt capture at the point of spend. A phone photo taken at checkout beats a receipt requested three weeks later. Whatever your tooling, the rule is "capture now, submit weekly."
- Keep a signed cardholder agreement for every card. It should state that the card is for business use, authorize payroll deduction for unrepaid personal charges, and spell out receipt and submission deadlines. Unsigned agreements surface exactly when you need them most.
- Separate duties. The person who spends should not be the person who approves. Even in a five-person company, the owner reviewing the office manager's charges — and someone reviewing the owner's — closes the loop.
- Review the register of recurring charges quarterly. Subscriptions accumulate silently on corporate cards. A quarterly pass over repeating descriptors cancels the zombie trials and renegotiates the renewals nobody uses.
None of this requires enterprise software. A shared spreadsheet of cardholders and limits, a receipt-capture habit, and a fixed weekly submission hour will carry a small team a long way before automation earns its keep.
Keep Your Card Spend Organized From the First Swipe
Corporate card reconciliation is really bookkeeping hygiene with a deadline: every charge attributed, every receipt filed, every refund netted, every personal purchase repaid. The businesses that struggle with it rarely have a tools problem — they have a timing problem, letting four weeks of other people's spending pile up until nobody remembers what half of it was.
Tracking card spend in plain-text accounting makes the discipline visible: each charge is a dated transaction with its receipt and business purpose attached, employee advances are explicit balances rather than forgotten favors, and the month-end control total is a query instead of a dig. Beancount.io gives you that transparency with version-controlled books you own outright. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
