When does camt.055 trigger camt.056?

Payment BA Awareness Series | EP47

camt.055 received. Should the Payment Engine automatically generate camt.056? 🤔

Not necessarily.

The obvious requirement:

“Receive camt.055 → Generate camt.056.”

But camt.055 is the customer's cancellation request. camt.056 is an interbank cancellation request.

Whether one triggers the other depends on where the original payment is in its lifecycle.

1️⃣ Not yet released (warehoused or in repair)

✅ Cancel internally, subject to payment status and controls. No interbank cancellation message required.

2️⃣ On-us / book-to-book

✅ No camt.056 needed.

⚠️ But reversing an already-booked credit requires appropriate internal authority and controls.

3️⃣ Already rejected or returned

✅ Check the existing status and accounting outcome. An unnecessary cancellation request only adds noise.

4️⃣ On sanctions hold

⚠️ Don't automatically cancel, release or refund. Follow the Compliance decision and applicable restrictions.

5️⃣ Released into an interbank chain

An external cancellation or recall request may be required, using camt.056 where applicable under the scheme or service rules.

And remember: A cancellation request is not a guarantee.

What if the response never arrives? (See EP40.)

💡 BA Takeaway

camt.055 is an event. camt.056 is a decision.

Before generating it, the requirement must consider:

Payment status · Release status · Settlement method · Compliance restrictions · Scheme rules

And on every path, the customer needs a clear outcome.

One cancellation request. Multiple journeys.

💬 Have you seen cancellation logic designed without checking the original payment status?

#BusinessAnalysis #Payments #ISO20022 #PaymentCancellation #PaymentLifecycle