ZagTrader

Settlement status codes

CYCL: Awaiting Next Settlement Cycle

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

CYCL tells you that the instruction is ready to settle and is simply waiting for the next settlement cycle or batch of the settlement system. No problem is reported on either side.

Code
CYCL
Kind
Reason (24B)
Used with
PEND, PENF

What CYCL means

Many settlement systems do not settle continuously. They run night-time and daytime cycles or batches, and an instruction that is matched and covered settles in the next one. CYCL says the instruction is in that queue: nothing is missing, it only needs the system to run.

Under PEND the next cycle still falls on the intended settlement date. Under PENF the instruction has already missed its date and will settle in a later cycle; it counts as a fail even though no cause is given. T2S uses this pattern: a matched leg with nothing wrong is reported as pending with FUTU, and once failing with CYCL, because FUTU is not used for failing instructions (ECB T2S CR-658 presentation).

In ISO 20022 the code list has moved: sese.024.001.08 to .001.10 allow CYCL as a pending reason and a failing reason, but from sese.024.001.11 the pending reason list no longer contains it and CYCL remains only as a failing reason. An MT548 still allows it under both PEND and PENF.

When you see it

  • In an MT548 or sese.024 after matching, in markets with batch or cycle settlement, and as the failing reason when an instruction missed its date for a reason that has since gone away (for example after a hold was released).
  • On the MT537 for instructions that settle overnight.

What to do next

  • Usually nothing: wait for the next cycle and look for the settlement confirmation (MT544 to MT547, or sese.025).
  • If PENF//CYCL persists across several cycles, ask the custodian what is really blocking settlement; a generic reason that does not change can hide a missing counterparty instruction or a position problem.

Where it appears in MT and ISO 20022

MT (ISO 15022)

  • MT548 sequence A2a (REAS), :24B::PEND//CYCL after :25D::SETT//PEND, or :24B::PENF//CYCL after :25D::SETT//PENF.
  • MT537 sequence B1 or C3a, :24B::PEND//CYCL or :24B::PENF//CYCL.

MX (ISO 20022)

  • sese.024 SttlmSts/Flng/Rsn/Cd/Cd = CYCL (failing), in every version from .001.08 to .001.14.
  • sese.024 SttlmSts/Pdg/Rsn/Cd/Cd = CYCL (pending) only in sese.024.001.08 to .001.10; the pending reason code lists of .001.11 and later do not contain it.

Questions

What does PENF CYCL mean in MT548?
The instruction missed its intended settlement date but nothing is currently blocking it: it waits for the next settlement cycle. It is still a fail. If it does not settle in the next cycle, ask the custodian for the real cause.
What is the difference between FUTU and CYCL?
FUTU means the intended settlement date has not been reached and nothing is wrong. CYCL means the instruction is ready and waits for the next cycle of the settlement system; under PENF it is the generic reason for a failing instruction with no specific problem.
Why can I not send CYCL as a pending reason in newer sese.024 versions?
From sese.024.001.11 the pending reason code list no longer includes CYCL; it stays in the failing reason list. Translating an MT548 :24B::PEND//CYCL into a newer sese.024 therefore needs a different pending reason, typically agreed in market practice; check your CSD’s usage guide.