setr

type Document00100102 ¶

type Document00100102 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:setr.001.001.02 Document"`
	Message *RedemptionBulkOrderV02 `xml:"setr.001.001.02"`
}

func (d *Document00100102) AddMessage() *RedemptionBulkOrderV02

type Document00100103 ¶

type Document00100103 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:setr.001.001.03 Document"`
	Message *RedemptionBulkOrderV03 `xml:"RedBlkOrdrV03"`
}

func (d *Document00100103) AddMessage() *RedemptionBulkOrderV03

type Document00100104 ¶

type Document00100104 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:setr.001.001.04 Document"`
	Message *RedemptionBulkOrderV04 `xml:"RedBlkOrdr"`
}

func (d *Document00100104) AddMessage() *RedemptionBulkOrderV04

type Document00200102 ¶

type Document00200102 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:setr.002.001.02 Document"`
	Message *RedemptionBulkOrderCancellationInstructionV02 `xml:"setr.002.001.02"`
}

func (d *Document00200102) AddMessage() *RedemptionBulkOrderCancellationInstructionV02

type Document00200103 ¶

type Document00200103 struct {
	XMLName xml.Name                                   `xml:"urn:iso:std:iso:20022:tech:xsd:setr.002.001.03 Document"`
	Message *RedemptionBulkOrderCancellationRequestV03 `xml:"RedBlkOrdrCxlReqV03"`
}

func (d *Document00200103) AddMessage() *RedemptionBulkOrderCancellationRequestV03

type Document00200104 ¶

type Document00200104 struct {
	XMLName xml.Name                                   `xml:"urn:iso:std:iso:20022:tech:xsd:setr.002.001.04 Document"`
	Message *RedemptionBulkOrderCancellationRequestV04 `xml:"RedBlkOrdrCxlReq"`
}

func (d *Document00200104) AddMessage() *RedemptionBulkOrderCancellationRequestV04

type Document00300102 ¶

type Document00300102 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:setr.003.001.02 Document"`
	Message *RedemptionBulkOrderConfirmationV02 `xml:"setr.003.001.02"`
}

func (d *Document00300102) AddMessage() *RedemptionBulkOrderConfirmationV02

type Document00300103 ¶

type Document00300103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:setr.003.001.03 Document"`
	Message *RedemptionBulkOrderConfirmationV03 `xml:"RedBlkOrdrConfV03"`
}

func (d *Document00300103) AddMessage() *RedemptionBulkOrderConfirmationV03

type Document00300104 ¶

type Document00300104 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:setr.003.001.04 Document"`
	Message *RedemptionBulkOrderConfirmationV04 `xml:"RedBlkOrdrConf"`
}

func (d *Document00300104) AddMessage() *RedemptionBulkOrderConfirmationV04

type Document00400102 ¶

type Document00400102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.004.001.02 Document"`
	Message *RedemptionMultipleOrderV02 `xml:"setr.004.001.02"`
}

func (d *Document00400102) AddMessage() *RedemptionMultipleOrderV02

type Document00400103 ¶

type Document00400103 struct {
	XMLName xml.Name            `xml:"urn:iso:std:iso:20022:tech:xsd:setr.004.001.03 Document"`
	Message *RedemptionOrderV03 `xml:"RedOrdrV03"`
}

func (d *Document00400103) AddMessage() *RedemptionOrderV03

type Document00400104 ¶

type Document00400104 struct {
	XMLName xml.Name            `xml:"urn:iso:std:iso:20022:tech:xsd:setr.004.001.04 Document"`
	Message *RedemptionOrderV04 `xml:"RedOrdr"`
}

func (d *Document00400104) AddMessage() *RedemptionOrderV04

type Document00500102 ¶

type Document00500102 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:setr.005.001.02 Document"`
	Message *RedemptionMultipleOrderCancellationInstructionV02 `xml:"setr.005.001.02"`
}

func (d *Document00500102) AddMessage() *RedemptionMultipleOrderCancellationInstructionV02

type Document00500103 ¶

type Document00500103 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:setr.005.001.03 Document"`
	Message *RedemptionOrderCancellationRequestV03 `xml:"RedOrdrCxlReqV03"`
}

func (d *Document00500103) AddMessage() *RedemptionOrderCancellationRequestV03

type Document00500104 ¶

type Document00500104 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:setr.005.001.04 Document"`
	Message *RedemptionOrderCancellationRequestV04 `xml:"RedOrdrCxlReq"`
}

func (d *Document00500104) AddMessage() *RedemptionOrderCancellationRequestV04

type Document00600102 ¶

type Document00600102 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:setr.006.001.02 Document"`
	Message *RedemptionMultipleOrderConfirmationV02 `xml:"setr.006.001.02"`
}

func (d *Document00600102) AddMessage() *RedemptionMultipleOrderConfirmationV02

type Document00600103 ¶

type Document00600103 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.006.001.03 Document"`
	Message *RedemptionOrderConfirmationV03 `xml:"RedOrdrConfV03"`
}

func (d *Document00600103) AddMessage() *RedemptionOrderConfirmationV03

type Document00600104 ¶

type Document00600104 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.006.001.04 Document"`
	Message *RedemptionOrderConfirmationV04 `xml:"RedOrdrConf"`
}

func (d *Document00600104) AddMessage() *RedemptionOrderConfirmationV04

type Document00700102 ¶

type Document00700102 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:setr.007.001.02 Document"`
	Message *SubscriptionBulkOrderV02 `xml:"setr.007.001.02"`
}

func (d *Document00700102) AddMessage() *SubscriptionBulkOrderV02

type Document00700103 ¶

type Document00700103 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:setr.007.001.03 Document"`
	Message *SubscriptionBulkOrderV03 `xml:"SbcptBlkOrdrV03"`
}

func (d *Document00700103) AddMessage() *SubscriptionBulkOrderV03

type Document00700104 ¶

type Document00700104 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:setr.007.001.04 Document"`
	Message *SubscriptionBulkOrderV04 `xml:"SbcptBlkOrdr"`
}

func (d *Document00700104) AddMessage() *SubscriptionBulkOrderV04

type Document00800102 ¶

type Document00800102 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:setr.008.001.02 Document"`
	Message *SubscriptionBulkOrderCancellationInstructionV02 `xml:"setr.008.001.02"`
}

func (d *Document00800102) AddMessage() *SubscriptionBulkOrderCancellationInstructionV02

type Document00800103 ¶

type Document00800103 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:setr.008.001.03 Document"`
	Message *SubscriptionBulkOrderCancellationRequestV03 `xml:"SbcptBlkOrdrCxlReqV03"`
}

func (d *Document00800103) AddMessage() *SubscriptionBulkOrderCancellationRequestV03

type Document00800104 ¶

type Document00800104 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:setr.008.001.04 Document"`
	Message *SubscriptionBulkOrderCancellationRequestV04 `xml:"SbcptBlkOrdrCxlReq"`
}

func (d *Document00800104) AddMessage() *SubscriptionBulkOrderCancellationRequestV04

type Document00900102 ¶

type Document00900102 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:setr.009.001.02 Document"`
	Message *SubscriptionBulkOrderConfirmationV02 `xml:"setr.009.001.02"`
}

func (d *Document00900102) AddMessage() *SubscriptionBulkOrderConfirmationV02

type Document00900103 ¶

type Document00900103 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:setr.009.001.03 Document"`
	Message *SubscriptionBulkOrderConfirmationV03 `xml:"SbcptBlkOrdrConfV03"`
}

func (d *Document00900103) AddMessage() *SubscriptionBulkOrderConfirmationV03

type Document00900104 ¶

type Document00900104 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:setr.009.001.04 Document"`
	Message *SubscriptionBulkOrderConfirmationV04 `xml:"SbcptBlkOrdrConf"`
}

func (d *Document00900104) AddMessage() *SubscriptionBulkOrderConfirmationV04

type Document01000102 ¶

type Document01000102 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:setr.010.001.02 Document"`
	Message *SubscriptionMultipleOrderV02 `xml:"setr.010.001.02"`
}

func (d *Document01000102) AddMessage() *SubscriptionMultipleOrderV02

type Document01000103 ¶

type Document01000103 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:setr.010.001.03 Document"`
	Message *SubscriptionOrderV03 `xml:"SbcptOrdrV03"`
}

func (d *Document01000103) AddMessage() *SubscriptionOrderV03

type Document01000104 ¶

type Document01000104 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:setr.010.001.04 Document"`
	Message *SubscriptionOrderV04 `xml:"SbcptOrdr"`
}

func (d *Document01000104) AddMessage() *SubscriptionOrderV04

type Document01100102 ¶

type Document01100102 struct {
	XMLName xml.Name                                             `xml:"urn:iso:std:iso:20022:tech:xsd:setr.011.001.02 Document"`
	Message *SubscriptionMultipleOrderCancellationInstructionV02 `xml:"setr.011.001.02"`
}

func (d *Document01100102) AddMessage() *SubscriptionMultipleOrderCancellationInstructionV02

type Document01100103 ¶

type Document01100103 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:setr.011.001.03 Document"`
	Message *SubscriptionOrderCancellationRequestV03 `xml:"SbcptOrdrCxlReqV03"`
}

func (d *Document01100103) AddMessage() *SubscriptionOrderCancellationRequestV03

type Document01100104 ¶

type Document01100104 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:setr.011.001.04 Document"`
	Message *SubscriptionOrderCancellationRequestV04 `xml:"SbcptOrdrCxlReq"`
}

func (d *Document01100104) AddMessage() *SubscriptionOrderCancellationRequestV04

type Document01200102 ¶

type Document01200102 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:setr.012.001.02 Document"`
	Message *SubscriptionMultipleOrderConfirmationV02 `xml:"setr.012.001.02"`
}

func (d *Document01200102) AddMessage() *SubscriptionMultipleOrderConfirmationV02

type Document01200103 ¶

type Document01200103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.012.001.03 Document"`
	Message *SubscriptionOrderConfirmationV03 `xml:"SbcptOrdrConfV03"`
}

func (d *Document01200103) AddMessage() *SubscriptionOrderConfirmationV03

type Document01200104 ¶

type Document01200104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.012.001.04 Document"`
	Message *SubscriptionOrderConfirmationV04 `xml:"SbcptOrdrConf"`
}

func (d *Document01200104) AddMessage() *SubscriptionOrderConfirmationV04

type Document01300102 ¶

type Document01300102 struct {
	XMLName xml.Name        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.013.001.02 Document"`
	Message *SwitchOrderV02 `xml:"setr.013.001.02"`
}

func (d *Document01300102) AddMessage() *SwitchOrderV02

type Document01300103 ¶

type Document01300103 struct {
	XMLName xml.Name        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.013.001.03 Document"`
	Message *SwitchOrderV03 `xml:"SwtchOrdrV03"`
}

func (d *Document01300103) AddMessage() *SwitchOrderV03

type Document01300104 ¶

type Document01300104 struct {
	XMLName xml.Name        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.013.001.04 Document"`
	Message *SwitchOrderV04 `xml:"SwtchOrdr"`
}

func (d *Document01300104) AddMessage() *SwitchOrderV04

type Document01400102 ¶

type Document01400102 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:setr.014.001.02 Document"`
	Message *SwitchOrderCancellationInstructionV02 `xml:"setr.014.001.02"`
}

func (d *Document01400102) AddMessage() *SwitchOrderCancellationInstructionV02

type Document01400103 ¶

type Document01400103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:setr.014.001.03 Document"`
	Message *SwitchOrderCancellationRequestV03 `xml:"SwtchOrdrCxlReqV03"`
}

func (d *Document01400103) AddMessage() *SwitchOrderCancellationRequestV03

type Document01400104 ¶

type Document01400104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:setr.014.001.04 Document"`
	Message *SwitchOrderCancellationRequestV04 `xml:"SwtchOrdrCxlReq"`
}

func (d *Document01400104) AddMessage() *SwitchOrderCancellationRequestV04

type Document01500102 ¶

type Document01500102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.015.001.02 Document"`
	Message *SwitchOrderConfirmationV02 `xml:"setr.015.001.02"`
}

func (d *Document01500102) AddMessage() *SwitchOrderConfirmationV02

type Document01500103 ¶

type Document01500103 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.015.001.03 Document"`
	Message *SwitchOrderConfirmationV03 `xml:"SwtchOrdrConfV03"`
}

func (d *Document01500103) AddMessage() *SwitchOrderConfirmationV03

type Document01500104 ¶

type Document01500104 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.015.001.04 Document"`
	Message *SwitchOrderConfirmationV04 `xml:"SwtchOrdrConf"`
}

func (d *Document01500104) AddMessage() *SwitchOrderConfirmationV04

type Document01600102 ¶

type Document01600102 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:setr.016.001.02 Document"`
	Message *OrderInstructionStatusReportV02 `xml:"setr.016.001.02"`
}

func (d *Document01600102) AddMessage() *OrderInstructionStatusReportV02

type Document01600103 ¶

type Document01600103 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:setr.016.001.03 Document"`
	Message *OrderInstructionStatusReportV03 `xml:"OrdrInstrStsRptV03"`
}

func (d *Document01600103) AddMessage() *OrderInstructionStatusReportV03

type Document01600104 ¶

type Document01600104 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:setr.016.001.04 Document"`
	Message *OrderInstructionStatusReportV04 `xml:"OrdrInstrStsRpt"`
}

func (d *Document01600104) AddMessage() *OrderInstructionStatusReportV04

type Document01700102 ¶

type Document01700102 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.017.001.02 Document"`
	Message *OrderCancellationStatusReportV02 `xml:"setr.017.001.02"`
}

func (d *Document01700102) AddMessage() *OrderCancellationStatusReportV02

type Document01700103 ¶

type Document01700103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.017.001.03 Document"`
	Message *OrderCancellationStatusReportV03 `xml:"OrdrCxlStsRptV03"`
}

func (d *Document01700103) AddMessage() *OrderCancellationStatusReportV03

type Document01700104 ¶

type Document01700104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.017.001.04 Document"`
	Message *OrderCancellationStatusReportV04 `xml:"OrdrCxlStsRpt"`
}

func (d *Document01700104) AddMessage() *OrderCancellationStatusReportV04

type Document01800102 ¶

type Document01800102 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.018.001.02 Document"`
	Message *RequestForOrderStatusReportV02 `xml:"setr.018.001.02"`
}

func (d *Document01800102) AddMessage() *RequestForOrderStatusReportV02

type Document01800103 ¶

type Document01800103 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.018.001.03 Document"`
	Message *RequestForOrderStatusReportV03 `xml:"ReqForOrdrStsRptV03"`
}

func (d *Document01800103) AddMessage() *RequestForOrderStatusReportV03

type Document01800104 ¶

type Document01800104 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.018.001.04 Document"`
	Message *RequestForOrderStatusReportV04 `xml:"ReqForOrdrStsRpt"`
}

func (d *Document01800104) AddMessage() *RequestForOrderStatusReportV04

type Document02700101 ¶

type Document02700101 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.027.001.01 Document"`
	Message *SecuritiesTradeConfirmationV01 `xml:"SctiesTradConf"`
}

func (d *Document02700101) AddMessage() *SecuritiesTradeConfirmationV01

type Document02700102 ¶

type Document02700102 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.027.001.02 Document"`
	Message *SecuritiesTradeConfirmationV02 `xml:"SctiesTradConf"`
}

func (d *Document02700102) AddMessage() *SecuritiesTradeConfirmationV02

type Document02700103 ¶

type Document02700103 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:setr.027.001.03 Document"`
	Message *SecuritiesTradeConfirmationV03 `xml:"SctiesTradConf"`
}

func (d *Document02700103) AddMessage() *SecuritiesTradeConfirmationV03

type Document02900101 ¶

type Document02900101 struct {
	XMLName xml.Name                                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.029.001.01 Document"`
	Message *SecuritiesTradeConfirmationCancellationV01 `xml:"SctiesTradConfCxl"`
}

func (d *Document02900101) AddMessage() *SecuritiesTradeConfirmationCancellationV01

type Document03000101 ¶

type Document03000101 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:setr.030.001.01 Document"`
	Message *SecuritiesTradeConfirmationResponseV01 `xml:"SctiesTradConfRspn"`
}

func (d *Document03000101) AddMessage() *SecuritiesTradeConfirmationResponseV01

type Document04400101 ¶

type Document04400101 struct {
	XMLName xml.Name                                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.044.001.01 Document"`
	Message *SecuritiesTradeConfirmationStatusAdviceV01 `xml:"SctiesTradConfStsAdvc"`
}

func (d *Document04400101) AddMessage() *SecuritiesTradeConfirmationStatusAdviceV01

type Document04400102 ¶

type Document04400102 struct {
	XMLName xml.Name                                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.044.001.02 Document"`
	Message *SecuritiesTradeConfirmationStatusAdviceV02 `xml:"SctiesTradConfStsAdvc"`
}

func (d *Document04400102) AddMessage() *SecuritiesTradeConfirmationStatusAdviceV02

type Document04700101 ¶

type Document04700101 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:setr.047.001.01 Document"`
	Message *SubscriptionOrderConfirmationCancellationInstructionV01 `xml:"SbcptOrdrConfCxlInstrV01"`
}

func (d *Document04700101) AddMessage() *SubscriptionOrderConfirmationCancellationInstructionV01

type Document04700102 ¶

type Document04700102 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:setr.047.001.02 Document"`
	Message *SubscriptionOrderConfirmationCancellationInstructionV02 `xml:"SbcptOrdrConfCxlInstr"`
}

func (d *Document04700102) AddMessage() *SubscriptionOrderConfirmationCancellationInstructionV02

type Document04800101 ¶

type Document04800101 struct {
	XMLName xml.Name                                   `xml:"urn:iso:std:iso:20022:tech:xsd:setr.048.001.01 Document"`
	Message *SubscriptionOrderConfirmationAmendmentV01 `xml:"SbcptOrdrConfAmdmntV01"`
}

func (d *Document04800101) AddMessage() *SubscriptionOrderConfirmationAmendmentV01

type Document04900101 ¶

type Document04900101 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:setr.049.001.01 Document"`
	Message *SubscriptionBulkOrderConfirmationCancellationInstructionV01 `xml:"SbcptBlkOrdrConfCxlInstrV01"`
}

func (d *Document04900101) AddMessage() *SubscriptionBulkOrderConfirmationCancellationInstructionV01

type Document04900102 ¶

type Document04900102 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:setr.049.001.02 Document"`
	Message *SubscriptionBulkOrderConfirmationCancellationInstructionV02 `xml:"SbcptBlkOrdrConfCxlInstr"`
}

func (d *Document04900102) AddMessage() *SubscriptionBulkOrderConfirmationCancellationInstructionV02

type Document05000101 ¶

type Document05000101 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:setr.050.001.01 Document"`
	Message *SubscriptionBulkOrderConfirmationAmendmentV01 `xml:"SbcptBlkOrdrConfAmdmntV01"`
}

func (d *Document05000101) AddMessage() *SubscriptionBulkOrderConfirmationAmendmentV01

type Document05100101 ¶

type Document05100101 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:setr.051.001.01 Document"`
	Message *RedemptionOrderConfirmationCancellationInstructionV01 `xml:"RedOrdrConfCxlInstrV01"`
}

func (d *Document05100101) AddMessage() *RedemptionOrderConfirmationCancellationInstructionV01

type Document05100102 ¶

type Document05100102 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:setr.051.001.02 Document"`
	Message *RedemptionOrderConfirmationCancellationInstructionV02 `xml:"RedOrdrConfCxlInstr"`
}

func (d *Document05100102) AddMessage() *RedemptionOrderConfirmationCancellationInstructionV02

type Document05200101 ¶

type Document05200101 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:setr.052.001.01 Document"`
	Message *RedemptionOrderConfirmationAmendmentV01 `xml:"RedOrdrConfAmdmntV01"`
}

func (d *Document05200101) AddMessage() *RedemptionOrderConfirmationAmendmentV01

type Document05300101 ¶

type Document05300101 struct {
	XMLName xml.Name                                                   `xml:"urn:iso:std:iso:20022:tech:xsd:setr.053.001.01 Document"`
	Message *RedemptionBulkOrderConfirmationCancellationInstructionV01 `xml:"RedBlkOrdrConfCxlInstrV01"`
}

func (d *Document05300101) AddMessage() *RedemptionBulkOrderConfirmationCancellationInstructionV01

type Document05300102 ¶

type Document05300102 struct {
	XMLName xml.Name                                                   `xml:"urn:iso:std:iso:20022:tech:xsd:setr.053.001.02 Document"`
	Message *RedemptionBulkOrderConfirmationCancellationInstructionV02 `xml:"RedBlkOrdrConfCxlInstr"`
}

func (d *Document05300102) AddMessage() *RedemptionBulkOrderConfirmationCancellationInstructionV02

type Document05400101 ¶

type Document05400101 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:setr.054.001.01 Document"`
	Message *RedemptionBulkOrderConfirmationAmendmentV01 `xml:"RedBlkOrdrConfAmdmntV01"`
}

func (d *Document05400101) AddMessage() *RedemptionBulkOrderConfirmationAmendmentV01

type Document05500101 ¶

type Document05500101 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:setr.055.001.01 Document"`
	Message *SwitchOrderConfirmationCancellationInstructionV01 `xml:"SwtchOrdrConfCxlInstrV01"`
}

func (d *Document05500101) AddMessage() *SwitchOrderConfirmationCancellationInstructionV01

type Document05500102 ¶

type Document05500102 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:setr.055.001.02 Document"`
	Message *SwitchOrderConfirmationCancellationInstructionV02 `xml:"SwtchOrdrConfCxlInstr"`
}

func (d *Document05500102) AddMessage() *SwitchOrderConfirmationCancellationInstructionV02

type Document05600101 ¶

type Document05600101 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:setr.056.001.01 Document"`
	Message *SwitchOrderConfirmationAmendmentV01 `xml:"SwtchOrdrConfAmdmntV01"`
}

func (d *Document05600101) AddMessage() *SwitchOrderConfirmationAmendmentV01

type Document05700101 ¶

type Document05700101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.057.001.01 Document"`
	Message *OrderConfirmationStatusReportV01 `xml:"OrdrConfStsRptV01"`
}

func (d *Document05700101) AddMessage() *OrderConfirmationStatusReportV01

type Document05700102 ¶

type Document05700102 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:setr.057.001.02 Document"`
	Message *OrderConfirmationStatusReportV02 `xml:"OrdrConfStsRpt"`
}

func (d *Document05700102) AddMessage() *OrderConfirmationStatusReportV02

type Document05800101 ¶

type Document05800101 struct {
	XMLName xml.Name                                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.058.001.01 Document"`
	Message *RequestForOrderConfirmationStatusReportV01 `xml:"ReqForOrdrConfStsRptV01"`
}

func (d *Document05800101) AddMessage() *RequestForOrderConfirmationStatusReportV01

type Document05800102 ¶

type Document05800102 struct {
	XMLName xml.Name                                    `xml:"urn:iso:std:iso:20022:tech:xsd:setr.058.001.02 Document"`
	Message *RequestForOrderConfirmationStatusReportV02 `xml:"ReqForOrdrConfStsRpt"`
}

func (d *Document05800102) AddMessage() *RequestForOrderConfirmationStatusReportV02

type OrderCancellationStatusReportV02 ¶

type OrderCancellationStatusReportV02 struct {

	// Reference to a linked message that was previously received.
	RelatedReference []*iso20022.AdditionalReference3 `xml:"RltdRef"`

	// Reference to a linked message sent in a proprietary way or reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef"`

	// Status report details of a bulk or multiple or switch order cancellation instruction that was previously received.
	CancellationStatusReport *iso20022.OrderStatusAndReason4 `xml:"CxlStsRpt"`
}

Scope The OrderCancellationStatusReport is sent by an executing party, eg, a transfer agent, to the instructing party, eg, an investment manager or its authorised representative. There may be one or more intermediary parties between the executing party and the instructing party. The intermediary party is, for example, an intermediary or a concentrator. The message gives the status of an order cancellation instruction message that was previously sent by the instructing party. Usage The OrderCancellationStatusReport message is used to report the status of an order cancellation instruction message that was previously sent by the instructing party. The message can be used to report one of the following: - the cancellation is accepted for further processing, or - the cancellation is rejected, or - the order has been cancelled. When the cancellation is rejected, the reason for the rejection must be specified.

func (o *OrderCancellationStatusReportV02) AddCancellationStatusReport() *iso20022.OrderStatusAndReason4

func (o *OrderCancellationStatusReportV02) AddOtherReference() *iso20022.AdditionalReference3

func (o *OrderCancellationStatusReportV02) AddRelatedReference() *iso20022.AdditionalReference3

type OrderCancellationStatusReportV03 ¶

type OrderCancellationStatusReportV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to a linked message that was previously received.
	RelatedReference []*iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// Reference to a linked message sent in a proprietary way or reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Status report details of a bulk or multiple or switch order cancellation message.
	CancellationStatusReport *iso20022.OrderStatusAndReason8 `xml:"CxlStsRpt"`

	// Status report details of one or more individual orders from a bulk or multiple or switch order cancellation request.
	IndividualCancellationStatusReport []*iso20022.IndividualOrderStatusAndReason4 `xml:"IndvCxlStsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the OrderCancellationStatusReport to the instructing party, for example, 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 message identification 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.

func (o *OrderCancellationStatusReportV03) AddCancellationStatusReport() *iso20022.OrderStatusAndReason8

func (o *OrderCancellationStatusReportV03) AddExtension() *iso20022.Extension1

func (o *OrderCancellationStatusReportV03) AddIndividualCancellationStatusReport() *iso20022.IndividualOrderStatusAndReason4

func (o *OrderCancellationStatusReportV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderCancellationStatusReportV03) AddOtherReference() *iso20022.AdditionalReference3

func (o *OrderCancellationStatusReportV03) AddRelatedReference() *iso20022.AdditionalReference3

type OrderCancellationStatusReportV04 ¶

type OrderCancellationStatusReportV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to the message or communication that was previously received.
	Reference *iso20022.References61Choice `xml:"Ref,omitempty"`

	// Status of the order cancellation.
	StatusReport *iso20022.Status26Choice `xml:"StsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The OrderCancellationStatusReport message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, 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 message identification of the message in which the individual order was conveyed may also be quoted in RelatedReference but this is not recommended. 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. The message identification of the order cancellation request message may also be quoted in RelatedReference but this is not recommended. 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.

func (o *OrderCancellationStatusReportV04) AddExtension() *iso20022.Extension1

func (o *OrderCancellationStatusReportV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderCancellationStatusReportV04) AddReference() *iso20022.References61Choice

func (o *OrderCancellationStatusReportV04) AddStatusReport() *iso20022.Status26Choice

type OrderConfirmationStatusReportV01 ¶

type OrderConfirmationStatusReportV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to a linked message sent in a proprietary way or reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference []*iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// Status report details of an individual order confirmation.
	IndividualOrderConfirmationDetailsReport []*iso20022.IndividualOrderConfirmationStatusAndReason1 `xml:"IndvOrdrConfDtlsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative, sends the OrderConfirmationStatusReport message to the executing party, for example, a transfer agent, to report the status of an order confirmation or an order confirmation amendment. Usage The OrderConfirmationStatusReport message is used to report on the status of one or more individual: - subscription confirmations, - subscription confirmation amendments, - redemption confirmations, - redemption confirmation amendments, - switch order confirmations, - switch order confirmation amendments. One of the following statuses can be reported: - confirmation rejected, or, - amendment rejected, or, - sent to next party, or, - communication problem with next party, or, - confirmation accepted, or, - confirmation received. It is likely that the OrderConfirmationStatusReport is only sent by the order instructing party to the order executing party to reject an order confirmation or to reject an order confirmation amendment, although if an intermediary party is used, the statuses sent to next party and communication problem with next party are also likely be used. The statuses confirmation accepted and confirmation received would only be used in the event the order executing party sends a RequestForOrderConfirmationStatusReport message and one of the other statuses does not apply. If the status being reported is either confirmation rejected or amendment rejected, then a reason for the rejection must be given. The individual order confirmation or confirmation amendment for which the status is given is identified with its order reference. The message identification of the message in which the individual order confirmation or confirmation amendment was conveyed may also be quoted in RelatedReference, but this is not recommended.

func (o *OrderConfirmationStatusReportV01) AddExtension() *iso20022.Extension1

func (o *OrderConfirmationStatusReportV01) AddIndividualOrderConfirmationDetailsReport() *iso20022.IndividualOrderConfirmationStatusAndReason1

func (o *OrderConfirmationStatusReportV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderConfirmationStatusReportV01) AddOtherReference() *iso20022.AdditionalReference3

func (o *OrderConfirmationStatusReportV01) AddRelatedReference() *iso20022.AdditionalReference3

type OrderConfirmationStatusReportV02 ¶

type OrderConfirmationStatusReportV02 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to the message or communication that was previously received.
	Reference *iso20022.References61Choice `xml:"Ref,omitempty"`

	// Status report details of an individual order confirmation.
	IndividualOrderConfirmationDetailsReport []*iso20022.IndividualOrderConfirmationStatusAndReason2 `xml:"IndvOrdrConfDtlsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The OrderConfirmationStatusReport message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to report the status of an order confirmation or an order confirmation amendment. Usage The OrderConfirmationStatusReport message is used to report on the status of one or more individual: - subscription confirmations, - subscription confirmation amendments, - redemption confirmations, - redemption confirmation amendments, - switch order confirmations, - switch order confirmation amendments. One of the following statuses can be reported: - confirmation rejected, or, - amendment rejected, or, - sent to next party, or, - communication problem with next party, or, - confirmation accepted, or, - confirmation received. It is likely that the OrderConfirmationStatusReport is only sent by the order instructing party to the order executing party to reject an order confirmation or to reject an order confirmation amendment, although if an intermediary party is used, the statuses sent to next party and communication problem with next party are also likely be used. The statuses confirmation accepted and confirmation received would only be used in the event the order executing party sends a RequestForOrderConfirmationStatusReport message and one of the other statuses does not apply. If the status being reported is either confirmation rejected or amendment rejected, then a reason for the rejection must be given. The individual order confirmation or confirmation amendment for which the status is given is identified with its order reference. The message identification of the message in which the individual order confirmation or confirmation amendment was conveyed may also be quoted in RelatedReference, but this is not recommended.

func (o *OrderConfirmationStatusReportV02) AddExtension() *iso20022.Extension1

func (o *OrderConfirmationStatusReportV02) AddIndividualOrderConfirmationDetailsReport() *iso20022.IndividualOrderConfirmationStatusAndReason2

func (o *OrderConfirmationStatusReportV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderConfirmationStatusReportV02) AddReference() *iso20022.References61Choice

type OrderInstructionStatusReportV02 ¶

type OrderInstructionStatusReportV02 struct {

	// Reference to a linked message sent in a proprietary way or reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef"`

	// Reference to a linked message that was previously received.
	RelatedReference []*iso20022.AdditionalReference3 `xml:"RltdRef"`

	// Reference to a multiple order or bulk order that represents the common reference of several individual orders.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Status report details of a bulk or multiple or switch order that was previously received.
	OrderDetailsReport *iso20022.OrderStatusAndReason3 `xml:"OrdrDtlsRpt"`

	// Status report details of the individual orders of a bulk or multiple order that was previously received.
	IndividualOrderDetailsReport []*iso20022.IndividualOrderStatusAndReason1 `xml:"IndvOrdrDtlsRpt"`
}

Scope The OrderInstructionStatusReport is sent by an executing party, eg, a transfer agent, to an instructing party, eg, an investment manager or its authorised representative. There may be one or more intermediary parties between the executing party and the instructing party. The intermediary party is, for example, an intermediary or a concentrator. This message reports the status of an order from the time the executing party receives the order until the order is executed. Usage The OrderInstructionStatusReport message is sent by an executing party to the instructing party to report on the status of a subscription, redemption or a switch order. The message can be used to report one of the following: - a received status, or - an accepted status, or - a sent to next party status, or - an already executed status, or - a cancelled status, or - a conditionally accepted status, or - a rejected status, or - a suspended status, or - an in-repair status (at the individual order level only), or - repaired conditions (at the individual order level only). For subscription and redemption orders, the OrderInstructionStatusReport message covers both bulk and multiple categories of orders, and this message may provide the status either at the bulk or at the individual level. For a switch order, this message provides the status of the whole order, ie, it is not possible to accept one leg and to reject the other leg, the entire switch order has to be rejected. In order to identify which leg within the switch is causing a problem, the redemption or subscription leg identification is used.

func (o *OrderInstructionStatusReportV02) AddIndividualOrderDetailsReport() *iso20022.IndividualOrderStatusAndReason1

func (o *OrderInstructionStatusReportV02) AddMasterReference() *iso20022.AdditionalReference3

func (o *OrderInstructionStatusReportV02) AddOrderDetailsReport() *iso20022.OrderStatusAndReason3

func (o *OrderInstructionStatusReportV02) AddOtherReference() *iso20022.AdditionalReference3

func (o *OrderInstructionStatusReportV02) AddRelatedReference() *iso20022.AdditionalReference3

type OrderInstructionStatusReportV03 ¶

type OrderInstructionStatusReportV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to a linked message sent in a proprietary way or reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference []*iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// Status report details of all the individual orders conveyed in a bulk or multiple order message. Can be used if all the individual orders conveyed in a bulk or multiple order message have the same status.
	OrderDetailsReport *iso20022.OrderStatusAndReason7 `xml:"OrdrDtlsRpt"`

	// Status report details of an individual order.
	IndividualOrderDetailsReport []*iso20022.IndividualOrderStatusAndReason2 `xml:"IndvOrdrDtlsRpt"`

	// Status report details of a switch order.
	SwitchOrderDetailsReport []*iso20022.SwitchOrderStatusAndReason1 `xml:"SwtchOrdrDtlsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the OrderInstructionStatusReport to the instructing party, for example, an investment manager or its authorised representative to report the status of an order from the time the executing party receives the order until the time the order is executed. Usage The OrderInstructionStatusReport message is used to report on the status of a subscription, redemption or a switch order. The OrderInstructionStatusReport message may be used to give the status of: - one order message by using OrderDetailsReport or, - one or more individual order instructions by using IndividualOrderDetailsReport, or - one or more switch orders by using SwitchOrderDetailsReport. If the OrderInstructionStatusReport message is used to report the status of an individual order, then IndividualOrderDetailsReport is used and the order reference of the individual order is quoted in OrderReference. The message identification of the message in which the individual order was conveyed may also be quoted in RelatedReference. If the OrderInstructionStatusReport message is used to report the status of a switch order, then SwitchOrderDetailsReport is used and the order reference of the switch order is quoted in OrderReference. The message identification of the message in which the switch order was conveyed may also be quoted in RelatedReference. If the OrderInstructionStatusReport message is used to report the status of an entire order message, for example, the SubscriptionBulkOrder, or a SubscriptionOrder containing several orders, then OrderDetailsReport is used and the message identification of the order message is quoted in RelatedReference. All the orders within the message must have the same status. One of the following statuses can be reported: - an accepted status , or, - an already executed status, or, - a sent to next party status, or, - a received status, or, - a settled status, or, - a communication problem with next party status, or, - a confirmation amendment status, or, - a done for the day status, or, - a partially done status, or, - an open status, or, - a cancelled status, or - a conditionally accepted status, or, - a rejected status, or, - a suspended status, or, - a partially settled status, or, - an in-repair status (only for an individual or switch order). For a switch order, the OrderInstructionStatusReport message provides the status of the whole switch order, that is, it is not possible to accept one leg and to reject the other leg: the entire switch order has to be rejected. In order to identify the legs within the switch that are causing the problem, the leg is identified in either the RedemptionLegIdentification or SubscriptionLegIdentification elements. When the OrderInstructionStatusReport is used to give the status of an individual or a switch order, the following can be specified: - repaired conditions (for a switch, this is at the level of a leg), - information related to the order, for example, settlement amount, number of units, expected trade date, etc.

func (o *OrderInstructionStatusReportV03) AddExtension() *iso20022.Extension1

func (o *OrderInstructionStatusReportV03) AddIndividualOrderDetailsReport() *iso20022.IndividualOrderStatusAndReason2

func (o *OrderInstructionStatusReportV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderInstructionStatusReportV03) AddOrderDetailsReport() *iso20022.OrderStatusAndReason7

func (o *OrderInstructionStatusReportV03) AddOtherReference() *iso20022.AdditionalReference3

func (o *OrderInstructionStatusReportV03) AddRelatedReference() *iso20022.AdditionalReference3

func (o *OrderInstructionStatusReportV03) AddSwitchOrderDetailsReport() *iso20022.SwitchOrderStatusAndReason1

type OrderInstructionStatusReportV04 ¶

type OrderInstructionStatusReportV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Reference to the message or communication that was previously received.
	Reference *iso20022.References61Choice `xml:"Ref,omitempty"`

	// Status of the order.
	StatusReport *iso20022.Status24Choice `xml:"StsRpt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The OrderInstructionStatusReport message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to report the status of an order from the time the executing party receives the order until the time the order is executed. Usage The OrderInstructionStatusReport message is used to report on the status of a subscription, redemption or a switch order. The OrderInstructionStatusReport message may be used to give the status of: - one order message by using OrderDetailsReport or, - one or more individual order instructions by using IndividualOrderDetailsReport, or - one or more switch orders by using SwitchOrderDetailsReport. If the OrderInstructionStatusReport message is used to report the status of an individual order, then IndividualOrderDetailsReport is used and the order reference of the individual order is quoted in OrderReference. The message identification of the message in which the individual order was conveyed may also be quoted in RelatedReference but this is not recommended. If the OrderInstructionStatusReport message is used to report the status of a switch order, then SwitchOrderDetailsReport is used and the order reference of the switch order is quoted in OrderReference. The message identification of the message in which the switch order was conveyed may also be quoted in RelatedReference but this is not recommended. If the OrderInstructionStatusReport message is used to report the status of an entire order message, for example, the SubscriptionBulkOrder, or a SubscriptionOrder containing several orders, then OrderDetailsReport is used and the message identification of the order message is quoted in RelatedReference. All the orders within the message must have the same status. One of the following statuses can be reported: - an accepted status , or, - an already executed status, or, - a sent to next party status, or, - a received status, or, - a settled status, or, - a communication problem with next party status, or, - a confirmation amendment status, or, - a done for the day status, or, - a partially done status, or, - an open status, or, - a cancelled status, or - a conditionally accepted status, or, - a rejected status, or, - a suspended status, or, - a partially settled status, or, - an in-repair status (only for an individual or switch order). For a switch order, the OrderInstructionStatusReport message provides the status of the whole switch order, that is, it is not possible to accept one leg and to reject the other leg: the entire switch order has to be rejected. In order to identify the legs within the switch that are causing the problem, the leg is identified in either the RedemptionLegIdentification or SubscriptionLegIdentification elements. When the OrderInstructionStatusReport is used to give the status of an individual or a switch order, the following can be specified: - repaired conditions (for a switch, this is at the level of a leg), - information related to the order, for example, settlement amount, number of units, expected trade date.

func (o *OrderInstructionStatusReportV04) AddExtension() *iso20022.Extension1

func (o *OrderInstructionStatusReportV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (o *OrderInstructionStatusReportV04) AddReference() *iso20022.References61Choice

func (o *OrderInstructionStatusReportV04) AddStatusReport() *iso20022.Status24Choice

type RedemptionBulkOrderCancellationInstructionV02 ¶

type RedemptionBulkOrderCancellationInstructionV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference3 `xml:"PrvsRef"`

	// Common information related to all the orders to be cancelled.
	OrderToBeCancelled *iso20022.RedemptionBulkOrderInstruction1 `xml:"OrdrToBeCanc,omitempty"`
}

Scope The RedemptionBulkOrderCancellationInstruction message is sent by an instructing party, eg, an investment manager or its authorised representative, to an executing party, eg, a transfer agent. There may be one or more intermediary parties between the instructing party and the executing party. The intermediary party is, for example, an intermediary or a concentrator. This message is sent to cancel a previously sent RedemptionBulkOrder instruction. Usage The RedemptionBulkOrderCancellationInstruction message is used to cancel the entire previously sent RedemptionBulkOrder message and all the individual orders that it contained. There is no amendment, but a cancellation and re-instruct policy. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended. The deadline and acceptance of a cancellation instruction is subject to a service level agreement (SLA). This cancellation message is a cancellation instruction. There is no automatic acceptance of the cancellation instruction. The rejection or acceptance of a cancellation message instruction is made using an OrderCancellationStatusReport message.

func (r *RedemptionBulkOrderCancellationInstructionV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderCancellationInstructionV02) AddOrderToBeCancelled() *iso20022.RedemptionBulkOrderInstruction1

func (r *RedemptionBulkOrderCancellationInstructionV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderCancellationInstructionV02) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderCancellationRequestV03 ¶

type RedemptionBulkOrderCancellationRequestV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// References of the orders to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrder1 `xml:"CxlByRef,omitempty"`

	// Common information related to all the orders to be cancelled.
	CancellationByOrderDetails *iso20022.RedemptionBulkOrderInstruction2 `xml:"CxlByOrdrDtls,omitempty"`

	// Message is a copy.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative, sends the RedemptionBulkOrderCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent RedemptionBulkOrder instruction. Usage The RedemptionBulkOrderCancellationRequest message is used to either: - request the cancellation of an entire RedemptionBulkOrder message, that is, all the individual orders that it contained, or, - request the cancellation of one or more individual orders included in a previously sent RedemptionBulkOrder message. There is no amendment, but a cancellation and re-instruct policy. There are two ways to use the message. (1) When the RedemptionBulkOrderCancellationRequest message is used to request the cancellation of an entire RedemptionBulkOrder message, this can be done by either: - quoting the order references of all the individual orders listed in the RedemptionBulkOrder message, or, - quoting the details of all the individual orders (this includes the OrderReference) listed in RedemptionBulkOrder message, but this is not recommended. The message identification of the RedemptionBulkOrder message may also be quoted in PreviousReference. It is also possible to request the cancellation of an entire RedemptionBulkOrder message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the RedemptionBulkOrderCancellationRequest message is used to request the cancellation of one or more individual orders, this can be done by either: - quoting the OrderReference of each individual order listed in the RedemptionOrder message, or, - quoting the details of each individual order (including the OrderReference) listed in RedemptionOrder message, but this is not recommended. The message identification of the RedemptionBulkOrder message in which the individual order was conveyed may also be quoted in PreviousReference. The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation.

func (r *RedemptionBulkOrderCancellationRequestV03) AddCancellationByOrderDetails() *iso20022.RedemptionBulkOrderInstruction2

func (r *RedemptionBulkOrderCancellationRequestV03) AddCancellationByReference() *iso20022.InvestmentFundOrder1

func (r *RedemptionBulkOrderCancellationRequestV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionBulkOrderCancellationRequestV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderCancellationRequestV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderCancellationRequestV03) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderCancellationRequestV04 ¶

type RedemptionBulkOrderCancellationRequestV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Identification of the individual order to be cancelled.
	OrderReferences []*iso20022.InvestmentFundOrder9 `xml:"OrdrRefs"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`
}

Scope The RedemptionBulkOrderCancellationRequest message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to request the cancellation of a previously sent RedemptionBulkOrder. Usage The RedemptionBulkOrderCancellationRequest message is used to request the cancellation of one or more individual orders. There is no amendment, but a cancellation and re-instruct policy. To request the cancellation of one or more individual orders, the order reference of each individual order listed in the original RedemptionBulkOrder message is specified in the order reference element. The message identification of the RedemptionBulkOrder message which contains the individual orders to be cancelled may also be quoted in PreviousReference but this is not recommended. The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation. The rejection or acceptance of a RedemptionBulkOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (r *RedemptionBulkOrderCancellationRequestV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionBulkOrderCancellationRequestV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderCancellationRequestV04) AddOrderReferences() *iso20022.InvestmentFundOrder9

func (r *RedemptionBulkOrderCancellationRequestV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionBulkOrderCancellationRequestV04) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionBulkOrderCancellationRequestV04) SetMasterReference(value string)

type RedemptionBulkOrderConfirmationAmendmentV01 ¶

type RedemptionBulkOrderConfirmationAmendmentV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// General information related to the execution of investment fund orders.
	BulkExecutionDetails *iso20022.RedemptionBulkExecution3 `xml:"BlkExctnDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary9 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the RedemptionBulkOrderConfirmationAmendment message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent RedemptionBulkOrderConfirmation message. Usage The RedemptionBulkOrderConfirmationAmendment message is used to amend one or more previously sent redemption bulk order confirmations. Each bulk order confirmation amendment specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionBulkOrder message in which the orders were conveyed may also be quoted in RelatedReference. The message identification of the RedemptionBulkOrderConfirmation message in which the original order confirmations were conveyed may also be quoted in PreviousReference.

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddBulkExecutionDetails() *iso20022.RedemptionBulkExecution3

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddRelatedPartyDetails() *iso20022.Intermediary9

func (r *RedemptionBulkOrderConfirmationAmendmentV01) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderConfirmationCancellationInstructionV01 ¶

type RedemptionBulkOrderConfirmationCancellationInstructionV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// References of the orders to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrderExecution1 `xml:"CxlByRef,omitempty"`

	// Common information related to all the orders to be cancelled.
	CancellationByOrderConfirmationDetails *iso20022.OrderConfirmationDetails1 `xml:"CxlByOrdrConfDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`
}

Scope An executing party, for example, a transfer agent sends the RedemptionBulkOrderConfirmationCancellationInstruction message to the instructing party, for example, an investment manager or its authorised representative to cancel a previously sent RedemptionBulkOrderConfirmation. Usage The RedemptionBulkOrderConfirmationCancellationInstruction message is used to cancel one or more previously sent subscription order confirmations. The amendment indicator element is used to specify whether the subscription order confirmation cancellation is to be followed by a RedemptionBulkOrderConfirmationAmendment. The RedemptionBulkOrderConfirmationCancellationInstruction message is used to either: - cancel an entire RedemptionBulkOrderConfirmation message, that is, all the individual order confirmations that it contained, or, - request the cancellation of one or more individual confirmations. There are two ways to use the message. (1) When the RedemptionBulkOrderConfirmationCancellationInstruction message is used to cancel an entire message, this can be done by either: - quoting the business references, for example, OrderReference, Deal Reference, of all the individual order confirmations listed in the SubscriptionOrderConfirmation message, or, - quoting the details of all the individual order confirmations (this includes the OrderReference and DealReference) listed in SubscriptionOrderConfirmation message but this is not recommended. The message identification of the RedemptionBulkOrderConfirmation message may also be quoted in PreviousReference. It is also possible to instruct the cancellation of an entire confirmation message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the RedemptionBulkOrderConfirmationCancellationInstruction message is used to cancel one or more individual order confirmations, this can be done by either: - quoting the business references, for example, OrderReference, Deal Reference, of each individual order confirmation listed in the RedemptionBulkOrderConfirmation message, or, - quoting the details of each individual order execution (this includes the OrderReference and DealReference) listed in RedemptionBulkOrderConfirmation message but this is not recommended. The message identification of the RedemptionBulkOrderConfirmation message in which the individual order confirmation was conveyed may also be quoted in PreviousReference.

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails() *iso20022.OrderConfirmationDetails1

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByReference() *iso20022.InvestmentFundOrderExecution1

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV01) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderConfirmationCancellationInstructionV02 ¶

type RedemptionBulkOrderConfirmationCancellationInstructionV02 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference8 `xml:"RltdRef,omitempty"`

	// Indicates whether a confirmation amendment message will follow the confirmation cancellation instruction or not.
	AmendmentIndicator *iso20022.YesNoIndicator `xml:"AmdmntInd"`

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Identification of the individual order confirmation to be cancelled.
	OrderReferences []*iso20022.InvestmentFundOrder11 `xml:"OrdrRefs"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`
}

Scope The RedemptionBulkOrderConfirmationCancellationInstruction message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent RedemptionBulkOrderConfirmation. Usage To request the cancellation of one or more individual order executions, the order reference and deal reference of each individual order execution in the original RedemptionBulkOrderConfirmation are specified in the order reference and deal reference elements respectively. The message identification of the RedemptionBulkOrderConfirmation message in which the individual order execution was conveyed may also be quoted in PreviousReference but this is not recommended. The AmendmentIndicator is used to specify whether the redemption order confirmation cancellation is to be followed by an amendment An amendment of a redemption order confirmation is carried out by sending a RedemptionBulkOrderConfirmation message in which the AmendmentIndicator contains the value ‘true’.

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddOrderReferences() *iso20022.InvestmentFundOrder11

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) AddRelatedReference() *iso20022.AdditionalReference8

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) SetMasterReference(value string)

type RedemptionBulkOrderConfirmationV02 ¶

type RedemptionBulkOrderConfirmationV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef"`

	// General information related to the execution of investment fund orders.
	BulkExecutionDetails *iso20022.RedemptionBulkExecution2 `xml:"BlkExctnDtls"`

	// Information related to an intermediary.
	IntermediaryDetails []*iso20022.Intermediary4 `xml:"IntrmyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation1 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionBulkOrderConfirmation message is sent by an executing party, eg, a transfer agent, to an instructing party, eg, an investment manager or its authorised representative. There may be one or more intermediary parties between the executing party and the instructing party. The intermediary party is, for example, an intermediary or a concentrator. This message is used to confirm the details of the execution of a RedemptionBulkOrder message. Usage The RedemptionBulkOrderConfirmation message is sent, after the price has been determined, to confirm the execution of all individual orders. There is usually one bulk confirmation message for one bulk order message. A RedemptionBulkOrder must in all cases be responded to by a RedemptionBulkOrderConfirmation and in no circumstances by a RedemptionMultipleOrderConfirmation. If the executing party needs to confirm a RedemptionMultipleOrder message, then the RedemptionMultipleOrderConfirmation message must be used.

func (r *RedemptionBulkOrderConfirmationV02) AddBulkExecutionDetails() *iso20022.RedemptionBulkExecution2

func (r *RedemptionBulkOrderConfirmationV02) AddCopyDetails() *iso20022.CopyInformation1

func (r *RedemptionBulkOrderConfirmationV02) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderConfirmationV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (r *RedemptionBulkOrderConfirmationV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationV02) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationV02) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderConfirmationV03 ¶

type RedemptionBulkOrderConfirmationV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// General information related to the execution of investment fund orders.
	BulkExecutionDetails *iso20022.RedemptionBulkExecution3 `xml:"BlkExctnDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary9 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the RedemptionBulkOrderConfirmation message to the instructing party, for example, an investment manager or its authorised representative to confirm the details of execution for a previously received RedemptionBulkOrder message. Usage The RedemptionBulkOrderConfirmation message is used to confirm the execution of all individual orders included in a previously sent RedemptionBulkOrder message. There is usually one bulk confirmation message for one bulk order message. Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionBulkOrder message in which the individual order was conveyed may also be quoted in RelatedReference, but this is not recommended. A RedemptionBulkOrder must in all cases be responded to by a RedemptionBulkOrderConfirmation and in no circumstances by a RedemptionOrderConfirmation. If the executing party needs to confirm a RedemptionOrder instruction, then the RedemptionOrderConfirmation must be used.

func (r *RedemptionBulkOrderConfirmationV03) AddBulkExecutionDetails() *iso20022.RedemptionBulkExecution3

func (r *RedemptionBulkOrderConfirmationV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionBulkOrderConfirmationV03) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderConfirmationV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationV03) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderConfirmationV03) AddRelatedPartyDetails() *iso20022.Intermediary9

func (r *RedemptionBulkOrderConfirmationV03) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderConfirmationV04 ¶

type RedemptionBulkOrderConfirmationV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference8 `xml:"RltdRef,omitempty"`

	// General information related to the execution of the orders.
	BulkExecutionDetails *iso20022.RedemptionBulkExecution5 `xml:"BlkExctnDtls"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionBulkOrderConfirmation message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to confirm the details of execution for a previously received RedemptionBulkOrder message. Usage The RedemptionBulkOrderConfirmation message is used to confirm the execution of all individual orders included in a previously sent RedemptionBulkOrder message. There is usually one bulk confirmation message for one bulk order message. Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionBulkOrder message in which the individual order was conveyed may also be quoted in RelatedReference, but this is not recommended. A RedemptionBulkOrder must in all cases be responded to by a RedemptionBulkOrderConfirmation and in no circumstances by a RedemptionOrderConfirmation. If the executing party needs to confirm a RedemptionOrder instruction, then the RedemptionOrderConfirmation must be used. When the message is used to convey a confirmation amendment/s, the AmendmentIndicator must be present with the value ‘true’ or ‘1’. When this is the case, the message must only contain a confirmation amendment/s and not contain both a confirmation amendment/s and a ‘new’ confirmation/s.

func (r *RedemptionBulkOrderConfirmationV04) AddBulkExecutionDetails() *iso20022.RedemptionBulkExecution5

func (r *RedemptionBulkOrderConfirmationV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionBulkOrderConfirmationV04) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderConfirmationV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionBulkOrderConfirmationV04) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionBulkOrderConfirmationV04) AddRelatedReference() *iso20022.AdditionalReference8

type RedemptionBulkOrderV02 ¶

type RedemptionBulkOrderV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Common information related to all the orders.
	BulkOrderDetails *iso20022.RedemptionBulkOrder2 `xml:"BlkOrdrDtls"`

	// The information related to an intermediary.
	IntermediaryDetails []*iso20022.Intermediary4 `xml:"IntrmyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation1 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionBulkOrder message is sent by an instructing party, eg, an investment manager or its authorised representative, to an executing party, eg, a transfer agent. There may be one or more intermediary parties between the instructing party and the executing party. The intermediary party is, for example, an intermediary or a concentrator. This message is used to instruct the executing party to redeem a financial instrument for two or more accounts. Usage The RedemptionBulkOrder message is used to bulk several individual orders into one bulk order. The individual orders come from different instructing parties, ie, account owners, but are the same financial instrument. The RedemptionBulkOrder can result in one single bulk cash settlement or several individual cash settlements. This message will be typically used by a party collecting orders and bulking these individual orders into one bulk order before sending it to another party. For a single redemption order, the RedemptionMultipleOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for different financial instruments but for the same account, then the RedemptionMultipleOrder must be used.

func (r *RedemptionBulkOrderV02) AddBulkOrderDetails() *iso20022.RedemptionBulkOrder2

func (r *RedemptionBulkOrderV02) AddCopyDetails() *iso20022.CopyInformation1

func (r *RedemptionBulkOrderV02) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (r *RedemptionBulkOrderV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderV02) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionBulkOrderV03 ¶

type RedemptionBulkOrderV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Common information related to all the orders.
	BulkOrderDetails *iso20022.RedemptionBulkOrder4 `xml:"BlkOrdrDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary8 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative sends the RedemptionBulkOrder message to the executing party, for example, a transfer agent, to instruct a redemption from a financial instrument for two or more accounts. Usage The RedemptionBulkOrder message is used to bulk several individual orders into one bulk order. The individual orders come from different instructing parties, that is, account owners, but are for the same financial instrument. The RedemptionBulkOrder can result in one single bulk cash settlement or several individual cash settlements. This message will be typically used by a party collecting orders, that is, a concentrator, bulking these individual orders into one bulk order before sending it to an executing party. For a single redemption order, the RedemptionOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for different financial instruments but for the same account, then the RedemptionOrder must be used.

func (r *RedemptionBulkOrderV03) AddBulkOrderDetails() *iso20022.RedemptionBulkOrder4

func (r *RedemptionBulkOrderV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionBulkOrderV03) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderV03) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionBulkOrderV03) AddRelatedPartyDetails() *iso20022.Intermediary8

type RedemptionBulkOrderV04 ¶

type RedemptionBulkOrderV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// General information related to the orders.
	BulkOrderDetails *iso20022.RedemptionBulkOrder6 `xml:"BlkOrdrDtls"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionBulkOrder message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to instruct a redemption from a financial instrument for two or more accounts. Usage The RedemptionBulkOrder message is used to bulk several individual orders into one bulk order. The individual orders come from different instructing parties, that is, account owners, but are for the same financial instrument. The RedemptionBulkOrder can result in one single bulk cash settlement or several individual cash settlements. This message will be typically used by a party collecting orders, that is, a concentrator, bulking these individual orders into one bulk order before sending it to an executing party. For a single redemption order, the RedemptionOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for different financial instruments but for the same account, then the RedemptionOrder must be used.

func (r *RedemptionBulkOrderV04) AddBulkOrderDetails() *iso20022.RedemptionBulkOrder6

func (r *RedemptionBulkOrderV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionBulkOrderV04) AddExtension() *iso20022.Extension1

func (r *RedemptionBulkOrderV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionBulkOrderV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionBulkOrderV04) AddPreviousReference() *iso20022.AdditionalReference8

type RedemptionMultipleOrderCancellationInstructionV02 ¶

type RedemptionMultipleOrderCancellationInstructionV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference3 `xml:"PrvsRef"`

	// Common information related to all the orders to be cancelled.
	OrderToBeCancelled *iso20022.RedemptionMultipleOrderInstruction1 `xml:"OrdrToBeCanc,omitempty"`
}

Scope The RedemptionMultipleOrderCancellationInstruction message is sent by an instructing party, eg, an investment manager or its authorised representative, to an executing party, eg, a transfer agent. There may be one or more intermediary parties between the instructing party and the executing party. The intermediary party is, for example, an intermediary or a concentrator. This message is sent to cancel a previously sent RedemptionMultipleOrder instruction. Usage The RedemptionMultipleOrderCancellationInstruction message is used to cancel the entire previously sent RedemptionMultipleOrder message and all the individual orders that it contained. There is no amendment, but a cancellation and re-instruct policy. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended. The deadline and acceptance of a cancellation instruction is subject to a service level agreement (SLA). This cancellation message is a cancellation instruction. There is no automatic acceptance of the cancellation instruction. The rejection or acceptance of a cancellation message instruction is made using an OrderCancellationStatusReport message.

func (r *RedemptionMultipleOrderCancellationInstructionV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderCancellationInstructionV02) AddOrderToBeCancelled() *iso20022.RedemptionMultipleOrderInstruction1

func (r *RedemptionMultipleOrderCancellationInstructionV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderCancellationInstructionV02) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionMultipleOrderConfirmationV02 ¶

type RedemptionMultipleOrderConfirmationV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef"`

	// General information related to the execution of investment fund orders.
	MultipleExecutionDetails *iso20022.RedemptionMultipleExecution2 `xml:"MltplExctnDtls"`

	// Information related to an intermediary.
	IntermediaryDetails []*iso20022.Intermediary4 `xml:"IntrmyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation1 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionMultipleOrderConfirmation message is sent by an exacting party, eg, a transfer agent, to an instructing party, eg, an investment manager or its authorised representative. There may be one or more intermediary parties between the executing party and the instructing party. The intermediary party is, for example, an intermediary or a concentrator. This message is used to confirm the details of the execution of a RedemptionMultipleOrder message. Usage The RedemptionMultipleOrderConfirmation message is sent, after the price has been determined, to confirm the execution of all individual orders. A RedemptionMultipleOrder may be responded to by more than one RedemptionMultipleOrderConfirmation, as the valuation cycle of the financial instruments in each individual order may be different. When the executing party sends several confirmations, there is no specific indication in the message that it is an incomplete confirmation. Reconciliation must be based on the references. A RedemptionMultipleOrder must in all cases be responded to by a RedemptionMultipleOrderConfirmation message/s and in no circumstances by a RedemptionBulkOrderConfirmation message/s. If the executing party needs to confirm a RedemptionBulkOrder message, then a RedemptionBulkOrderConfirmation message must be used.

func (r *RedemptionMultipleOrderConfirmationV02) AddCopyDetails() *iso20022.CopyInformation1

func (r *RedemptionMultipleOrderConfirmationV02) AddExtension() *iso20022.Extension1

func (r *RedemptionMultipleOrderConfirmationV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (r *RedemptionMultipleOrderConfirmationV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderConfirmationV02) AddMultipleExecutionDetails() *iso20022.RedemptionMultipleExecution2

func (r *RedemptionMultipleOrderConfirmationV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderConfirmationV02) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderConfirmationV02) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionMultipleOrderV02 ¶

type RedemptionMultipleOrderV02 struct {

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.AdditionalReference3 `xml:"MstrRef,omitempty"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// General information related to the order.
	MultipleOrderDetails *iso20022.RedemptionMultipleOrder2 `xml:"MltplOrdrDtls"`

	// The information related to an intermediary.
	IntermediaryDetails []*iso20022.Intermediary4 `xml:"IntrmyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation1 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionMultipleOrder message is sent by an instructing party, eg, an investment manager or its authorised representative, to an executing party, eg, a transfer agent. There may be one or more intermediary parties between the instructing party and the executing party. The intermediary party is, for example, an intermediary or a concentrator. This message is used to instruct the executing party to redeem to one or more financial instruments, for the same account. Usage The RedemptionMultipleOrder message is used for multiple orders. It may also be used for single orders, ie, a message containing one order for one financial instrument and related to one investment account. For a single redemption order, the RedemptionMultipleOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for the same financial instrument but for different accounts, then the RedemptionBulkOrder must be used.

func (r *RedemptionMultipleOrderV02) AddCopyDetails() *iso20022.CopyInformation1

func (r *RedemptionMultipleOrderV02) AddExtension() *iso20022.Extension1

func (r *RedemptionMultipleOrderV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (r *RedemptionMultipleOrderV02) AddMasterReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderV02) AddMultipleOrderDetails() *iso20022.RedemptionMultipleOrder2

func (r *RedemptionMultipleOrderV02) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionMultipleOrderV02) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionOrderCancellationRequestV03 ¶

type RedemptionOrderCancellationRequestV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// References of the orders to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrder1 `xml:"CxlByRef,omitempty"`

	// Common information related to all the orders to be cancelled.
	CancellationByOrderDetails *iso20022.RedemptionMultipleOrderInstruction2 `xml:"CxlByOrdrDtls,omitempty"`

	// Message is a copy.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative, sends the RedemptionOrderCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent RedemptionOrder instruction. Usage The RedemptionOrderCancellationRequest message is used to either: - request the cancellation of an entire RedemptionOrder message, that is, all the individual orders that it contained, or, - request the cancellation of one or more individual orders. There is no amendment, but a cancellation and re-instruct policy. There are two ways to use the message: (1) When the RedemptionOrderCancellationRequest message is used to request the cancellation of an entire RedemptionOrder message, this can be done by either: - quoting the order references of all the individual orders listed in the RedemptionOrder message, or, - quoting the details of all the individual orders (this includes the OrderReference) listed in RedemptionOrder message, but this is not recommended. The message identification of the RedemptionOrder message may also be quoted in PreviousReference. It is also possible to request the cancellation of an entire RedemptionOrder message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the RedemptionOrderCancellationRequest message is used to request the cancellation of one or more individual orders, this can be done by either: - quoting the OrderReference of each individual order listed in the RedemptionOrder message, or, - quoting the details of each individual order (including the OrderReference) listed in RedemptionOrder message, but this is not recommended. The message identification of the RedemptionOrder message in which the individual order was conveyed may also be quoted in PreviousReference. The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation. The rejection or acceptance of a RedemptionOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (r *RedemptionOrderCancellationRequestV03) AddCancellationByOrderDetails() *iso20022.RedemptionMultipleOrderInstruction2

func (r *RedemptionOrderCancellationRequestV03) AddCancellationByReference() *iso20022.InvestmentFundOrder1

func (r *RedemptionOrderCancellationRequestV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionOrderCancellationRequestV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderCancellationRequestV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderCancellationRequestV03) AddPreviousReference() *iso20022.AdditionalReference3

type RedemptionOrderCancellationRequestV04 ¶

type RedemptionOrderCancellationRequestV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Identification of the individual order to be cancelled.
	OrderReferences []*iso20022.InvestmentFundOrder9 `xml:"OrdrRefs"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`
}

Scope The RedemptionOrderCancellationRequest message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to request the cancellation of a previously sent RedemptionOrder. Usage The RedemptionOrderCancellationRequest message is used to message is used to request the cancellation of one or more individual orders. There is no amendment, but a cancellation and re-instruct policy. To request the cancellation of one or more individual orders, the order reference of each individual order listed in the original RedemptionOrder message in the order reference element. The message identification of the RedemptionOrder message which contains the individual orders to be cancelled may also be quoted in PreviousReference but this is not recommended. The deadline and acceptance of a cancellation request is subject to a service level agreement (SLA). This cancellation message is a cancellation request. There is no automatic acceptance of the cancellation. The rejection or acceptance of a RedemptionOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (r *RedemptionOrderCancellationRequestV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionOrderCancellationRequestV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderCancellationRequestV04) AddOrderReferences() *iso20022.InvestmentFundOrder9

func (r *RedemptionOrderCancellationRequestV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionOrderCancellationRequestV04) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionOrderCancellationRequestV04) SetMasterReference(value string)

type RedemptionOrderConfirmationAmendmentV01 ¶

type RedemptionOrderConfirmationAmendmentV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// General information related to the execution of investment fund orders.
	MultipleExecutionDetails *iso20022.RedemptionMultipleExecution3 `xml:"MltplExctnDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary9 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the RedemptionOrderConfirmationAmendment message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent RedemptionOrderConfirmation message. Usage The RedemptionOrderConfirmationAmendment message is used to amend one or more previously sent redemption order confirmations. Each individual order confirmation amendment specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionOrder message in which the individual orders were conveyed may also be quoted in RelatedReference. The message identification of the RedemptionOrderConfirmation message in which the original order confirmations were conveyed may also be quoted in PreviousReference.

func (r *RedemptionOrderConfirmationAmendmentV01) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionOrderConfirmationAmendmentV01) AddExtension() *iso20022.Extension1

func (r *RedemptionOrderConfirmationAmendmentV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderConfirmationAmendmentV01) AddMultipleExecutionDetails() *iso20022.RedemptionMultipleExecution3

func (r *RedemptionOrderConfirmationAmendmentV01) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationAmendmentV01) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationAmendmentV01) AddRelatedPartyDetails() *iso20022.Intermediary9

func (r *RedemptionOrderConfirmationAmendmentV01) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionOrderConfirmationCancellationInstructionV01 ¶

type RedemptionOrderConfirmationCancellationInstructionV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// References of the orders confirmations to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrderExecution1 `xml:"CxlByRef,omitempty"`

	// Common information related to all the orders confirmations to be cancelled.
	CancellationByOrderConfirmationDetails *iso20022.RedemptionOrderConfirmation1 `xml:"CxlByOrdrConfDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the RedemptionOrderConfirmationCancellationInstruction message to the instructing party, for example, an investment manager or its authorised representative to cancel a previously sent RedemptionOrderConfirmation message. Usage The RedemptionOrderConfirmationCancellationInstruction message is used to cancel one or more previously sent redemption order confirmations. The amendment indicator element is used to specify whether the redemption order confirmation cancellation is to be followed by a RedemptionOrderConfirmationAmendment. The RedemptionOrderConfirmationCancellationInstruction message is used to either: - cancel an entire RedemptionOrderConfirmation messae, that is, all the individual order confirmations that it contained, or, - request the cancellation of one or more individual confirmations. There are two ways to use the message. (1) When the RedemptionOrderConfirmationCancellationInstruction message is used to cancel an entire message, this can be done by either: - quoting the business references, for example, OrderReference, Deal Reference, of all the individual order confirmations listed in the RedemptionOrderConfirmation message, or, - quoting the details of all the individual order confirmations (this includes the OrderReference and DealReference) listed in RedemptionOrderConfirmation message but this is not recommended. The message identification of the RedemptionOrderConfirmation message may also be quoted in PreviousReference. It is also possible to instruct the cancellation of an entire confirmation message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the RedemptionOrderConfirmationCancellationInstruction message is used to cancel one or more individual order confirmations, this can be done by either: - quoting the business references, for example, OrderReference, Deal Reference, of each individual order confirmation listed in the RedemptionOrderConfirmation message, or, - quoting the details of each individual order execution (this includes the OrderReference and DealReference) listed in RedemptionOrderConfirmation message but this is not recommended. The message identification of the RedemptionOrderConfirmation message in which the individual order confirmation was conveyed may also be quoted in PreviousReference. The rejection or acceptance of a RedemptionOrderConfirmationCancellationInstruction is made using an OrderConfirmationStatusReport message.

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails() *iso20022.RedemptionOrderConfirmation1

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddCancellationByReference() *iso20022.InvestmentFundOrderExecution1

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationCancellationInstructionV01) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionOrderConfirmationCancellationInstructionV02 ¶

type RedemptionOrderConfirmationCancellationInstructionV02 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference8 `xml:"RltdRef,omitempty"`

	// Indicates whether a confirmation amendment message will follow the confirmation cancellation instruction or not.
	AmendmentIndicator *iso20022.YesNoIndicator `xml:"AmdmntInd"`

	// Reference assigned to a set of orders or trades in order to link them together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Identification of the individual order confirmation to be cancelled.
	OrderReferences []*iso20022.InvestmentFundOrder11 `xml:"OrdrRefs"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`
}

Scope The RedemptionOrderConfirmationCancellationInstruction message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent RedemptionOrderConfirmation. Usage To request the cancellation of one or more individual order executions, the order reference and deal reference of each individual order execution in the original RedemptionOrderConfirmation are specified in the order reference and deal reference elements respectively. The message identification of the RedemptionOrderConfirmation message in which the individual order execution was conveyed may also be quoted in PreviousReference but this is not recommended. The AmendmentIndicator is used to specify whether the redemption order confirmation cancellation is to be followed by an amendment An amendment of a redemption order confirmation is carried out by sending a RedemptionOrderConfirmation message in which the AmendmentIndicator contains the value ‘true’.

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddOrderReferences() *iso20022.InvestmentFundOrder11

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionOrderConfirmationCancellationInstructionV02) AddRelatedReference() *iso20022.AdditionalReference8

func (r *RedemptionOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (r *RedemptionOrderConfirmationCancellationInstructionV02) SetMasterReference(value string)

type RedemptionOrderConfirmationV03 ¶

type RedemptionOrderConfirmationV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference3 `xml:"RltdRef,omitempty"`

	// General information related to the execution of investment fund orders.
	MultipleExecutionDetails *iso20022.RedemptionMultipleExecution3 `xml:"MltplExctnDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary9 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, sends the RedemptionOrderConfirmation message to the instructing party, for example, an investment manager or its authorised representative to confirm the details of execution for a previously received RedemptionOrder message. Usage The RedemptionOrderConfirmation message is used to confirm the execution of one or more individual orders. A RedemptionOrder message containing more than one individual order may be responded to by more than one RedemptionOrderConfirmation message, as the valuation cycle of the financial instruments in each individual order may be different. Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionOrder message in which the individual order was conveyed may also be quoted in RelatedReference. When the executing party sends several confirmations, there is no specific indication in the message that it is an incomplete confirmation. Reconciliation should be based on the references. A RedemptionOrder must in all cases be responded to by a RedemptionOrderConfirmation message and in no circumstances by a RedemptionBulkOrderConfirmation message. If the executing party needs to confirm a RedemptionBulkOrder message, then a RedemptionBulkOrderConfirmation message must be used.

func (r *RedemptionOrderConfirmationV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionOrderConfirmationV03) AddExtension() *iso20022.Extension1

func (r *RedemptionOrderConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderConfirmationV03) AddMultipleExecutionDetails() *iso20022.RedemptionMultipleExecution3

func (r *RedemptionOrderConfirmationV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationV03) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderConfirmationV03) AddRelatedPartyDetails() *iso20022.Intermediary9

func (r *RedemptionOrderConfirmationV03) AddRelatedReference() *iso20022.AdditionalReference3

type RedemptionOrderConfirmationV04 ¶

type RedemptionOrderConfirmationV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// Reference to a linked message that was previously received.
	RelatedReference *iso20022.AdditionalReference8 `xml:"RltdRef,omitempty"`

	// General information related to the execution of investment fund orders.
	MultipleExecutionDetails *iso20022.RedemptionMultipleExecution5 `xml:"MltplExctnDtls"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionOrderConfirmation message is sent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to confirm the details of execution for a previously received RedemptionOrder message. Usage The RedemptionOrderConfirmation message is used to confirm the execution of one or more individual orders. A RedemptionOrder message containing more than one individual order may be responded to by more than one RedemptionOrderConfirmation message, as the valuation cycle of the financial instruments in each individual order may be different. When a RedemptionOrderConfirmation message contains fewer confirmations that originally instructed in the original RedemptionOrder message, there is no specification indication in the confirmation for this. Reconciliation must be based on the references. Each individual order confirmation specified is identified in DealReference. The reference of the original individual order is specified in OrderReference. The message identification of the RedemptionOrder message in which the individual order was conveyed may also be quoted in RelatedReference but this is not recommended. A RedemptionOrder must in all cases be responded to by a RedemptionOrderConfirmation message and in no circumstances by a RedemptionBulkOrderConfirmation message. If the executing party needs to confirm one or more redemption orders for the same financial instrument then a RedemptionBulkOrderConfirmation message must be used. When the message is used to convey a confirmation amendment/s, the AmendmentIndicator must be present with the value ‘true’ or ‘1’. When this is the case, the message must only contain a confirmation amendment/s and not contain both a confirmation amendment/s and a ‘new’ confirmation/s.

func (r *RedemptionOrderConfirmationV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionOrderConfirmationV04) AddExtension() *iso20022.Extension1

func (r *RedemptionOrderConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderConfirmationV04) AddMultipleExecutionDetails() *iso20022.RedemptionMultipleExecution5

func (r *RedemptionOrderConfirmationV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionOrderConfirmationV04) AddPreviousReference() *iso20022.AdditionalReference8

func (r *RedemptionOrderConfirmationV04) AddRelatedReference() *iso20022.AdditionalReference8

type RedemptionOrderV03 ¶

type RedemptionOrderV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference3 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference3 `xml:"PrvsRef,omitempty"`

	// General information related to the order.
	MultipleOrderDetails *iso20022.RedemptionMultipleOrder4 `xml:"MltplOrdrDtls"`

	// Information about parties related to the transaction.
	RelatedPartyDetails []*iso20022.Intermediary8 `xml:"RltdPtyDtls,omitempty"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation2 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative, sends the RedemptionOrder message to the executing party, for example, a transfer agent, to instruct the redemption of one or more financial instruments for one investment fund account. Usage The RedemptionOrder message is used to instruct single redemption orders, that is, a message containing one order for one financial instrument and related to one investment account. The RedemptionOrder message may also be used for multiple orders, that is, a message containing several orders related to the same investment account for different financial instruments. For a single redemption order, the RedemptionOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for the same financial instrument but for different accounts, then the RedemptionBulkOrder message must be used.

func (r *RedemptionOrderV03) AddCopyDetails() *iso20022.CopyInformation2

func (r *RedemptionOrderV03) AddExtension() *iso20022.Extension1

func (r *RedemptionOrderV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderV03) AddMultipleOrderDetails() *iso20022.RedemptionMultipleOrder4

func (r *RedemptionOrderV03) AddPoolReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderV03) AddPreviousReference() *iso20022.AdditionalReference3

func (r *RedemptionOrderV03) AddRelatedPartyDetails() *iso20022.Intermediary8

type RedemptionOrderV04 ¶

type RedemptionOrderV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Collective reference identifying a set of messages.
	PoolReference *iso20022.AdditionalReference9 `xml:"PoolRef,omitempty"`

	// Reference to a linked message that was previously sent.
	PreviousReference []*iso20022.AdditionalReference8 `xml:"PrvsRef,omitempty"`

	// General information related to the orders.
	MultipleOrderDetails *iso20022.RedemptionMultipleOrder6 `xml:"MltplOrdrDtls"`

	// Information provided when the message is a copy of a previous message.
	CopyDetails *iso20022.CopyInformation4 `xml:"CpyDtls,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RedemptionOrder message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to instruct the redemption of one or more financial instruments for one investment fund account. Usage The RedemptionOrder message is used to instruct single redemption orders, that is, a message containing one order for one financial instrument and related to one investment account. The RedemptionOrder message may also be used for multiple orders, that is, a message containing several orders related to the same investment account for different financial instruments. For a single redemption order, the RedemptionOrder message, not the RedemptionBulkOrder message, must be used. If there are redemption orders for the same financial instrument but for different accounts that are to be communicated in a single message, then the RedemptionBulkOrder message must be used.

func (r *RedemptionOrderV04) AddCopyDetails() *iso20022.CopyInformation4

func (r *RedemptionOrderV04) AddExtension() *iso20022.Extension1

func (r *RedemptionOrderV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RedemptionOrderV04) AddMultipleOrderDetails() *iso20022.RedemptionMultipleOrder6

func (r *RedemptionOrderV04) AddPoolReference() *iso20022.AdditionalReference9

func (r *RedemptionOrderV04) AddPreviousReference() *iso20022.AdditionalReference8

type RequestForOrderConfirmationStatusReportV01 ¶

type RequestForOrderConfirmationStatusReportV01 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Information to identify the order confirmation for which the status is requested.
	RequestDetails []*iso20022.MessageAndBusinessReference5 `xml:"ReqDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An executing party, for example, a transfer agent, send the RequestForOrderConfirmationStatusReport message to the instructing party, for example, an investment manager or its authorised representative, to request the status of one or several order confirmations. Usage The RequestForOrderConfirmationStatusReport message is used to request the status of either: - one or several individual order confirmations, or, - one or several order confirmation messages. The response to a RequestForOrderConfirmationStatusReport message is the OrderConfirmationStatusReport message. When the RequestForOrderConfirmationStatusReport message is used to request the status of several individual order confirmations or one or more order confirmation messages, the executing party may receive several OrderConfirmationStatusReport messages from the instructing party. When the RequestForOrderConfirmationStatusReport is used to request the status of one or more individual order confirmations, each individual order confirmation is identified with its order reference. The message identification of the message in which the individual order confirmation was conveyed may also be quoted in PreviousReference. When the RequestForOrderConfirmationStatusReport is used to request the status of an order confirmation message, then the message identification of the order confirmation message is identified in PreviousReference.

func (r *RequestForOrderConfirmationStatusReportV01) AddExtension() *iso20022.Extension1

func (r *RequestForOrderConfirmationStatusReportV01) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RequestForOrderConfirmationStatusReportV01) AddRequestDetails() *iso20022.MessageAndBusinessReference5

type RequestForOrderConfirmationStatusReportV02 ¶

type RequestForOrderConfirmationStatusReportV02 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Information to identify the order confirmation for which the status is requested.
	RequestDetails []*iso20022.MessageAndBusinessReference10 `xml:"ReqDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RequestForOrderConfirmationStatusReport message is ent by an executing party, for example, a transfer agent, to the instructing party, for example, an investment manager or its authorised representative, to request the status of one or more order confirmations. Usage The RequestForOrderConfirmationStatusReport message is used to request the status of either: - one or several individual order confirmations, or, - one or several order confirmation messages. The response to a RequestForOrderConfirmationStatusReport message is the OrderConfirmationStatusReport message. When the RequestForOrderConfirmationStatusReport message is used to request the status of several individual order confirmations or one or more order confirmation messages, the executing party may receive several OrderConfirmationStatusReport messages from the instructing party. When the RequestForOrderConfirmationStatusReport is used to request the status of one or more individual order confirmations, each individual order confirmation is identified with its order reference. The message identification of the message in which the individual order confirmation was conveyed may also be quoted in PreviousReference. When the RequestForOrderConfirmationStatusReport is used to request the status of an order confirmation message, then the message identification of the order confirmation message is identified in PreviousReference.

func (r *RequestForOrderConfirmationStatusReportV02) AddExtension() *iso20022.Extension1

func (r *RequestForOrderConfirmationStatusReportV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RequestForOrderConfirmationStatusReportV02) AddRequestDetails() *iso20022.MessageAndBusinessReference10

type RequestForOrderStatusReportV02 ¶

type RequestForOrderStatusReportV02 struct {

	// Information to identify the order(s) for which the status is requested.
	RequestDetails []*iso20022.MessageAndBusinessReference2 `xml:"ReqDtls"`
}

Scope The RequestForOrderStatusReport is sent by an instructing party, eg, an investment manager or its authorised representative, to the executing party, eg, a transfer agent. There may be one or more intermediary parties between the instructing party and the executing party. This message requests the status of one or several order instruction or order cancellation messages. Usage The RequestForOrderStatusReport message is used to request the status of: - one or several order messages, - one or several cancellation messages, - one or several individual orders within a bulk or multiple order message. If the RequestForOrderStatusReport message is used to request the status of several messages, then the instructing party will receive several reply messages from the executing party, ie, several OrderInstructionStatusReport messages and/or OrderCancellationStatusReport messages. The number of reply messages will match the number of references stated in the RequestForOrderStatusReport message. The RequestForOrderStatusReport message may not be used to request the status of an investment account, a transfer or the status of a financial instrument.

func (r *RequestForOrderStatusReportV02) AddRequestDetails() *iso20022.MessageAndBusinessReference2

type RequestForOrderStatusReportV03 ¶

type RequestForOrderStatusReportV03 struct {

	// Reference that uniquely identifies a message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Information to identify the order(s) for which the status is requested.
	RequestDetails []*iso20022.MessageAndBusinessReference4 `xml:"ReqDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope An instructing party, for example, an investment manager or its authorised representative, sends the RequestForOrderStatusReport to the executing party, for example, a transfer agent, to request the status of one or more order instruction or order cancellation request messages. Usage The RequestForOrderStatusReport message is used to request the status of: - one or several individual order instructions, or, - one or several order messages, or - one or several individual order cancellation requests, or, - one or several order cancellation request messages. The response to a RequestForOrderStatusReport message is the OrderInstructionStatusReport message or OrderCancellationStatusReport message. If the RequestForOrderStatusReport message is used to request the status of several individual order instructions or one or more order instruction messages, then the instructing party may receive several OrderInstructionStatusReport messages from the executing party. If the RequestForOrderStatusReport message is used to request the status of several individual order cancellation requests or one or more order cancellation messages, then the instructing party may receive several OrderCancellationStatusReport messages from the executing party. When the RequestForOrderStatusReport is used to request the status of one or more individual orders or order cancellations, each individual order is identified with its order reference. The investment account and/or financial instrument related to the order can also be identified. The message identification of the message in which the individual order was conveyed may also be quoted in PreviousReference. When the RequestForOrderStatusReport is used to request the status of an order message or an order cancellations request message, then the message identification of the order or cancellation message is identified in PreviousReference. The RequestForOrderStatusReport message may not be used to request the status of an investment account, a transfer or the status of a financial instrument.

func (r *RequestForOrderStatusReportV03) AddExtension() *iso20022.Extension1

func (r *RequestForOrderStatusReportV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RequestForOrderStatusReportV03) AddRequestDetails() *iso20022.MessageAndBusinessReference4

type RequestForOrderStatusReportV04 ¶

type RequestForOrderStatusReportV04 struct {

	// Reference that uniquely identifies the message from a business application standpoint.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Information to identify the order(s) for which the status is requested.
	RequestDetails []*iso20022.MessageAndBusinessReference10 `xml:"ReqDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	Extension []*iso20022.Extension1 `xml:"Xtnsn,omitempty"`
}

Scope The RequestForOrderStatusReport message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to request the status of one or more order instructions or order cancellation requests. Usage The RequestForOrderStatusReport message is used to request the status of: - one or several individual order instructions, or, - one or several order messages, or - one or several individual order cancellation requests, or, - one or several order cancellation request messages. The response to a RequestForOrderStatusReport message is the OrderInstructionStatusReport message or OrderCancellationStatusReport message. If the RequestForOrderStatusReport message is used to request the status of several individual order instructions or one or more order instruction messages, then the instructing party may receive several OrderInstructionStatusReport messages from the executing party. If the RequestForOrderStatusReport message is used to request the status of several individual order cancellation requests or one or more order cancellation messages, then the instructing party may receive several OrderCancellationStatusReport messages from the executing party. When the RequestForOrderStatusReport is used to request the status of one or more individual orders or order cancellations, each individual order is identified with its order reference. The investment account and/or financial instrument related to the order can also be identified. The message identification of the message in which the individual order was conveyed may also be quoted in PreviousReference. When the RequestForOrderStatusReport is used to request the status of an order message or an order cancellations request message, then the message identification of the order or cancellation message is identified in PreviousReference. The RequestForOrderStatusReport message may not be used to request the status of an investment account, a transfer or the status of a financial instrument.

func (r *RequestForOrderStatusReportV04) AddExtension() *iso20022.Extension1

func (r *RequestForOrderStatusReportV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (r *RequestForOrderStatusReportV04) AddRequestDetails() *iso20022.MessageAndBusinessReference10

type SecuritiesTradeConfirmationCancellationV01 ¶

type SecuritiesTradeConfirmationCancellationV01 struct {

	// Information that unambiguously identifies an SecuritiesTradeConfirmationCancellation message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactiontIdentification4 `xml:"Id"`

	// Link to another transaction that must be processed after, before or at the same time.
	References []*iso20022.Linkages15 `xml:"Refs,omitempty"`

	// Chain of parties involved in the settlement of a transaction, including receipts and deliveries, book transfers, treasury deals, or other activities, resulting in the movement of a security or amount of money from one account to another.
	OtherBusinessParties *iso20022.OtherParties18 `xml:"OthrBizPties,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope Sent by an executing party to an instructing party directly or through Central Matching Utility (CMU) to cancel the referenced SecuritiesTradeConfirmation message that was previously sent. The instructing party is typically the investment manager or an intermediary system/vendor communicating on behalf of the investment manager or of other categories of investors. The executing party is typically the broker/dealer or an intermediary system/vendor communicating on behalf of the broker/dealer. It may also be used to cancel the trade confirmation previously sent from an executing party or an instructing party to a custodian or an affirming party directly or through CMU. The ISO 20022 Business Application Header must be used Usage Initiator: Both in local and central matching, the Initiator may be either the Executing Party or Instructing Party. Respondent: Instructing party, a custodian or an affirming party optionally responds with SecuritiesTradeConfirmationResponse (accept or reject) message.

func (s *SecuritiesTradeConfirmationCancellationV01) AddIdentification() *iso20022.TransactiontIdentification4

func (s *SecuritiesTradeConfirmationCancellationV01) AddOtherBusinessParties() *iso20022.OtherParties18

func (s *SecuritiesTradeConfirmationCancellationV01) AddReferences() *iso20022.Linkages15

func (s *SecuritiesTradeConfirmationCancellationV01) AddSupplementaryData() *iso20022.SupplementaryData1

type SecuritiesTradeConfirmationResponseV01 ¶

type SecuritiesTradeConfirmationResponseV01 struct {

	// Information that unambiguously identifies an SecuritiesTradeConfirmationResponse message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactiontIdentification4 `xml:"Id"`

	// Link to another transaction that must be processed after, before or at the same time.
	References []*iso20022.Linkages15 `xml:"Refs"`

	// Provides details on the processing status of the trade.
	Status *iso20022.StatusAndReason10 `xml:"Sts"`

	// Provides clearing member information.
	ClearingDetails *iso20022.Clearing3 `xml:"ClrDtls,omitempty"`

	// Parties involved in the confirmation of the details of a trade.
	ConfirmationParties []*iso20022.ConfirmationParties3 `xml:"ConfPties,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope Sent by an instructing party, a custodian or an affirming party to an executing party (local matching) or to Central Matching Utility (CMU) to affirm (accept) or disaffirm (reject) (central matching) the SecuritiesTradeConfirmation message. If accepting the SecuritiesTradeConfirmation message, then the trade is ready for settlement processing. If rejecting the SecuritiesTradeConfirmation message, then the trade is not ready for settlement. The executing party is typically the broker/dealer or an intermediary system/vendor communicating on behalf of the broker/dealer. The instructing party is typically the investment manager or an intermediary system/vendor communicating on behalf of the investment manager or of other categories of investors. The custodian or an affirming party is typically the custodian, trustee, financial institution, intermediary system/vendor communicating on behalf of them, or their agent. The ISO 20022 Business Application Header must be used Usage Initiator: Both in local and central matching, the Initiator may be the Instructing Party, Custodian or Affirming party. Respondent: Executing party does not need to respond if an affirmation. Executing party may respond with modification or cancellation of the rejected SecuritiesTradeConfirmation message.

func (s *SecuritiesTradeConfirmationResponseV01) AddClearingDetails() *iso20022.Clearing3

func (s *SecuritiesTradeConfirmationResponseV01) AddConfirmationParties() *iso20022.ConfirmationParties3

func (s *SecuritiesTradeConfirmationResponseV01) AddIdentification() *iso20022.TransactiontIdentification4

func (s *SecuritiesTradeConfirmationResponseV01) AddReferences() *iso20022.Linkages15

func (s *SecuritiesTradeConfirmationResponseV01) AddStatus() *iso20022.StatusAndReason10

func (s *SecuritiesTradeConfirmationResponseV01) AddSupplementaryData() *iso20022.SupplementaryData1

type SecuritiesTradeConfirmationStatusAdviceV01 ¶

type SecuritiesTradeConfirmationStatusAdviceV01 struct {

	// Information that unambiguously identifies an SecuritiesTradeConfirmationStatusAdvice message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactiontIdentification4 `xml:"Id"`

	// Link to another transaction that must be processed after, before or at the same time.
	References []*iso20022.Linkages18 `xml:"Refs"`

	// Provides details on the affitrmation status of a trade.
	AffirmationStatus *iso20022.AffirmationStatus6Choice `xml:"AffirmSts,omitempty"`

	// Provides the processing status of a trade.
	ProcessingStatus *iso20022.ProcessingStatus17Choice `xml:"PrcgSts,omitempty"`

	// Provides details on the matching status of a trade.
	MatchingStatus *iso20022.MatchingStatus9Choice `xml:"MtchgSts,omitempty"`

	// Provides the replacement processing status of a trade.
	ReplacementProcessingStatus *iso20022.ReplacementProcessingStatus7Choice `xml:"RplcmntPrcgSts,omitempty"`

	// Provides details on the cancellation status of a trade.
	CancellationProcessingStatus *iso20022.CancellationProcessingStatus6Choice `xml:"CxlPrcgSts,omitempty"`

	// Details of the trading party.
	PartyTradingDetails *iso20022.Order16 `xml:"PtyTradgDtls,omitempty"`

	// Details of the trading counterparty.
	CounterpartyTradingDetails *iso20022.Order16 `xml:"CtrPtyTradgDtls,omitempty"`

	// Parties used for acting parties that applies either to the whole message or to individual sides.
	ConfirmationParties []*iso20022.ConfirmationParties4 `xml:"ConfPties,omitempty"`

	// Identifies the chain of delivering settlement parties.
	DeliveringSettlementParties *iso20022.SettlementParties23 `xml:"DlvrgSttlmPties,omitempty"`

	// Identifies the chain of receiving settlement parties.
	ReceivingSettlementParties *iso20022.SettlementParties23 `xml:"RcvgSttlmPties,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope This message is sent from Central Matching Utility (CMU) to an executing party or an instructing party to advise the status of the SecuritiesTradeConfirmation message previously sent by the party. The status may be a processing, pending processing, affirmed or disaffirmed, cancel or replacement by an instructing party, a custodian or an affirming party, internal matching, and/or matching status. The instructing party is typically the investment manager or an intermediary system/vendor communicating on behalf of the investment manager or of other categories of investors. The executing party is typically the broker/dealer or an intermediary system/vendor communicating on behalf of the broker/dealer. The ISO 20022 Business Application Header must be used Usage Initiator: In central matching the Initiator is the Central Matching Utility. Respondent: no response is needed by the recipient of the message.

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddAffirmationStatus() *iso20022.AffirmationStatus6Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddCancellationProcessingStatus() *iso20022.CancellationProcessingStatus6Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddConfirmationParties() *iso20022.ConfirmationParties4

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddCounterpartyTradingDetails() *iso20022.Order16

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddDeliveringSettlementParties() *iso20022.SettlementParties23

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddIdentification() *iso20022.TransactiontIdentification4

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddMatchingStatus() *iso20022.MatchingStatus9Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddPartyTradingDetails() *iso20022.Order16

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddProcessingStatus() *iso20022.ProcessingStatus17Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddReceivingSettlementParties() *iso20022.SettlementParties23

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddReferences() *iso20022.Linkages18

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddReplacementProcessingStatus() *iso20022.ReplacementProcessingStatus7Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV01) AddSupplementaryData() *iso20022.SupplementaryData1

type SecuritiesTradeConfirmationStatusAdviceV02 ¶

type SecuritiesTradeConfirmationStatusAdviceV02 struct {

	// Information that unambiguously identifies an SecuritiesTradeConfirmationStatusAdvice message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactiontIdentification4 `xml:"Id"`

	// Link to another transaction that must be processed after, before or at the same time.
	References []*iso20022.Linkages18 `xml:"Refs"`

	// Provides details on the affitrmation status of a trade.
	AffirmationStatus *iso20022.AffirmationStatus6Choice `xml:"AffirmSts,omitempty"`

	// Provides the processing status of a trade.
	ProcessingStatus *iso20022.ProcessingStatus17Choice `xml:"PrcgSts,omitempty"`

	// Provides details on the matching status of a trade.
	MatchingStatus *iso20022.MatchingStatus23Choice `xml:"MtchgSts,omitempty"`

	// Provides the replacement processing status of a trade.
	ReplacementProcessingStatus *iso20022.ReplacementProcessingStatus7Choice `xml:"RplcmntPrcgSts,omitempty"`

	// Provides details on the cancellation status of a trade.
	CancellationProcessingStatus *iso20022.CancellationProcessingStatus6Choice `xml:"CxlPrcgSts,omitempty"`

	// Details of the trading party.
	PartyTradingDetails *iso20022.Order18 `xml:"PtyTradgDtls,omitempty"`

	// Details of the trading counterparty.
	CounterpartyTradingDetails *iso20022.Order18 `xml:"CtrPtyTradgDtls,omitempty"`

	// Parties used for acting parties that applies either to the whole message or to individual sides.
	ConfirmationParties []*iso20022.ConfirmationParties4 `xml:"ConfPties,omitempty"`

	// Identifies the chain of delivering settlement parties.
	DeliveringSettlementParties *iso20022.SettlementParties23 `xml:"DlvrgSttlmPties,omitempty"`

	// Identifies the chain of receiving settlement parties.
	ReceivingSettlementParties *iso20022.SettlementParties23 `xml:"RcvgSttlmPties,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope This message is sent from Central Matching Utility (CMU) to an executing party or an instructing party to advise the status of the SecuritiesTradeConfirmation message previously sent by the party. The status may be a processing, pending processing, affirmed or disaffirmed, cancel or replacement by an instructing party, a custodian or an affirming party, internal matching, and/or matching status. The instructing party is typically the investment manager or an intermediary system/vendor communicating on behalf of the investment manager or of other categories of investors. The executing party is typically the broker/dealer or an intermediary system/vendor communicating on behalf of the broker/dealer. The ISO 20022 Business Application Header must be used Usage Initiator: In central matching the Initiator is the Central Matching Utility. Respondent: no response is needed by the recipient of the message.

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddAffirmationStatus() *iso20022.AffirmationStatus6Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddCancellationProcessingStatus() *iso20022.CancellationProcessingStatus6Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddConfirmationParties() *iso20022.ConfirmationParties4

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddCounterpartyTradingDetails() *iso20022.Order18

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddDeliveringSettlementParties() *iso20022.SettlementParties23

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddIdentification() *iso20022.TransactiontIdentification4

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddMatchingStatus() *iso20022.MatchingStatus23Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddPartyTradingDetails() *iso20022.Order18

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddProcessingStatus() *iso20022.ProcessingStatus17Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddReceivingSettlementParties() *iso20022.SettlementParties23

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddReferences() *iso20022.Linkages18

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddReplacementProcessingStatus() *iso20022.ReplacementProcessingStatus7Choice

func (s *SecuritiesTradeConfirmationStatusAdviceV02) AddSupplementaryData() *iso20022.SupplementaryData1

type SecuritiesTradeConfirmationV01 ¶

type SecuritiesTradeConfirmationV01 struct {

	// Information that unambiguously identifies an SecuritiesTradeConfirmation message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactiontIdentification4 `xml:"Id"`

	// Count of the number of transactions linked.
	NumberCount *iso20022.NumberCount1Choice `xml:"NbCnt,omitempty"`

	// Reference to the transaction identifier issued by a business party and/or market infrastructure. It may also be used to reference a previous transaction, for example, a block/allocation instruction, or tie a set of messages together.
	References []*iso20022.Linkages15 `xml:"Refs,omitempty"`

	// Details of the trade.
	TradeDetails *iso20022.Order14 `xml:"TradDtls"`

	// Unique and unambiguous identifier of a financial instrument, assigned under a formal or proprietary identification scheme.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

	// Elements characterising a financial instrument.
	FinancialInstrumentAttributes *iso20022.FinancialInstrumentAttributes31 `xml:"FinInstrmAttrbts,omitempty"`

	// Underlying financial instrument to which an trade confirmation is related.
	UnderlyingFinancialInstrument []*iso20022.UnderlyingFinancialInstrument1 `xml:"UndrlygFinInstrm,omitempty"`

	// Additional restrictions on the financial instrument, related to the stipulation.
	Stipulations *iso20022.FinancialInstrumentStipulations2 `xml:"Stiptns,omitempty"`

	// Parties involved in the confirmation of the details of a trade.
	ConfirmationParties []*iso20022.ConfirmationParties2 `xml:"ConfPties"`

	// Parameters which explicitly state the conditions that must be fulfilled before a particular transaction of a financial instrument can be settled.  These parameters are defined by the instructing party in compliance with settlement rules in the market the transaction will settle in.
	SettlementParameters *iso20022.SettlementDetails43 `xml:"SttlmParams,omitempty"`

	// Specifies what settlement standing instruction database is to be used to derive the settlement parties involved in the transaction.
	StandingSettlementInstruction *iso20022.StandingSettlementInstruction9 `xml:"StgSttlmInstr,omitempty"`

	// Identifies the chain of delivering settlement parties.
	DeliveringSettlementParties *iso20022.SettlementParties23 `xml:"DlvrgSttlmPties,omitempty"`

	// Identifies the chain of receiving settlement parties.
	ReceivingSettlementParties *iso20022.SettlementParties23 `xml:"RcvgSttlmPties,omitempty"`

	// Cash parties involved in the specific transaction.
	CashParties *iso20022.CashParties6 `xml:"CshPties,omitempty"`

	// Provides clearing member information.
	ClearingDetails *iso20022.Clearing3 `xml:"ClrDtls,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.  The amount includes the principal with any commissions and fees or accrued interest.
	SettlementAmount *iso20022.AmountAndDirection28 `xml:"SttlmAmt,omitempty"`

	// Other amounts than the settlement amount.
	OtherAmounts []*iso20022.OtherAmounts16 `xml:"OthrAmts,omitempty"`

	// Other prices than the deal price.
	OtherPrices []*iso20022.OtherPrices1 `xml:"OthrPrics,omitempty"`

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties18 `xml:"OthrBizPties,omitempty"`

	// Identifies a transaction that the trading parties are agreeing to repurchase, sell back or return the same or similar securities at a later time.
	// The two leg transaction details defines the closing leg conditions of a two leg transaction. It is also used to define the anticipated closing leg conditions at the time of opening the closed-end transaction.
	//
	//
	TwoLegTransactionDetails *iso20022.TwoLegTransactionDetails1 `xml:"TwoLegTxDtls,omitempty"`

	// Specifies regulatory stipulations that financial institutions must be compliant with in the country, region, and/or area they conduct business.
	RegulatoryStipulations *iso20022.RegulatoryStipulations1 `xml:"RgltryStiptns,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}