← Payments and SEPA: project and operational decisions
05 / 6 · 35 MIN

Exceptions and transaction-level reconciliation

Interpret codes in context and recover without duplicates.

Concept and mechanism

Payment exceptions have a type, initiator, reason, and link to the original transaction. Reject, return, and recall should not be compressed into one error state. Sending a recall request does not prove funds were recovered. Preserve request state, response, and corresponding financial evidence. Codes also require scheme and message context. In SCT, AC01 indicates an invalid or incorrect account identifier. In SDD, AM05 indicates possible duplication; handling requires checking whether the collection actually is duplicated. A generic reason such as MS03 can reflect legal restrictions on disclosing details. Do not automatically map it to one cause such as insufficient funds.

Guided application

In operations, reconcile identities and outcomes rather than file counts alone. A batch of 80 instructions with six rejections should not be repeated in full when 74 payments already have positive outcomes. Separate completed, rejected, and unknown items, preserve approved amounts, and handle each group through the applicable procedure. Comparing data before and after migration helps test a concrete IBAN-corruption hypothesis. A new reference neither repairs data nor removes an earlier collection. A recovery report should state the expected population, known outcomes, unresolved items, authorized action, and final confirmation. This structure gives managers an impact view and support a verifiable sequence of work.

IN PRACTICE

Example: batch restoration produces AM05 and MS03. Investigate duplicates separately; preserve the generic reason as incomplete information rather than inventing a diagnosis to improve the dashboard.

Common pitfalls

Whole-batch retry after partial outcomes; new reference treated as repair; generic reason treated as known cause; request treated as completed result.

Related topics: Instruments, participants, and settlement · Timing, confirmations, and late outcomes · Mandates, Core, and B2B

Take this idea with you

Each recovery action should correspond to known identity, state, and reason.

Create account

Reference: SCT R-transaction guidance · DR Payments and SEPA professional assessment2026.10