Reconciliation¶
Payments occasionally succeed at the gateway while Salesforce fails to finish recording them — a dropped connection, a browser closed mid-flow, a governor limit. These pages are how you find those and put them right.
| Page | What it covers |
|---|---|
| Reconcile payments | Comparing gateway settlement against your Transaction History, on demand or on a schedule |
| Resolve unresolved transactions | Payments the gateway took that Salesforce did not finish recording |
Unresolved transactions are real money
An unresolved transaction means the customer has been charged and your records do not show it. Left alone, it becomes a duplicate charge when someone retries, or a write-off when nobody notices. Work the queue.
Two different problems, two different pages¶
It helps to know which one you actually have before you start:
- Reconciliation answers "does what the gateway settled match what Salesforce recorded?" — a scheduled or on-demand comparison across a date range, covering every transaction on a supported gateway. Most of what it finds is fine; it is a health check, not an alarm.
- Unresolved transactions answers a narrower, more urgent question: "did the gateway take money that Salesforce never got around to recording at all?" ChargeOn catches this specific failure itself, at the moment it happens, and holds everything needed to finish the job safely — you do not have to go looking for it the way you do with reconciliation.
If a customer or your finance team flags a charge that Salesforce shows nothing for, check unresolved transactions first — it is very often already sitting there, waiting to be resolved.
Which gateways reconciliation covers¶
Reconciliation works with 14 of ChargeOn's 20 gateways. If your gateway is not on the list, its transactions are not compared automatically — see reconcile payments for the full list and what to do instead.