Guide

Credit card reconciliation for the month-end close

By the Vanward team · Last updated

A corporate credit card reconciliation proves that the card liability in the general ledger agrees with the issuer records at the same date, after supported timing differences. Roll the beginning statement balance forward through charges, fees, credits, cash back applied, and payments to the ending statement balance. If the statement closes before month end, bridge the remaining days with issuer activity before comparing it with the ledger. List uncleared charges and payments in transit separately, trace them to later settlement, and correct missing or duplicate postings. Keep receipts, coding, the statement, and a lead sheet showing the ledger, card sub-ledger, and reconciling items for preparation and independent review.

Start with the statement balance and the ledger date

Reconcile the issuer liability, not available credit, a spending limit, or a payment reminder. Record the statement cutoff and the close date at the top of the workbook. Use a consistent sign convention. The examples below show an amount owed as positive, even if the ledger export displays the liability as a negative credit balance.

Define which cards belong to each issuer account and which ledger account holds the liability. Employee card detail may be part of one master account. Confirm that the sub-ledger includes every employee card once, along with account-level fees, credits, and payments. An imported transaction feed is useful detail, but matching feed lines does not prove the ending balance.

Roll the statement from beginning to ending balance

Fictional Juniper Deskworks has a corporate card from fictional issuer Copper Finch Card. Its October 25 statement begins at $10,000. The statement roll-forward is beginning liability plus charges and fees, less merchant credits, cash back applied, and payments.

Statement movementAmountRunning liability
Beginning statement balance$10,000$10,000
Charges, including any fees$18,000$28,000
Merchant credits($600)$27,400
Cash back applied to the card($200)$27,200
Payments posted by the issuer($20,000)$7,200
Ending statement balance, October 25$7,200

Trace every movement to the statement detail. If fees are included in charges, do not add them again. Confirm whether a rewards credit is already included in a downloaded credits total before subtracting it separately. Rewards earned but not applied to the card do not belong in this balance roll-forward.

Bridge a statement cutoff that falls before month end

The October 25 statement does not support October 31 by itself. Download issuer activity for October 26 through October 31 and retain it with the statement. In this example, those days have $2,400 of charges, $100 of merchant credits, and $1,000 of payments posted by the issuer. The card sub-ledger at October 31 is $8,500.

Use the next statement to confirm the bridge, but do not include November activity in the October balance. Transaction dates, issuer posting dates, and ledger dates can differ. Document which date the supporting report uses and investigate transactions around the boundary. If the cutoff falls after month end, remove subsequent activity to arrive at the month-end balance instead.

Separate uncleared items from posting errors

A payment recorded in the ledger on October 31 may not post with the issuer until November 2. A booked charge may also settle after month end. List each supported timing item with its transaction date, posting date, reference, amount, and expected clearance. Confirm it against subsequent issuer activity rather than carrying the same note forward indefinitely.

A pending authorization is not necessarily a final charge. Confirm the goods or services received and the appropriate liability under the company's cutoff policy. Do not book every temporary authorization as a settled card purchase. If a cost is accrued elsewhere, check that the eventual card posting does not leave the expense counted twice.

Missing issuer fees and duplicate imports are posting errors to correct. An old unexplained item is not evidence of timing. Assign each unresolved item an owner and follow-up date. A disputed charge also needs tracking. Submitting a dispute is not, by itself, a reason to remove a posted liability; remove it when the issuer credits the charge or the support shows the company does not owe it.

A month-end lead sheet against the card sub-ledger

Juniper Deskworks also records a separate $400 payment on October 31 that reaches the issuer on November 2. It is not part of the $1,000 already posted in the bridge. The ledger therefore shows $8,100 owed at October 31. The lead sheet explains the difference from the issuer-supported sub-ledger as follows:

Lead sheet lineAmountSupport
October 25 statement balance$7,200Statement PDF
October 26 through 31 charges$2,400Issuer activity detail
October 26 through 31 merchant credits($100)Issuer activity detail
October 26 through 31 posted payments($1,000)Issuer activity and cash entries
October 31 card sub-ledger$8,500Statement plus cutoff bridge
Payment in transit, recorded October 31($400)Payment reference and November 2 settlement
Adjusted supporting balance$8,100Sub-ledger less reconciling payment
October 31 general ledger liability$8,100Final ledger account detail
Unexplained difference$0Ledger less adjusted supporting balance

Keep the card sub-ledger date and scope visible. A difference between imported transaction detail and issuer records needs its own explanation before using that detail as support. Check the $400 payment against the cash reconciliation too, so a bank-feed match does not create a second card payment. Payments debit the card liability and credit cash; they do not repeat the expense recorded when the purchase was made.

Receipts and coding are a separate review

Match charges to receipts, business purpose, account, and department or project. An annual software charge may belong on the prepaid schedule. Equipment may need capitalization. Request missing receipts while keeping the actual charge visible. A zero balance difference does not prove the expense coding is correct or the purchase was authorized.

The preparer should identify corrections and attach their posting references. The reviewer checks the arithmetic, cutoff bridge, clearance evidence, receipts, and coding, then signs the completed reconciliation against the final ledger balance.

What this looks like in Vanward

Each card account is a step on the close board, with the liability balance pulled from QuickBooks. Attach the statement and the reconciliation workbook to the step, and the reviewer checks the cutoff bridge and the payments in transit against the same files you used.

Any amount left unexplained needs a note, and a reviewer other than the preparer signs the step off.

Questions controllers ask

Is the statement balance supposed to equal the ledger balance?
Only when both cover the same date and all activity has been recorded without timing differences. A statement ending October 25 needs a bridge through October 31 for the monthly close. The amount due and available credit are not substitutes for the ending liability.
How do card payments affect the reconciliation?
A payment reduces the card liability. Trace it to the cash account and the issuer record. If the ledger records it before the issuer does, list it as a payment in transit with its date, amount, reference, and later settlement evidence. It is not another expense.
How should cash back appear in the schedule?
Show cash back applied to the card as a separate reduction of the liability. Use the company's book policy for the offsetting account. Rewards earned but not applied do not reduce the statement balance, and a cash deposit to a bank account is a different transaction.
Do I reconcile each employee card or the master account?
Reconcile each ledger liability to the issuer account that supports it. If employee cards roll into one master statement, sum their detail once and reconcile that total to the master liability. Do not add employee card balances again on top of a master total that already includes them.
Does a missing receipt create a reconciling item?
A missing receipt is a support issue, not automatically a balance difference. The charge may already agree between issuer and ledger. Keep the charge in the reconciliation, request support, and resolve its business purpose and coding without deleting it to make the receipt list look complete.
What should the reviewer see on a credit card lead sheet?
The account and close date, final ledger balance, statement balance, cutoff bridge, card sub-ledger total, individually supported reconciling items, and remaining difference. Attach the statement and transaction detail, and record who prepared and independently reviewed the reconciliation.

How ready is your close?

Eight yes-or-no questions, two minutes, no account. You get a score out of 100 and the three gaps most likely to come up in an audit or a diligence request.

Take the free close check

Related

Keep the card statement with the reconciliation.

FinReadi Close keeps the statement and the card reconciliation on the close step, ties the card liability to the balance in QuickBooks, and records who prepared and who reviewed it. Starter is $400 a month or $4,000 a year for one entity.

See FinReadi Close