The Hold&Release service was launched in December 2014.
The Hold&Release mechanism provides clients with the ability to use a new instruction status "for matching" to manage operation execution. An instruction in "for matching" status is not sent for execution and can only be executed after client confirmation - by changing the instruction status to "for execution". The new "for matching" status allows suspending execution at the following stages of the instruction lifecycle:
When submitting an instruction to NSD, the client can specify two statuses: "for execution" and "for matching". The instruction lifecycle for both options will be the same up to the execution stage. Instructions with "for matching" status do not proceed to the "execution" stage, i.e., cannot be executed until the status of both instructions in the matched pair changes to "for execution". Using the "for matching" status only prevents execution of matched instructions, while this status does not affect existing procedures: search for potential matching instructions (preliminary matching), matching, reservation of funds and other procedures. Including, changing from "for matching" status to "for execution" status does not affect the execution priority of matched instructions.
To change the instruction status via LUCH software, operation code 530 is used, for which two completion methods are provided:
Create MF530 instruction "Change Instruction Details", specifying the details of the original instruction and its new status.
Select the original instruction previously submitted to NSD, and create MF530 automatically via the "Change Status" button. In this case, the system will independently determine the parameters of the original instruction and its new status.
Two methods are also available for managing statuses via SWIFT system:
All SWIFT instructions after receipt at NSD are converted to operation code 530. Examples of completing SWIFT instructions are presented in the "User Guide".
Requirements for instruction status change operation:
If the MF530 instruction does not meet the requirements described above, the operation will be rejected.
Instruction status does not affect the instruction cancellation procedure. The original instruction before matching can be cancelled in any status. If the instruction was matched, bilateral cancellation is required - cancellation instructions must be received from both parties to the transaction. Matched FOP instructions are cancelled unilaterally after the execution period expires.