 |
Scope
An executing party, eg, a transfer agent, sends the OrderCancellationStatusReport to the instructing party, eg, an investment manager or its authorised representative, to report the status of an order cancellation request that was previously received.
Usage
The OrderCancellationStatusReport message is used to provide the status of:
- one or more individual order cancellation requests by using IndividualCancellationStatusReport, or,
- an order cancellation request message by using CancellationStatusReport.
If the OrderCancellationStatusReport message is used to report the status of an individual order cancellation request, then the repetitive IndividualCancellationStatusReport sequence is used and the order reference of the individual order is quoted in OrderReference. The messageidentification of the message in which the individual order was conveyed may also be quoted in RelatedReference.
If the OrderCancellationStatusReport message is used to report the status of an entire order cancellation request message, for example, the SubscriptionBulkOrderCancellationRequest, or a SubscriptionOrderCancellationRequest containing several orders, then the CancellationStatusReport sequence. is used and the message identification of the order cancellation request message is quoted in RelatedReference.
All the order cancellation requests within the message must have the same status. One of the following statuses can be reported:
- the order cancellation is pending, or,
- the order cancellation request is rejected, or,
- the order is cancelled.
When the cancellation is rejected, the reason for the rejection must be specified.
Main characteristics
The OrderCancellationStatusReport message has the following main characteristics:
References
It is mandatory to include the reference of the previously sent message, ie the OrderCancellationInstruction, for which the Sender is requesting a status. Status must be either specified in the CancellationStatusReport building block or in the IndividualCancellationStatusReport building block. If it is in the CancellationStatusReport building block, then that building block is mandatory. If it is in the IndividualCancellationStatusReport building block, then that building block is mandatory.
CancellationStatusReport
This building block can be mandatory (see rule above) but is not repetitive. This means that it is not possible to report on more than one cancellation instruction per message. It is mandatory to specify either the status of the order instruction (using Status) or why cancellation is not possible (using Rejected).
IndividualCancellationStatusReport
This building block can be mandatory (see rule above) and is repetitive. This means that it is possible to report on more than one cancellation instruction per message. It is mandatory to specify either the status of the order instruction (using Status) or why cancellation is not possible (using Rejected).
|
