setr

package
v0.0.0-...-00ea27e Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Feb 26, 2018 License: Apache-2.0, MIT Imports: 2 Imported by: 0

Documentation

Index

Constants

This section is empty.

Variables

This section is empty.

Functions

This section is empty.

Types

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 (*Document00100102) AddMessage

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 (*Document00100103) AddMessage

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 (*Document00100104) AddMessage

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 (*Document00200102) AddMessage

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 (*Document00200103) AddMessage

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 (*Document00200104) AddMessage

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 (*Document00300102) AddMessage

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 (*Document00300103) AddMessage

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 (*Document00300104) AddMessage

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 (*Document00400102) AddMessage

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 (*Document00400103) AddMessage

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 (*Document00400104) AddMessage

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 (*Document00500102) AddMessage

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 (*Document00500103) AddMessage

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 (*Document00500104) AddMessage

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 (*Document00600102) AddMessage

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 (*Document00600103) AddMessage

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 (*Document00600104) AddMessage

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 (*Document00700102) AddMessage

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 (*Document00700103) AddMessage

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 (*Document00700104) AddMessage

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 (*Document00800102) AddMessage

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 (*Document00800103) AddMessage

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 (*Document00800104) AddMessage

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 (*Document00900102) AddMessage

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 (*Document00900103) AddMessage

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 (*Document00900104) AddMessage

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 (*Document01000102) AddMessage

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 (*Document01000103) AddMessage

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 (*Document01000104) AddMessage

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 (*Document01100102) AddMessage

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 (*Document01100103) AddMessage

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 (*Document01100104) AddMessage

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 (*Document01200102) AddMessage

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 (*Document01200103) AddMessage

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 (*Document01200104) AddMessage

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 (*Document01300102) AddMessage

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 (*Document01300103) AddMessage

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 (*Document01300104) AddMessage

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 (*Document01400102) AddMessage

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 (*Document01400103) AddMessage

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 (*Document01400104) AddMessage

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 (*Document01500102) AddMessage

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 (*Document01500103) AddMessage

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 (*Document01500104) AddMessage

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 (*Document01600102) AddMessage

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 (*Document01600103) AddMessage

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 (*Document01600104) AddMessage

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 (*Document01700102) AddMessage

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 (*Document01700103) AddMessage

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 (*Document01700104) AddMessage

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 (*Document01800102) AddMessage

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 (*Document01800103) AddMessage

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 (*Document01800104) AddMessage

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 (*Document02700101) AddMessage

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 (*Document02700102) AddMessage

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 (*Document02700103) AddMessage

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 (*Document02900101) AddMessage

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 (*Document03000101) AddMessage

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 (*Document04400101) AddMessage

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 (*Document04400102) AddMessage

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"`
}

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"`
}

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 (*Document04800101) AddMessage

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"`
}

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"`
}

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 (*Document05000101) AddMessage

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 (*Document05100101) AddMessage

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 (*Document05100102) AddMessage

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 (*Document05200101) AddMessage

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"`
}

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"`
}

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 (*Document05400101) AddMessage

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 (*Document05500101) AddMessage

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 (*Document05500102) AddMessage

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 (*Document05600101) AddMessage

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 (*Document05700101) AddMessage

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 (*Document05700102) AddMessage

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 (*Document05800101) AddMessage

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 (*Document05800102) AddMessage

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 (*OrderCancellationStatusReportV02) AddCancellationStatusReport

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

func (*OrderCancellationStatusReportV02) AddOtherReference

func (*OrderCancellationStatusReportV02) AddRelatedReference

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 (*OrderCancellationStatusReportV03) AddCancellationStatusReport

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

func (*OrderCancellationStatusReportV03) AddExtension

func (*OrderCancellationStatusReportV03) AddIndividualCancellationStatusReport

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

func (*OrderCancellationStatusReportV03) AddMessageIdentification

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

func (*OrderCancellationStatusReportV03) AddOtherReference

func (*OrderCancellationStatusReportV03) AddRelatedReference

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 (*OrderCancellationStatusReportV04) AddExtension

func (*OrderCancellationStatusReportV04) AddMessageIdentification

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

func (*OrderCancellationStatusReportV04) AddReference

func (*OrderCancellationStatusReportV04) AddStatusReport

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 (*OrderConfirmationStatusReportV01) AddExtension

func (*OrderConfirmationStatusReportV01) AddIndividualOrderConfirmationDetailsReport

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

func (*OrderConfirmationStatusReportV01) AddMessageIdentification

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

func (*OrderConfirmationStatusReportV01) AddOtherReference

func (*OrderConfirmationStatusReportV01) AddRelatedReference

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 (*OrderConfirmationStatusReportV02) AddExtension

func (*OrderConfirmationStatusReportV02) AddIndividualOrderConfirmationDetailsReport

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

func (*OrderConfirmationStatusReportV02) AddMessageIdentification

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

func (*OrderConfirmationStatusReportV02) AddReference

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 (*OrderInstructionStatusReportV02) AddIndividualOrderDetailsReport

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

func (*OrderInstructionStatusReportV02) AddMasterReference

func (*OrderInstructionStatusReportV02) AddOrderDetailsReport

func (*OrderInstructionStatusReportV02) AddOtherReference

func (*OrderInstructionStatusReportV02) AddRelatedReference

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 (*OrderInstructionStatusReportV03) AddExtension

func (*OrderInstructionStatusReportV03) AddIndividualOrderDetailsReport

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

func (*OrderInstructionStatusReportV03) AddMessageIdentification

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

func (*OrderInstructionStatusReportV03) AddOrderDetailsReport

func (*OrderInstructionStatusReportV03) AddOtherReference

func (*OrderInstructionStatusReportV03) AddRelatedReference

func (*OrderInstructionStatusReportV03) AddSwitchOrderDetailsReport

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 (*OrderInstructionStatusReportV04) AddExtension

func (*OrderInstructionStatusReportV04) AddMessageIdentification

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

func (*OrderInstructionStatusReportV04) AddReference

func (*OrderInstructionStatusReportV04) AddStatusReport

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 (*RedemptionBulkOrderCancellationInstructionV02) AddMasterReference

func (*RedemptionBulkOrderCancellationInstructionV02) AddOrderToBeCancelled

func (*RedemptionBulkOrderCancellationInstructionV02) AddPoolReference

func (*RedemptionBulkOrderCancellationInstructionV02) AddPreviousReference

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 (*RedemptionBulkOrderCancellationRequestV03) AddCancellationByOrderDetails

func (*RedemptionBulkOrderCancellationRequestV03) AddCancellationByReference

func (*RedemptionBulkOrderCancellationRequestV03) AddCopyDetails

func (*RedemptionBulkOrderCancellationRequestV03) AddMessageIdentification

func (*RedemptionBulkOrderCancellationRequestV03) AddPoolReference

func (*RedemptionBulkOrderCancellationRequestV03) AddPreviousReference

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 (*RedemptionBulkOrderCancellationRequestV04) AddCopyDetails

func (*RedemptionBulkOrderCancellationRequestV04) AddMessageIdentification

func (*RedemptionBulkOrderCancellationRequestV04) AddOrderReferences

func (*RedemptionBulkOrderCancellationRequestV04) AddPoolReference

func (*RedemptionBulkOrderCancellationRequestV04) AddPreviousReference

func (*RedemptionBulkOrderCancellationRequestV04) SetMasterReference

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 (*RedemptionBulkOrderConfirmationAmendmentV01) AddBulkExecutionDetails

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddCopyDetails

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddExtension

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddMessageIdentification

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddPoolReference

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddPreviousReference

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddRelatedPartyDetails

func (*RedemptionBulkOrderConfirmationAmendmentV01) AddRelatedReference

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 (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddCopyDetails

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddMessageIdentification

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddPoolReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddPreviousReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV01) AddRelatedReference

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 (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddCopyDetails

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddMessageIdentification

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddOrderReferences

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddPoolReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddPreviousReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) AddRelatedReference

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator

func (r *RedemptionBulkOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (*RedemptionBulkOrderConfirmationCancellationInstructionV02) SetMasterReference

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 (*RedemptionBulkOrderConfirmationV02) AddBulkExecutionDetails

func (*RedemptionBulkOrderConfirmationV02) AddCopyDetails

func (*RedemptionBulkOrderConfirmationV02) AddExtension

func (*RedemptionBulkOrderConfirmationV02) AddIntermediaryDetails

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

func (*RedemptionBulkOrderConfirmationV02) AddMasterReference

func (*RedemptionBulkOrderConfirmationV02) AddPoolReference

func (*RedemptionBulkOrderConfirmationV02) AddPreviousReference

func (*RedemptionBulkOrderConfirmationV02) AddRelatedReference

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 (*RedemptionBulkOrderConfirmationV03) AddBulkExecutionDetails

func (*RedemptionBulkOrderConfirmationV03) AddCopyDetails

func (*RedemptionBulkOrderConfirmationV03) AddExtension

func (*RedemptionBulkOrderConfirmationV03) AddMessageIdentification

func (*RedemptionBulkOrderConfirmationV03) AddPoolReference

func (*RedemptionBulkOrderConfirmationV03) AddPreviousReference

func (*RedemptionBulkOrderConfirmationV03) AddRelatedPartyDetails

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

func (*RedemptionBulkOrderConfirmationV03) AddRelatedReference

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 (*RedemptionBulkOrderConfirmationV04) AddBulkExecutionDetails

func (*RedemptionBulkOrderConfirmationV04) AddCopyDetails

func (*RedemptionBulkOrderConfirmationV04) AddExtension

func (*RedemptionBulkOrderConfirmationV04) AddMessageIdentification

func (*RedemptionBulkOrderConfirmationV04) AddPoolReference

func (*RedemptionBulkOrderConfirmationV04) AddPreviousReference

func (*RedemptionBulkOrderConfirmationV04) AddRelatedReference

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 (*RedemptionBulkOrderV02) AddBulkOrderDetails

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

func (*RedemptionBulkOrderV02) AddCopyDetails

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

func (*RedemptionBulkOrderV02) AddExtension

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

func (*RedemptionBulkOrderV02) AddIntermediaryDetails

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

func (*RedemptionBulkOrderV02) AddMasterReference

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

func (*RedemptionBulkOrderV02) AddPoolReference

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

func (*RedemptionBulkOrderV02) AddPreviousReference

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 (*RedemptionBulkOrderV03) AddBulkOrderDetails

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

func (*RedemptionBulkOrderV03) AddCopyDetails

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

func (*RedemptionBulkOrderV03) AddExtension

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

func (*RedemptionBulkOrderV03) AddMessageIdentification

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

func (*RedemptionBulkOrderV03) AddPoolReference

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

func (*RedemptionBulkOrderV03) AddPreviousReference

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

func (*RedemptionBulkOrderV03) AddRelatedPartyDetails

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 (*RedemptionBulkOrderV04) AddBulkOrderDetails

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

func (*RedemptionBulkOrderV04) AddCopyDetails

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

func (*RedemptionBulkOrderV04) AddExtension

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

func (*RedemptionBulkOrderV04) AddMessageIdentification

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

func (*RedemptionBulkOrderV04) AddPoolReference

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

func (*RedemptionBulkOrderV04) AddPreviousReference

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 (*RedemptionMultipleOrderCancellationInstructionV02) AddMasterReference

func (*RedemptionMultipleOrderCancellationInstructionV02) AddOrderToBeCancelled

func (*RedemptionMultipleOrderCancellationInstructionV02) AddPoolReference

func (*RedemptionMultipleOrderCancellationInstructionV02) AddPreviousReference

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 (*RedemptionMultipleOrderConfirmationV02) AddCopyDetails

func (*RedemptionMultipleOrderConfirmationV02) AddExtension

func (*RedemptionMultipleOrderConfirmationV02) AddIntermediaryDetails

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

func (*RedemptionMultipleOrderConfirmationV02) AddMasterReference

func (*RedemptionMultipleOrderConfirmationV02) AddMultipleExecutionDetails

func (*RedemptionMultipleOrderConfirmationV02) AddPoolReference

func (*RedemptionMultipleOrderConfirmationV02) AddPreviousReference

func (*RedemptionMultipleOrderConfirmationV02) AddRelatedReference

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 (*RedemptionMultipleOrderV02) AddCopyDetails

func (*RedemptionMultipleOrderV02) AddExtension

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

func (*RedemptionMultipleOrderV02) AddIntermediaryDetails

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

func (*RedemptionMultipleOrderV02) AddMasterReference

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

func (*RedemptionMultipleOrderV02) AddMultipleOrderDetails

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

func (*RedemptionMultipleOrderV02) AddPoolReference

func (*RedemptionMultipleOrderV02) AddPreviousReference

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 (*RedemptionOrderCancellationRequestV03) AddCancellationByOrderDetails

func (*RedemptionOrderCancellationRequestV03) AddCancellationByReference

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

func (*RedemptionOrderCancellationRequestV03) AddCopyDetails

func (*RedemptionOrderCancellationRequestV03) AddMessageIdentification

func (*RedemptionOrderCancellationRequestV03) AddPoolReference

func (*RedemptionOrderCancellationRequestV03) AddPreviousReference

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 (*RedemptionOrderCancellationRequestV04) AddCopyDetails

func (*RedemptionOrderCancellationRequestV04) AddMessageIdentification

func (*RedemptionOrderCancellationRequestV04) AddOrderReferences

func (*RedemptionOrderCancellationRequestV04) AddPoolReference

func (*RedemptionOrderCancellationRequestV04) AddPreviousReference

func (*RedemptionOrderCancellationRequestV04) SetMasterReference

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 (*RedemptionOrderConfirmationAmendmentV01) AddCopyDetails

func (*RedemptionOrderConfirmationAmendmentV01) AddExtension

func (*RedemptionOrderConfirmationAmendmentV01) AddMessageIdentification

func (*RedemptionOrderConfirmationAmendmentV01) AddMultipleExecutionDetails

func (*RedemptionOrderConfirmationAmendmentV01) AddPoolReference

func (*RedemptionOrderConfirmationAmendmentV01) AddPreviousReference

func (*RedemptionOrderConfirmationAmendmentV01) AddRelatedPartyDetails

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

func (*RedemptionOrderConfirmationAmendmentV01) AddRelatedReference

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 (*RedemptionOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddCancellationByReference

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddCopyDetails

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddMessageIdentification

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddPoolReference

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddPreviousReference

func (*RedemptionOrderConfirmationCancellationInstructionV01) AddRelatedReference

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 (*RedemptionOrderConfirmationCancellationInstructionV02) AddCopyDetails

func (*RedemptionOrderConfirmationCancellationInstructionV02) AddMessageIdentification

func (*RedemptionOrderConfirmationCancellationInstructionV02) AddOrderReferences

func (*RedemptionOrderConfirmationCancellationInstructionV02) AddPoolReference

func (*RedemptionOrderConfirmationCancellationInstructionV02) AddPreviousReference

func (*RedemptionOrderConfirmationCancellationInstructionV02) AddRelatedReference

func (*RedemptionOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator

func (r *RedemptionOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (*RedemptionOrderConfirmationCancellationInstructionV02) SetMasterReference

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 (*RedemptionOrderConfirmationV03) AddCopyDetails

func (*RedemptionOrderConfirmationV03) AddExtension

func (*RedemptionOrderConfirmationV03) AddMessageIdentification

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

func (*RedemptionOrderConfirmationV03) AddMultipleExecutionDetails

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

func (*RedemptionOrderConfirmationV03) AddPoolReference

func (*RedemptionOrderConfirmationV03) AddPreviousReference

func (*RedemptionOrderConfirmationV03) AddRelatedPartyDetails

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

func (*RedemptionOrderConfirmationV03) AddRelatedReference

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 (*RedemptionOrderConfirmationV04) AddCopyDetails

func (*RedemptionOrderConfirmationV04) AddExtension

func (*RedemptionOrderConfirmationV04) AddMessageIdentification

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

func (*RedemptionOrderConfirmationV04) AddMultipleExecutionDetails

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

func (*RedemptionOrderConfirmationV04) AddPoolReference

func (*RedemptionOrderConfirmationV04) AddPreviousReference

func (*RedemptionOrderConfirmationV04) AddRelatedReference

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 (*RedemptionOrderV03) AddCopyDetails

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

func (*RedemptionOrderV03) AddExtension

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

func (*RedemptionOrderV03) AddMessageIdentification

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

func (*RedemptionOrderV03) AddMultipleOrderDetails

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

func (*RedemptionOrderV03) AddPoolReference

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

func (*RedemptionOrderV03) AddPreviousReference

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

func (*RedemptionOrderV03) AddRelatedPartyDetails

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 (*RedemptionOrderV04) AddCopyDetails

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

func (*RedemptionOrderV04) AddExtension

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

func (*RedemptionOrderV04) AddMessageIdentification

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

func (*RedemptionOrderV04) AddMultipleOrderDetails

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

func (*RedemptionOrderV04) AddPoolReference

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

func (*RedemptionOrderV04) AddPreviousReference

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 (*RequestForOrderConfirmationStatusReportV01) AddExtension

func (*RequestForOrderConfirmationStatusReportV01) AddMessageIdentification

func (*RequestForOrderConfirmationStatusReportV01) AddRequestDetails

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 (*RequestForOrderConfirmationStatusReportV02) AddExtension

func (*RequestForOrderConfirmationStatusReportV02) AddMessageIdentification

func (*RequestForOrderConfirmationStatusReportV02) AddRequestDetails

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 (*RequestForOrderStatusReportV02) AddRequestDetails

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 (*RequestForOrderStatusReportV03) AddExtension

func (*RequestForOrderStatusReportV03) AddMessageIdentification

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

func (*RequestForOrderStatusReportV03) AddRequestDetails

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 (*RequestForOrderStatusReportV04) AddExtension

func (*RequestForOrderStatusReportV04) AddMessageIdentification

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

func (*RequestForOrderStatusReportV04) AddRequestDetails

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 (*SecuritiesTradeConfirmationCancellationV01) AddIdentification

func (*SecuritiesTradeConfirmationCancellationV01) AddOtherBusinessParties

func (*SecuritiesTradeConfirmationCancellationV01) AddReferences

func (*SecuritiesTradeConfirmationCancellationV01) AddSupplementaryData

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 (*SecuritiesTradeConfirmationResponseV01) AddClearingDetails

func (*SecuritiesTradeConfirmationResponseV01) AddConfirmationParties

func (*SecuritiesTradeConfirmationResponseV01) AddIdentification

func (*SecuritiesTradeConfirmationResponseV01) AddReferences

func (*SecuritiesTradeConfirmationResponseV01) AddStatus

func (*SecuritiesTradeConfirmationResponseV01) AddSupplementaryData

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 (*SecuritiesTradeConfirmationStatusAdviceV01) AddAffirmationStatus

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddCancellationProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddConfirmationParties

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddCounterpartyTradingDetails

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

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddDeliveringSettlementParties

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

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddIdentification

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddMatchingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddPartyTradingDetails

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

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddReceivingSettlementParties

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

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddReferences

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddReplacementProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV01) AddSupplementaryData

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 (*SecuritiesTradeConfirmationStatusAdviceV02) AddAffirmationStatus

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddCancellationProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddConfirmationParties

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddCounterpartyTradingDetails

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

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddDeliveringSettlementParties

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

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddIdentification

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddMatchingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddPartyTradingDetails

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

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddReceivingSettlementParties

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

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddReferences

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddReplacementProcessingStatus

func (*SecuritiesTradeConfirmationStatusAdviceV02) AddSupplementaryData

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"`
}

Scope Sent by an executing party to an instructing party directly or through Central Matching Utility (CMU) to provide trade confirmation on a per-account basis based on instructions provided by the instructing party in the SecuritiesAllocationInstruction message. It may also be used to provide trade confirmation on the trade level from an executing party or an instructing party to the custodian or an affirming party directly or through CMU. 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 custodian or the 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: In local matching, the initiator of this message is always the executing party. In central matching the initiator may be either the executing party or instructing party. Respondent: instructing party, a custodian or an affirming party responds with SecuritiesTradeConfirmationResponse (accept or reject) message.

func (*SecuritiesTradeConfirmationV01) AddCashParties

func (*SecuritiesTradeConfirmationV01) AddClearingDetails

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

func (*SecuritiesTradeConfirmationV01) AddConfirmationParties

func (s *SecuritiesTradeConfirmationV01) AddConfirmationParties() *iso20022.ConfirmationParties2

func (*SecuritiesTradeConfirmationV01) AddDeliveringSettlementParties

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

func (*SecuritiesTradeConfirmationV01) AddFinancialInstrumentAttributes

func (s *SecuritiesTradeConfirmationV01) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes31

func (*SecuritiesTradeConfirmationV01) AddFinancialInstrumentIdentification

func (s *SecuritiesTradeConfirmationV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*SecuritiesTradeConfirmationV01) AddIdentification

func (*SecuritiesTradeConfirmationV01) AddNumberCount

func (*SecuritiesTradeConfirmationV01) AddOtherAmounts

func (*SecuritiesTradeConfirmationV01) AddOtherBusinessParties

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

func (*SecuritiesTradeConfirmationV01) AddOtherPrices

func (*SecuritiesTradeConfirmationV01) AddReceivingSettlementParties

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

func (*SecuritiesTradeConfirmationV01) AddReferences

func (*SecuritiesTradeConfirmationV01) AddRegulatoryStipulations

func (s *SecuritiesTradeConfirmationV01) AddRegulatoryStipulations() *iso20022.RegulatoryStipulations1

func (*SecuritiesTradeConfirmationV01) AddSettlementAmount

func (*SecuritiesTradeConfirmationV01) AddSettlementParameters

func (s *SecuritiesTradeConfirmationV01) AddSettlementParameters() *iso20022.SettlementDetails43

func (*SecuritiesTradeConfirmationV01) AddStandingSettlementInstruction

func (s *SecuritiesTradeConfirmationV01) AddStandingSettlementInstruction() *iso20022.StandingSettlementInstruction9

func (*SecuritiesTradeConfirmationV01) AddStipulations

func (*SecuritiesTradeConfirmationV01) AddSupplementaryData

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

func (*SecuritiesTradeConfirmationV01) AddTradeDetails

func (s *SecuritiesTradeConfirmationV01) AddTradeDetails() *iso20022.Order14

func (*SecuritiesTradeConfirmationV01) AddTwoLegTransactionDetails

func (s *SecuritiesTradeConfirmationV01) AddTwoLegTransactionDetails() *iso20022.TwoLegTransactionDetails1

func (*SecuritiesTradeConfirmationV01) AddUnderlyingFinancialInstrument

func (s *SecuritiesTradeConfirmationV01) AddUnderlyingFinancialInstrument() *iso20022.UnderlyingFinancialInstrument1

type SecuritiesTradeConfirmationV02

type SecuritiesTradeConfirmationV02 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.FinancialInstrumentAttributes44 `xml:"FinInstrmAttrbts,omitempty"`

	// Underlying financial instrument to which an trade confirmation is related.
	UnderlyingFinancialInstrument []*iso20022.UnderlyingFinancialInstrument2 `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.CashParties18 `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"`
}

SCOPE Sent by an executing party to an instructing party directly or through Central Matching Utility (CMU) to provide trade confirmation on a per-account basis based on instructions provided by the instructing party in the SecuritiesAllocationInstruction message.

It may also be used to provide trade confirmation on the trade level from an executing party or an instructing party to the custodian or an affirming party directly or through CMU.

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 custodian or the affirming party is typically the custodian, trustee, financial institution, intermediary system/vendor communicating on behalf of them, or their agent.

USAGE Initiator: In local matching, the initiator of this message is always the executing party. In central matching the initiator may be either the executing party or instructing party. Respondent: instructing party, a custodian or an affirming party responds with SecuritiesTradeConfirmationResponse (accept or reject) message.

func (*SecuritiesTradeConfirmationV02) AddCashParties

func (*SecuritiesTradeConfirmationV02) AddClearingDetails

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

func (*SecuritiesTradeConfirmationV02) AddConfirmationParties

func (s *SecuritiesTradeConfirmationV02) AddConfirmationParties() *iso20022.ConfirmationParties2

func (*SecuritiesTradeConfirmationV02) AddDeliveringSettlementParties

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

func (*SecuritiesTradeConfirmationV02) AddFinancialInstrumentAttributes

func (s *SecuritiesTradeConfirmationV02) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes44

func (*SecuritiesTradeConfirmationV02) AddFinancialInstrumentIdentification

func (s *SecuritiesTradeConfirmationV02) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*SecuritiesTradeConfirmationV02) AddIdentification

func (*SecuritiesTradeConfirmationV02) AddNumberCount

func (*SecuritiesTradeConfirmationV02) AddOtherAmounts

func (*SecuritiesTradeConfirmationV02) AddOtherBusinessParties

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

func (*SecuritiesTradeConfirmationV02) AddOtherPrices

func (*SecuritiesTradeConfirmationV02) AddReceivingSettlementParties

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

func (*SecuritiesTradeConfirmationV02) AddReferences

func (*SecuritiesTradeConfirmationV02) AddRegulatoryStipulations

func (s *SecuritiesTradeConfirmationV02) AddRegulatoryStipulations() *iso20022.RegulatoryStipulations1

func (*SecuritiesTradeConfirmationV02) AddSettlementAmount

func (*SecuritiesTradeConfirmationV02) AddSettlementParameters

func (s *SecuritiesTradeConfirmationV02) AddSettlementParameters() *iso20022.SettlementDetails43

func (*SecuritiesTradeConfirmationV02) AddStandingSettlementInstruction

func (s *SecuritiesTradeConfirmationV02) AddStandingSettlementInstruction() *iso20022.StandingSettlementInstruction9

func (*SecuritiesTradeConfirmationV02) AddStipulations

func (*SecuritiesTradeConfirmationV02) AddSupplementaryData

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

func (*SecuritiesTradeConfirmationV02) AddTradeDetails

func (s *SecuritiesTradeConfirmationV02) AddTradeDetails() *iso20022.Order14

func (*SecuritiesTradeConfirmationV02) AddTwoLegTransactionDetails

func (s *SecuritiesTradeConfirmationV02) AddTwoLegTransactionDetails() *iso20022.TwoLegTransactionDetails1

func (*SecuritiesTradeConfirmationV02) AddUnderlyingFinancialInstrument

func (s *SecuritiesTradeConfirmationV02) AddUnderlyingFinancialInstrument() *iso20022.UnderlyingFinancialInstrument2

type SecuritiesTradeConfirmationV03

type SecuritiesTradeConfirmationV03 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.Order17 `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.FinancialInstrumentAttributes44 `xml:"FinInstrmAttrbts,omitempty"`

	// Underlying financial instrument to which an trade confirmation is related.
	UnderlyingFinancialInstrument []*iso20022.UnderlyingFinancialInstrument2 `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.CashParties18 `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.OtherPrices2 `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"`
}

SCOPE Sent by an executing party to an instructing party directly or through Central Matching Utility (CMU) to provide trade confirmation on a per-account basis based on instructions provided by the instructing party in the SecuritiesAllocationInstruction message.

It may also be used to provide trade confirmation on the trade level from an executing party or an instructing party to the custodian or an affirming party directly or through CMU.

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 custodian or the affirming party is typically the custodian, trustee, financial institution, intermediary system/vendor communicating on behalf of them, or their agent.

USAGE Initiator: In local matching, the initiator of this message is always the executing party. In central matching the initiator may be either the executing party or instructing party. Respondent: instructing party, a custodian or an affirming party responds with SecuritiesTradeConfirmationResponse (accept or reject) message.

func (*SecuritiesTradeConfirmationV03) AddCashParties

func (*SecuritiesTradeConfirmationV03) AddClearingDetails

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

func (*SecuritiesTradeConfirmationV03) AddConfirmationParties

func (s *SecuritiesTradeConfirmationV03) AddConfirmationParties() *iso20022.ConfirmationParties2

func (*SecuritiesTradeConfirmationV03) AddDeliveringSettlementParties

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

func (*SecuritiesTradeConfirmationV03) AddFinancialInstrumentAttributes

func (s *SecuritiesTradeConfirmationV03) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes44

func (*SecuritiesTradeConfirmationV03) AddFinancialInstrumentIdentification

func (s *SecuritiesTradeConfirmationV03) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*SecuritiesTradeConfirmationV03) AddIdentification

func (*SecuritiesTradeConfirmationV03) AddNumberCount

func (*SecuritiesTradeConfirmationV03) AddOtherAmounts

func (*SecuritiesTradeConfirmationV03) AddOtherBusinessParties

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

func (*SecuritiesTradeConfirmationV03) AddOtherPrices

func (*SecuritiesTradeConfirmationV03) AddReceivingSettlementParties

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

func (*SecuritiesTradeConfirmationV03) AddReferences

func (*SecuritiesTradeConfirmationV03) AddRegulatoryStipulations

func (s *SecuritiesTradeConfirmationV03) AddRegulatoryStipulations() *iso20022.RegulatoryStipulations1

func (*SecuritiesTradeConfirmationV03) AddSettlementAmount

func (*SecuritiesTradeConfirmationV03) AddSettlementParameters

func (s *SecuritiesTradeConfirmationV03) AddSettlementParameters() *iso20022.SettlementDetails43

func (*SecuritiesTradeConfirmationV03) AddStandingSettlementInstruction

func (s *SecuritiesTradeConfirmationV03) AddStandingSettlementInstruction() *iso20022.StandingSettlementInstruction9

func (*SecuritiesTradeConfirmationV03) AddStipulations

func (*SecuritiesTradeConfirmationV03) AddSupplementaryData

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

func (*SecuritiesTradeConfirmationV03) AddTradeDetails

func (s *SecuritiesTradeConfirmationV03) AddTradeDetails() *iso20022.Order17

func (*SecuritiesTradeConfirmationV03) AddTwoLegTransactionDetails

func (s *SecuritiesTradeConfirmationV03) AddTwoLegTransactionDetails() *iso20022.TwoLegTransactionDetails1

func (*SecuritiesTradeConfirmationV03) AddUnderlyingFinancialInstrument

func (s *SecuritiesTradeConfirmationV03) AddUnderlyingFinancialInstrument() *iso20022.UnderlyingFinancialInstrument2

type SubscriptionBulkOrderCancellationInstructionV02

type SubscriptionBulkOrderCancellationInstructionV02 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.SubscriptionBulkOrderInstruction1 `xml:"OrdrToBeCanc,omitempty"`
}

Scope The SubscriptionBulkOrderCancellationInstruction 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 SubscriptionBulkOrder instruction. Usage The SubscriptionBulkOrderCancellationInstruction message is used to cancel the entire previously sent SubscriptionBulkOrder 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 (*SubscriptionBulkOrderCancellationInstructionV02) AddMasterReference

func (*SubscriptionBulkOrderCancellationInstructionV02) AddOrderToBeCancelled

func (*SubscriptionBulkOrderCancellationInstructionV02) AddPoolReference

func (*SubscriptionBulkOrderCancellationInstructionV02) AddPreviousReference

type SubscriptionBulkOrderCancellationRequestV03

type SubscriptionBulkOrderCancellationRequestV03 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.SubscriptionBulkOrderInstruction2 `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 SubscriptionBulkOrderCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent SubscriptionBulkOrder instruction. Usage The SubscriptionBulkOrderCancellationRequest message is used to either: - request the cancellation of an entire SubscriptionBulkOrder 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 SubscriptionBulkOrderCancellationRequest message is used to request the cancellation of an entire SubscriptionBulkOrder message, this can be done by either: - quoting the order references of all the individual orders listed in the SubscriptionBulkOrder message, or, - quoting the details of all the individual orders (this includes the OrderReference) listed in SubscriptionBulkOrder message, but this is not recommended. The message identification of the SubscriptionBulkOrder message may also be quoted in PreviousReference. It is also possible to request the cancellation of an entire SubscriptionBulkOrder message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the SubscriptionBulkOrderCancellationRequest 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 SubscriptionBulkOrder message, or, - quoting the details of each individual order (including the OrderReference) listed in SubscriptionBulkOrder message, but this is not recommended. The message identification of the SubscriptionBulkOrder 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 an SubscriptionBulkOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SubscriptionBulkOrderCancellationRequestV03) AddCancellationByOrderDetails

func (*SubscriptionBulkOrderCancellationRequestV03) AddCancellationByReference

func (*SubscriptionBulkOrderCancellationRequestV03) AddCopyDetails

func (*SubscriptionBulkOrderCancellationRequestV03) AddMessageIdentification

func (*SubscriptionBulkOrderCancellationRequestV03) AddPoolReference

func (*SubscriptionBulkOrderCancellationRequestV03) AddPreviousReference

type SubscriptionBulkOrderCancellationRequestV04

type SubscriptionBulkOrderCancellationRequestV04 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 SubscriptionBulkOrderCancellationRequest 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 SubscriptionBulkOrder. Usage The SubscriptionBulkOrderCancellationRequest 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 SubscriptionBulkOrder message is specified in the order reference element. The message identification of the SubscriptionBulkOrder 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 SubscriptionBulkOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SubscriptionBulkOrderCancellationRequestV04) AddCopyDetails

func (*SubscriptionBulkOrderCancellationRequestV04) AddMessageIdentification

func (*SubscriptionBulkOrderCancellationRequestV04) AddOrderReferences

func (*SubscriptionBulkOrderCancellationRequestV04) AddPoolReference

func (*SubscriptionBulkOrderCancellationRequestV04) AddPreviousReference

func (*SubscriptionBulkOrderCancellationRequestV04) SetMasterReference

func (s *SubscriptionBulkOrderCancellationRequestV04) SetMasterReference(value string)

type SubscriptionBulkOrderConfirmationAmendmentV01

type SubscriptionBulkOrderConfirmationAmendmentV01 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 orders.
	BulkExecutionDetails *iso20022.SubscriptionBulkExecution3 `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 SubscriptionBulkOrderConfirmationAmendment message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent SubscriptionBulkOrderConfirmation message. Usage The SubscriptionBulkOrderConfirmationAmendment message is used to amend one or more previously sent subscription 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 SubscriptionBulkOrder message in which the orders were conveyed may also be quoted in RelatedReference. The message identification of the SubscriptionBulkOrderConfirmation message in which the original order confirmations were conveyed may also be quoted in PreviousReference.

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddBulkExecutionDetails

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddExtension

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddMessageIdentification

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddPoolReference

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddRelatedPartyDetails

func (*SubscriptionBulkOrderConfirmationAmendmentV01) AddRelatedReference

type SubscriptionBulkOrderConfirmationCancellationInstructionV01

type SubscriptionBulkOrderConfirmationCancellationInstructionV01 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.SubscriptionBulkOrderConfirmation1 `xml:"CxlByOrdrConfDtls,omitempty"`

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

Scope An executing party, for example, a transfer agent sends the SubscriptionBulkOrderConfirmationCancellationInstruction message to the instructing party, for example, an investment manager or its authorised representative to cancel a previously sent SubscriptionBulkOrderConfirmation. Usage The SubscriptionBulkOrderConfirmationCancellationInstruction message is used to cancel one or more previously sent subscription bulk order confirmations. The amendment indicator element is used to specify whether the subscription bulk order confirmation cancellation is to be followed by a SubscriptionBulkOrderConfirmationAmendment. The SubscriptionBulkOrderConfirmationCancellationInstruction message is used to either: - cancel an entire SubscriptionBulkOrderConfirmation 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 SubscriptionBulkOrderConfirmationCancellationInstruction 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 SubscriptionBulkOrderConfirmation message, or, - quoting the details of all the individual order confirmations (this includes the OrderReference and DealReference) listed in SubscriptionBulkOrderConfirmation message but this is not recommended. The message identification of the SubscriptionOrderConfirmation 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 SubscriptionBulkOrderConfirmationCancellationInstruction 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 SubscriptionBulkOrderConfirmation message, or, - quoting the details of each individual order execution (this includes the OrderReference and DealReference) listed in SubscriptionBulkOrderConfirmation message but this is not recommended. The message identification of the SubscriptionBulkOrderConfirmation message in which the individual order confirmation was conveyed may also be quoted in PreviousReference. The rejection or acceptance of a SubscriptionBulkOrderConfirmationCancellationInstruction is made using an OrderConfirmationStatusReport message.

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddCancellationByReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddMessageIdentification

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddPoolReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV01) AddRelatedReference

type SubscriptionBulkOrderConfirmationCancellationInstructionV02

type SubscriptionBulkOrderConfirmationCancellationInstructionV02 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"`

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

Scope The SubscriptionBulkOrderConfirmationCancellationInstruction 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 SubscriptionBulkOrderConfirmation. 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 SubscriptionBulkOrderConfirmation are specified in the order reference and deal reference elements respectively. The message identification of the SubscriptionBulkOrderConfirmation 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 subscription bulk order confirmation cancellation is to be followed by an amendment An amendment of a subscription bulk order confirmation is carried out by sending a SubscriptionBulkOrderConfirmation message in which the AmendmentIndicator contains the value ‘true’.

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddMessageIdentification

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddOrderReferences

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddPoolReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) AddRelatedReference

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator

func (*SubscriptionBulkOrderConfirmationCancellationInstructionV02) SetMasterReference

type SubscriptionBulkOrderConfirmationV02

type SubscriptionBulkOrderConfirmationV02 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 orders.
	BulkExecutionDetails *iso20022.SubscriptionBulkExecution2 `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 SubscriptionBulkOrderConfirmation 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 SubscriptionBulkOrder message. Usage The SubscriptionBulkOrderConfirmation 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 SubscriptionBulkOrder must in all cases be responded to by a SubscriptionBulkOrderConfirmation and in no circumstances by a SubscriptionMultipleOrderConfirmation. If the executing party needs to confirm a SubscriptionMultipleOrder message, then the SubscriptionMultipleOrderConfirmation message must be used.

func (*SubscriptionBulkOrderConfirmationV02) AddBulkExecutionDetails

func (*SubscriptionBulkOrderConfirmationV02) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationV02) AddExtension

func (*SubscriptionBulkOrderConfirmationV02) AddIntermediaryDetails

func (s *SubscriptionBulkOrderConfirmationV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (*SubscriptionBulkOrderConfirmationV02) AddMasterReference

func (*SubscriptionBulkOrderConfirmationV02) AddPoolReference

func (*SubscriptionBulkOrderConfirmationV02) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationV02) AddRelatedReference

type SubscriptionBulkOrderConfirmationV03

type SubscriptionBulkOrderConfirmationV03 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 orders.
	BulkExecutionDetails *iso20022.SubscriptionBulkExecution3 `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 SubscriptionBulkOrderConfirmation message to the instructing party, for example, an investment manager or its authorised representative to confirm the details of the execution of a SubscriptionBulkOrder instruction. Usage The SubscriptionBulkOrderConfirmation message is used to confirm the execution of all individual orders. 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 SubscriptionBulkOrder message in which the individual order was conveyed may also be quoted in RelatedReference. A SubscriptionBulkOrder must in all cases be responded to by a SubscriptionBulkOrderConfirmation and in no circumstances by a SubscriptionOrderConfirmation. If the executing party needs to confirm a SubscriptionOrder instruction, then the SubscriptionOrderConfirmation must be used.

func (*SubscriptionBulkOrderConfirmationV03) AddBulkExecutionDetails

func (*SubscriptionBulkOrderConfirmationV03) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationV03) AddExtension

func (*SubscriptionBulkOrderConfirmationV03) AddMessageIdentification

func (*SubscriptionBulkOrderConfirmationV03) AddPoolReference

func (*SubscriptionBulkOrderConfirmationV03) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationV03) AddRelatedPartyDetails

func (s *SubscriptionBulkOrderConfirmationV03) AddRelatedPartyDetails() *iso20022.Intermediary9

func (*SubscriptionBulkOrderConfirmationV03) AddRelatedReference

type SubscriptionBulkOrderConfirmationV04

type SubscriptionBulkOrderConfirmationV04 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.SubscriptionBulkExecution4 `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 SubscriptionBulkOrderConfirmation 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 the execution of a SubscriptionBulkOrder instruction. Usage The SubscriptionBulkOrderConfirmation message is used to confirm the execution of all individual orders. 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 SubscriptionBulkOrder message in which the individual order was conveyed may also be quoted in RelatedReference. A SubscriptionBulkOrder must in all cases be responded to by a SubscriptionBulkOrderConfirmation and in no circumstances by a SubscriptionOrderConfirmation. If the executing party needs to confirm a SubscriptionOrder instruction, then the SubscriptionOrderConfirmation 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 (*SubscriptionBulkOrderConfirmationV04) AddBulkExecutionDetails

func (*SubscriptionBulkOrderConfirmationV04) AddCopyDetails

func (*SubscriptionBulkOrderConfirmationV04) AddExtension

func (*SubscriptionBulkOrderConfirmationV04) AddMessageIdentification

func (*SubscriptionBulkOrderConfirmationV04) AddPoolReference

func (*SubscriptionBulkOrderConfirmationV04) AddPreviousReference

func (*SubscriptionBulkOrderConfirmationV04) AddRelatedReference

type SubscriptionBulkOrderV02

type SubscriptionBulkOrderV02 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.
	BulkOrderDetails *iso20022.SubscriptionBulkOrder2 `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 SubscriptionBulkOrder 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 subscribe to a financial instrument, for two or more accounts. Usage The SubscriptionBulkOrder 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 related to the same financial instrument. This message will be typically be used by a party collecting orders and bulking these individual orders into one bulk order before sending it to another party. For a single subscription order, the SubscriptionMultipleOrder message, not the SubscriptionBulkOrder message, must be used. If there are subscription orders for different financial instruments but for the same account, then the SubscriptionMultipleOrder must be used.

func (*SubscriptionBulkOrderV02) AddBulkOrderDetails

func (s *SubscriptionBulkOrderV02) AddBulkOrderDetails() *iso20022.SubscriptionBulkOrder2

func (*SubscriptionBulkOrderV02) AddCopyDetails

func (s *SubscriptionBulkOrderV02) AddCopyDetails() *iso20022.CopyInformation1

func (*SubscriptionBulkOrderV02) AddExtension

func (s *SubscriptionBulkOrderV02) AddExtension() *iso20022.Extension1

func (*SubscriptionBulkOrderV02) AddIntermediaryDetails

func (s *SubscriptionBulkOrderV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (*SubscriptionBulkOrderV02) AddMasterReference

func (s *SubscriptionBulkOrderV02) AddMasterReference() *iso20022.AdditionalReference3

func (*SubscriptionBulkOrderV02) AddPoolReference

func (*SubscriptionBulkOrderV02) AddPreviousReference

func (s *SubscriptionBulkOrderV02) AddPreviousReference() *iso20022.AdditionalReference3

type SubscriptionBulkOrderV03

type SubscriptionBulkOrderV03 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.
	BulkOrderDetails *iso20022.SubscriptionBulkOrder4 `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 SubscriptionBulkOrder message to the executing party, for example, a transfer agent, to instruct a subscription to a financial instrument for two or more accounts. Usage The SubscriptionBulkOrder 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 related to the same financial instrument. This message will typically be used by a party collecting orders and bulking these individual orders into one bulk order before sending it to another party. For a single subscription order, the SubscriptionOrder message, not the SubscriptionBulkOrder message, must be used. If there are subscription orders for different financial instruments but for the same account, then the SubscriptionOrder must be used.

func (*SubscriptionBulkOrderV03) AddBulkOrderDetails

func (s *SubscriptionBulkOrderV03) AddBulkOrderDetails() *iso20022.SubscriptionBulkOrder4

func (*SubscriptionBulkOrderV03) AddCopyDetails

func (s *SubscriptionBulkOrderV03) AddCopyDetails() *iso20022.CopyInformation2

func (*SubscriptionBulkOrderV03) AddExtension

func (s *SubscriptionBulkOrderV03) AddExtension() *iso20022.Extension1

func (*SubscriptionBulkOrderV03) AddMessageIdentification

func (s *SubscriptionBulkOrderV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionBulkOrderV03) AddPoolReference

func (*SubscriptionBulkOrderV03) AddPreviousReference

func (s *SubscriptionBulkOrderV03) AddPreviousReference() *iso20022.AdditionalReference3

func (*SubscriptionBulkOrderV03) AddRelatedPartyDetails

func (s *SubscriptionBulkOrderV03) AddRelatedPartyDetails() *iso20022.Intermediary8

type SubscriptionBulkOrderV04

type SubscriptionBulkOrderV04 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.SubscriptionBulkOrder5 `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 SubscriptionBulkOrder 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 subscription to a financial instrument for two or more accounts. Usage The SubscriptionBulkOrder 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. This message will typically be used by a party collecting orders and bulking these individual orders into one bulk order before sending it to another party. For a single subscription order, the SubscriptionOrder message, not the SubscriptionBulkOrder message, must be used.

func (*SubscriptionBulkOrderV04) AddBulkOrderDetails

func (s *SubscriptionBulkOrderV04) AddBulkOrderDetails() *iso20022.SubscriptionBulkOrder5

func (*SubscriptionBulkOrderV04) AddCopyDetails

func (s *SubscriptionBulkOrderV04) AddCopyDetails() *iso20022.CopyInformation4

func (*SubscriptionBulkOrderV04) AddExtension

func (s *SubscriptionBulkOrderV04) AddExtension() *iso20022.Extension1

func (*SubscriptionBulkOrderV04) AddMessageIdentification

func (s *SubscriptionBulkOrderV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionBulkOrderV04) AddPoolReference

func (*SubscriptionBulkOrderV04) AddPreviousReference

func (s *SubscriptionBulkOrderV04) AddPreviousReference() *iso20022.AdditionalReference8

type SubscriptionMultipleOrderCancellationInstructionV02

type SubscriptionMultipleOrderCancellationInstructionV02 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.SubscriptionMultipleOrderInstruction1 `xml:"OrdrToBeCanc,omitempty"`
}

Scope The SubscriptionMultipleOrderCancellationInstruction 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 SubscriptionMultipleOrder instruction. Usage The SubscriptionMultipleOrderCancellationInstruction message is used to cancel the entire previously sent SubscriptionMultipleOrder 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 (*SubscriptionMultipleOrderCancellationInstructionV02) AddMasterReference

func (*SubscriptionMultipleOrderCancellationInstructionV02) AddOrderToBeCancelled

func (*SubscriptionMultipleOrderCancellationInstructionV02) AddPoolReference

func (*SubscriptionMultipleOrderCancellationInstructionV02) AddPreviousReference

type SubscriptionMultipleOrderConfirmationV02

type SubscriptionMultipleOrderConfirmationV02 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 order.
	MultipleExecutionDetails *iso20022.SubscriptionMultipleExecution2 `xml:"MltplExctnDtls"`

	// Confirmation of 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 SubscriptionMultipleOrderConfirmation message 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 instruction 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 SubscriptionMultipleOrder message. Usage The SubscriptionMultipleOrderConfirmation message is sent, after the price has been determined, to confirm the execution of the individual orders. A SubscriptionMultipleOrder may be responded to by more than one SubscriptionMultipleOrderConfirmation message, 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 SubscriptionMultipleOrder must in all cases be responded to by a SubscriptionMultipleOrderConfirmation message/s and in no circumstances by a SubscriptionBulkOrderConfirmation message/s. If the executing party needs to confirm a SubscriptionBulkOrder message, then a SubscriptionBulkOrderConfirmation message must be used.

func (*SubscriptionMultipleOrderConfirmationV02) AddCopyDetails

func (*SubscriptionMultipleOrderConfirmationV02) AddExtension

func (*SubscriptionMultipleOrderConfirmationV02) AddIntermediaryDetails

func (*SubscriptionMultipleOrderConfirmationV02) AddMasterReference

func (*SubscriptionMultipleOrderConfirmationV02) AddMultipleExecutionDetails

func (*SubscriptionMultipleOrderConfirmationV02) AddPoolReference

func (*SubscriptionMultipleOrderConfirmationV02) AddPreviousReference

func (*SubscriptionMultipleOrderConfirmationV02) AddRelatedReference

type SubscriptionMultipleOrderV02

type SubscriptionMultipleOrderV02 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.SubscriptionMultipleOrder2 `xml:"MltplOrdrDtls"`

	// Information related to the 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 SubscriptionMultipleOrder 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 subscribe to one or more financial instruments, for the same account. Usage The SubscriptionMultipleOrder 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 subscription order, the SubscriptionMultipleOrder message, not the SubscriptionBulkOrder message, must be used. If there are subscription orders for the same financial instrument but for different accounts, then the SubscriptionBulkOrder message must be used.

func (*SubscriptionMultipleOrderV02) AddCopyDetails

func (*SubscriptionMultipleOrderV02) AddExtension

func (*SubscriptionMultipleOrderV02) AddIntermediaryDetails

func (s *SubscriptionMultipleOrderV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (*SubscriptionMultipleOrderV02) AddMasterReference

func (*SubscriptionMultipleOrderV02) AddMultipleOrderDetails

func (*SubscriptionMultipleOrderV02) AddPoolReference

func (*SubscriptionMultipleOrderV02) AddPreviousReference

func (s *SubscriptionMultipleOrderV02) AddPreviousReference() *iso20022.AdditionalReference3

type SubscriptionOrderCancellationRequestV03

type SubscriptionOrderCancellationRequestV03 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.SubscriptionMultipleOrderInstruction2 `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 SubscriptionOrderCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent SubscriptionOrder. Usage The SubscriptionOrderCancellationRequest message is used to either: - request the cancellation of an entire SubscriptionOrder 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 SubscriptionOrderCancellationRequest message is used to request the cancellation of an entire SubscriptionOrder message, this can be done by either: - quoting the order references of all the individual orders listed in the SubscriptionOrder message, or, - quoting the details of all the individual orders (this includes the OrderReference) listed in SubscriptionOrder message, but this is not recommended. The message identification of the SubscriptionOrder message may also be quoted in PreviousReference. It is also possible to request the cancellation of an entire SubscriptionOrder message by quoting its message identification in PreviousReference, but this is not recommended. (2) When the SubscriptionOrderCancellationRequest 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 SubscriptionOrder message, or, - quoting the details of each individual order (including the OrderReference) listed in SubscriptionOrder message, but this is not recommended. The message identification of the SubscriptionOrder 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 SubscriptionOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SubscriptionOrderCancellationRequestV03) AddCancellationByOrderDetails

func (*SubscriptionOrderCancellationRequestV03) AddCancellationByReference

func (*SubscriptionOrderCancellationRequestV03) AddCopyDetails

func (*SubscriptionOrderCancellationRequestV03) AddMessageIdentification

func (*SubscriptionOrderCancellationRequestV03) AddPoolReference

func (*SubscriptionOrderCancellationRequestV03) AddPreviousReference

type SubscriptionOrderCancellationRequestV04

type SubscriptionOrderCancellationRequestV04 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 SubscriptionOrderCancellationRequest 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 SubscriptionOrder. Usage The SubscriptionOrderCancellationRequest 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 SubscriptionOrder message is specified in the order reference element. The message identification of the SubscriptionOrder 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 SubscriptionOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SubscriptionOrderCancellationRequestV04) AddCopyDetails

func (*SubscriptionOrderCancellationRequestV04) AddMessageIdentification

func (*SubscriptionOrderCancellationRequestV04) AddOrderReferences

func (*SubscriptionOrderCancellationRequestV04) AddPoolReference

func (*SubscriptionOrderCancellationRequestV04) AddPreviousReference

func (*SubscriptionOrderCancellationRequestV04) SetMasterReference

func (s *SubscriptionOrderCancellationRequestV04) SetMasterReference(value string)

type SubscriptionOrderConfirmationAmendmentV01

type SubscriptionOrderConfirmationAmendmentV01 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 order.
	MultipleExecutionDetails *iso20022.SubscriptionMultipleExecution3 `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 SubscriptionOrderConfirmationAmendment message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent SubscriptionOrderConfirmation. Usage The SubscriptionOrderConfirmationAmendment message is used to amend one or more previously sent subscription 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 SubscriptionOrder message in which the individual orders were conveyed may also be quoted in RelatedReference. The message identification of the SubscriptionOrderConfirmation message in which the original order confirmations were conveyed may also be quoted in PreviousReference.

func (*SubscriptionOrderConfirmationAmendmentV01) AddCopyDetails

func (*SubscriptionOrderConfirmationAmendmentV01) AddExtension

func (*SubscriptionOrderConfirmationAmendmentV01) AddMessageIdentification

func (*SubscriptionOrderConfirmationAmendmentV01) AddMultipleExecutionDetails

func (*SubscriptionOrderConfirmationAmendmentV01) AddPoolReference

func (*SubscriptionOrderConfirmationAmendmentV01) AddPreviousReference

func (*SubscriptionOrderConfirmationAmendmentV01) AddRelatedPartyDetails

func (*SubscriptionOrderConfirmationAmendmentV01) AddRelatedReference

type SubscriptionOrderConfirmationCancellationInstructionV01

type SubscriptionOrderConfirmationCancellationInstructionV01 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.SubscriptionOrderConfirmation1 `xml:"CxlByOrdrConfDtls,omitempty"`

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

Scope An executing party, for example, a transfer agent, sends the SubscriptionOrderConfirmationCancellationInstruction message to the instructing party, for example, an investment manager or its authorised representative to cancel a previously sent SubscriptionOrderConfirmation. Usage The SubscriptionOrderConfirmationCancellationInstruction 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 SubscriptionOrderConfirmationAmendment. The SubscriptionOrderConfirmationCancellationInstruction message is used to either: - cancel an entire SubscriptionOrderConfirmation 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 SubscriptionOrderConfirmationCancellationInstruction 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 SubscriptionOrderConfirmation 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. (2) When the SubscriptionOrderConfirmationCancellationInstruction 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 SubscriptionOrderConfirmation message, or, - quoting the details of each individual order execution (this includes the OrderReference and DealReference) listed in SubscriptionOrderConfirmation message but this is not recommended. The message identification of the SubscriptionOrderConfirmation message in which the individual order confirmation was conveyed may also be quoted in PreviousReference. The rejection or acceptance of a SubscriptionOrderConfirmationCancellationInstruction is made using an OrderConfirmationStatusReport message.

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddCancellationByReference

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddCopyDetails

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddMessageIdentification

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddPoolReference

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddPreviousReference

func (*SubscriptionOrderConfirmationCancellationInstructionV01) AddRelatedReference

type SubscriptionOrderConfirmationCancellationInstructionV02

type SubscriptionOrderConfirmationCancellationInstructionV02 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 SubscriptionOrderConfirmationCancellationInstruction 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 SubscriptionOrderConfirmation. 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 SubscriptionOrderConfirmation are specified in the order reference and deal reference elements respectively. The message identification of the SubscriptionOrderConfirmation 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 subscription order confirmation cancellation is to be followed by an amendment An amendment of a subscription order confirmation is carried out by sending a SubscriptionOrderConfirmation message in which the AmendmentIndicator contains the value ‘true’.

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddCopyDetails

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddMessageIdentification

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddOrderReferences

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddPoolReference

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddPreviousReference

func (*SubscriptionOrderConfirmationCancellationInstructionV02) AddRelatedReference

func (*SubscriptionOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator

func (s *SubscriptionOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (*SubscriptionOrderConfirmationCancellationInstructionV02) SetMasterReference

type SubscriptionOrderConfirmationV03

type SubscriptionOrderConfirmationV03 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 order.
	MultipleExecutionDetails *iso20022.SubscriptionMultipleExecution3 `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 SubscriptionOrderConfirmation message to the instructing party, for example, an investment manager or its authorised representative to confirm the details of the execution of a SubscriptionOrder instruction. Usage The SubscriptionOrderConfirmation message is used to confirm the execution of one or more individual orders. A SubscriptionOrder message containing more than one individual order may be responded to by more than one SubscriptionOrderConfirmation 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 SubscriptionOrder message in which the individual orders 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 must be based on the references. A SubscriptionOrder must in all cases be responded to by a SubscriptionOrderConfirmation message and in no circumstances by a SubscriptionBulkOrderConfirmation message. If the executing party needs to confirm a SubscriptionBulkOrder message, then a SubscriptionBulkOrderConfirmation message must be used.

func (*SubscriptionOrderConfirmationV03) AddCopyDetails

func (*SubscriptionOrderConfirmationV03) AddExtension

func (*SubscriptionOrderConfirmationV03) AddMessageIdentification

func (s *SubscriptionOrderConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionOrderConfirmationV03) AddMultipleExecutionDetails

func (*SubscriptionOrderConfirmationV03) AddPoolReference

func (*SubscriptionOrderConfirmationV03) AddPreviousReference

func (*SubscriptionOrderConfirmationV03) AddRelatedPartyDetails

func (s *SubscriptionOrderConfirmationV03) AddRelatedPartyDetails() *iso20022.Intermediary9

func (*SubscriptionOrderConfirmationV03) AddRelatedReference

type SubscriptionOrderConfirmationV04

type SubscriptionOrderConfirmationV04 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.
	MultipleExecutionDetails *iso20022.SubscriptionMultipleExecution5 `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 SubscriptionOrderConfirmation 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 the execution of a SubscriptionOrder instruction. Usage The SubscriptionOrderConfirmation message is used to confirm the execution of one or more individual orders. A SubscriptionOrder message containing more than one individual order may be responded to by more than one SubscriptionOrderConfirmation message, as the valuation cycle of the financial instruments in each individual order may be different. When a SubscriptionOrderConfirmation message contains fewer confirmations that originally instructed in the original SubscriptionOrder 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 SubscriptionOrder message in which the individual orders was conveyed may also be quoted in RelatedReference but this is not recommended.

A SubscriptionOrder must in all cases be responded to by a SubscriptionOrderConfirmation message and in no circumstances by a SubscriptionBulkOrderConfirmation message. If the executing party needs to confirm one or more subscription orders for the same financial instrument, then a SubscriptionBulkOrderConfirmation 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 (*SubscriptionOrderConfirmationV04) AddCopyDetails

func (*SubscriptionOrderConfirmationV04) AddExtension

func (*SubscriptionOrderConfirmationV04) AddMessageIdentification

func (s *SubscriptionOrderConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionOrderConfirmationV04) AddMultipleExecutionDetails

func (*SubscriptionOrderConfirmationV04) AddPoolReference

func (*SubscriptionOrderConfirmationV04) AddPreviousReference

func (*SubscriptionOrderConfirmationV04) AddRelatedReference

type SubscriptionOrderV03

type SubscriptionOrderV03 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.SubscriptionMultipleOrder4 `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 SubscriptionOrder message to the executing party, for example, a transfer agent, to instruct the subscription of one or more financial instruments for one investment fund account. Usage The SubscriptionOrder message is used to instruct single subscription orders, that is, a message containing one order for one financial instrument and related to one investment account. The SubscriptionOrder 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 subscription order, the SubscriptionOrder message, not the SubscriptionBulkOrder message, must be used. If there are subscription orders for the same financial instrument but for different accounts, then the SubscriptionBulkOrder message must be used.

func (*SubscriptionOrderV03) AddCopyDetails

func (s *SubscriptionOrderV03) AddCopyDetails() *iso20022.CopyInformation2

func (*SubscriptionOrderV03) AddExtension

func (s *SubscriptionOrderV03) AddExtension() *iso20022.Extension1

func (*SubscriptionOrderV03) AddMessageIdentification

func (s *SubscriptionOrderV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionOrderV03) AddMultipleOrderDetails

func (s *SubscriptionOrderV03) AddMultipleOrderDetails() *iso20022.SubscriptionMultipleOrder4

func (*SubscriptionOrderV03) AddPoolReference

func (s *SubscriptionOrderV03) AddPoolReference() *iso20022.AdditionalReference3

func (*SubscriptionOrderV03) AddPreviousReference

func (s *SubscriptionOrderV03) AddPreviousReference() *iso20022.AdditionalReference3

func (*SubscriptionOrderV03) AddRelatedPartyDetails

func (s *SubscriptionOrderV03) AddRelatedPartyDetails() *iso20022.Intermediary8

type SubscriptionOrderV04

type SubscriptionOrderV04 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.SubscriptionMultipleOrder6 `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 SubscriptionOrder 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 subscription of one or more financial instruments for one investment fund account. Usage The SubscriptionOrder message is used to instruct single subscription orders, that is, a message containing one order for one financial instrument for one investment account. The SubscriptionOrder message may also be used for multiple orders, that is, a message containing several orders for the same investment account for different financial instruments. For a single subscription order, the SubscriptionOrder message, not the SubscriptionBulkOrder message, must be used. If there are subscription orders for the same financial instrument but for different accounts that are to be communicated in a single message, then the SubscriptionBulkOrder message must be used.

func (*SubscriptionOrderV04) AddCopyDetails

func (s *SubscriptionOrderV04) AddCopyDetails() *iso20022.CopyInformation4

func (*SubscriptionOrderV04) AddExtension

func (s *SubscriptionOrderV04) AddExtension() *iso20022.Extension1

func (*SubscriptionOrderV04) AddMessageIdentification

func (s *SubscriptionOrderV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SubscriptionOrderV04) AddMultipleOrderDetails

func (s *SubscriptionOrderV04) AddMultipleOrderDetails() *iso20022.SubscriptionMultipleOrder6

func (*SubscriptionOrderV04) AddPoolReference

func (s *SubscriptionOrderV04) AddPoolReference() *iso20022.AdditionalReference9

func (*SubscriptionOrderV04) AddPreviousReference

func (s *SubscriptionOrderV04) AddPreviousReference() *iso20022.AdditionalReference8

type SwitchOrderCancellationInstructionV02

type SwitchOrderCancellationInstructionV02 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.SwitchOrderInstruction1 `xml:"OrdrToBeCanc,omitempty"`
}

Scope The SwitchOrderCancellationInstruction 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 SwitchOrderInstruction message. Usage The SwitchOrderCancellationInstruction message is used to cancel the entire previously sent SwitchOrder message and all the individual legs that it contains. 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 (*SwitchOrderCancellationInstructionV02) AddMasterReference

func (*SwitchOrderCancellationInstructionV02) AddOrderToBeCancelled

func (*SwitchOrderCancellationInstructionV02) AddPoolReference

func (*SwitchOrderCancellationInstructionV02) AddPreviousReference

type SwitchOrderCancellationRequestV03

type SwitchOrderCancellationRequestV03 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 switch orders to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrder1 `xml:"CxlByRef,omitempty"`

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

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

Scope An instructing party, for example, an investment manager or its authorised representative, sends the SwitchOrderCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent SwitchOrder instruction. Usage The SwitchOrderCancellationRequest is used to cancel the entire previously sent SwitchOrder instruction and all the individual legs that it contains. There is no amendment, but a cancellation and re-instruct policy. There are two ways to specify the switch cancellation. Either: - the order reference of the original switch order is quoted, or, - all the details of the original switch order (this includes the OrderReference) are quoted, but this is not recommended. The message identification of the SwitchOrder message may also be quoted in PreviousReference. It is also possible to request the cancellation of a SwitchOrder message by quoting its message identification 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 request. The rejection or acceptance of a SwitchOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SwitchOrderCancellationRequestV03) AddCancellationByOrderDetails

func (s *SwitchOrderCancellationRequestV03) AddCancellationByOrderDetails() *iso20022.SwitchOrderInstruction2

func (*SwitchOrderCancellationRequestV03) AddCancellationByReference

func (s *SwitchOrderCancellationRequestV03) AddCancellationByReference() *iso20022.InvestmentFundOrder1

func (*SwitchOrderCancellationRequestV03) AddCopyDetails

func (*SwitchOrderCancellationRequestV03) AddMessageIdentification

func (s *SwitchOrderCancellationRequestV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderCancellationRequestV03) AddPoolReference

func (*SwitchOrderCancellationRequestV03) AddPreviousReference

type SwitchOrderCancellationRequestV04

type SwitchOrderCancellationRequestV04 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 SwitchOrderCancellationRequest 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 SwitchOrder instruction. Usage The SwitchOrderCancellationRequest is used to cancel the entire previously sent SwitchOrder instruction/s and all the individual legs that it contains. There is no amendment, but a cancellation and re-instruct policy. To request the cancellation of a switch order, the order reference of the original switch order is quoted in the order reference element. The message identification of the SwitchOrder message 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 request. The rejection or acceptance of a SwitchOrderCancellationRequest is made using an OrderCancellationStatusReport message.

func (*SwitchOrderCancellationRequestV04) AddCopyDetails

func (*SwitchOrderCancellationRequestV04) AddMessageIdentification

func (s *SwitchOrderCancellationRequestV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderCancellationRequestV04) AddOrderReferences

func (*SwitchOrderCancellationRequestV04) AddPoolReference

func (*SwitchOrderCancellationRequestV04) AddPreviousReference

func (*SwitchOrderCancellationRequestV04) SetMasterReference

func (s *SwitchOrderCancellationRequestV04) SetMasterReference(value string)

type SwitchOrderConfirmationAmendmentV01

type SwitchOrderConfirmationAmendmentV01 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"`

	// Information related to a switch execution.
	SwitchExecutionDetails []*iso20022.SwitchExecution4 `xml:"SwtchExctnDtls"`

	// 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 SwitchOrderConfirmationAmendment message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent SwitchOrderConfirmation message. Usage The SwitchOrderConfirmationAmendment message is used to amend a previously sent switch order confirmation. Each order confirmation amendment specified is identified in DealReference. The reference of the original order is specified in OrderReference. The message identification of the SwitchOrder message in which the switch order was conveyed may also be quoted in RelatedReference. The message identification of the SwitchOrderConfirmation message in which the original switch order confirmation was conveyed may also be quoted in PreviousReference.

func (*SwitchOrderConfirmationAmendmentV01) AddCopyDetails

func (*SwitchOrderConfirmationAmendmentV01) AddExtension

func (*SwitchOrderConfirmationAmendmentV01) AddMessageIdentification

func (*SwitchOrderConfirmationAmendmentV01) AddPoolReference

func (*SwitchOrderConfirmationAmendmentV01) AddPreviousReference

func (*SwitchOrderConfirmationAmendmentV01) AddRelatedReference

func (*SwitchOrderConfirmationAmendmentV01) AddSwitchExecutionDetails

func (s *SwitchOrderConfirmationAmendmentV01) AddSwitchExecutionDetails() *iso20022.SwitchExecution4

type SwitchOrderConfirmationCancellationInstructionV01

type SwitchOrderConfirmationCancellationInstructionV01 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 switch orders to be cancelled.
	CancellationByReference *iso20022.InvestmentFundOrderExecution1 `xml:"CxlByRef,omitempty"`

	// Common information related to all the switch orders confirmations to be cancelled.
	CancellationByOrderConfirmationDetails *iso20022.SwitchOrderConfirmation1 `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 SwitchOrderConfirmationCancellationInstruction message to the instructing party, for example, an investment manager or its authorised representative to amend a previously sent SwitchOrderConfirmation message. Usage The SwitchOrderConfirmationCancellationInstruction message is used to cancel a previously sent SwitchOrderConfirmation. The amendment indicator element is used to specify whether the switch order confirmation cancellation is to be followed by a switch order confirmation amendment. There are two ways to specify the switch order confirmation cancellation. Either: - the business references, for example, OrderReference, DealReference, of the switch order confirmation are quoted, or, - all the details of the switch order confirmation (this includes the OrderReference and DealReference) are quoted, but this is not recommended. The message identification of the SwitchOrderConfirmation message may also be quoted in PreviousReference. It is also possible to instruct the cancellation of the confirmation message by quoting its message identification in PreviousReference, but this is not recommended.

func (*SwitchOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails

func (s *SwitchOrderConfirmationCancellationInstructionV01) AddCancellationByOrderConfirmationDetails() *iso20022.SwitchOrderConfirmation1

func (*SwitchOrderConfirmationCancellationInstructionV01) AddCancellationByReference

func (*SwitchOrderConfirmationCancellationInstructionV01) AddCopyDetails

func (*SwitchOrderConfirmationCancellationInstructionV01) AddMessageIdentification

func (*SwitchOrderConfirmationCancellationInstructionV01) AddPoolReference

func (*SwitchOrderConfirmationCancellationInstructionV01) AddPreviousReference

func (*SwitchOrderConfirmationCancellationInstructionV01) AddRelatedReference

type SwitchOrderConfirmationCancellationInstructionV02

type SwitchOrderConfirmationCancellationInstructionV02 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 SwitchOrderConfirmationCancellationInstruction 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 SwitchOrderConfirmation. 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 SwitchOrderConfirmation are specified in the order reference and deal reference elements respectively. The message identification of the SwitchOrderConfirmation 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 switch order confirmation cancellation is to be followed by an amendment An amendment of a switch order confirmation is carried out by sending a SwitchOrderConfirmation message in which the AmendmentIndicator contains the value ‘true’.

func (*SwitchOrderConfirmationCancellationInstructionV02) AddCopyDetails

func (*SwitchOrderConfirmationCancellationInstructionV02) AddMessageIdentification

func (*SwitchOrderConfirmationCancellationInstructionV02) AddOrderReferences

func (*SwitchOrderConfirmationCancellationInstructionV02) AddPoolReference

func (*SwitchOrderConfirmationCancellationInstructionV02) AddPreviousReference

func (*SwitchOrderConfirmationCancellationInstructionV02) AddRelatedReference

func (*SwitchOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator

func (s *SwitchOrderConfirmationCancellationInstructionV02) SetAmendmentIndicator(value string)

func (*SwitchOrderConfirmationCancellationInstructionV02) SetMasterReference

func (s *SwitchOrderConfirmationCancellationInstructionV02) SetMasterReference(value string)

type SwitchOrderConfirmationV02

type SwitchOrderConfirmationV02 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"`

	// Information related to a switch execution.
	SwitchExecutionDetails *iso20022.SwitchExecution3 `xml:"SwtchExctnDtls"`

	// Confirmation of 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 SwitchOrderConfirmation message is sent by an executing party, eg, a transfer agent, to an instruction party, eg, an investment manager or its authorised representative. 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 confirm the details of the execution of a SwitchOrder message. Usage The SwitchOrderConfirmation message is sent to confirm that all the legs of the switch have been executed.

func (*SwitchOrderConfirmationV02) AddCopyDetails

func (*SwitchOrderConfirmationV02) AddExtension

func (s *SwitchOrderConfirmationV02) AddExtension() *iso20022.Extension1

func (*SwitchOrderConfirmationV02) AddIntermediaryDetails

func (s *SwitchOrderConfirmationV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (*SwitchOrderConfirmationV02) AddMasterReference

func (s *SwitchOrderConfirmationV02) AddMasterReference() *iso20022.AdditionalReference3

func (*SwitchOrderConfirmationV02) AddPoolReference

func (*SwitchOrderConfirmationV02) AddPreviousReference

func (s *SwitchOrderConfirmationV02) AddPreviousReference() *iso20022.AdditionalReference3

func (*SwitchOrderConfirmationV02) AddRelatedReference

func (s *SwitchOrderConfirmationV02) AddRelatedReference() *iso20022.AdditionalReference3

func (*SwitchOrderConfirmationV02) AddSwitchExecutionDetails

func (s *SwitchOrderConfirmationV02) AddSwitchExecutionDetails() *iso20022.SwitchExecution3

type SwitchOrderConfirmationV03

type SwitchOrderConfirmationV03 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"`

	// Information related to a switch execution.
	SwitchExecutionDetails []*iso20022.SwitchExecution4 `xml:"SwtchExctnDtls"`

	// 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 SwitchOrderConfirmation message to the instructing party, for example, an investment manager or its authorised representative to confirm the details of the execution of a previously received SwitchOrder instruction. Usage The SwitchOrderConfirmation message is used to confirm that all the legs of the previously instructed switch order have been executed. The reference of the switch order confirmation is identified in DealReference. The reference of the original switch order is specified in OrderReference. The message identification of the SwitchOrder message in which the switch order was conveyed may also be quoted in RelatedReference. If the SwitchOrderConfirmation Details sequence is present more than once, then the redemption leg details and subscription leg details sequences may only be present once. If Switch Confirmation Order Details\Investment Account is used, then the Investment Account Details sequences in Subscription Leg Details and Redemption Leg Details are not allowed. If the SwitchOrderConfirmation Details sequence is present more than once, then the redemption leg details and subscription leg details sequences may only be present once. If SwitchOrderConfirmationDetails\InvestmentAccount is used, then the InvestmentAccountDetails sequences in SubscriptionLegDetails and RedemptionLegDetails are not allowed. This functionality is to be used by institutions that set up two accounts per investor, rather than one investment account.

func (*SwitchOrderConfirmationV03) AddCopyDetails

func (*SwitchOrderConfirmationV03) AddExtension

func (s *SwitchOrderConfirmationV03) AddExtension() *iso20022.Extension1

func (*SwitchOrderConfirmationV03) AddMessageIdentification

func (s *SwitchOrderConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderConfirmationV03) AddPoolReference

func (*SwitchOrderConfirmationV03) AddPreviousReference

func (s *SwitchOrderConfirmationV03) AddPreviousReference() *iso20022.AdditionalReference3

func (*SwitchOrderConfirmationV03) AddRelatedReference

func (s *SwitchOrderConfirmationV03) AddRelatedReference() *iso20022.AdditionalReference3

func (*SwitchOrderConfirmationV03) AddSwitchExecutionDetails

func (s *SwitchOrderConfirmationV03) AddSwitchExecutionDetails() *iso20022.SwitchExecution4

type SwitchOrderConfirmationV04

type SwitchOrderConfirmationV04 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"`

	// Information related to a switch execution.
	SwitchExecutionDetails []*iso20022.SwitchExecution7 `xml:"SwtchExctnDtls"`

	// 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 SwitchOrderConfirmation 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 the execution of a previously received SwitchOrder instruction. Usage The SwitchOrderConfirmation message is used to confirm that all the legs of the previously instructed switch order have been executed. The reference of the switch order confirmation is identified in DealReference. The reference of the original switch order is specified in OrderReference. The message identification of the SwitchOrder message in which the switch order was conveyed may also be quoted in RelatedReference but this is not recommended. 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 (*SwitchOrderConfirmationV04) AddCopyDetails

func (*SwitchOrderConfirmationV04) AddExtension

func (s *SwitchOrderConfirmationV04) AddExtension() *iso20022.Extension1

func (*SwitchOrderConfirmationV04) AddMessageIdentification

func (s *SwitchOrderConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderConfirmationV04) AddPoolReference

func (*SwitchOrderConfirmationV04) AddPreviousReference

func (s *SwitchOrderConfirmationV04) AddPreviousReference() *iso20022.AdditionalReference8

func (*SwitchOrderConfirmationV04) AddRelatedReference

func (s *SwitchOrderConfirmationV04) AddRelatedReference() *iso20022.AdditionalReference8

func (*SwitchOrderConfirmationV04) AddSwitchExecutionDetails

func (s *SwitchOrderConfirmationV04) AddSwitchExecutionDetails() *iso20022.SwitchExecution7

type SwitchOrderV02

type SwitchOrderV02 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"`

	// Information related to the switch order
	SwitchOrderDetails *iso20022.SwitchOrder2 `xml:"SwtchOrdrDtls"`

	// 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 SwitchOrder 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 switch from a specified amount/quantity of specified financial instruments to a specified amount/quantity of different financial instruments. Usage The SwitchOrder message is used when the instructing party, ie, an investor, wants to change its investments within the same fund family, according to the terms of the prospectus.

func (*SwitchOrderV02) AddCopyDetails

func (s *SwitchOrderV02) AddCopyDetails() *iso20022.CopyInformation1

func (*SwitchOrderV02) AddExtension

func (s *SwitchOrderV02) AddExtension() *iso20022.Extension1

func (*SwitchOrderV02) AddIntermediaryDetails

func (s *SwitchOrderV02) AddIntermediaryDetails() *iso20022.Intermediary4

func (*SwitchOrderV02) AddMasterReference

func (s *SwitchOrderV02) AddMasterReference() *iso20022.AdditionalReference3

func (*SwitchOrderV02) AddPoolReference

func (s *SwitchOrderV02) AddPoolReference() *iso20022.AdditionalReference3

func (*SwitchOrderV02) AddPreviousReference

func (s *SwitchOrderV02) AddPreviousReference() *iso20022.AdditionalReference3

func (*SwitchOrderV02) AddSwitchOrderDetails

func (s *SwitchOrderV02) AddSwitchOrderDetails() *iso20022.SwitchOrder2

type SwitchOrderV03

type SwitchOrderV03 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"`

	// Pagination of the message.
	MessagePagination *iso20022.Pagination `xml:"MsgPgntn,omitempty"`

	// Information related to the switch order
	SwitchOrderDetails []*iso20022.SwitchOrder4 `xml:"SwtchOrdrDtls"`

	// 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 SwitchOrder message to the executing party, for example, a transfer agent, to instruct a switch transaction from a financial instrument or multiple financial instruments to a different specified financial instrument or instruments for a specified amount/quantity. Usage The SwitchOrder message is used to either: - instruct one switch transaction comprising one or more redemption legs and one or more subscription legs, that is, a single switch transaction that can be a one to one, many to one, many to many or one to many switch transaction, or, - instruct one or many switch transactions each comprising one redemption leg and one subscription leg, that is, multiple simple switch transactions. The SwitchOrder message may be used to either: - instruct a switch transaction for one investment account, or, - instruct a switch transaction for separate accounts at the redemption and subscription leg levels. The message caters for a switch from one financial instrument to another financial instrument (within the same fund family), many to one, many to many and one to many. The message caters for switch transactions that result in an additional cash payment from the investor or a transaction that results in a net payment to the investor. Not all institutions or funds permit this type of switch and acceptance is therefore not automatic. There is no limitation on the number of switch legs in a switch message. The number allowed is defined by the fund prospectus or by the service level agreement (SLA) in place between the two parties. However, if the SwitchOrderDetails sequence is present more than once, then the RedemptionLegDetails and SubscriptionLegDetails sequences may only be present once. If SwitchOrderDetails\InvestmentAccount is used, then the InvestmentAccountDetails sequences in SubscriptionLegDetails and RedemptionLegDetails are not allowed. This functionality is to be used by institutions that set up two accounts per investor, rather than one investment account. There is no switch driver type in the message to indicate whether the switch is buy or sell driven. A driver is not needed since it is possible to indicate the total subscription amount or the total redemption amount. Only one of these two amounts should be used. The subscription quantity can be expressed in one of the following ways: - Amount: the monetary value (either GROSS or NET) of the financial instrument to be subscribed to, eg, the subscription of EUR 1,000 of financial instrument ISIN LU1234567890 or - Unit: the number of units of the financial instrument to be subscribed to, eg, the subscription of 10 units of financial instrument ISIN LU1234567890 or - Percentage of the total redemption amount: when the switch transaction is redemption driven, it is the part of the redemption amount that must be switched to a specific financial instrument, for example, the subscription quantity of financial instrument ISIN LU1234567890 represents 50% of the redemption amount of the financial instrument ISIN LU4444444444. The redemption quantity can be expressed in one of the following ways: - Amount: the monetary value (either GROSS or NET) of the financial instrument to be redeemed, eg, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or - Unit: the number of units of financial instrument to be redeemed, eg, the redemption of 10 units of financial instrument ISIN LU1234567890, or - Rate: the part of the portfolio to be redeemed, eg, the redemption of 10% of the holdings in financial instrument ISIN LU1234567890, or - Percentage of the total subscription amount: when the switch transaction is subscription driven, it is the part of the subscription amount that must be the result of the redemption of a specific financial instrument, for example, the redemption quantity in financial instrument ABC represents 50% of the subscription amount of the financial instrument ISIN LU4444444444

func (*SwitchOrderV03) AddCopyDetails

func (s *SwitchOrderV03) AddCopyDetails() *iso20022.CopyInformation2

func (*SwitchOrderV03) AddExtension

func (s *SwitchOrderV03) AddExtension() *iso20022.Extension1

func (*SwitchOrderV03) AddMessageIdentification

func (s *SwitchOrderV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderV03) AddMessagePagination

func (s *SwitchOrderV03) AddMessagePagination() *iso20022.Pagination

func (*SwitchOrderV03) AddPoolReference

func (s *SwitchOrderV03) AddPoolReference() *iso20022.AdditionalReference3

func (*SwitchOrderV03) AddPreviousReference

func (s *SwitchOrderV03) AddPreviousReference() *iso20022.AdditionalReference3

func (*SwitchOrderV03) AddSwitchOrderDetails

func (s *SwitchOrderV03) AddSwitchOrderDetails() *iso20022.SwitchOrder4

type SwitchOrderV04

type SwitchOrderV04 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"`

	// Pagination of the message.
	MessagePagination *iso20022.Pagination `xml:"MsgPgntn,omitempty"`

	// Information related to the switch order.
	SwitchOrderDetails []*iso20022.SwitchOrder7 `xml:"SwtchOrdrDtls"`

	// 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 SwitchOrder 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 switch transaction from a financial instrument or multiple financial instruments to a different specified financial instrument or instruments for a specified amount/quantity. Usage The SwitchOrder message is used to either: - instruct one switch transaction comprising one or more redemption legs and one or more subscription legs, that is, a single switch transaction that can be a one to one, many to one, many to many or one to many switch transaction, or, - instruct one or many switch transactions each comprising one redemption leg and one subscription leg, that is, multiple simple switch transactions. The SwitchOrder message may be used to either: - instruct a switch transaction for one investment account, or, - instruct a switch transaction for separate accounts at the redemption and subscription leg levels. The message caters for a switch from one financial instrument to another financial instrument (within the same fund family), many to one, many to many and one to many. The message caters for switch transactions that result in an additional cash payment from the investor or a transaction that results in a net payment to the investor. Not all institutions or funds permit this type of switch and acceptance is therefore not automatic. There is no limitation on the number of switch legs in a switch message. The number allowed is defined by the fund prospectus or by the service level agreement (SLA) in place between the two parties. However, if the SwitchOrderDetails sequence is present more than once, then the RedemptionLegDetails and SubscriptionLegDetails sequences may only be present once. If SwitchOrderDetails\InvestmentAccount is used, then the InvestmentAccountDetails sequences in SubscriptionLegDetails and RedemptionLegDetails are not allowed. This functionality is to be used by institutions that set up two accounts per investor, rather than one investment account. There is no switch driver type in the message to indicate whether the switch is buy or sell driven. A driver is not needed since it is possible to indicate the total subscription amount or the total redemption amount. Only one of these two amounts should be used. The subscription quantity can be expressed in one of the following ways: - Amount: the monetary value (either GROSS or NET) of the financial instrument to be subscribed to, for example, the subscription of EUR 1,000 of financial instrument ISIN LU1234567890 or - Unit: the number of units of the financial instrument to be subscribed to, for example, the subscription of 10 units of financial instrument ISIN LU1234567890 or - Percentage of the total redemption amount: when the switch transaction is redemption driven, it is the part of the redemption amount that must be switched to a specific financial instrument, for example, the subscription quantity of financial instrument ISIN LU1234567890 represents 50% of the redemption amount of the financial instrument ISIN LU4444444444. The redemption quantity can be expressed in one of the following ways: - Amount: the monetary value (either GROSS or NET) of the financial instrument to be redeemed, for example, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or - Unit: the number of units of financial instrument to be redeemed, for example, the redemption of 10 units of financial instrument ISIN LU1234567890, or - Rate: the part of the portfolio to be redeemed, for example, the redemption of 10% of the holdings in financial instrument ISIN LU1234567890, or - Percentage of the total subscription amount: when the switch transaction is subscription driven, it is the part of the subscription amount that must be the result of the redemption of a specific financial instrument, for example, the redemption quantity in financial instrument ABC represents 50% of the subscription amount of the financial instrument ISIN LU4444444444

func (*SwitchOrderV04) AddCopyDetails

func (s *SwitchOrderV04) AddCopyDetails() *iso20022.CopyInformation4

func (*SwitchOrderV04) AddExtension

func (s *SwitchOrderV04) AddExtension() *iso20022.Extension1

func (*SwitchOrderV04) AddMessageIdentification

func (s *SwitchOrderV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*SwitchOrderV04) AddMessagePagination

func (s *SwitchOrderV04) AddMessagePagination() *iso20022.Pagination

func (*SwitchOrderV04) AddPoolReference

func (s *SwitchOrderV04) AddPoolReference() *iso20022.AdditionalReference9

func (*SwitchOrderV04) AddPreviousReference

func (s *SwitchOrderV04) AddPreviousReference() *iso20022.AdditionalReference8

func (*SwitchOrderV04) AddSwitchOrderDetails

func (s *SwitchOrderV04) AddSwitchOrderDetails() *iso20022.SwitchOrder7

Source Files

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL