Credit Card Reconciliation

Definition — what it is

Credit card reconciliation is the periodic process of matching every charge on a corporate or purchasing card to a receipt, coding it to the correct job and cost code, verifying it is a legitimate business expense within policy, and approving it, so the card statement balance is fully substantiated and posted. It exists because corporate cards let employees spend company money directly, without a purchase order or an invoice, which is fast and convenient but bypasses the normal preventive controls, so reconciliation is the compensating control applied after the fact. It is not an expense report, in which the employee is reimbursed, because with a card the money has already left the company; the task is to account for spend that already happened. Reconciliation is where undocumented, personal, duplicate, and mis-coded card spend is caught, and its rigor determines whether the card is a controlled tool or an open channel of leakage.

Also known as: Corporate Card Reconciliation, P-Card Reconciliation, Card Statement Reconciliation, Purchasing-Card Reconciliation

Why it matters — what it protects

The corporate card bypasses purchase orders and the three-way match, so reconciliation is the only real control on that spend. Every charge is money already gone, and if it is not substantiated and reviewed after the fact there is no barrier at all between the cardholder and the company's cash. The discipline of the monthly reconciliation is what keeps a card program from becoming uncontrolled spending.

Card charges are job costs, and their coding drives cost-report accuracy just as invoices do. Cards are used heavily in the field for fuel, small materials, and incidentals, and when those charges are coded to a default account or the wrong job to clear the statement quickly, real project cost is misstated in a way that is small per charge and large in aggregate.

It is a primary fraud and misuse control. Personal purchases, cash-equivalent charges, split transactions to stay under limits, and charges without receipts all surface in reconciliation, and lax reconciliation lets misuse persist because the money is already spent and the only chance to detect it is the review. Auditors and sureties look for evidence that card reconciliation actually enforces substantiation.

It carries tax and compliance weight. Missing receipts undermine deductibility and substantiation, sales and use tax must be assessed on many card purchases, and reportable spend must be captured, so a reconciliation that just clears the statement without receipts and coding leaves compliance exposure behind.

Lifecycle — how it moves

1. Charge posting

   Transactions post from the card provider to the statement or a feed. The available data is often just merchant, amount, and date, which is not enough to code or substantiate without a receipt.

2. Receipt capture

   Cardholders attach receipts to each charge, ideally at the point of sale. The gap between charge and receipt capture is where substantiation is lost.

3. Coding

   Each charge is coded to a job and cost code and a sales or use-tax treatment. Coding by the cardholder who knows the purchase beats office guesswork from a merchant name.

4. Policy and legitimacy check

   Charges are checked against policy: allowed merchants and categories, spending limits, and no personal or cash-equivalent use. Split charges and limit-avoidance are looked for here.

5. Cardholder certification

   The cardholder attests that the charges are legitimate business expenses with receipts attached, the equivalent of the substantiation step on an expense report.

6. Approval

   A manager independent of the cardholder reviews and approves the reconciled statement, the segregation the control relies on.

7. Posting to job cost and GL

   Approved, coded charges post to the coded jobs and the general ledger, and the card liability is cleared, converting card spend into recorded cost.

8. Statement reconciliation and payment

   The posted charges reconcile to the card statement balance, exceptions are cleared, and the card is paid, closing the cycle with a fully substantiated statement.

Anatomy — the data it carries

Cardholder

Who incurred the charge and is accountable for substantiating and coding it, the basis of certification.

Transaction date and post date

When the charge occurred and posted, used for period assignment and duplicate detection.

Merchant

The vendor, which hints at category but is not enough alone to code or justify the charge without a receipt.

Amount

The charge value, checked against the receipt and against any per-transaction limit.

Receipt image

The substantiation that justifies the charge and supports deductibility and tax. Missing receipts are the central reconciliation defect.

Job number

The project the cost belongs to, mis-assignment of which distorts the cost report from the field side.

Cost code

The category within the job the charge hits, determining whether fuel or small materials land where the cost report expects.

Tax treatment

Sales tax paid or use-tax to self-assess, a compliance element easily lost when charges are cleared quickly.

Business-purpose note

The cardholder's explanation of why the charge was incurred, required substantiation beyond the receipt alone.

Policy status

Whether the charge is within policy, over limit, out of category, or flagged as possible personal or split spend.

Certification and approval

The cardholder attestation and the independent approval, the audit record the control produces.

Statement reconciliation status

Whether all charges are substantiated, coded, and posted to match the statement balance, the completion check for the cycle.

Failure modes — how it breaks

Charges cleared without receipts

To close the statement on time, charges are approved without receipts attached, so spend is substantiated by a merchant name alone. Deductibility and audit defensibility are undermined, and genuine misuse hides comfortably among the undocumented charges.

Blanket-coded to a default account

Under time pressure, charges are coded en masse to a single default cost code or overhead account rather than the jobs they belong to. The statement clears but the job-cost report is wrong, and the small amounts are never reclassified.

Personal charges cleared as business

Personal purchases are approved because review is cursory and the money is already spent. Each is small, but a pattern is both a real cost and a fraud problem, and reconciliation is the only place it can be caught.

Split transactions to evade limits

A cardholder splits a purchase into two charges to stay under a per-transaction limit, and without detection the limit control is defeated. Recognizing paired charges at the same merchant on the same day is the check that catches it.

Duplicate with an expense report

The same cost appears both as a card charge and on an employee expense report, and without a cross-check the company effectively pays twice, once on the card and once as reimbursement.

Reconciliation chronically behind

The reconciliation lags by months because it is tedious, so charges post to cost late or not at all, receipts are long lost by the time anyone looks, and the control degrades into a rubber stamp on stale data.

Metrics — how it is measured

Reconciliation cycle time

Days after statement close to a fully substantiated, posted reconciliation. Lag is the core health metric; behind means the control is weak.

Receipt compliance rate

Share of charges with adequate receipts attached. Directly measures substantiation and audit defensibility.

Coding accuracy

Rate of charges later reclassified between jobs or from a default account. Measures cost-report integrity from the card side.

Policy exception rate

Portion of charges over limit, out of category, or flagged personal or split. Measures cardholder compliance and program health.

Duplicate-with-expense-report rate

Frequency of card charges also claimed on expense reports. A direct double-payment leakage metric.

Unsubstantiated spend

Dollar value of charges posted without receipts. Quantifies the compliance and misuse exposure the program carries.

The AI shift — what actually changes

Conversational

You interrogate the card feed rather than scrolling a statement: which charges still lack receipts, which are coded to a default account when the merchant suggests a specific job, which pairs look like a split to evade a limit, and which duplicate an expense-report claim, each answered from the transaction, receipt, and expense data.

Generative

Receipts are read and matched to charges and a coded, policy-checked draft reconciliation is produced. Given the card feed and receipt images, a model matches each receipt to its charge, proposes job and cost-code coding, drafts the business-purpose note from the receipt and context, assesses tax treatment, and flags each charge's policy status for the cardholder to confirm.

Orchestrated

Reconciliation is coordinated with expense reports, job cost, and the general ledger. Charges are cross-checked against expense claims to catch duplicates, split-transaction patterns are surfaced, coded charges post to their jobs and the GL, and the posted total reconciles to the statement, so the card cycle is tied into the wider cost and cash picture rather than run in isolation.

Autonomous

Routine reconciliation runs continuously inside guardrails: matching receipts to charges, proposing coding, drafting purpose notes, checking policy, detecting splits and expense-report duplicates, and preparing the reconciled statement for approval. Missing receipts, over-policy and personal charges, suspected splits or duplicates, and the final certification and approval all stay with a person.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Finding the problems in a card statement before you certify it.

Review this month's corporate-card charges before I certify the reconciliation. List every charge still missing a receipt with its amount, and every charge coded to our default account that, based on the merchant, likely belongs to a specific job. Identify any pairs of charges at the same merchant on the same day that could be a purchase split to stay under a per-transaction limit. Flag any charge whose merchant or category looks personal or outside policy. Cross-check these charges against expense reports submitted for the same period and dates and flag any that appear to be the same cost claimed twice. Give me a prioritized list of what needs attention before this statement can be certified.

What good output looks like: A prioritized list naming specific missing-receipt charges, mis-coded charges, suspected splits, possible personal charges, and expense-report duplicates, not a general reconciliation checklist.

Follow-ups:

• Which unsubstantiated charges are the largest exposure if we get audited?
• Recode the misfiled default-account charges to the jobs they belong to.
• Which split pairs are confirmed versus need a human to judge?

Generative — Building a coded, substantiated draft reconciliation from the feed and receipts.

Build a draft card reconciliation from this month's charge feed and the attached receipts. Match each receipt to its charge and note charges left without a receipt. For each matched charge, propose the job and cost-code coding from the receipt and the cardholder's assignment, draft a short business-purpose note, and assess the sales or use-tax treatment. Check each charge against our policy limits and allowed categories and flag anything over limit, out of category, or that looks personal. Present the reconciliation as ready for cardholder certification with a clear list of the charges still needing a receipt or a purpose note before it can be certified.

What good output looks like: A coded, receipt-matched draft reconciliation with purpose notes and tax treatment proposed, policy flags applied, and a clear list of charges still needing substantiation.

Follow-ups:

• Which charges will fail substantiation as they stand?
• Split the coding on the mixed fuel-and-materials charge across the two jobs.
• Show the total unsubstantiated amount and which cardholders it belongs to.

Orchestrated — Reconciling the card against expense reports, job cost, and the statement balance.

Reconcile this month's corporate card end to end for review. Cross-check every charge against expense reports for the same period and hold any that duplicate a reimbursement claim. Post the substantiated, coded charges to their jobs and cost codes and to the general ledger, and confirm the posted total reconciles to the card statement balance, listing any difference. Surface any charges still missing receipts and any coded to a default account. Produce a completion summary showing what posted, what was held as a duplicate, what remains unsubstantiated, and whether the statement fully reconciles, and flag anything that could not be resolved.

What good output looks like: A reconciled statement with duplicates held, substantiated charges posted to job cost and the GL, unsubstantiated charges surfaced, and the statement-balance tie-out shown with any difference explained.

Follow-ups:

• What is the statement difference and which charges explain it?
• Which duplicate charges did you hold, and what should we recover?
• Confirm the job-cost impact by project for this statement.

Autonomous — Standing policy for operating card reconciliation inside guardrails.

Operate our corporate-card reconciliation continuously under these rules. As charges post, match receipts to charges, propose coding, draft business-purpose notes, assess tax treatment, and check each charge against policy limits and categories. Cross-check against expense reports for duplicates and scan for same-merchant same-day pairs that suggest a split to evade limits. Prepare the reconciliation for cardholder certification and approval, posting only substantiated, in-policy, coded charges. Hold and escalate to me, with the specific reason, any charge missing a receipt, over a limit, out of category, appearing personal, suspected of being a split, or duplicating an expense claim. Never post an unsubstantiated charge, never certify or approve on a cardholder's behalf, and never clear a statement that does not fully reconcile without my sign-off.

What good output looks like: A running reconciliation that posts only substantiated, in-policy, coded charges and surfaces a short exception queue, with hard boundaries around substantiation, certification and approval, and clearing an unreconciled statement.

Follow-ups:

• Show me everything posted, held, and escalated this cycle and why.
• Which cardholders repeatedly submit late, without receipts, or over policy?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Clear the statement

   Charges are approved to clear the statement with little coding or receipt discipline, so unsubstantiated, mis-coded, and personal spend passes and the card is effectively uncontrolled.

1. Level 1 — Manual reconciliation

   Cardholders code charges and attach receipts in a system with manager approval, though matching, policy checks, and cross-checks against expense reports are manual and often lag.

2. Level 2 — Policy- and job-linked

   Reconciliation enforces policy and limits, codes to jobs and cost codes, cross-checks against expense reports, and ties the posted total to the statement, so exceptions surface before certification.

3. Level 3 — Assisted matching and coding

   Receipts are read and matched, coding and purpose notes are proposed, and missing receipts, policy breaches, splits, and duplicates are flagged for human review.

4. Level 4 — Operated

   Receipt matching, coding, policy and duplicate checks, and statement tie-out run unattended inside guardrails, while people own certification, approval, and clearing any unreconciled statement.

Common questions

How is card reconciliation different from an expense report?

With an expense report the employee paid personally and is reimbursed, so cash still has to flow out. With a corporate card the money has already left the company at the point of purchase, so reconciliation is not about paying anyone but about accounting for spend that already happened, substantiating it with receipts, coding it, and confirming it was legitimate. Because the spend is already gone, reconciliation is a detective and compensating control rather than a preventive one.

Why is the card considered a control gap?

A corporate card lets an employee commit company money directly, without raising a purchase order or generating a vendor invoice, so it bypasses the three-way match and approval controls that normally sit in front of spend. That convenience is the point of the card, but it means the only control is the after-the-fact reconciliation. If reconciliation is lax or chronically behind, there is no effective barrier on that spend at all, which is why auditors scrutinize card programs.

What is transaction splitting and why does it matter?

Transaction splitting is dividing a single purchase into two or more charges to keep each below a per-transaction spending limit, defeating a control meant to require higher approval for larger buys. It shows up as multiple charges at the same merchant on the same day that together exceed the limit. Detecting these paired charges is a specific reconciliation check, because splitting is both a policy violation and a common technique in card misuse.

Why do receipts matter so much on card charges?

The card statement shows only merchant, amount, and date, which is not enough to prove what was bought, that it was a business expense, or how it should be coded and taxed. The receipt provides that substantiation, supporting the tax deduction and satisfying an audit, and its absence is where misuse hides because an undocumented charge cannot be verified. Clearing a statement without receipts substantiates spend by merchant name alone, which is not substantiation at all.