What is credit card payment reconciliation?
For a merchant, reconciliation means following the money from the sale to the bank. The team compares sales records, provider payment records, settlements, and bank statements. This shows which sales have been paid out and which are still pending.
The term can also refer to reconciling a card a company uses to pay expenses. This guide covers payments received by a merchant.
A payment provider may settle a sale after recording the payment. Before investigating a difference, check the dates and status of each transaction.
How do you follow a sale through to the bank deposit?
The process depends on the provider and your agreement. Keep each stage separate so you don't mistake a pending sale for missing money.
- Gather the records. Download sales records, provider payment records, settlements, and bank transactions. Keep the reporting period, currency, and identifier for each file. File-based reconciliation compares these downloaded records instead of looking them up one at a time.
- Match sales to payments. Find the transaction reference and compare the amount and status. Review voided sales separately. Also review payments that appear with the provider but not in your sales records. Don't match transactions solely because they have the same amount.
- Check the settlement. Match payments to their settlement and review the reported adjustments. Fields and applicable deductions vary by provider.
- Verify the deposit. Compare the net settlement amount with the bank transaction using the reference and expected date. One deposit may cover several sales. If the provider groups or splits settlements, keep track of those relationships before flagging a difference.
- Assign exceptions. Record the reason, owner, and next review date for each pending item. Don't store card security codes: PCI DSS prohibits storing sensitive authentication data after authorization. Limit access to the files people need.
How do you investigate a difference? An example
This example is illustrative; it doesn't describe a client or a provider's terms.
A store records two sales: one for 100,000 pesos and another for 50,000 pesos. The provider confirms both payments but includes only the first sale in that day's settlement.
For that sale, the settlement shows a hypothetical fee of 3,000 pesos and a net amount of 97,000 pesos. The bank statement shows a deposit of 97,000 pesos with the matching reference. The team reconciles that sale and marks the 50,000-peso sale as pending settlement.
The team keeps the pending sale's reference and checks the payment date provided by the provider. If the sale doesn't appear in the expected settlement, the team asks the provider for details. A missing bank deposit alone doesn't mean the money is lost.
If a refund occurs later, the team links it to the original sale and checks which settlement includes the adjustment. A chargeback needs a separate review. The team should track the claim's status and check its effect on the deposit. It shouldn't treat a chargeback as an ordinary refund.
Which reconciliation tool should you use?
The choice depends on transaction volume, file quality, and the control you need over exceptions.
| Option | When it fits | What to check |
|---|---|---|
| Provider's tool | When its reports cover the payments and settlements you need. | Data exports and traceability through to the bank. |
| Spreadsheet | When the volume is manageable and one person can review each difference. | Versions, formulas, and who is responsible for changes. |
| Rules-based automation platform | When files are consistent and matching criteria are clear. | Access to sources, errors, and duplicates. |
| Custom development | When you need to integrate several systems or handle complex groupings. | Maintenance, permissions, and decision logs. |
| AI for support | When variable documents or descriptions need interpretation. | Human review and interpretation errors. |
Cost and timing depend on data access, the number of sources, and the exceptions involved. Testing, security controls, and maintenance also affect both.
How do you measure reconciliation automation?
Before changing the process, we measure a sample reviewed by the team. Then we compare results using the same definition for each metric.
- Coverage: Divide automatically reconciled transactions by the transactions that entered the process. Review transactions missing from the files separately.
- Incorrect matches: Count matches the system marked as correct but the team rejected. Review a sample of accepted matches, not just exceptions.
- Pending items: Measure their count, value, and age. Separate sales still within the expected timeframe from those that need investigation.
- Review time: Compare the time the team spends investigating and closing differences before and after automation. Include time spent correcting automation errors.
- Tests with real cases: Prepare a reviewed set that includes fees, refunds, and grouped deposits. Check that the system preserves references and explains each match.