Reconcile Corporate Card Receipts Without Guesswork

Set the boundary between cardholder and payables

The cardholder is closest to the purchase and usually owns the business-purpose explanation. Payables support can compare the statement to the receipt, check the coding, identify missing documentation, and route exceptions. It should not invent a business purpose, approve a policy exception, or attest that an unsupported charge is valid.

Write that boundary into the request template. Ask for the receipt, the business purpose, the participants or project, and the coding. If the cardholder cannot provide a receipt, use a separate attestation path with a named approver. The path should be visible in the record, not handled through a private message that disappears.

Design the missing receipt path

A missing receipt is an exception, not a reason to stop the close. Define who may attest to the purchase, what they must confirm, and which charges require a higher level of review. The attestation should state what was purchased, when, for what business purpose, and why the receipt is unavailable.

Keep the attestation linked to the card transaction and the statement period. If the charge is later disputed or audited, the reviewer needs to see the original request, the response, the approver, and the final disposition. A blanket annual attestation is weaker than a transaction-level record because it cannot distinguish one missing receipt from a pattern.

Use the related specialist service role as a starting point for defining scope and evidence.

Reconcile statements to receipts

Match each statement line to a receipt or attestation using the transaction date, amount, merchant, and card ending. Flag duplicates, split transactions, foreign currency differences, and refunds that do not appear on the same statement. A refund missing from the current statement may belong to a later period, so the record needs an open-item status rather than a forced match.

Coding should follow the approved chart of accounts and project structure. The assistant can suggest a code based on the receipt and prior treatment, but the cardholder or budget owner should confirm anything ambiguous. Repeated coding questions are a sign that the request template or the chart guidance needs improvement.

Handle disputes and credits

When a charge is disputed, record the reason, the amount, the date the dispute was opened, the card issuer reference, and the expected resolution date. Keep the disputed amount visible in the reconciliation so it is not counted as both an open dispute and a normal payable. If a provisional credit is issued, link it to the dispute and record the conditions.

Credits and refunds should be matched to the original transaction where possible. If the original is in a prior period, document the cross-period link. Do not net a credit against an unrelated charge just to make the statement balance. That obscures the history and makes it harder to spot a missing refund.

IRS Recordkeeping Guidance provides public guidance that can help your team test relevant workflow assumptions.

Review policy exceptions

Group exceptions by type: missing receipt, late submission, unapproved merchant category, personal portion, split purchase, or repeated coding change. Review the pattern with the policy owner. A high volume of late submissions may be a workflow problem, while a repeated personal charge may require a management conversation.

The payables role can prepare the exception summary and the evidence. The policy owner decides whether to approve, decline, or require repayment. Record that decision and the date. The review should focus on the control, not on creating a narrative about an individual employee.

Compare this approach with our guide to the next related workflow.

Launch with one card program

Start with one card program, one statement cycle, and a named approver. Test the receipt request, the missing receipt path, the coding review, and the dispute log. Measure how many transactions required a second request and where the delay occurred.

Expand after the first cycle produces a clean reconciliation and a usable exception history. A corporate card process is only as good as its evidence trail. If the team cannot show why a charge was accepted, the reconciliation is not finished.

Common questions answered

Ready to create a clearer support role?

Bring the workflow that consumes the most attention. We will help you shape the role, handoff, decision boundaries, and review points.