Clearing, Settlement and Reconciliation Explained

A payment that shows as successful on screen is not the same as money in your bank account. Between the moment a transaction is approved and the moment funds are available, it passes through clearing and settlement, and only reconciliation confirms that what you expected to receive actually arrived.

Understanding these three stages helps operations teams explain timing differences to finance, spot missing funds early and close the books with confidence.

What is clearing?

Clearing is the process of exchanging and confirming payment instructions between banks. For card payments, the acquirer and issuer exchange transaction details through the card schemes. For debit orders and EFT payments, instructions flow through the South African national payment system on defined processing cycles.

During clearing:

• Transaction details are validated and matched between the paying and receiving banks.
• Each bank works out what it owes or is owed.
• Nothing has moved yet; clearing establishes the obligation, not the funds.

What is settlement?

Settlement is the actual transfer of value between banks, typically across accounts held at the South African Reserve Bank. Once interbank settlement completes, the receiving bank credits the beneficiary, and the funds become real.

Settlement timing differs by payment method:

• Card payments settle to the merchant on the acquirer's settlement schedule, usually a day or more after authorisation.
• EFT credits and debit orders settle on batch cycles tied to cut-off times and value dates, and debit order collections can still be reversed afterwards as unpaids.
• Real-time payments clear and settle within seconds, so the distinction is less visible to the merchant.

A key point for collections: a debit order that settled successfully today can still come back as an unpaid over the following days, so settled does not always mean final. See unpaids, returns and resubmissions for how returns work.

What is reconciliation?

Reconciliation is the process of matching three views of the same money:

1. Your system's view: the payments you submitted or expected to receive.
2. The provider's view: transaction reports, response files and settlement statements.
3. The bank's view: actual credits and debits on your bank statement.

A payment is fully reconciled when it appears consistently in all three, with the same reference and amount.

What should you reconcile daily?

• Submitted collections against response and unpaid files or API status updates.
• Settlement batches against individual transactions, so every batch total can be broken down to line level.
• Bank statement credits against expected settlement amounts, after fees.
• Unpaids and reversals against the original transactions they relate to.

Why do reconciliation breaks happen?

Common causes of mismatches include:

• Timing differences: a transaction cleared today but settles tomorrow, so it appears in one view and not the other.
• Reference problems: truncated, reused or missing references make matching unreliable. Unique references per instruction, as covered in payment statuses and references, are the foundation of clean reconciliation.
• Unpaids and reversals: funds arrive and are later clawed back, which must be matched to the original item rather than treated as a new transaction.
• Fees and netting: providers may settle gross with fees invoiced separately, or net of fees, and the model must match what finance expects.

How do you build a reliable reconciliation process?

• Assign a unique reference to every payment instruction and carry it through every system.
• Store the interim and final status of each transaction, since many outcomes are asynchronous.
• Ingest settlement reports and unpaid files automatically rather than manually.
• Investigate breaks the same day; aged breaks are far harder to resolve.
• Keep an audit trail of every status change, as described in logging, masking and audit trails.

For more operational topics, return to the Payment Operations hub.