Payments Academy
Out of order arrival PAYMENT OPERATIONS STARTED LIVE 01 Out of order arrival - normal in payment networks ACTIVE 02 Harbour Bank - worked example, Harbour Bank receives QUEUED 03 Held message ages - If the predecessor never arrives QUEUED 04 Holding area - operations dashboard QUEUED 05 Business rules decide when to wait - act, balancing delay against the risk QUEUED 06 Testing these rules - means sending each message type early QUEUED Out of order arrival is normal in payment networks Step 1 of 6 Out of order arrival STARTED Out of order arrival normal in payment networks ACTIVE Harbour Bank worked example, Harbour Bank receives QUEUED Held message ages If the predecessor never arrives QUEUED Holding area operations dashboard QUEUED Business rules decide when to wait act, balancing delay against the risk QUEUED Testing these rules means sending each message type early QUEUED Out of order arrival is normal in payment networks
Harbour Bank PAYMENT OPERATIONS IN PROGRESS LIVE 01 Out of order arrival - normal in payment networks DONE 02 Harbour Bank - worked example, Harbour Bank receives ACTIVE 03 Held message ages - If the predecessor never arrives QUEUED 04 Holding area - operations dashboard QUEUED 05 Business rules decide when to wait - act, balancing delay against the risk QUEUED 06 Testing these rules - means sending each message type early QUEUED In the worked example, Harbour Bank receives the cover for the USD 120,000 payment before the announcement from Meridian Bank, so it holds the cover in a pending queue instead of crediting Step 2 of 6 Harbour Bank IN PROGRESS Out of order arrival normal in payment networks DONE Harbour Bank worked example, Harbour Bank receives ACTIVE Held message ages If the predecessor never arrives QUEUED Holding area operations dashboard QUEUED Business rules decide when to wait act, balancing delay against the risk QUEUED Testing these rules means sending each message type early QUEUED In the worked example, Harbour Bank receives the cover for the USD 120,000 payment before the announcement from Meridian Bank, so it holds the cover in a pending queue instead of crediting
Held message ages PAYMENT OPERATIONS IN PROGRESS LIVE 01 Out of order arrival - normal in payment networks DONE 02 Harbour Bank - worked example, Harbour Bank receives DONE 03 Held message ages - If the predecessor never arrives ACTIVE 04 Holding area - operations dashboard QUEUED 05 Business rules decide when to wait - act, balancing delay against the risk QUEUED 06 Testing these rules - means sending each message type early QUEUED If the predecessor never arrives, the held message ages and is escalated to operations after a defined waiting period. Step 3 of 6 Held message ages IN PROGRESS Out of order arrival normal in payment networks DONE Harbour Bank worked example, Harbour Bank receives DONE Held message ages If the predecessor never arrives ACTIVE Holding area operations dashboard QUEUED Business rules decide when to wait act, balancing delay against the risk QUEUED Testing these rules means sending each message type early QUEUED If the predecessor never arrives, the held message ages and is escalated to operations after a defined waiting period.
Holding area must be visible PAYMENT OPERATIONS IN PROGRESS LIVE 01 Out of order arrival - normal in payment networks DONE 02 Harbour Bank - worked example, Harbour Bank receives DONE 03 Held message ages - If the predecessor never arrives DONE 04 Holding area - operations dashboard ACTIVE 05 Business rules decide when to wait - act, balancing delay against the risk QUEUED 06 Testing these rules - means sending each message type early QUEUED The holding area must be visible on the operations dashboard, with the age of each held message, the missing predecessor, and the time at which it will escalate. Step 4 of 6 Holding area must be visible IN PROGRESS Out of order arrival normal in payment networks DONE Harbour Bank worked example, Harbour Bank receives DONE Held message ages If the predecessor never arrives DONE Holding area operations dashboard ACTIVE Business rules decide when to wait act, balancing delay against the risk QUEUED Testing these rules means sending each message type early QUEUED The holding area must be visible on the operations dashboard, with the age of each held message, the missing predecessor, and the time at which it will escalate.
Business rules decide when to wait PAYMENT OPERATIONS IN PROGRESS LIVE 01 Out of order arrival - normal in payment networks DONE 02 Harbour Bank - worked example, Harbour Bank receives DONE 03 Held message ages - If the predecessor never arrives DONE 04 Holding area - operations dashboard DONE 05 Business rules decide when to wait - act, balancing delay against the risk ACTIVE 06 Testing these rules - means sending each message type early QUEUED The business rules decide when to wait and when to act, balancing delay against the risk of acting on incomplete information. Step 5 of 6 Business rules decide when to wait IN PROGRESS Out of order arrival normal in payment networks DONE Harbour Bank worked example, Harbour Bank receives DONE Held message ages If the predecessor never arrives DONE Holding area operations dashboard DONE Business rules decide when to wait act, balancing delay against the risk ACTIVE Testing these rules means sending each message type early QUEUED The business rules decide when to wait and when to act, balancing delay against the risk of acting on incomplete information.
Testing these rules PAYMENT OPERATIONS COMPLETE LIVE 01 Out of order arrival - normal in payment networks DONE 02 Harbour Bank - worked example, Harbour Bank receives DONE 03 Held message ages - If the predecessor never arrives DONE 04 Holding area - operations dashboard DONE 05 Business rules decide when to wait - act, balancing delay against the risk DONE 06 Testing these rules - means sending each message type early ACTIVE Testing these rules means sending each message type early, confirming the wait or act decision matches the rule, and confirming escalation fires on expiry. Step 6 of 6 Testing these rules COMPLETE Out of order arrival normal in payment networks DONE Harbour Bank worked example, Harbour Bank receives DONE Held message ages If the predecessor never arrives DONE Holding area operations dashboard DONE Business rules decide when to wait act, balancing delay against the risk DONE Testing these rules means sending each message type early ACTIVE Testing these rules means sending each message type early, confirming the wait or act decision matches the rule, and confirming escalation fires on expiry.

Key points of this lesson, in order.

0:00 / 3:30 Step 1 of 6

Out of Order Events: Messages and Acknowledgements Arriving Out of Order

Payment Operations Architecture: State, Resilience and Control, Lesson 4 of 8, Narration 3:30, D11 Operations, exceptions and reconciliation

Cover paymentSettlementpacs.002

What you will learn

Your objective. By the end of this lesson, you will be able to explain out of order events: messages and acknowledgements arriving out of order. Out of order arrival is normal in payment networks, because messages travel different routes, systems process at different speeds, and a fast acknowledgement can overtake a slow settlement confirmation.

Why it matters. This matters because operations is where payments are reconciled, investigated and fixed. The work in this lesson is what keeps the money right.

Chapter objective: How payments are tracked, recovered and controlled in operations

Key learning points

  • Out of order arrival
  • Harbour Bank
  • Held message ages
  • Holding area must be visible
  • Business rules decide when to wait
  • Testing these rules

Key terms

Cover payment: A payment method where the customer instruction travels one route while the funds travel separately as a bank to bank cover message.

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

pacs.002: An ISO 20022 message one financial institution sends to another to report the status of a payment instruction.

Banking architecture diagram showing Out of Order Events: Messages and Acknowledgements Arriving Out of Order.

Insights and practice scenarios

Worked insights and practice scenarios for this lesson. Each one is a reusable PaymentForge case, so the same case may appear in more than one lesson.

Practise this lesson

Exercise

Read the pacs.002 message described in this lesson and identify its key parts.

Use the message structure, fields and example in this lesson.

  1. What to do. List the three levels of the message and name the field that carries the amount and the field that carries the end-to-end reference.

Correct result. The amount is carried in the instructed amount element and the reference in the end-to-end identification. The three levels are the group header, the payment information, and the credit transfer transaction information.

Why. A message is only useful if you can read it. The group header identifies the message, the payment information identifies the batch, and the transaction information carries the single payment.

Check your understanding

Practice question

Which of the following best describes out of order events: messages and acknowledgements arriving out of order?

Takeaway and next step

What to remember

If the predecessor never arrives, the held message ages and is escalated to operations after a defined waiting period.

Open the message type from this lesson and inspect its fields, then find the field that carries the amount.

Open the ISO 20022 Message Explorer →

Builds on "Retries, Dead Letter Queues, Timeouts and Unknown Outcomes".

Transcript and full text

Show transcript

Out of order arrival is normal in payment networks, because messages travel different routes, systems process at different speeds, and a fast acknowledgement can overtake a slow settlement confirmation. A cover payment can arrive at the correspondent before the announcement that explains it, and a pacs.002 status report can arrive before the settlement confirmation it refers to. Each message carries a sequence or a reference that lets the receiving system place it in the right order, and the system must hold an early message until its predecessor arrives rather than acting on it alone. In the worked example, Harbour Bank receives the cover for the USD 120,000 payment before the announcement from Meridian Bank, so it holds the cover in a pending queue instead of crediting the Tokyo supplier immediately. Resequencing is the work of putting messages back into their intended order using the sequence number, the timestamp and the correlation identifiers on each message. When a message arrives early, the system stores it in a holding area keyed by its UETR and its instruction identification, and when the missing predecessor arrives the system releases the held message for processing in the correct order. If the predecessor never arrives, the held message ages and is escalated to operations after a defined waiting period. In the worked example, Harbour Bank holds the cover under the payment UETR, receives the announcement ninety minutes later, matches the two by the end to end identification, and releases the cover for settlement. Testing resequencing means sending messages out of order, confirming the early message is held, confirming it is released when its predecessor arrives, and confirming nothing is processed twice. Holding and matching protect the customer, because acting on an early message can credit the wrong account, release funds before the cover has arrived, or report a payment as settled when settlement has not happened. The holding area must be visible on the operations dashboard, with the age of each held message, the missing predecessor, and the time at which it will escalate. An operator can release a held message manually only with a recorded reason and a second approval for large amounts, so a manual release is a controlled act rather than a shortcut. In the worked example, the USD 120,000 cover sits in the holding area at Harbour Bank for ninety minutes, visible to operations with its missing announcement flagged, and no operator releases it early because the rule forbids crediting a supplier before the cover and the announcement are matched. The business rules decide when to wait and when to act, balancing delay against the risk of acting on incomplete information. A bank waits when the missing piece is essential, such as the cover or the settlement confirmation that proves finality, and it acts when the missing piece is only informational, such as a remittance detail that changes neither amount nor beneficiary. Each rule carries a maximum waiting time, and on expiry the payment is escalated to operations with the full history attached. In the worked example, Harbour Bank waits for the announcement because it confirms the cover belongs to the USD 120,000 payment, but it does not wait for the remittance detail, which arrives later and is matched to the settled payment. Testing these rules means sending each message type early, confirming the wait or act decision matches the rule, and confirming escalation fires on expiry.

Out of order arrival is normal in payment networks, because messages travel different routes, systems process at different speeds, and a fast acknowledgement can overtake a slow settlement confirmation. A cover payment can arrive at the correspondent before the announcement that explains it, and a pacs.002 status report can arrive before the settlement confirmation it refers to. Each message carries a sequence or a reference that lets the receiving system place it in the right order, and the system must hold an early message until its predecessor arrives rather than acting on it alone. In the worked example, Harbour Bank receives the cover for the USD 120,000 payment before the announcement from Meridian Bank, so it holds the cover in a pending queue instead of crediting the Tokyo supplier immediately.

Resequencing is the work of putting messages back into their intended order using the sequence number, the timestamp and the correlation identifiers on each message. When a message arrives early, the system stores it in a holding area keyed by its UETR and its instruction identification, and when the missing predecessor arrives the system releases the held message for processing in the correct order. If the predecessor never arrives, the held message ages and is escalated to operations after a defined waiting period. In the worked example, Harbour Bank holds the cover under the payment UETR, receives the announcement ninety minutes later, matches the two by the end to end identification, and releases the cover for settlement. Testing resequencing means sending messages out of order, confirming the early message is held, confirming it is released when its predecessor arrives, and confirming nothing is processed twice.

Holding and matching protect the customer, because acting on an early message can credit the wrong account, release funds before the cover has arrived, or report a payment as settled when settlement has not happened. The holding area must be visible on the operations dashboard, with the age of each held message, the missing predecessor, and the time at which it will escalate. An operator can release a held message manually only with a recorded reason and a second approval for large amounts, so a manual release is a controlled act rather than a shortcut. In the worked example, the USD 120,000 cover sits in the holding area at Harbour Bank for ninety minutes, visible to operations with its missing announcement flagged, and no operator releases it early because the rule forbids crediting a supplier before the cover and the announcement are matched.

The business rules decide when to wait and when to act, balancing delay against the risk of acting on incomplete information. A bank waits when the missing piece is essential, such as the cover or the settlement confirmation that proves finality, and it acts when the missing piece is only informational, such as a remittance detail that changes neither amount nor beneficiary. Each rule carries a maximum waiting time, and on expiry the payment is escalated to operations with the full history attached. In the worked example, Harbour Bank waits for the announcement because it confirms the cover belongs to the USD 120,000 payment, but it does not wait for the remittance detail, which arrives later and is matched to the settled payment. Testing these rules means sending each message type early, confirming the wait or act decision matches the rule, and confirming escalation fires on expiry.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.