sese

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 AccountHoldingInformationRequestV02 ¶

type AccountHoldingInformationRequestV02 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Identifies the business flow type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer5 `xml:"PdctTrf"`

	// 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, a (new) plan manager (Transferee) sends the AccountHoldingInformationRequest message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to request information about financial instruments held on behalf of the client. Usage The AccountHoldingInformationRequest message is used to request information about one or more ISA or portfolio products held in a client's account for which it intends to instruct a transfer at a later time.

func (*AccountHoldingInformationRequestV02) AddExtension ¶

func (*AccountHoldingInformationRequestV02) AddMessageReference ¶

func (*AccountHoldingInformationRequestV02) AddNomineeAccount ¶

func (a *AccountHoldingInformationRequestV02) AddNomineeAccount() *iso20022.Account6

func (*AccountHoldingInformationRequestV02) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV02) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV02) AddPoolReference ¶

func (*AccountHoldingInformationRequestV02) AddPreviousReference ¶

func (*AccountHoldingInformationRequestV02) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV02) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV02) AddProductTransfer ¶

func (*AccountHoldingInformationRequestV02) AddRelatedReference ¶

func (*AccountHoldingInformationRequestV02) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV02) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV02) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV02) AddTransferee ¶

func (*AccountHoldingInformationRequestV02) AddTransferorAccount ¶

func (a *AccountHoldingInformationRequestV02) AddTransferorAccount() *iso20022.Account5

func (*AccountHoldingInformationRequestV02) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationRequestV02) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationRequestV03 ¶

type AccountHoldingInformationRequestV03 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Identifies the business flow type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer15 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a (new) plan manager (Transferee) sends the AccountHoldingInformationRequest message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to request information about financial instruments held on behalf of the client. Usage The AccountHoldingInformationRequest message is used to request information about one or more ISA or portfolio products held in a client's account for which it intends to instruct a transfer at a later time.

func (*AccountHoldingInformationRequestV03) AddExtension ¶

func (*AccountHoldingInformationRequestV03) AddMarketPracticeVersion ¶

func (*AccountHoldingInformationRequestV03) AddMessageReference ¶

func (*AccountHoldingInformationRequestV03) AddNomineeAccount ¶

func (a *AccountHoldingInformationRequestV03) AddNomineeAccount() *iso20022.Account16

func (*AccountHoldingInformationRequestV03) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV03) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV03) AddPoolReference ¶

func (*AccountHoldingInformationRequestV03) AddPreviousReference ¶

func (*AccountHoldingInformationRequestV03) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV03) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV03) AddProductTransfer ¶

func (*AccountHoldingInformationRequestV03) AddRelatedReference ¶

func (*AccountHoldingInformationRequestV03) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationRequestV03) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV03) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV03) AddTransferee ¶

func (*AccountHoldingInformationRequestV03) AddTransferorAccount ¶

func (a *AccountHoldingInformationRequestV03) AddTransferorAccount() *iso20022.Account15

func (*AccountHoldingInformationRequestV03) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationRequestV03) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationRequestV04 ¶

type AccountHoldingInformationRequestV04 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

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

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

	// Identifies the business flow type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation21 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation21 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation21 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account19 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account19 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification70Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer27 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a (new) plan manager (Transferee) sends the AccountHoldingInformationRequest message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to request information about financial instruments held on behalf of the client. Usage The AccountHoldingInformationRequest message is used to request information about one or more ISA or portfolio products held in a client's account for which it intends to instruct a transfer at a later time.

func (*AccountHoldingInformationRequestV04) AddExtension ¶

func (*AccountHoldingInformationRequestV04) AddMarketPracticeVersion ¶

func (*AccountHoldingInformationRequestV04) AddMessageReference ¶

func (*AccountHoldingInformationRequestV04) AddNomineeAccount ¶

func (a *AccountHoldingInformationRequestV04) AddNomineeAccount() *iso20022.Account19

func (*AccountHoldingInformationRequestV04) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddOtherCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationRequestV04) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV04) AddPoolReference ¶

func (*AccountHoldingInformationRequestV04) AddPreviousReference ¶

func (*AccountHoldingInformationRequestV04) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddPrimaryCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationRequestV04) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV04) AddProductTransfer ¶

func (*AccountHoldingInformationRequestV04) AddRelatedReference ¶

func (*AccountHoldingInformationRequestV04) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddSecondaryCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationRequestV04) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationRequestV04) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationRequestV04) AddTransferee ¶

func (*AccountHoldingInformationRequestV04) AddTransferorAccount ¶

func (a *AccountHoldingInformationRequestV04) AddTransferorAccount() *iso20022.Account19

func (*AccountHoldingInformationRequestV04) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationRequestV04) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationV02 ¶

type AccountHoldingInformationV02 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Identifies the business flow direction type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer4 `xml:"PdctTrf"`

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

Scope An executing party, eg, a (old) plan manager (Transferor), sends the AccountHoldingInformation message to the instructing party, eg, a (new) plan manager (Transferee), to provide information about financial instruments held on behalf of a client. Usage The AccountHoldingInformation message is used to provide information about one or more ISA or portfolio products held in a client's account.

func (*AccountHoldingInformationV02) AddExtension ¶

func (*AccountHoldingInformationV02) AddMessageReference ¶

func (*AccountHoldingInformationV02) AddNomineeAccount ¶

func (a *AccountHoldingInformationV02) AddNomineeAccount() *iso20022.Account6

func (*AccountHoldingInformationV02) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationV02) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV02) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationV02) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV02) AddPoolReference ¶

func (*AccountHoldingInformationV02) AddPreviousReference ¶

func (a *AccountHoldingInformationV02) AddPreviousReference() *iso20022.AdditionalReference3

func (*AccountHoldingInformationV02) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationV02) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV02) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationV02) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV02) AddProductTransfer ¶

func (a *AccountHoldingInformationV02) AddProductTransfer() *iso20022.ISATransfer4

func (*AccountHoldingInformationV02) AddRelatedReference ¶

func (*AccountHoldingInformationV02) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationV02) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV02) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationV02) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV02) AddTransferee ¶

func (*AccountHoldingInformationV02) AddTransferorAccount ¶

func (a *AccountHoldingInformationV02) AddTransferorAccount() *iso20022.Account5

func (*AccountHoldingInformationV02) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationV02) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationV03 ¶

type AccountHoldingInformationV03 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Identifies the business flow direction type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer6 `xml:"PdctTrf"`

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

Scope An executing party, for example, a (old) plan manager (Transferor), sends the AccountHoldingInformation message to the instructing party, for example, a (new) plan manager (Transferee), to provide information about financial instruments held on behalf of a client. Usage The AccountHoldingInformation message is used to provide information about one or more ISA or portfolio products held in a client's account.

func (*AccountHoldingInformationV03) AddExtension ¶

func (*AccountHoldingInformationV03) AddMessageReference ¶

func (*AccountHoldingInformationV03) AddNomineeAccount ¶

func (a *AccountHoldingInformationV03) AddNomineeAccount() *iso20022.Account6

func (*AccountHoldingInformationV03) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationV03) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV03) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationV03) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV03) AddPoolReference ¶

func (*AccountHoldingInformationV03) AddPreviousReference ¶

func (a *AccountHoldingInformationV03) AddPreviousReference() *iso20022.AdditionalReference3

func (*AccountHoldingInformationV03) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationV03) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV03) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationV03) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV03) AddProductTransfer ¶

func (a *AccountHoldingInformationV03) AddProductTransfer() *iso20022.ISATransfer6

func (*AccountHoldingInformationV03) AddRelatedReference ¶

func (*AccountHoldingInformationV03) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationV03) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV03) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationV03) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV03) AddTransferee ¶

func (*AccountHoldingInformationV03) AddTransferorAccount ¶

func (a *AccountHoldingInformationV03) AddTransferorAccount() *iso20022.Account5

func (*AccountHoldingInformationV03) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationV03) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationV04 ¶

type AccountHoldingInformationV04 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Identifies the business flow direction type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer14 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An executing party, for example, a (old) plan manager (Transferor), sends the AccountHoldingInformation message to the instructing party, for example, a (new) plan manager (Transferee), to provide information about financial instruments held on behalf of a client. Usage The AccountHoldingInformation message is used to provide information about one or more ISA or portfolio products held in a client's account.

func (*AccountHoldingInformationV04) AddExtension ¶

func (*AccountHoldingInformationV04) AddMarketPracticeVersion ¶

func (a *AccountHoldingInformationV04) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*AccountHoldingInformationV04) AddMessageReference ¶

func (*AccountHoldingInformationV04) AddNomineeAccount ¶

func (a *AccountHoldingInformationV04) AddNomineeAccount() *iso20022.Account16

func (*AccountHoldingInformationV04) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationV04) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV04) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationV04) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV04) AddPoolReference ¶

func (*AccountHoldingInformationV04) AddPreviousReference ¶

func (a *AccountHoldingInformationV04) AddPreviousReference() *iso20022.AdditionalReference3

func (*AccountHoldingInformationV04) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationV04) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV04) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationV04) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV04) AddProductTransfer ¶

func (a *AccountHoldingInformationV04) AddProductTransfer() *iso20022.ISATransfer14

func (*AccountHoldingInformationV04) AddRelatedReference ¶

func (*AccountHoldingInformationV04) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationV04) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*AccountHoldingInformationV04) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationV04) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV04) AddTransferee ¶

func (*AccountHoldingInformationV04) AddTransferorAccount ¶

func (a *AccountHoldingInformationV04) AddTransferorAccount() *iso20022.Account15

func (*AccountHoldingInformationV04) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationV04) SetBusinessFlowDirectionType(value string)

type AccountHoldingInformationV05 ¶

type AccountHoldingInformationV05 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

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

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

	// Identifies the business flow direction type (assets to be delivered or received).
	BusinessFlowDirectionType *iso20022.BusinessFlowDirectionType1Code `xml:"BizFlowDrctnTp,omitempty"`

	// Information identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation21 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation21 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation21 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account19 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account19 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification70Choice `xml:"Trfee"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer23 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An executing party, for example, a (old) plan manager (Transferor), sends the AccountHoldingInformation message to the instructing party, for example, a (new) plan manager (Transferee), to provide information about financial instruments held on behalf of a client. Usage The AccountHoldingInformation message is used to provide information about one or more ISA or portfolio products held in a client's account.

func (*AccountHoldingInformationV05) AddExtension ¶

func (*AccountHoldingInformationV05) AddMarketPracticeVersion ¶

func (a *AccountHoldingInformationV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*AccountHoldingInformationV05) AddMessageReference ¶

func (*AccountHoldingInformationV05) AddNomineeAccount ¶

func (a *AccountHoldingInformationV05) AddNomineeAccount() *iso20022.Account19

func (*AccountHoldingInformationV05) AddOtherCorporateInvestor ¶

func (a *AccountHoldingInformationV05) AddOtherCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationV05) AddOtherIndividualInvestor ¶

func (a *AccountHoldingInformationV05) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV05) AddPoolReference ¶

func (*AccountHoldingInformationV05) AddPreviousReference ¶

func (a *AccountHoldingInformationV05) AddPreviousReference() *iso20022.AdditionalReference6

func (*AccountHoldingInformationV05) AddPrimaryCorporateInvestor ¶

func (a *AccountHoldingInformationV05) AddPrimaryCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationV05) AddPrimaryIndividualInvestor ¶

func (a *AccountHoldingInformationV05) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV05) AddProductTransfer ¶

func (a *AccountHoldingInformationV05) AddProductTransfer() *iso20022.ISATransfer23

func (*AccountHoldingInformationV05) AddRelatedReference ¶

func (*AccountHoldingInformationV05) AddSecondaryCorporateInvestor ¶

func (a *AccountHoldingInformationV05) AddSecondaryCorporateInvestor() *iso20022.Organisation21

func (*AccountHoldingInformationV05) AddSecondaryIndividualInvestor ¶

func (a *AccountHoldingInformationV05) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*AccountHoldingInformationV05) AddTransferee ¶

func (*AccountHoldingInformationV05) AddTransferorAccount ¶

func (a *AccountHoldingInformationV05) AddTransferorAccount() *iso20022.Account19

func (*AccountHoldingInformationV05) SetBusinessFlowDirectionType ¶

func (a *AccountHoldingInformationV05) SetBusinessFlowDirectionType(value string)

type Document00100101 ¶

type Document00100101 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.01 Document"`
	Message *TransferOutInstruction `xml:"sese.001.001.01"`
}

func (*Document00100101) AddMessage ¶

func (d *Document00100101) AddMessage() *TransferOutInstruction

type Document00100102 ¶

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

func (*Document00100102) AddMessage ¶

type Document00100103 ¶

type Document00100103 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.03 Document"`
	Message *TransferOutInstructionV03 `xml:"TrfOutInstr"`
}

func (*Document00100103) AddMessage ¶

type Document00100104 ¶

type Document00100104 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.04 Document"`
	Message *TransferOutInstructionV04 `xml:"TrfOutInstr"`
}

func (*Document00100104) AddMessage ¶

type Document00100105 ¶

type Document00100105 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.05 Document"`
	Message *TransferOutInstructionV05 `xml:"TrfOutInstr"`
}

func (*Document00100105) AddMessage ¶

type Document00100106 ¶

type Document00100106 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.06 Document"`
	Message *TransferOutInstructionV06 `xml:"TrfOutInstr"`
}

func (*Document00100106) AddMessage ¶

type Document00100107 ¶

type Document00100107 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.001.001.07 Document"`
	Message *TransferOutInstructionV07 `xml:"TrfOutInstr"`
}

func (*Document00100107) AddMessage ¶

type Document00200101 ¶

type Document00200101 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.01 Document"`
	Message *TransferOutCancellationInstruction `xml:"sese.002.001.01"`
}

func (*Document00200101) AddMessage ¶

type Document00200102 ¶

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

func (*Document00200102) AddMessage ¶

type Document00200103 ¶

type Document00200103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.03 Document"`
	Message *TransferOutCancellationRequestV03 `xml:"TrfOutCxlReq"`
}

func (*Document00200103) AddMessage ¶

type Document00200104 ¶

type Document00200104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.04 Document"`
	Message *TransferOutCancellationRequestV04 `xml:"TrfOutCxlReq"`
}

func (*Document00200104) AddMessage ¶

type Document00200105 ¶

type Document00200105 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.05 Document"`
	Message *TransferOutCancellationRequestV05 `xml:"TrfOutCxlReq"`
}

func (*Document00200105) AddMessage ¶

type Document00200106 ¶

type Document00200106 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.06 Document"`
	Message *TransferOutCancellationRequestV06 `xml:"TrfOutCxlReq"`
}

func (*Document00200106) AddMessage ¶

type Document00200107 ¶

type Document00200107 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.002.001.07 Document"`
	Message *TransferOutCancellationRequestV07 `xml:"TrfOutCxlReq"`
}

func (*Document00200107) AddMessage ¶

type Document00300101 ¶

type Document00300101 struct {
	XMLName xml.Name                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.01 Document"`
	Message *TransferOutConfirmation `xml:"sese.003.001.01"`
}

func (*Document00300101) AddMessage ¶

func (d *Document00300101) AddMessage() *TransferOutConfirmation

type Document00300102 ¶

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

func (*Document00300102) AddMessage ¶

type Document00300103 ¶

type Document00300103 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.03 Document"`
	Message *TransferOutConfirmationV03 `xml:"TrfOutConf"`
}

func (*Document00300103) AddMessage ¶

type Document00300104 ¶

type Document00300104 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.04 Document"`
	Message *TransferOutConfirmationV04 `xml:"TrfOutConf"`
}

func (*Document00300104) AddMessage ¶

type Document00300105 ¶

type Document00300105 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.05 Document"`
	Message *TransferOutConfirmationV05 `xml:"TrfOutConf"`
}

func (*Document00300105) AddMessage ¶

type Document00300106 ¶

type Document00300106 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.06 Document"`
	Message *TransferOutConfirmationV06 `xml:"TrfOutConf"`
}

func (*Document00300106) AddMessage ¶

type Document00300107 ¶

type Document00300107 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.003.001.07 Document"`
	Message *TransferOutConfirmationV07 `xml:"TrfOutConf"`
}

func (*Document00300107) AddMessage ¶

type Document00400101 ¶

type Document00400101 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.01 Document"`
	Message *ReversalOfTransferOutConfirmation `xml:"sese.004.001.01"`
}

func (*Document00400101) AddMessage ¶

type Document00400102 ¶

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

func (*Document00400102) AddMessage ¶

type Document00400103 ¶

type Document00400103 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.03 Document"`
	Message *ReversalOfTransferOutConfirmationV03 `xml:"RvslOfTrfOutConf"`
}

func (*Document00400103) AddMessage ¶

type Document00400104 ¶

type Document00400104 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.04 Document"`
	Message *ReversalOfTransferOutConfirmationV04 `xml:"RvslOfTrfOutConf"`
}

func (*Document00400104) AddMessage ¶

type Document00400105 ¶

type Document00400105 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.05 Document"`
	Message *ReversalOfTransferOutConfirmationV05 `xml:"RvslOfTrfOutConf"`
}

func (*Document00400105) AddMessage ¶

type Document00400106 ¶

type Document00400106 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.06 Document"`
	Message *ReversalOfTransferOutConfirmationV06 `xml:"RvslOfTrfOutConf"`
}

func (*Document00400106) AddMessage ¶

type Document00400107 ¶

type Document00400107 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.004.001.07 Document"`
	Message *ReversalOfTransferOutConfirmationV07 `xml:"RvslOfTrfOutConf"`
}

func (*Document00400107) AddMessage ¶

type Document00500101 ¶

type Document00500101 struct {
	XMLName xml.Name               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.01 Document"`
	Message *TransferInInstruction `xml:"sese.005.001.01"`
}

func (*Document00500101) AddMessage ¶

func (d *Document00500101) AddMessage() *TransferInInstruction

type Document00500102 ¶

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

func (*Document00500102) AddMessage ¶

func (d *Document00500102) AddMessage() *TransferInInstructionV02

type Document00500103 ¶

type Document00500103 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.03 Document"`
	Message *TransferInInstructionV03 `xml:"TrfInInstr"`
}

func (*Document00500103) AddMessage ¶

func (d *Document00500103) AddMessage() *TransferInInstructionV03

type Document00500104 ¶

type Document00500104 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.04 Document"`
	Message *TransferInInstructionV04 `xml:"TrfInInstr"`
}

func (*Document00500104) AddMessage ¶

func (d *Document00500104) AddMessage() *TransferInInstructionV04

type Document00500105 ¶

type Document00500105 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.05 Document"`
	Message *TransferInInstructionV05 `xml:"TrfInInstr"`
}

func (*Document00500105) AddMessage ¶

func (d *Document00500105) AddMessage() *TransferInInstructionV05

type Document00500106 ¶

type Document00500106 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.06 Document"`
	Message *TransferInInstructionV06 `xml:"TrfInInstr"`
}

func (*Document00500106) AddMessage ¶

func (d *Document00500106) AddMessage() *TransferInInstructionV06

type Document00500107 ¶

type Document00500107 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.005.001.07 Document"`
	Message *TransferInInstructionV07 `xml:"TrfInInstr"`
}

func (*Document00500107) AddMessage ¶

func (d *Document00500107) AddMessage() *TransferInInstructionV07

type Document00600101 ¶

type Document00600101 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.01 Document"`
	Message *TransferInCancellationInstruction `xml:"sese.006.001.01"`
}

func (*Document00600101) AddMessage ¶

type Document00600102 ¶

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

func (*Document00600102) AddMessage ¶

type Document00600103 ¶

type Document00600103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.03 Document"`
	Message *TransferInCancellationRequestV03 `xml:"TrfInCxlReq"`
}

func (*Document00600103) AddMessage ¶

type Document00600104 ¶

type Document00600104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.04 Document"`
	Message *TransferInCancellationRequestV04 `xml:"TrfInCxlReq"`
}

func (*Document00600104) AddMessage ¶

type Document00600105 ¶

type Document00600105 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.05 Document"`
	Message *TransferInCancellationRequestV05 `xml:"TrfInCxlReq"`
}

func (*Document00600105) AddMessage ¶

type Document00600106 ¶

type Document00600106 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.06 Document"`
	Message *TransferInCancellationRequestV06 `xml:"TrfInCxlReq"`
}

func (*Document00600106) AddMessage ¶

type Document00600107 ¶

type Document00600107 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.006.001.07 Document"`
	Message *TransferInCancellationRequestV07 `xml:"TrfInCxlReq"`
}

func (*Document00600107) AddMessage ¶

type Document00700101 ¶

type Document00700101 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.01 Document"`
	Message *TransferInConfirmation `xml:"sese.007.001.01"`
}

func (*Document00700101) AddMessage ¶

func (d *Document00700101) AddMessage() *TransferInConfirmation

type Document00700102 ¶

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

func (*Document00700102) AddMessage ¶

type Document00700103 ¶

type Document00700103 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.03 Document"`
	Message *TransferInConfirmationV03 `xml:"TrfInConf"`
}

func (*Document00700103) AddMessage ¶

type Document00700104 ¶

type Document00700104 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.04 Document"`
	Message *TransferInConfirmationV04 `xml:"TrfInConf"`
}

func (*Document00700104) AddMessage ¶

type Document00700105 ¶

type Document00700105 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.05 Document"`
	Message *TransferInConfirmationV05 `xml:"TrfInConf"`
}

func (*Document00700105) AddMessage ¶

type Document00700106 ¶

type Document00700106 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.06 Document"`
	Message *TransferInConfirmationV06 `xml:"TrfInConf"`
}

func (*Document00700106) AddMessage ¶

type Document00700107 ¶

type Document00700107 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.007.001.07 Document"`
	Message *TransferInConfirmationV07 `xml:"TrfInConf"`
}

func (*Document00700107) AddMessage ¶

type Document00800101 ¶

type Document00800101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.01 Document"`
	Message *ReversalOfTransferInConfirmation `xml:"sese.008.001.01"`
}

func (*Document00800101) AddMessage ¶

type Document00800102 ¶

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

func (*Document00800102) AddMessage ¶

type Document00800103 ¶

type Document00800103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.03 Document"`
	Message *ReversalOfTransferInConfirmationV03 `xml:"RvslOfTrfInConf"`
}

func (*Document00800103) AddMessage ¶

type Document00800104 ¶

type Document00800104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.04 Document"`
	Message *ReversalOfTransferInConfirmationV04 `xml:"RvslOfTrfInConf"`
}

func (*Document00800104) AddMessage ¶

type Document00800105 ¶

type Document00800105 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.05 Document"`
	Message *ReversalOfTransferInConfirmationV05 `xml:"RvslOfTrfInConf"`
}

func (*Document00800105) AddMessage ¶

type Document00800106 ¶

type Document00800106 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.06 Document"`
	Message *ReversalOfTransferInConfirmationV06 `xml:"RvslOfTrfInConf"`
}

func (*Document00800106) AddMessage ¶

type Document00800107 ¶

type Document00800107 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.008.001.07 Document"`
	Message *ReversalOfTransferInConfirmationV07 `xml:"RvslOfTrfInConf"`
}

func (*Document00800107) AddMessage ¶

type Document00900101 ¶

type Document00900101 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.009.001.01 Document"`
	Message *RequestForTransferStatusReport `xml:"sese.009.001.01"`
}

func (*Document00900101) AddMessage ¶

type Document00900102 ¶

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

func (*Document00900102) AddMessage ¶

type Document00900103 ¶

type Document00900103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.009.001.03 Document"`
	Message *RequestForTransferStatusReportV03 `xml:"ReqForTrfStsRpt"`
}

func (*Document00900103) AddMessage ¶

type Document00900104 ¶

type Document00900104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.009.001.04 Document"`
	Message *RequestForTransferStatusReportV04 `xml:"ReqForTrfStsRpt"`
}

func (*Document00900104) AddMessage ¶

type Document00900105 ¶

type Document00900105 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.009.001.05 Document"`
	Message *RequestForTransferStatusReportV05 `xml:"ReqForTrfStsRpt"`
}

func (*Document00900105) AddMessage ¶

type Document01000101 ¶

type Document01000101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.010.001.01 Document"`
	Message *TransferCancellationStatusReport `xml:"sese.010.001.01"`
}

func (*Document01000101) AddMessage ¶

type Document01000102 ¶

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

func (*Document01000102) AddMessage ¶

type Document01000103 ¶

type Document01000103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.010.001.03 Document"`
	Message *TransferCancellationStatusReportV03 `xml:"TrfCxlStsRpt"`
}

func (*Document01000103) AddMessage ¶

type Document01000104 ¶

type Document01000104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.010.001.04 Document"`
	Message *TransferCancellationStatusReportV04 `xml:"TrfCxlStsRpt"`
}

func (*Document01000104) AddMessage ¶

type Document01000105 ¶

type Document01000105 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.010.001.05 Document"`
	Message *TransferCancellationStatusReportV05 `xml:"TrfCxlStsRpt"`
}

func (*Document01000105) AddMessage ¶

type Document01100101 ¶

type Document01100101 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.011.001.01 Document"`
	Message *TransferInstructionStatusReport `xml:"sese.011.001.01"`
}

func (*Document01100101) AddMessage ¶

type Document01100102 ¶

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

func (*Document01100102) AddMessage ¶

type Document01100103 ¶

type Document01100103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.011.001.03 Document"`
	Message *TransferInstructionStatusReportV03 `xml:"TrfInstrStsRpt"`
}

func (*Document01100103) AddMessage ¶

type Document01100104 ¶

type Document01100104 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.011.001.04 Document"`
	Message *TransferInstructionStatusReportV04 `xml:"TrfInstrStsRpt"`
}

func (*Document01100104) AddMessage ¶

type Document01100105 ¶

type Document01100105 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.011.001.05 Document"`
	Message *TransferInstructionStatusReportV05 `xml:"TrfInstrStsRpt"`
}

func (*Document01100105) AddMessage ¶

type Document01200102 ¶

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

func (*Document01200102) AddMessage ¶

type Document01200103 ¶

type Document01200103 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.012.001.03 Document"`
	Message *PortfolioTransferInstructionV03 `xml:"PrtflTrfInstr"`
}

func (*Document01200103) AddMessage ¶

type Document01200104 ¶

type Document01200104 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.012.001.04 Document"`
	Message *PortfolioTransferInstructionV04 `xml:"PrtflTrfInstr"`
}

func (*Document01200104) AddMessage ¶

type Document01200105 ¶

type Document01200105 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.012.001.05 Document"`
	Message *PortfolioTransferInstructionV05 `xml:"PrtflTrfInstr"`
}

func (*Document01200105) AddMessage ¶

type Document01200106 ¶

type Document01200106 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.012.001.06 Document"`
	Message *PortfolioTransferInstructionV06 `xml:"PrtflTrfInstr"`
}

func (*Document01200106) AddMessage ¶

type Document01200107 ¶

type Document01200107 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.012.001.07 Document"`
	Message *PortfolioTransferInstructionV07 `xml:"PrtflTrfInstr"`
}

func (*Document01200107) AddMessage ¶

type Document01300102 ¶

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

func (*Document01300102) AddMessage ¶

type Document01300103 ¶

type Document01300103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.013.001.03 Document"`
	Message *PortfolioTransferConfirmationV03 `xml:"PrtflTrfConf"`
}

func (*Document01300103) AddMessage ¶

type Document01300104 ¶

type Document01300104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.013.001.04 Document"`
	Message *PortfolioTransferConfirmationV04 `xml:"PrtflTrfConf"`
}

func (*Document01300104) AddMessage ¶

type Document01300105 ¶

type Document01300105 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.013.001.05 Document"`
	Message *PortfolioTransferConfirmationV05 `xml:"PrtflTrfConf"`
}

func (*Document01300105) AddMessage ¶

type Document01300106 ¶

type Document01300106 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.013.001.06 Document"`
	Message *PortfolioTransferConfirmationV06 `xml:"PrtflTrfConf"`
}

func (*Document01300106) AddMessage ¶

type Document01300107 ¶

type Document01300107 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.013.001.07 Document"`
	Message *PortfolioTransferConfirmationV07 `xml:"PrtflTrfConf"`
}

func (*Document01300107) AddMessage ¶

type Document01400102 ¶

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

func (*Document01400102) AddMessage ¶

type Document01400103 ¶

type Document01400103 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.014.001.03 Document"`
	Message *PortfolioTransferCancellationRequestV03 `xml:"PrtflTrfCxlReq"`
}

func (*Document01400103) AddMessage ¶

type Document01400104 ¶

type Document01400104 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.014.001.04 Document"`
	Message *PortfolioTransferCancellationRequestV04 `xml:"PrtflTrfCxlReq"`
}

func (*Document01400104) AddMessage ¶

type Document01400105 ¶

type Document01400105 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.014.001.05 Document"`
	Message *PortfolioTransferCancellationRequestV05 `xml:"PrtflTrfCxlReq"`
}

func (*Document01400105) AddMessage ¶

type Document01400106 ¶

type Document01400106 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.014.001.06 Document"`
	Message *PortfolioTransferCancellationRequestV06 `xml:"PrtflTrfCxlReq"`
}

func (*Document01400106) AddMessage ¶

type Document01400107 ¶

type Document01400107 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.014.001.07 Document"`
	Message *PortfolioTransferCancellationRequestV07 `xml:"PrtflTrfCxlReq"`
}

func (*Document01400107) AddMessage ¶

type Document01800101 ¶

type Document01800101 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.018.001.01 Document"`
	Message *PEPOrISAOrPortfolioInformationV01 `xml:"PEPOrISAOrPrtflInfV01"`
}

func (*Document01800101) AddMessage ¶

type Document01800102 ¶

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

func (*Document01800102) AddMessage ¶

type Document01800103 ¶

type Document01800103 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:sese.018.001.03 Document"`
	Message *AccountHoldingInformationV03 `xml:"AcctHldgInf"`
}

func (*Document01800103) AddMessage ¶

type Document01800104 ¶

type Document01800104 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:sese.018.001.04 Document"`
	Message *AccountHoldingInformationV04 `xml:"AcctHldgInf"`
}

func (*Document01800104) AddMessage ¶

type Document01800105 ¶

type Document01800105 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:sese.018.001.05 Document"`
	Message *AccountHoldingInformationV05 `xml:"AcctHldgInf"`
}

func (*Document01800105) AddMessage ¶

type Document01900101 ¶

type Document01900101 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.019.001.01 Document"`
	Message *RequestForPEPOrISAOrPortfolioInformationV01 `xml:"ReqForPEPOrISAOrPrtflInfV01"`
}

func (*Document01900101) AddMessage ¶

type Document01900102 ¶

type Document01900102 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.019.001.02 Document"`
	Message *AccountHoldingInformationRequestV02 `xml:"AcctHldgInfReq"`
}

func (*Document01900102) AddMessage ¶

type Document01900103 ¶

type Document01900103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.019.001.03 Document"`
	Message *AccountHoldingInformationRequestV03 `xml:"AcctHldgInfReq"`
}

func (*Document01900103) AddMessage ¶

type Document01900104 ¶

type Document01900104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.019.001.04 Document"`
	Message *AccountHoldingInformationRequestV04 `xml:"AcctHldgInfReq"`
}

func (*Document01900104) AddMessage ¶

type Document02000101 ¶

type Document02000101 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.001.01 Document"`
	Message *SecuritiesTransactionCancellationRequestV01 `xml:"SctiesTxCxlReq"`
}

func (*Document02000101) AddMessage ¶

type Document02000102 ¶

type Document02000102 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.001.02 Document"`
	Message *SecuritiesTransactionCancellationRequestV02 `xml:"SctiesTxCxlReq"`
}

func (*Document02000102) AddMessage ¶

type Document02000103 ¶

type Document02000103 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.001.03 Document"`
	Message *SecuritiesTransactionCancellationRequestV03 `xml:"SctiesTxCxlReq"`
}

func (*Document02000103) AddMessage ¶

type Document02000104 ¶

type Document02000104 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.001.04 Document"`
	Message *SecuritiesTransactionCancellationRequestV04 `xml:"SctiesTxCxlReq"`
}

func (*Document02000104) AddMessage ¶

type Document02000105 ¶

type Document02000105 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.001.05 Document"`
	Message *SecuritiesTransactionCancellationRequestV05 `xml:"SctiesTxCxlReq"`
}

func (*Document02000105) AddMessage ¶

type Document02000205 ¶

type Document02000205 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.020.002.05 Document"`
	Message *SecuritiesTransactionCancellationRequest002V05 `xml:"SctiesTxCxlReq"`
}

func (*Document02000205) AddMessage ¶

type Document02100101 ¶

type Document02100101 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.021.001.01 Document"`
	Message *SecuritiesTransactionStatusQueryV01 `xml:"SctiesTxStsQry"`
}

func (*Document02100101) AddMessage ¶

type Document02100102 ¶

type Document02100102 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.021.001.02 Document"`
	Message *SecuritiesTransactionStatusQueryV02 `xml:"SctiesTxStsQry"`
}

func (*Document02100102) AddMessage ¶

type Document02100103 ¶

type Document02100103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.021.001.03 Document"`
	Message *SecuritiesTransactionStatusQueryV03 `xml:"SctiesTxStsQry"`
}

func (*Document02100103) AddMessage ¶

type Document02100104 ¶

type Document02100104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.021.001.04 Document"`
	Message *SecuritiesTransactionStatusQueryV04 `xml:"SctiesTxStsQry"`
}

func (*Document02100104) AddMessage ¶

type Document02100204 ¶

type Document02100204 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:sese.021.002.04 Document"`
	Message *SecuritiesTransactionStatusQuery002V04 `xml:"SctiesTxStsQry"`
}

func (*Document02100204) AddMessage ¶

type Document02200101 ¶

type Document02200101 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.022.001.01 Document"`
	Message *SecuritiesStatusOrStatementQueryStatusAdviceV01 `xml:"SctiesStsOrStmtQryStsAdvc"`
}

func (*Document02200101) AddMessage ¶

type Document02200102 ¶

type Document02200102 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.022.001.02 Document"`
	Message *SecuritiesStatusOrStatementQueryStatusAdviceV02 `xml:"SctiesStsOrStmtQryStsAdvc"`
}

func (*Document02200102) AddMessage ¶

type Document02200103 ¶

type Document02200103 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.022.001.03 Document"`
	Message *SecuritiesStatusOrStatementQueryStatusAdviceV03 `xml:"SctiesStsOrStmtQryStsAdvc"`
}

func (*Document02200103) AddMessage ¶

type Document02200104 ¶

type Document02200104 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:sese.022.001.04 Document"`
	Message *SecuritiesStatusOrStatementQueryStatusAdviceV04 `xml:"SctiesStsOrStmtQryStsAdvc"`
}

func (*Document02200104) AddMessage ¶

type Document02200204 ¶

type Document02200204 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.022.002.04 Document"`
	Message *SecuritiesStatusOrStatementQueryStatusAdvice002V04 `xml:"SctiesStsOrStmtQryStsAdvc"`
}

func (*Document02200204) AddMessage ¶

type Document02300101 ¶

type Document02300101 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.01 Document"`
	Message *SecuritiesSettlementTransactionInstructionV01 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300101) AddMessage ¶

type Document02300102 ¶

type Document02300102 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.02 Document"`
	Message *SecuritiesSettlementTransactionInstructionV02 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300102) AddMessage ¶

type Document02300103 ¶

type Document02300103 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.03 Document"`
	Message *SecuritiesSettlementTransactionInstructionV03 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300103) AddMessage ¶

type Document02300104 ¶

type Document02300104 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.04 Document"`
	Message *SecuritiesSettlementTransactionInstructionV04 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300104) AddMessage ¶

type Document02300105 ¶

type Document02300105 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.05 Document"`
	Message *SecuritiesSettlementTransactionInstructionV05 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300105) AddMessage ¶

type Document02300106 ¶

type Document02300106 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.06 Document"`
	Message *SecuritiesSettlementTransactionInstructionV06 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300106) AddMessage ¶

type Document02300107 ¶

type Document02300107 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.001.07 Document"`
	Message *SecuritiesSettlementTransactionInstructionV07 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300107) AddMessage ¶

type Document02300206 ¶

type Document02300206 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.002.06 Document"`
	Message *SecuritiesSettlementTransactionInstruction002V06 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300206) AddMessage ¶

type Document02300207 ¶

type Document02300207 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.023.002.07 Document"`
	Message *SecuritiesSettlementTransactionInstruction002V07 `xml:"SctiesSttlmTxInstr"`
}

func (*Document02300207) AddMessage ¶

type Document02400101 ¶

type Document02400101 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.01 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV01 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400101) AddMessage ¶

type Document02400102 ¶

type Document02400102 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.02 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV02 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400102) AddMessage ¶

type Document02400103 ¶

type Document02400103 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.03 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV03 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400103) AddMessage ¶

type Document02400104 ¶

type Document02400104 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.04 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV04 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400104) AddMessage ¶

type Document02400105 ¶

type Document02400105 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.05 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV05 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400105) AddMessage ¶

type Document02400106 ¶

type Document02400106 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.06 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV06 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400106) AddMessage ¶

type Document02400107 ¶

type Document02400107 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.07 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV07 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400107) AddMessage ¶

type Document02400108 ¶

type Document02400108 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.001.08 Document"`
	Message *SecuritiesSettlementTransactionStatusAdviceV08 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400108) AddMessage ¶

type Document02400207 ¶

type Document02400207 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.002.07 Document"`
	Message *SecuritiesSettlementTransactionStatusAdvice002V07 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400207) AddMessage ¶

type Document02400208 ¶

type Document02400208 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.024.002.08 Document"`
	Message *SecuritiesSettlementTransactionStatusAdvice002V08 `xml:"SctiesSttlmTxStsAdvc"`
}

func (*Document02400208) AddMessage ¶

type Document02500101 ¶

type Document02500101 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.01 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV01 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500101) AddMessage ¶

type Document02500102 ¶

type Document02500102 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.02 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV02 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500102) AddMessage ¶

type Document02500103 ¶

type Document02500103 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.03 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV03 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500103) AddMessage ¶

type Document02500104 ¶

type Document02500104 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.04 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV04 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500104) AddMessage ¶

type Document02500105 ¶

type Document02500105 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.05 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV05 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500105) AddMessage ¶

type Document02500106 ¶

type Document02500106 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.06 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV06 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500106) AddMessage ¶

type Document02500107 ¶

type Document02500107 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.001.07 Document"`
	Message *SecuritiesSettlementTransactionConfirmationV07 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500107) AddMessage ¶

type Document02500206 ¶

type Document02500206 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.002.06 Document"`
	Message *SecuritiesSettlementTransactionConfirmation002V06 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500206) AddMessage ¶

type Document02500207 ¶

type Document02500207 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.025.002.07 Document"`
	Message *SecuritiesSettlementTransactionConfirmation002V07 `xml:"SctiesSttlmTxConf"`
}

func (*Document02500207) AddMessage ¶

type Document02600101 ¶

type Document02600101 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.01 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV01 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600101) AddMessage ¶

type Document02600102 ¶

type Document02600102 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.02 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV02 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600102) AddMessage ¶

type Document02600103 ¶

type Document02600103 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.03 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV03 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600103) AddMessage ¶

type Document02600104 ¶

type Document02600104 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.04 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV04 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600104) AddMessage ¶

type Document02600105 ¶

type Document02600105 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.05 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV05 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600105) AddMessage ¶

type Document02600106 ¶

type Document02600106 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.001.06 Document"`
	Message *SecuritiesSettlementTransactionReversalAdviceV06 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600106) AddMessage ¶

type Document02600205 ¶

type Document02600205 struct {
	XMLName xml.Name                                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.002.05 Document"`
	Message *SecuritiesSettlementTransactionReversalAdvice002V05 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600205) AddMessage ¶

type Document02600206 ¶

type Document02600206 struct {
	XMLName xml.Name                                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.026.002.06 Document"`
	Message *SecuritiesSettlementTransactionReversalAdvice002V06 `xml:"SctiesSttlmTxRvslAdvc"`
}

func (*Document02600206) AddMessage ¶

type Document02700101 ¶

type Document02700101 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.001.01 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdviceV01 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02700102 ¶

type Document02700102 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.001.02 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdviceV02 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02700103 ¶

type Document02700103 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.001.03 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdviceV03 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02700104 ¶

type Document02700104 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.001.04 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdviceV04 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02700105 ¶

type Document02700105 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.001.05 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdviceV05 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02700205 ¶

type Document02700205 struct {
	XMLName xml.Name                                                    `xml:"urn:iso:std:iso:20022:tech:xsd:sese.027.002.05 Document"`
	Message *SecuritiesTransactionCancellationRequestStatusAdvice002V05 `xml:"SctiesTxCxlReqStsAdvc"`
}

type Document02800101 ¶

type Document02800101 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.01 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV01 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800102 ¶

type Document02800102 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.02 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV02 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800103 ¶

type Document02800103 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.03 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV03 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800104 ¶

type Document02800104 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.04 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV04 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800105 ¶

type Document02800105 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.05 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV05 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800106 ¶

type Document02800106 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.001.06 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotificationV06 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800205 ¶

type Document02800205 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.002.05 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotification002V05 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02800206 ¶

type Document02800206 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.028.002.06 Document"`
	Message *SecuritiesSettlementTransactionAllegementNotification002V06 `xml:"SctiesSttlmTxAllgmtNtfctn"`
}

type Document02900101 ¶

type Document02900101 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.029.001.01 Document"`
	Message *SecuritiesSettlementAllegementRemovalAdviceV01 `xml:"SctiesSttlmAllgmtRmvlAdvc"`
}

func (*Document02900101) AddMessage ¶

type Document02900102 ¶

type Document02900102 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.029.001.02 Document"`
	Message *SecuritiesSettlementAllegementRemovalAdviceV02 `xml:"SctiesSttlmAllgmtRmvlAdvc"`
}

func (*Document02900102) AddMessage ¶

type Document02900103 ¶

type Document02900103 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.029.001.03 Document"`
	Message *SecuritiesSettlementAllegementRemovalAdviceV03 `xml:"SctiesSttlmAllgmtRmvlAdvc"`
}

func (*Document02900103) AddMessage ¶

type Document02900104 ¶

type Document02900104 struct {
	XMLName xml.Name                                        `xml:"urn:iso:std:iso:20022:tech:xsd:sese.029.001.04 Document"`
	Message *SecuritiesSettlementAllegementRemovalAdviceV04 `xml:"SctiesSttlmAllgmtRmvlAdvc"`
}

func (*Document02900104) AddMessage ¶

type Document02900204 ¶

type Document02900204 struct {
	XMLName xml.Name                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.029.002.04 Document"`
	Message *SecuritiesSettlementAllegementRemovalAdvice002V04 `xml:"SctiesSttlmAllgmtRmvlAdvc"`
}

func (*Document02900204) AddMessage ¶

type Document03000101 ¶

type Document03000101 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.01 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV01 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000102 ¶

type Document03000102 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.02 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV02 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000103 ¶

type Document03000103 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.03 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV03 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000104 ¶

type Document03000104 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.04 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV04 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000105 ¶

type Document03000105 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.05 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV05 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000106 ¶

type Document03000106 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.06 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV06 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000107 ¶

type Document03000107 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.001.07 Document"`
	Message *SecuritiesSettlementConditionsModificationRequestV07 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000206 ¶

type Document03000206 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.002.06 Document"`
	Message *SecuritiesSettlementConditionsModificationRequest002V06 `xml:"SctiesSttlmCondsModReq"`
}

type Document03000207 ¶

type Document03000207 struct {
	XMLName xml.Name                                                 `xml:"urn:iso:std:iso:20022:tech:xsd:sese.030.002.07 Document"`
	Message *SecuritiesSettlementConditionsModificationRequest002V07 `xml:"SctiesSttlmCondsModReq"`
}

type Document03100101 ¶

type Document03100101 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.01 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV01 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100102 ¶

type Document03100102 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.02 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV02 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100103 ¶

type Document03100103 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.03 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV03 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100104 ¶

type Document03100104 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.04 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV04 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100105 ¶

type Document03100105 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.05 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV05 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100106 ¶

type Document03100106 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.06 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV06 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100107 ¶

type Document03100107 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.001.07 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdviceV07 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03100207 ¶

type Document03100207 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.031.002.07 Document"`
	Message *SecuritiesSettlementConditionModificationStatusAdvice002V07 `xml:"SctiesSttlmCondModStsAdvc"`
}

type Document03200101 ¶

type Document03200101 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.01 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV01 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200102 ¶

type Document03200102 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.02 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV02 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200103 ¶

type Document03200103 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.03 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV03 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200104 ¶

type Document03200104 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.04 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV04 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200105 ¶

type Document03200105 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.05 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV05 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200106 ¶

type Document03200106 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.06 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV06 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200107 ¶

type Document03200107 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.001.07 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotificationV07 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200206 ¶

type Document03200206 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.002.06 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotification002V06 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03200207 ¶

type Document03200207 struct {
	XMLName xml.Name                                                     `xml:"urn:iso:std:iso:20022:tech:xsd:sese.032.002.07 Document"`
	Message *SecuritiesSettlementTransactionGenerationNotification002V07 `xml:"SctiesSttlmTxGnrtnNtfctn"`
}

type Document03300101 ¶

type Document03300101 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.01 Document"`
	Message *SecuritiesFinancingInstructionV01 `xml:"SctiesFincgInstr"`
}

func (*Document03300101) AddMessage ¶

type Document03300102 ¶

type Document03300102 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.02 Document"`
	Message *SecuritiesFinancingInstructionV02 `xml:"SctiesFincgInstr"`
}

func (*Document03300102) AddMessage ¶

type Document03300103 ¶

type Document03300103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.03 Document"`
	Message *SecuritiesFinancingInstructionV03 `xml:"SctiesFincgInstr"`
}

func (*Document03300103) AddMessage ¶

type Document03300104 ¶

type Document03300104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.04 Document"`
	Message *SecuritiesFinancingInstructionV04 `xml:"SctiesFincgInstr"`
}

func (*Document03300104) AddMessage ¶

type Document03300105 ¶

type Document03300105 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.05 Document"`
	Message *SecuritiesFinancingInstructionV05 `xml:"SctiesFincgInstr"`
}

func (*Document03300105) AddMessage ¶

type Document03300106 ¶

type Document03300106 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.06 Document"`
	Message *SecuritiesFinancingInstructionV06 `xml:"SctiesFincgInstr"`
}

func (*Document03300106) AddMessage ¶

type Document03300107 ¶

type Document03300107 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.001.07 Document"`
	Message *SecuritiesFinancingInstructionV07 `xml:"SctiesFincgInstr"`
}

func (*Document03300107) AddMessage ¶

type Document03300206 ¶

type Document03300206 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.002.06 Document"`
	Message *SecuritiesFinancingInstruction002V06 `xml:"SctiesFincgInstr"`
}

func (*Document03300206) AddMessage ¶

type Document03300207 ¶

type Document03300207 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.033.002.07 Document"`
	Message *SecuritiesFinancingInstruction002V07 `xml:"SctiesFincgInstr"`
}

func (*Document03300207) AddMessage ¶

type Document03400101 ¶

type Document03400101 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.01 Document"`
	Message *SecuritiesFinancingStatusAdviceV01 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400101) AddMessage ¶

type Document03400102 ¶

type Document03400102 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.02 Document"`
	Message *SecuritiesFinancingStatusAdviceV02 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400102) AddMessage ¶

type Document03400103 ¶

type Document03400103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.03 Document"`
	Message *SecuritiesFinancingStatusAdviceV03 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400103) AddMessage ¶

type Document03400104 ¶

type Document03400104 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.04 Document"`
	Message *SecuritiesFinancingStatusAdviceV04 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400104) AddMessage ¶

type Document03400105 ¶

type Document03400105 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.05 Document"`
	Message *SecuritiesFinancingStatusAdviceV05 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400105) AddMessage ¶

type Document03400106 ¶

type Document03400106 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.06 Document"`
	Message *SecuritiesFinancingStatusAdviceV06 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400106) AddMessage ¶

type Document03400107 ¶

type Document03400107 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.001.07 Document"`
	Message *SecuritiesFinancingStatusAdviceV07 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400107) AddMessage ¶

type Document03400206 ¶

type Document03400206 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.002.06 Document"`
	Message *SecuritiesFinancingStatusAdvice002V06 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400206) AddMessage ¶

type Document03400207 ¶

type Document03400207 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.034.002.07 Document"`
	Message *SecuritiesFinancingStatusAdvice002V07 `xml:"SctiesFincgStsAdvc"`
}

func (*Document03400207) AddMessage ¶

type Document03500101 ¶

type Document03500101 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.01 Document"`
	Message *SecuritiesFinancingConfirmationV01 `xml:"SctiesFincgConf"`
}

func (*Document03500101) AddMessage ¶

type Document03500102 ¶

type Document03500102 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.02 Document"`
	Message *SecuritiesFinancingConfirmationV02 `xml:"SctiesFincgConf"`
}

func (*Document03500102) AddMessage ¶

type Document03500103 ¶

type Document03500103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.03 Document"`
	Message *SecuritiesFinancingConfirmationV03 `xml:"SctiesFincgConf"`
}

func (*Document03500103) AddMessage ¶

type Document03500104 ¶

type Document03500104 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.04 Document"`
	Message *SecuritiesFinancingConfirmationV04 `xml:"SctiesFincgConf"`
}

func (*Document03500104) AddMessage ¶

type Document03500105 ¶

type Document03500105 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.05 Document"`
	Message *SecuritiesFinancingConfirmationV05 `xml:"SctiesFincgConf"`
}

func (*Document03500105) AddMessage ¶

type Document03500106 ¶

type Document03500106 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.06 Document"`
	Message *SecuritiesFinancingConfirmationV06 `xml:"SctiesFincgConf"`
}

func (*Document03500106) AddMessage ¶

type Document03500107 ¶

type Document03500107 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.001.07 Document"`
	Message *SecuritiesFinancingConfirmationV07 `xml:"SctiesFincgConf"`
}

func (*Document03500107) AddMessage ¶

type Document03500206 ¶

type Document03500206 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.002.06 Document"`
	Message *SecuritiesFinancingConfirmation002V06 `xml:"SctiesFincgConf"`
}

func (*Document03500206) AddMessage ¶

type Document03500207 ¶

type Document03500207 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.035.002.07 Document"`
	Message *SecuritiesFinancingConfirmation002V07 `xml:"SctiesFincgConf"`
}

func (*Document03500207) AddMessage ¶

type Document03600101 ¶

type Document03600101 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.01 Document"`
	Message *SecuritiesFinancingModificationInstructionV01 `xml:"SctiesFincgModInstr"`
}

func (*Document03600101) AddMessage ¶

type Document03600102 ¶

type Document03600102 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.02 Document"`
	Message *SecuritiesFinancingModificationInstructionV02 `xml:"SctiesFincgModInstr"`
}

func (*Document03600102) AddMessage ¶

type Document03600103 ¶

type Document03600103 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.03 Document"`
	Message *SecuritiesFinancingModificationInstructionV03 `xml:"SctiesFincgModInstr"`
}

func (*Document03600103) AddMessage ¶

type Document03600104 ¶

type Document03600104 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.04 Document"`
	Message *SecuritiesFinancingModificationInstructionV04 `xml:"SctiesFincgModInstr"`
}

func (*Document03600104) AddMessage ¶

type Document03600105 ¶

type Document03600105 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.05 Document"`
	Message *SecuritiesFinancingModificationInstructionV05 `xml:"SctiesFincgModInstr"`
}

func (*Document03600105) AddMessage ¶

type Document03600106 ¶

type Document03600106 struct {
	XMLName xml.Name                                       `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.001.06 Document"`
	Message *SecuritiesFinancingModificationInstructionV06 `xml:"SctiesFincgModInstr"`
}

func (*Document03600106) AddMessage ¶

type Document03600205 ¶

type Document03600205 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.002.05 Document"`
	Message *SecuritiesFinancingModificationInstruction002V05 `xml:"SctiesFincgModInstr"`
}

func (*Document03600205) AddMessage ¶

type Document03600206 ¶

type Document03600206 struct {
	XMLName xml.Name                                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.036.002.06 Document"`
	Message *SecuritiesFinancingModificationInstruction002V06 `xml:"SctiesFincgModInstr"`
}

func (*Document03600206) AddMessage ¶

type Document03700101 ¶

type Document03700101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.037.001.01 Document"`
	Message *PortfolioTransferNotificationV01 `xml:"PrtflTrfNtfctn"`
}

func (*Document03700101) AddMessage ¶

type Document03700102 ¶

type Document03700102 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.037.001.02 Document"`
	Message *PortfolioTransferNotificationV02 `xml:"PrtflTrfNtfctn"`
}

func (*Document03700102) AddMessage ¶

type Document03700103 ¶

type Document03700103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.037.001.03 Document"`
	Message *PortfolioTransferNotificationV03 `xml:"PrtflTrfNtfctn"`
}

func (*Document03700103) AddMessage ¶

type Document03700104 ¶

type Document03700104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:sese.037.001.04 Document"`
	Message *PortfolioTransferNotificationV04 `xml:"PrtflTrfNtfctn"`
}

func (*Document03700104) AddMessage ¶

type Document03700204 ¶

type Document03700204 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:sese.037.002.04 Document"`
	Message *PortfolioTransferNotification002V04 `xml:"PrtflTrfNtfctn"`
}

func (*Document03700204) AddMessage ¶

type Document03800101 ¶

type Document03800101 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.001.01 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestV01 `xml:"SctiesSttlmTxModReq"`
}

type Document03800102 ¶

type Document03800102 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.001.02 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestV02 `xml:"SctiesSttlmTxModReq"`
}

type Document03800103 ¶

type Document03800103 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.001.03 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestV03 `xml:"SctiesSttlmTxModReq"`
}

type Document03800104 ¶

type Document03800104 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.001.04 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestV04 `xml:"SctiesSttlmTxModReq"`
}

type Document03800105 ¶

type Document03800105 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.001.05 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestV05 `xml:"SctiesSttlmTxModReq"`
}

type Document03800204 ¶

type Document03800204 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.002.04 Document"`
	Message *SecuritiesSettlementTransactionModificationRequest002V04 `xml:"SctiesSttlmTxModReq"`
}

type Document03800205 ¶

type Document03800205 struct {
	XMLName xml.Name                                                  `xml:"urn:iso:std:iso:20022:tech:xsd:sese.038.002.05 Document"`
	Message *SecuritiesSettlementTransactionModificationRequest002V05 `xml:"SctiesSttlmTxModReq"`
}

type Document03900101 ¶

type Document03900101 struct {
	XMLName xml.Name                                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.039.001.01 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestStatusAdviceV01 `xml:"SctiesSttlmTxModReqStsAdvc"`
}

type Document03900102 ¶

type Document03900102 struct {
	XMLName xml.Name                                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.039.001.02 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestStatusAdviceV02 `xml:"SctiesSttlmTxModReqStsAdvc"`
}

type Document03900103 ¶

type Document03900103 struct {
	XMLName xml.Name                                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.039.001.03 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestStatusAdviceV03 `xml:"SctiesSttlmTxModReqStsAdvc"`
}

type Document03900104 ¶

type Document03900104 struct {
	XMLName xml.Name                                                           `xml:"urn:iso:std:iso:20022:tech:xsd:sese.039.001.04 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestStatusAdviceV04 `xml:"SctiesSttlmTxModReqStsAdvc"`
}

type Document03900204 ¶

type Document03900204 struct {
	XMLName xml.Name                                                              `xml:"urn:iso:std:iso:20022:tech:xsd:sese.039.002.04 Document"`
	Message *SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 `xml:"SctiesSttlmTxModReqStsAdvc"`
}

type Document04000101 ¶

type Document04000101 struct {
	XMLName xml.Name                                                `xml:"urn:iso:std:iso:20022:tech:xsd:sese.040.001.01 Document"`
	Message *SecuritiesSettlementTransactionCounterpartyResponseV01 `xml:"SctiesSttlmTxCtrPtyRspn"`
}

type Document04000102 ¶

type Document04000102 struct {
	XMLName xml.Name                                                `xml:"urn:iso:std:iso:20022:tech:xsd:sese.040.001.02 Document"`
	Message *SecuritiesSettlementTransactionCounterpartyResponseV02 `xml:"SctiesSttlmTxCtrPtyRspn"`
}

type Document04000202 ¶

type Document04000202 struct {
	XMLName xml.Name                                                   `xml:"urn:iso:std:iso:20022:tech:xsd:sese.040.002.02 Document"`
	Message *SecuritiesSettlementTransactionCounterpartyResponse002V02 `xml:"SctiesSttlmTxCtrPtyRspn"`
}

type PEPOrISAOrPortfolioInformationV01 ¶

type PEPOrISAOrPortfolioInformationV01 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	ClientAccount *iso20022.Account5 `xml:"ClntAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	NewPlanManager *iso20022.PartyIdentification2Choice `xml:"NewPlanMgr"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.PEPISATransfer6 `xml:"PdctTrf"`

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

Scope An executing party, eg, a (old) plan manager, sends the PEPOrISAOrPortfolioInformation message to the instructing party, eg, a (new) plan manager, to provide information about financial instruments held on behalf of a client. Usage The PEPOrISAOrPortfolioInformation message is used to provide information about one or more PEP or ISA or portfolio products held in a client's account.

func (*PEPOrISAOrPortfolioInformationV01) AddClientAccount ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddClientAccount() *iso20022.Account5

func (*PEPOrISAOrPortfolioInformationV01) AddExtension ¶

func (*PEPOrISAOrPortfolioInformationV01) AddMessageReference ¶

func (*PEPOrISAOrPortfolioInformationV01) AddNewPlanManager ¶

func (*PEPOrISAOrPortfolioInformationV01) AddNomineeAccount ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddNomineeAccount() *iso20022.Account6

func (*PEPOrISAOrPortfolioInformationV01) AddOtherCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioInformationV01) AddOtherIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PEPOrISAOrPortfolioInformationV01) AddPoolReference ¶

func (*PEPOrISAOrPortfolioInformationV01) AddPreviousReference ¶

func (*PEPOrISAOrPortfolioInformationV01) AddPrimaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioInformationV01) AddPrimaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PEPOrISAOrPortfolioInformationV01) AddProductTransfer ¶

func (*PEPOrISAOrPortfolioInformationV01) AddRelatedReference ¶

func (*PEPOrISAOrPortfolioInformationV01) AddSecondaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioInformationV01) AddSecondaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioInformationV01) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

type PEPOrISAOrPortfolioTransferCancellationRequestV02 ¶

type PEPOrISAOrPortfolioTransferCancellationRequestV02 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 the transfer instruction to be cancelled.
	CancellationByTransferInstructionDetails *iso20022.PEPISATransfer7 `xml:"CxlByTrfInstrDtls,omitempty"`

	// Reference of the transfer instruction to be cancelled.
	CancellationByReference *iso20022.TransferReference3 `xml:"CxlByRef,omitempty"`
}

Scope An instructing party, eg, a (new) plan manager, sends the PEPOrISAOrPortfolioTransferCancellationRequest message to the executing party, eg, a (old) plan manager, to request the cancellation of a previously sent PEPOrISAOrPortfolioTransferInstruction. Usage The PEPOrISAOrPortfolioTransferCancellationRequest message is used to request the cancellation of an entire PEPOrISAOrPortfolioTransferInstruction message, ie, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PEPOrISAOrPortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PEPOrISAOrPortfolioTransferInstruction message. The message identification of the PEPOrISAOrPortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PEPOrISAOrPortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddCancellationByReference ¶

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddCancellationByTransferInstructionDetails ¶

func (p *PEPOrISAOrPortfolioTransferCancellationRequestV02) AddCancellationByTransferInstructionDetails() *iso20022.PEPISATransfer7

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddMessageReference ¶

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddPoolReference ¶

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddPreviousReference ¶

func (*PEPOrISAOrPortfolioTransferCancellationRequestV02) AddRelatedReference ¶

type PEPOrISAOrPortfolioTransferConfirmationV02 ¶

type PEPOrISAOrPortfolioTransferConfirmationV02 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	ClientAccount *iso20022.Account5 `xml:"ClntAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	NewPlanManager *iso20022.PartyIdentification2Choice `xml:"NewPlanMgr"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.PEPISATransfer4 `xml:"PdctTrf"`

	// 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, eg, a (old) plan manager, sends the PEPOrISAOrPortfolioTransferConfirmation message to the instructing party, eg, a (new) plan manager, to confirm the transfer of one or more PEP or ISA or portfolio products from the client's account at the old plan manager to the client's account at the new plan manager through a nominee account. Usage The PEPOrISAOrPortfolioTransferConfirmation message is used to confirm the transfer of one or more PEP or ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PEPOrISAPOrPortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddCashAccount ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddClientAccount ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddExtension ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddMessageReference ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddNewPlanManager ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddNomineeAccount ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddOtherCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferConfirmationV02) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddOtherIndividualInvestor ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddPoolReference ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddPreviousReference ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddPrimaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferConfirmationV02) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddPrimaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioTransferConfirmationV02) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddProductTransfer ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddRelatedReference ¶

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddSecondaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferConfirmationV02) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferConfirmationV02) AddSecondaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioTransferConfirmationV02) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

type PEPOrISAOrPortfolioTransferInstructionV02 ¶

type PEPOrISAOrPortfolioTransferInstructionV02 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	ClientAccount *iso20022.Account5 `xml:"ClntAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	NewPlanManager *iso20022.PartyIdentification2Choice `xml:"NewPlanMgr"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.PEPISATransfer3 `xml:"PdctTrf"`

	// 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, eg, a (new) plan manager, sends the PEPOrISAOrPortfolioTransferInstruction message to the executing party, eg, a (old) plan manager, on behalf of the initiating party, eg, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager to the clients account at the new plan manager through a nominee account. Usage The PEPOrISAOrPortfolioTransferInstruction message is used to instruct the withdrawal of one or more PEP or ISA or portfolio products from one account and deliver them to another account. The PEPOrISAOrPortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a RequestForPEPOrISAOrPortfolioInformation message to the executing party in order to receive a PEPOrISAOrPortfolioInformation message.

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddCashAccount ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddClientAccount ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddExtension ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddMessageReference ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddNewPlanManager ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddNomineeAccount ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddOtherCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddOtherIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddPoolReference ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddPreviousReference ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddPrimaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddPrimaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddProductTransfer ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddRelatedReference ¶

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddSecondaryCorporateInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PEPOrISAOrPortfolioTransferInstructionV02) AddSecondaryIndividualInvestor ¶

func (p *PEPOrISAOrPortfolioTransferInstructionV02) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

type PortfolioTransferCancellationRequestV03 ¶

type PortfolioTransferCancellationRequestV03 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 the transfer instruction to be cancelled.
	CancellationByTransferInstructionDetails *iso20022.PEPISATransfer11 `xml:"CxlByTrfInstrDtls,omitempty"`

	// Reference of the transfer instruction to be cancelled.
	CancellationByReference *iso20022.TransferReference3 `xml:"CxlByRef,omitempty"`
}

Scope An instructing party, eg, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, eg, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, ie, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PortfolioTransferCancellationRequestV03) AddCancellationByReference ¶

func (p *PortfolioTransferCancellationRequestV03) AddCancellationByReference() *iso20022.TransferReference3

func (*PortfolioTransferCancellationRequestV03) AddCancellationByTransferInstructionDetails ¶

func (p *PortfolioTransferCancellationRequestV03) AddCancellationByTransferInstructionDetails() *iso20022.PEPISATransfer11

func (*PortfolioTransferCancellationRequestV03) AddMessageReference ¶

func (*PortfolioTransferCancellationRequestV03) AddPoolReference ¶

func (*PortfolioTransferCancellationRequestV03) AddPreviousReference ¶

func (*PortfolioTransferCancellationRequestV03) AddRelatedReference ¶

type PortfolioTransferCancellationRequestV04 ¶

type PortfolioTransferCancellationRequestV04 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Choice between cancellation by transfer details or reference.
	Cancellation *iso20022.Cancellation3Choice `xml:"Cxl"`
}

Scope An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, ie, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PortfolioTransferCancellationRequestV04) AddCancellation ¶

func (*PortfolioTransferCancellationRequestV04) AddMessageReference ¶

func (*PortfolioTransferCancellationRequestV04) AddPoolReference ¶

func (*PortfolioTransferCancellationRequestV04) AddPreviousReference ¶

func (*PortfolioTransferCancellationRequestV04) AddRelatedReference ¶

type PortfolioTransferCancellationRequestV05 ¶

type PortfolioTransferCancellationRequestV05 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Choice between cancellation by transfer details or reference.
	Cancellation *iso20022.Cancellation6Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`
}

Scope An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, ie, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PortfolioTransferCancellationRequestV05) AddCancellation ¶

func (*PortfolioTransferCancellationRequestV05) AddMarketPracticeVersion ¶

func (*PortfolioTransferCancellationRequestV05) AddMessageReference ¶

func (*PortfolioTransferCancellationRequestV05) AddPoolReference ¶

func (*PortfolioTransferCancellationRequestV05) AddPreviousReference ¶

func (*PortfolioTransferCancellationRequestV05) AddRelatedReference ¶

type PortfolioTransferCancellationRequestV06 ¶

type PortfolioTransferCancellationRequestV06 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

	// Choice between cancellation by transfer details or reference.
	Cancellation *iso20022.Cancellation7Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`
}

Scope An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, ie, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PortfolioTransferCancellationRequestV06) AddCancellation ¶

func (*PortfolioTransferCancellationRequestV06) AddMarketPracticeVersion ¶

func (*PortfolioTransferCancellationRequestV06) AddMessageReference ¶

func (*PortfolioTransferCancellationRequestV06) AddPoolReference ¶

func (*PortfolioTransferCancellationRequestV06) AddPreviousReference ¶

func (*PortfolioTransferCancellationRequestV06) AddRelatedReference ¶

type PortfolioTransferCancellationRequestV07 ¶

type PortfolioTransferCancellationRequestV07 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

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

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

	// Choice between cancellation by transfer details or reference.
	Cancellation *iso20022.Cancellation11Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`
}

Scope An instructing party, for example, a (new) plan manager (Transferee), sends the PortfolioTransferCancellationRequest message to the executing party, for example, a (old) plan manager (Transferor), to request the cancellation of a previously sent PortfolioTransferInstruction. Usage The PortfolioTransferCancellationRequest message is used to request the cancellation of an entire PortfolioTransferInstruction message, that is, all the product transfers that it contained. The cancellation request can be specified either by: - quoting the transfer references of all the product transfers listed in the PortfolioTransferInstruction message, or, - quoting the details of all the product transfers (this includes TransferReference) listed in PortfolioTransferInstruction message. The message identification of the PortfolioTransferInstruction may also be quoted in PreviousReference. It is also possible to request the cancellation of PortfolioTransferInstruction by just quoting its message identification in PreviousReference.

func (*PortfolioTransferCancellationRequestV07) AddCancellation ¶

func (*PortfolioTransferCancellationRequestV07) AddMarketPracticeVersion ¶

func (*PortfolioTransferCancellationRequestV07) AddMessageReference ¶

func (*PortfolioTransferCancellationRequestV07) AddPoolReference ¶

func (*PortfolioTransferCancellationRequestV07) AddPreviousReference ¶

func (*PortfolioTransferCancellationRequestV07) AddRelatedReference ¶

type PortfolioTransferConfirmationV03 ¶

type PortfolioTransferConfirmationV03 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer2 `xml:"PdctTrf"`

	// 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, eg, a (old) plan manager (Transferor), sends the PortfolioTransferConfirmation message to the instructing party, eg, a (new) plan manager (Transferee), to confirm the transfer of one or more ISA or portfolio products from the client's account at the old plan manager (Transferor) to the client's account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferConfirmation message is used to confirm the transfer of one or more ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PortfolioTransferConfirmationV03) AddCashAccount ¶

func (*PortfolioTransferConfirmationV03) AddExtension ¶

func (*PortfolioTransferConfirmationV03) AddMessageReference ¶

func (*PortfolioTransferConfirmationV03) AddNomineeAccount ¶

func (p *PortfolioTransferConfirmationV03) AddNomineeAccount() *iso20022.Account6

func (*PortfolioTransferConfirmationV03) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV03) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV03) AddPoolReference ¶

func (*PortfolioTransferConfirmationV03) AddPreviousReference ¶

func (*PortfolioTransferConfirmationV03) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV03) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV03) AddProductTransfer ¶

func (p *PortfolioTransferConfirmationV03) AddProductTransfer() *iso20022.ISATransfer2

func (*PortfolioTransferConfirmationV03) AddRelatedReference ¶

func (*PortfolioTransferConfirmationV03) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV03) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV03) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV03) AddTransferee ¶

func (*PortfolioTransferConfirmationV03) AddTransferorAccount ¶

func (p *PortfolioTransferConfirmationV03) AddTransferorAccount() *iso20022.Account5

type PortfolioTransferConfirmationV04 ¶

type PortfolioTransferConfirmationV04 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer10 `xml:"PdctTrf"`

	// 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 (old) plan manager (Transferor), sends the PortfolioTransferConfirmation message to the instructing party, for example, a (new) plan manager (Transferee), to confirm the transfer of one or more ISA or portfolio products from the client's account at the old plan manager (Transferor) to the client's account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferConfirmation message is used to confirm the transfer of one or more ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PortfolioTransferConfirmationV04) AddCashAccount ¶

func (*PortfolioTransferConfirmationV04) AddExtension ¶

func (*PortfolioTransferConfirmationV04) AddMessageReference ¶

func (*PortfolioTransferConfirmationV04) AddNomineeAccount ¶

func (p *PortfolioTransferConfirmationV04) AddNomineeAccount() *iso20022.Account6

func (*PortfolioTransferConfirmationV04) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV04) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV04) AddPoolReference ¶

func (*PortfolioTransferConfirmationV04) AddPreviousReference ¶

func (*PortfolioTransferConfirmationV04) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV04) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV04) AddProductTransfer ¶

func (p *PortfolioTransferConfirmationV04) AddProductTransfer() *iso20022.ISATransfer10

func (*PortfolioTransferConfirmationV04) AddRelatedReference ¶

func (*PortfolioTransferConfirmationV04) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV04) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV04) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV04) AddTransferee ¶

func (*PortfolioTransferConfirmationV04) AddTransferorAccount ¶

func (p *PortfolioTransferConfirmationV04) AddTransferorAccount() *iso20022.Account5

type PortfolioTransferConfirmationV05 ¶

type PortfolioTransferConfirmationV05 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount29 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer13 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 (old) plan manager (Transferor), sends the PortfolioTransferConfirmation message to the instructing party, for example, a (new) plan manager (Transferee), to confirm the transfer of one or more ISA or portfolio products from the client's account at the old plan manager (Transferor) to the client's account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferConfirmation message is used to confirm the transfer of one or more ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PortfolioTransferConfirmationV05) AddCashAccount ¶

func (*PortfolioTransferConfirmationV05) AddExtension ¶

func (*PortfolioTransferConfirmationV05) AddMarketPracticeVersion ¶

func (p *PortfolioTransferConfirmationV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferConfirmationV05) AddMessageReference ¶

func (*PortfolioTransferConfirmationV05) AddNomineeAccount ¶

func (p *PortfolioTransferConfirmationV05) AddNomineeAccount() *iso20022.Account16

func (*PortfolioTransferConfirmationV05) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV05) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV05) AddPoolReference ¶

func (*PortfolioTransferConfirmationV05) AddPreviousReference ¶

func (*PortfolioTransferConfirmationV05) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV05) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV05) AddProductTransfer ¶

func (p *PortfolioTransferConfirmationV05) AddProductTransfer() *iso20022.ISATransfer13

func (*PortfolioTransferConfirmationV05) AddRelatedReference ¶

func (*PortfolioTransferConfirmationV05) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV05) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV05) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV05) AddTransferee ¶

func (*PortfolioTransferConfirmationV05) AddTransferorAccount ¶

func (p *PortfolioTransferConfirmationV05) AddTransferorAccount() *iso20022.Account15

type PortfolioTransferConfirmationV06 ¶

type PortfolioTransferConfirmationV06 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount29 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer21 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 (old) plan manager (Transferor), sends the PortfolioTransferConfirmation message to the instructing party, for example, a (new) plan manager (Transferee), to confirm the transfer of one or more ISA or portfolio products from the client's account at the old plan manager (Transferor) to the client's account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferConfirmation message is used to confirm the transfer of one or more ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PortfolioTransferConfirmationV06) AddCashAccount ¶

func (*PortfolioTransferConfirmationV06) AddExtension ¶

func (*PortfolioTransferConfirmationV06) AddMarketPracticeVersion ¶

func (p *PortfolioTransferConfirmationV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferConfirmationV06) AddMessageReference ¶

func (*PortfolioTransferConfirmationV06) AddNomineeAccount ¶

func (p *PortfolioTransferConfirmationV06) AddNomineeAccount() *iso20022.Account16

func (*PortfolioTransferConfirmationV06) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV06) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV06) AddPoolReference ¶

func (*PortfolioTransferConfirmationV06) AddPreviousReference ¶

func (*PortfolioTransferConfirmationV06) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV06) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV06) AddProductTransfer ¶

func (p *PortfolioTransferConfirmationV06) AddProductTransfer() *iso20022.ISATransfer21

func (*PortfolioTransferConfirmationV06) AddRelatedReference ¶

func (*PortfolioTransferConfirmationV06) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferConfirmationV06) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV06) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV06) AddTransferee ¶

func (*PortfolioTransferConfirmationV06) AddTransferorAccount ¶

func (p *PortfolioTransferConfirmationV06) AddTransferorAccount() *iso20022.Account15

type PortfolioTransferConfirmationV07 ¶

type PortfolioTransferConfirmationV07 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

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

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

	// Information identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation21 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation21 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation21 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account19 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account19 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification70Choice `xml:"Trfee"`

	// Identification of a related party or intermediary.
	IntermediaryInformation []*iso20022.Intermediary34 `xml:"IntrmyInf,omitempty"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount34 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer26 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 (old) plan manager (Transferor), sends the PortfolioTransferConfirmation message to the instructing party, for example, a (new) plan manager (Transferee), to confirm the transfer of one or more ISA or portfolio products from the client's account at the old plan manager (Transferor) to the client's account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferConfirmation message is used to confirm the transfer of one or more ISA or portfolio products. The reference of each product transfer confirmation is identified in TransferConfirmationIdentification. The reference of the original product transfer is specified in TransferInstructionReference. The message identification of the PortfolioTransferInstruction message in which the product transfers were conveyed may also be quoted in RelatedReference.

func (*PortfolioTransferConfirmationV07) AddCashAccount ¶

func (*PortfolioTransferConfirmationV07) AddExtension ¶

func (*PortfolioTransferConfirmationV07) AddIntermediaryInformation ¶

func (p *PortfolioTransferConfirmationV07) AddIntermediaryInformation() *iso20022.Intermediary34

func (*PortfolioTransferConfirmationV07) AddMarketPracticeVersion ¶

func (p *PortfolioTransferConfirmationV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferConfirmationV07) AddMessageReference ¶

func (*PortfolioTransferConfirmationV07) AddNomineeAccount ¶

func (p *PortfolioTransferConfirmationV07) AddNomineeAccount() *iso20022.Account19

func (*PortfolioTransferConfirmationV07) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddOtherCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferConfirmationV07) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV07) AddPoolReference ¶

func (*PortfolioTransferConfirmationV07) AddPreviousReference ¶

func (*PortfolioTransferConfirmationV07) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddPrimaryCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferConfirmationV07) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV07) AddProductTransfer ¶

func (p *PortfolioTransferConfirmationV07) AddProductTransfer() *iso20022.ISATransfer26

func (*PortfolioTransferConfirmationV07) AddRelatedReference ¶

func (*PortfolioTransferConfirmationV07) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddSecondaryCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferConfirmationV07) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferConfirmationV07) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferConfirmationV07) AddTransferee ¶

func (*PortfolioTransferConfirmationV07) AddTransferorAccount ¶

func (p *PortfolioTransferConfirmationV07) AddTransferorAccount() *iso20022.Account19

type PortfolioTransferInstructionV03 ¶

type PortfolioTransferInstructionV03 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer1 `xml:"PdctTrf"`

	// 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, eg, a (new) plan manager (Transferee), sends the PortfolioTransferInstruction message to the executing party, eg, a (old) plan manager (Transferor), on behalf of the initiating party, eg, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager (Transferor) to the clients account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferInstruction message is used to instruct the withdrawal of one or more ISA or portfolio products from one account and deliver them to another account. The PortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a AccountHoldingInformationRequest message to the executing party in order to receive a AccountHoldingInformation message.

func (*PortfolioTransferInstructionV03) AddCashAccount ¶

func (*PortfolioTransferInstructionV03) AddExtension ¶

func (*PortfolioTransferInstructionV03) AddMessageReference ¶

func (*PortfolioTransferInstructionV03) AddNomineeAccount ¶

func (p *PortfolioTransferInstructionV03) AddNomineeAccount() *iso20022.Account6

func (*PortfolioTransferInstructionV03) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferInstructionV03) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV03) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferInstructionV03) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV03) AddPoolReference ¶

func (*PortfolioTransferInstructionV03) AddPreviousReference ¶

func (*PortfolioTransferInstructionV03) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV03) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV03) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV03) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV03) AddProductTransfer ¶

func (p *PortfolioTransferInstructionV03) AddProductTransfer() *iso20022.ISATransfer1

func (*PortfolioTransferInstructionV03) AddRelatedReference ¶

func (*PortfolioTransferInstructionV03) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV03) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV03) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV03) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV03) AddTransferee ¶

func (*PortfolioTransferInstructionV03) AddTransferorAccount ¶

func (p *PortfolioTransferInstructionV03) AddTransferorAccount() *iso20022.Account5

type PortfolioTransferInstructionV04 ¶

type PortfolioTransferInstructionV04 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account5 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount11 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer7 `xml:"PdctTrf"`

	// 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, a (new) plan manager (Transferee), sends the PortfolioTransferInstruction message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager (Transferor) to the clients account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferInstruction message is used to instruct the withdrawal of one or more ISA or portfolio products from one account and deliver them to another account. The PortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a AccountHoldingInformationRequest message to the executing party in order to receive a AccountHoldingInformation message.

func (*PortfolioTransferInstructionV04) AddCashAccount ¶

func (*PortfolioTransferInstructionV04) AddExtension ¶

func (*PortfolioTransferInstructionV04) AddMessageReference ¶

func (*PortfolioTransferInstructionV04) AddNomineeAccount ¶

func (p *PortfolioTransferInstructionV04) AddNomineeAccount() *iso20022.Account6

func (*PortfolioTransferInstructionV04) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferInstructionV04) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV04) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferInstructionV04) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV04) AddPoolReference ¶

func (*PortfolioTransferInstructionV04) AddPreviousReference ¶

func (*PortfolioTransferInstructionV04) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV04) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV04) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV04) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV04) AddProductTransfer ¶

func (p *PortfolioTransferInstructionV04) AddProductTransfer() *iso20022.ISATransfer7

func (*PortfolioTransferInstructionV04) AddRelatedReference ¶

func (*PortfolioTransferInstructionV04) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV04) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV04) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV04) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV04) AddTransferee ¶

func (*PortfolioTransferInstructionV04) AddTransferorAccount ¶

func (p *PortfolioTransferInstructionV04) AddTransferorAccount() *iso20022.Account5

type PortfolioTransferInstructionV05 ¶

type PortfolioTransferInstructionV05 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount29 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer16 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a (new) plan manager (Transferee), sends the PortfolioTransferInstruction message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager (Transferor) to the clients account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferInstruction message is used to instruct the withdrawal of one or more ISA or portfolio products from one account and deliver them to another account. The PortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a AccountHoldingInformationRequest message to the executing party in order to receive a AccountHoldingInformation message.

func (*PortfolioTransferInstructionV05) AddCashAccount ¶

func (*PortfolioTransferInstructionV05) AddExtension ¶

func (*PortfolioTransferInstructionV05) AddMarketPracticeVersion ¶

func (p *PortfolioTransferInstructionV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferInstructionV05) AddMessageReference ¶

func (*PortfolioTransferInstructionV05) AddNomineeAccount ¶

func (p *PortfolioTransferInstructionV05) AddNomineeAccount() *iso20022.Account16

func (*PortfolioTransferInstructionV05) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferInstructionV05) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV05) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferInstructionV05) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV05) AddPoolReference ¶

func (*PortfolioTransferInstructionV05) AddPreviousReference ¶

func (*PortfolioTransferInstructionV05) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV05) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV05) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV05) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV05) AddProductTransfer ¶

func (p *PortfolioTransferInstructionV05) AddProductTransfer() *iso20022.ISATransfer16

func (*PortfolioTransferInstructionV05) AddRelatedReference ¶

func (*PortfolioTransferInstructionV05) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV05) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV05) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV05) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV05) AddTransferee ¶

func (*PortfolioTransferInstructionV05) AddTransferorAccount ¶

func (p *PortfolioTransferInstructionV05) AddTransferorAccount() *iso20022.Account15

type PortfolioTransferInstructionV06 ¶

type PortfolioTransferInstructionV06 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account15 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account16 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification2Choice `xml:"Trfee"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount29 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer18 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a (new) plan manager (Transferee), sends the PortfolioTransferInstruction message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager (Transferor) to the clients account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferInstruction message is used to instruct the withdrawal of one or more ISA or portfolio products from one account and deliver them to another account. The PortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a AccountHoldingInformationRequest message to the executing party in order to receive a AccountHoldingInformation message.

func (*PortfolioTransferInstructionV06) AddCashAccount ¶

func (*PortfolioTransferInstructionV06) AddExtension ¶

func (*PortfolioTransferInstructionV06) AddMarketPracticeVersion ¶

func (p *PortfolioTransferInstructionV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferInstructionV06) AddMessageReference ¶

func (*PortfolioTransferInstructionV06) AddNomineeAccount ¶

func (p *PortfolioTransferInstructionV06) AddNomineeAccount() *iso20022.Account16

func (*PortfolioTransferInstructionV06) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferInstructionV06) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV06) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferInstructionV06) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV06) AddPoolReference ¶

func (*PortfolioTransferInstructionV06) AddPreviousReference ¶

func (*PortfolioTransferInstructionV06) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV06) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV06) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV06) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV06) AddProductTransfer ¶

func (p *PortfolioTransferInstructionV06) AddProductTransfer() *iso20022.ISATransfer18

func (*PortfolioTransferInstructionV06) AddRelatedReference ¶

func (*PortfolioTransferInstructionV06) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV06) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*PortfolioTransferInstructionV06) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV06) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV06) AddTransferee ¶

func (*PortfolioTransferInstructionV06) AddTransferorAccount ¶

func (p *PortfolioTransferInstructionV06) AddTransferorAccount() *iso20022.Account15

type PortfolioTransferInstructionV07 ¶

type PortfolioTransferInstructionV07 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

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

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

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

	// Information identifying the primary individual investor, for example, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, for example, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying the other individual investors, for example, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, for example, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation21 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, for example, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation21 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, for example, name and address.
	OtherCorporateInvestor []*iso20022.Organisation21 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	TransferorAccount *iso20022.Account19 `xml:"TrfrAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account19 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	Transferee *iso20022.PartyIdentification70Choice `xml:"Trfee"`

	// Identification of a related party or intermediary.
	IntermediaryInformation []*iso20022.Intermediary34 `xml:"IntrmyInf,omitempty"`

	// Identification of an account owned by the investor to which a cash entry is made based on the transfer of asset(s).
	CashAccount *iso20022.CashAccount34 `xml:"CshAcct,omitempty"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.ISATransfer22 `xml:"PdctTrf"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a (new) plan manager (Transferee), sends the PortfolioTransferInstruction message to the executing party, for example, a (old) plan manager (Transferor), on behalf of the initiating party, for example, an investor (client), to instruct the transfer of financial instruments from the clients account at the old plan manager (Transferor) to the clients account at the new plan manager (Transferee) through a nominee account. Usage The PortfolioTransferInstruction message is used to instruct the withdrawal of one or more ISA or portfolio products from one account and deliver them to another account. The PortfolioTransferInstruction message is used to instruct one or more transfers for one client. Each transfer is for delivery to the same account. The account may be owned by one or more individual investors or one or more corporate investors. Each transfer is identified in TransferIdentification. If the instructing party does not have enough information to instruct the transfer, then it must first send a AccountHoldingInformationRequest message to the executing party in order to receive a AccountHoldingInformation message.

func (*PortfolioTransferInstructionV07) AddCashAccount ¶

func (*PortfolioTransferInstructionV07) AddExtension ¶

func (*PortfolioTransferInstructionV07) AddIntermediaryInformation ¶

func (p *PortfolioTransferInstructionV07) AddIntermediaryInformation() *iso20022.Intermediary34

func (*PortfolioTransferInstructionV07) AddMarketPracticeVersion ¶

func (p *PortfolioTransferInstructionV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*PortfolioTransferInstructionV07) AddMessageReference ¶

func (*PortfolioTransferInstructionV07) AddNomineeAccount ¶

func (p *PortfolioTransferInstructionV07) AddNomineeAccount() *iso20022.Account19

func (*PortfolioTransferInstructionV07) AddOtherCorporateInvestor ¶

func (p *PortfolioTransferInstructionV07) AddOtherCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferInstructionV07) AddOtherIndividualInvestor ¶

func (p *PortfolioTransferInstructionV07) AddOtherIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV07) AddPoolReference ¶

func (*PortfolioTransferInstructionV07) AddPreviousReference ¶

func (*PortfolioTransferInstructionV07) AddPrimaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV07) AddPrimaryCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferInstructionV07) AddPrimaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV07) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV07) AddProductTransfer ¶

func (p *PortfolioTransferInstructionV07) AddProductTransfer() *iso20022.ISATransfer22

func (*PortfolioTransferInstructionV07) AddRelatedReference ¶

func (*PortfolioTransferInstructionV07) AddSecondaryCorporateInvestor ¶

func (p *PortfolioTransferInstructionV07) AddSecondaryCorporateInvestor() *iso20022.Organisation21

func (*PortfolioTransferInstructionV07) AddSecondaryIndividualInvestor ¶

func (p *PortfolioTransferInstructionV07) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

func (*PortfolioTransferInstructionV07) AddTransferee ¶

func (*PortfolioTransferInstructionV07) AddTransferorAccount ¶

func (p *PortfolioTransferInstructionV07) AddTransferorAccount() *iso20022.Account19

type PortfolioTransferNotification002V04 ¶

type PortfolioTransferNotification002V04 struct {

	// Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement.
	Pagination *iso20022.Pagination `xml:"Pgntn"`

	// Provides general information on the notification
	StatementGeneralDetails *iso20022.Statement50 `xml:"StmtGnlDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Details of transfer.
	TransferNotificationDetails []*iso20022.SecuritiesTradeDetails57 `xml:"TrfNtfctnDtls,omitempty"`
}

Scope An account servicer sends a PortfolioTransferNotification to another account servicer to exchange transfer settlement details information during a retail or institutional client portfolio transfer. The account servicers will typically be local agents or global custodians acting on behalf of an investment management institution, a broker/dealer or a retail client.

Usage By exchange of transfer settlement details, it is understood the providing, by the delivering account servicer to the receiving account servicer, of the settlement details (trade date, settlement date, delivering settlement chain, quantities, etc.) of the individual transfers that will take place during a full or partial portfolio transfer. This delivering account servicer message may also include, for validation, the receiving settlement chain as provided by the client. In case the receiving settlement chain is not available to the delivering account servicer, the receiving account servicer may in return provide to the delivering account servicer the receiving settlement chain using the same message.

The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*PortfolioTransferNotification002V04) AddAccountOwner ¶

func (*PortfolioTransferNotification002V04) AddPagination ¶

func (*PortfolioTransferNotification002V04) AddSafekeepingAccount ¶

func (*PortfolioTransferNotification002V04) AddStatementGeneralDetails ¶

func (p *PortfolioTransferNotification002V04) AddStatementGeneralDetails() *iso20022.Statement50

func (*PortfolioTransferNotification002V04) AddTransferNotificationDetails ¶

func (p *PortfolioTransferNotification002V04) AddTransferNotificationDetails() *iso20022.SecuritiesTradeDetails57

type PortfolioTransferNotificationV01 ¶

type PortfolioTransferNotificationV01 struct {

	// Information that unambiguously identifies a PortfolioTransferNotification message as known by the sender.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement.
	Pagination *iso20022.Pagination `xml:"Pgntn"`

	// Provides general information on the notification
	StatementGeneralDetails *iso20022.Statement19 `xml:"StmtGnlDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification13Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of transfer.
	TransferNotificationDetails []*iso20022.SecuritiesTradeDetails7 `xml:"TrfNtfctnDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`
}

Scope An account servicer sends a PortfolioTransferNotification to another account servicer to exchange transfer settlement details information during a retail or institutional client portfolio transfers. The account servicers will typically be local agents or global custodians acting on behalf of an investment management institution, a broker/dealer or a retail client. Usage By exchange of transfer settlement details, it is understood the providing, by the delivering account servicer to the receiving account servicer, of the settlement details (trade date, settlement date, delivering settlement chain, quantities, etc.) of the individual transfers that will take place during a full or partial portfolio transfer. This delivering account servicer message may also include, for validation, the receiving settlement chain as provided by the client. In case the receiving settlement chain is not available to the delivering account servicer, the receiving account servicer may in return provide to the delivering account servicer the receiving settlement chain using the same message. The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*PortfolioTransferNotificationV01) AddAccountOwner ¶

func (*PortfolioTransferNotificationV01) AddIdentification ¶

func (*PortfolioTransferNotificationV01) AddMessageOriginator ¶

func (*PortfolioTransferNotificationV01) AddMessageRecipient ¶

func (*PortfolioTransferNotificationV01) AddPagination ¶

func (*PortfolioTransferNotificationV01) AddSafekeepingAccount ¶

func (*PortfolioTransferNotificationV01) AddStatementGeneralDetails ¶

func (p *PortfolioTransferNotificationV01) AddStatementGeneralDetails() *iso20022.Statement19

func (*PortfolioTransferNotificationV01) AddTransferNotificationDetails ¶

func (p *PortfolioTransferNotificationV01) AddTransferNotificationDetails() *iso20022.SecuritiesTradeDetails7

type PortfolioTransferNotificationV02 ¶

type PortfolioTransferNotificationV02 struct {

	// Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement.
	Pagination *iso20022.Pagination `xml:"Pgntn"`

	// Provides general information on the notification
	StatementGeneralDetails *iso20022.Statement19 `xml:"StmtGnlDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of transfer.
	TransferNotificationDetails []*iso20022.SecuritiesTradeDetails19 `xml:"TrfNtfctnDtls,omitempty"`
}

Scope An account servicer sends a PortfolioTransferNotification to another account servicer to exchange transfer settlement details information during a retail or institutional client portfolio transfers. The account servicers will typically be local agents or global custodians acting on behalf of an investment management institution, a broker/dealer or a retail client. Usage By exchange of transfer settlement details, it is understood the providing, by the delivering account servicer to the receiving account servicer, of the settlement details (trade date, settlement date, delivering settlement chain, quantities, etc.) of the individual transfers that will take place during a full or partial portfolio transfer. This delivering account servicer message may also include, for validation, the receiving settlement chain as provided by the client. In case the receiving settlement chain is not available to the delivering account servicer, the receiving account servicer may in return provide to the delivering account servicer the receiving settlement chain using the same message. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*PortfolioTransferNotificationV02) AddAccountOwner ¶

func (*PortfolioTransferNotificationV02) AddPagination ¶

func (*PortfolioTransferNotificationV02) AddSafekeepingAccount ¶

func (*PortfolioTransferNotificationV02) AddStatementGeneralDetails ¶

func (p *PortfolioTransferNotificationV02) AddStatementGeneralDetails() *iso20022.Statement19

func (*PortfolioTransferNotificationV02) AddTransferNotificationDetails ¶

func (p *PortfolioTransferNotificationV02) AddTransferNotificationDetails() *iso20022.SecuritiesTradeDetails19

type PortfolioTransferNotificationV03 ¶

type PortfolioTransferNotificationV03 struct {

	// Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement.
	Pagination *iso20022.Pagination `xml:"Pgntn"`

	// Provides general information on the notification
	StatementGeneralDetails *iso20022.Statement19 `xml:"StmtGnlDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of transfer.
	TransferNotificationDetails []*iso20022.SecuritiesTradeDetails24 `xml:"TrfNtfctnDtls,omitempty"`
}

Scope An account servicer sends a PortfolioTransferNotification to another account servicer to exchange transfer settlement details information during a retail or institutional client portfolio transfer. The account servicers will typically be local agents or global custodians acting on behalf of an investment management institution, a broker/dealer or a retail client.

Usage By exchange of transfer settlement details, it is understood the providing, by the delivering account servicer to the receiving account servicer, of the settlement details (trade date, settlement date, delivering settlement chain, quantities, etc.) of the individual transfers that will take place during a full or partial portfolio transfer. This delivering account servicer message may also include, for validation, the receiving settlement chain as provided by the client. In case the receiving settlement chain is not available to the delivering account servicer, the receiving account servicer may in return provide to the delivering account servicer the receiving settlement chain using the same message. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*PortfolioTransferNotificationV03) AddAccountOwner ¶

func (*PortfolioTransferNotificationV03) AddPagination ¶

func (*PortfolioTransferNotificationV03) AddSafekeepingAccount ¶

func (*PortfolioTransferNotificationV03) AddStatementGeneralDetails ¶

func (p *PortfolioTransferNotificationV03) AddStatementGeneralDetails() *iso20022.Statement19

func (*PortfolioTransferNotificationV03) AddTransferNotificationDetails ¶

func (p *PortfolioTransferNotificationV03) AddTransferNotificationDetails() *iso20022.SecuritiesTradeDetails24

type PortfolioTransferNotificationV04 ¶

type PortfolioTransferNotificationV04 struct {

	// Page number of the message (within a statement) and continuation indicator to indicate that the statement is to continue or that the message is the last page of the statement.
	Pagination *iso20022.Pagination `xml:"Pgntn"`

	// Provides general information on the notification
	StatementGeneralDetails *iso20022.Statement46 `xml:"StmtGnlDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Details of transfer.
	TransferNotificationDetails []*iso20022.SecuritiesTradeDetails48 `xml:"TrfNtfctnDtls,omitempty"`
}

Scope An account servicer sends a PortfolioTransferNotification to another account servicer to exchange transfer settlement details information during a retail or institutional client portfolio transfer. The account servicers will typically be local agents or global custodians acting on behalf of an investment management institution, a broker/dealer or a retail client.

Usage By exchange of transfer settlement details, it is understood the providing, by the delivering account servicer to the receiving account servicer, of the settlement details (trade date, settlement date, delivering settlement chain, quantities, etc.) of the individual transfers that will take place during a full or partial portfolio transfer. This delivering account servicer message may also include, for validation, the receiving settlement chain as provided by the client. In case the receiving settlement chain is not available to the delivering account servicer, the receiving account servicer may in return provide to the delivering account servicer the receiving settlement chain using the same message.

The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*PortfolioTransferNotificationV04) AddAccountOwner ¶

func (*PortfolioTransferNotificationV04) AddPagination ¶

func (*PortfolioTransferNotificationV04) AddSafekeepingAccount ¶

func (*PortfolioTransferNotificationV04) AddStatementGeneralDetails ¶

func (p *PortfolioTransferNotificationV04) AddStatementGeneralDetails() *iso20022.Statement46

func (*PortfolioTransferNotificationV04) AddTransferNotificationDetails ¶

func (p *PortfolioTransferNotificationV04) AddTransferNotificationDetails() *iso20022.SecuritiesTradeDetails48

type RequestForPEPOrISAOrPortfolioInformationV01 ¶

type RequestForPEPOrISAOrPortfolioInformationV01 struct {

	// Identifies the message.
	MessageReference *iso20022.MessageIdentification1 `xml:"MsgRef"`

	// 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 identifying the primary individual investor, eg, name, address, social security number and date of birth.
	PrimaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"PmryIndvInvstr,omitempty"`

	// Information identifying the secondary individual investor, eg, name, address, social security number and date of birth.
	SecondaryIndividualInvestor *iso20022.IndividualPerson8 `xml:"ScndryIndvInvstr,omitempty"`

	// Information identifying other individual investors, eg, name, address, social security number and date of birth.
	OtherIndividualInvestor []*iso20022.IndividualPerson8 `xml:"OthrIndvInvstr,omitempty"`

	// Information identifying the primary corporate investor, eg, name and address.
	PrimaryCorporateInvestor *iso20022.Organisation4 `xml:"PmryCorpInvstr,omitempty"`

	// Information identifying the secondary corporate investor, eg, name and address.
	SecondaryCorporateInvestor *iso20022.Organisation4 `xml:"ScndryCorpInvstr,omitempty"`

	// Information identifying the other corporate investors, eg, name and address.
	OtherCorporateInvestor []*iso20022.Organisation4 `xml:"OthrCorpInvstr,omitempty"`

	// Identification of an account owned by the investor at the old plan manager (account servicer).
	ClientAccount *iso20022.Account5 `xml:"ClntAcct"`

	// Account held in the name of a party that is not the name of the beneficial owner of the shares.
	NomineeAccount *iso20022.Account6 `xml:"NmneeAcct,omitempty"`

	// Information related to the institution to which the financial instrument is to be transferred.
	NewPlanManager *iso20022.PartyIdentification2Choice `xml:"NewPlanMgr"`

	// Provides information related to the asset(s) transferred.
	ProductTransfer []*iso20022.PEPISATransfer5 `xml:"PdctTrf"`

	// 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, eg, a (new) plan manager sends the RequestForPEPorISAOrPortfolioInformation message to the executing party, eg, a (old) plan manager, on behalf of the initiating party, eg, an investor (client), to request information about financial instruments held on behalf of the client. Usage The RequestForPEPOrISAOrPortfolioInformation message is used to request information about one or more PEP or ISA or portfolio products held in a client's account for which it intends to instruct a transfer at a later time.

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddClientAccount ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddExtension ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddMessageReference ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddNewPlanManager ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddNomineeAccount ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddOtherCorporateInvestor ¶

func (r *RequestForPEPOrISAOrPortfolioInformationV01) AddOtherCorporateInvestor() *iso20022.Organisation4

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddOtherIndividualInvestor ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddPoolReference ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddPreviousReference ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddPrimaryCorporateInvestor ¶

func (r *RequestForPEPOrISAOrPortfolioInformationV01) AddPrimaryCorporateInvestor() *iso20022.Organisation4

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddPrimaryIndividualInvestor ¶

func (r *RequestForPEPOrISAOrPortfolioInformationV01) AddPrimaryIndividualInvestor() *iso20022.IndividualPerson8

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddProductTransfer ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddRelatedReference ¶

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddSecondaryCorporateInvestor ¶

func (r *RequestForPEPOrISAOrPortfolioInformationV01) AddSecondaryCorporateInvestor() *iso20022.Organisation4

func (*RequestForPEPOrISAOrPortfolioInformationV01) AddSecondaryIndividualInvestor ¶

func (r *RequestForPEPOrISAOrPortfolioInformationV01) AddSecondaryIndividualInvestor() *iso20022.IndividualPerson8

type RequestForTransferStatusReport ¶

type RequestForTransferStatusReport struct {

	// Information to identify the transfer for which the status is requested.
	//
	RequestDetails []*iso20022.MessageAndBusinessReference1 `xml:"ReqDtls"`
}

Scope The RequestForTransferStatusReport is sent by an instructing party to the executing party. This message requests the status of a transfer instruction or the status of a transfer cancellation instruction. Usage The RequestForTransferStatusReport is sent by an instructing party to the executing party to request - the status of one or several transfer instructions or - the status of one or several transfer cancellation instructions.

func (*RequestForTransferStatusReport) AddRequestDetails ¶

type RequestForTransferStatusReportV02 ¶

type RequestForTransferStatusReportV02 struct {

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

	// Information to identify the transfer for which the status is requested.
	//
	RequestDetails []*iso20022.MessageAndBusinessReference6 `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, eg, an investment manager or its authorised representative, sends the RequestForTransferStatusReport to the executing party, eg, a transfer agent to request the status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either: - the status of one or several transfer instructions or, - the status of one or several transfer cancellation instructions.

func (*RequestForTransferStatusReportV02) AddExtension ¶

func (*RequestForTransferStatusReportV02) AddMessageIdentification ¶

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

func (*RequestForTransferStatusReportV02) AddRequestDetails ¶

type RequestForTransferStatusReportV03 ¶

type RequestForTransferStatusReportV03 struct {

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

	// Information to identify the transfer for which the status is requested.
	//
	RequestDetails []*iso20022.MessageAndBusinessReference6 `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 RequestForTransferStatusReport to the executing party, for example, a transfer agent to request the status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either: - the status of one or several transfer instructions or, - the status of one or several transfer cancellation instructions.

func (*RequestForTransferStatusReportV03) AddExtension ¶

func (*RequestForTransferStatusReportV03) AddMessageIdentification ¶

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

func (*RequestForTransferStatusReportV03) AddRequestDetails ¶

type RequestForTransferStatusReportV04 ¶

type RequestForTransferStatusReportV04 struct {

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

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

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 RequestForTransferStatusReport to the executing party, for example, a transfer agent to request the status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either: - the status of one or several transfer instructions or, - the status of one or several transfer cancellation instructions.

func (*RequestForTransferStatusReportV04) AddExtension ¶

func (*RequestForTransferStatusReportV04) AddMarketPracticeVersion ¶

func (r *RequestForTransferStatusReportV04) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*RequestForTransferStatusReportV04) AddMessageIdentification ¶

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

func (*RequestForTransferStatusReportV04) AddRequestDetails ¶

type RequestForTransferStatusReportV05 ¶

type RequestForTransferStatusReportV05 struct {

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

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

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 RequestForTransferStatusReport to the executing party, for example, a transfer agent to request the status of a previously instructed transfer. Usage The RequestForTransferStatusReport is used to request either: - the status of one or several transfer instructions or, - the status of one or several transfer cancellation instructions.

func (*RequestForTransferStatusReportV05) AddExtension ¶

func (*RequestForTransferStatusReportV05) AddMarketPracticeVersion ¶

func (r *RequestForTransferStatusReportV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*RequestForTransferStatusReportV05) AddMessageIdentification ¶

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

func (*RequestForTransferStatusReportV05) AddRequestDetails ¶

type ReversalOfTransferInConfirmation ¶

type ReversalOfTransferInConfirmation struct {

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

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

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

	// Copy of the transfer in confirmation to reverse.
	TransferInConfirmationToBeReversed *iso20022.TransferIn1 `xml:"TrfInConfToBeRvsd,omitempty"`
}

Scope The ReversalOfTransferInConfirmation message is sent by an executing party to the instructing party or the instructing party's designated agent. This message is used to reverse a TransferInConfirmation that was previously sent by the instructing party. Usage The ReversalOfTransferInConfirmation message is sent by an executing party to reverse a previously sent TransferInConfirmation. This message must contain the reference of the message to be reversed. The message may also contain all the details of the reversed message, but this is not recommended.

func (*ReversalOfTransferInConfirmation) AddPoolReference ¶

func (*ReversalOfTransferInConfirmation) AddPreviousReference ¶

func (*ReversalOfTransferInConfirmation) AddRelatedReference ¶

func (*ReversalOfTransferInConfirmation) AddTransferInConfirmationToBeReversed ¶

func (r *ReversalOfTransferInConfirmation) AddTransferInConfirmationToBeReversed() *iso20022.TransferIn1

type ReversalOfTransferInConfirmationV02 ¶

type ReversalOfTransferInConfirmationV02 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 sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

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

	// Reference of the transfer in confirmation to be reversed.
	ReversalByReference *iso20022.TransferReference2 `xml:"RvslByRef,omitempty"`

	// Copy of the transfer in confirmation to reverse.
	ReversalByTransferInConfirmationDetails *iso20022.TransferIn4 `xml:"RvslByTrfInConfDtls,omitempty"`

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

Scope An executing party, eg, a transfer agent, sends the ReversalOfTransferInConfirmation message to the instructing party, eg, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, eg, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. It is also possible to request a reversal of a TransferInConfirmation by quoting its message reference (MessageIdentification) in PreviousReference.

func (*ReversalOfTransferInConfirmationV02) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV02) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV02) AddPoolReference ¶

func (*ReversalOfTransferInConfirmationV02) AddPreviousReference ¶

func (*ReversalOfTransferInConfirmationV02) AddRelatedReference ¶

func (*ReversalOfTransferInConfirmationV02) AddReversalByReference ¶

func (*ReversalOfTransferInConfirmationV02) AddReversalByTransferInConfirmationDetails ¶

func (r *ReversalOfTransferInConfirmationV02) AddReversalByTransferInConfirmationDetails() *iso20022.TransferIn4

type ReversalOfTransferInConfirmationV03 ¶

type ReversalOfTransferInConfirmationV03 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Reference of the transfer in confirmation to be reversed.
	ReversalByReference *iso20022.TransferReference2 `xml:"RvslByRef,omitempty"`

	// Copy of the transfer in confirmation to reverse.
	ReversalByTransferInConfirmationDetails *iso20022.TransferIn6 `xml:"RvslByTrfInConfDtls,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 ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. It is also possible to request a reversal of a TransferInConfirmation by quoting its message reference (MessageIdentification) in PreviousReference.

func (*ReversalOfTransferInConfirmationV03) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV03) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV03) AddReferences ¶

func (*ReversalOfTransferInConfirmationV03) AddReversalByReference ¶

func (*ReversalOfTransferInConfirmationV03) AddReversalByTransferInConfirmationDetails ¶

func (r *ReversalOfTransferInConfirmationV03) AddReversalByTransferInConfirmationDetails() *iso20022.TransferIn6

type ReversalOfTransferInConfirmationV04 ¶

type ReversalOfTransferInConfirmationV04 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal2Choice `xml:"Rvsl"`

	// 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 ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferInConfirmationV04) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV04) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV04) AddReferences ¶

func (*ReversalOfTransferInConfirmationV04) AddReversal ¶

type ReversalOfTransferInConfirmationV05 ¶

type ReversalOfTransferInConfirmationV05 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal4Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferInConfirmationV05) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV05) AddMarketPracticeVersion ¶

func (*ReversalOfTransferInConfirmationV05) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV05) AddReferences ¶

func (*ReversalOfTransferInConfirmationV05) AddReversal ¶

type ReversalOfTransferInConfirmationV06 ¶

type ReversalOfTransferInConfirmationV06 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal6Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferInConfirmationV06) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV06) AddMarketPracticeVersion ¶

func (*ReversalOfTransferInConfirmationV06) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV06) AddReferences ¶

func (*ReversalOfTransferInConfirmationV06) AddReversal ¶

type ReversalOfTransferInConfirmationV07 ¶

type ReversalOfTransferInConfirmationV07 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References20 `xml:"Refs,omitempty"`

	// Function of the transfer-in, that is, whether the message is used as a reversal of a previously sent confirmation or as a reversal of a previously sent advice. The absence of Function indicates the message is a reversal of a previously sent confirmation.
	Function *iso20022.TransferInFunction2Code `xml:"Fctn,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal7Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An executing party, for example, a transfer agent, sends the ReversalOfTransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferInConfirmation message. Usage The ReversalOfTransferInConfirmation message is used to reverse a previously sent TransferInConfirmation. There are two ways to specify the reversal of the transfer in confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferInConfirmation message in which the transfer confirmation was conveyed may also be quoted in PreviousReference. The message reference (MessageIdentification) of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferInConfirmationV07) AddCopyDetails ¶

func (*ReversalOfTransferInConfirmationV07) AddMarketPracticeVersion ¶

func (*ReversalOfTransferInConfirmationV07) AddMessageIdentification ¶

func (*ReversalOfTransferInConfirmationV07) AddReferences ¶

func (*ReversalOfTransferInConfirmationV07) AddReversal ¶

func (*ReversalOfTransferInConfirmationV07) SetFunction ¶

func (r *ReversalOfTransferInConfirmationV07) SetFunction(value string)

type ReversalOfTransferOutConfirmation ¶

type ReversalOfTransferOutConfirmation struct {

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

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

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

	// Copy of the transfer out confirmation to reverse.
	TransferOutConfirmationToBeReversed *iso20022.TransferOut1 `xml:"TrfOutConfToBeRvsd,omitempty"`
}

Scope The ReversalOfTransferOutConfirmation message is sent by an executing party to the instructing party or the instructing party's designated agent. This message is used to reverse a TransferOutConfirmation that was previously sent by the instructing party. Usage The ReversalOfTransferOutConfirmation message is sent by an executing party to reverse a previously sent TransferOutConfirmation. This message must contain the reference of the message to be reversed. The message may also contain all the details of the reversed message, but this is not recommended.

func (*ReversalOfTransferOutConfirmation) AddPoolReference ¶

func (*ReversalOfTransferOutConfirmation) AddPreviousReference ¶

func (*ReversalOfTransferOutConfirmation) AddRelatedReference ¶

func (*ReversalOfTransferOutConfirmation) AddTransferOutConfirmationToBeReversed ¶

func (r *ReversalOfTransferOutConfirmation) AddTransferOutConfirmationToBeReversed() *iso20022.TransferOut1

type ReversalOfTransferOutConfirmationV02 ¶

type ReversalOfTransferOutConfirmationV02 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 sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

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

	// Reference of the transfer out confirmation to be reversed.
	ReversalByReference *iso20022.TransferReference2 `xml:"RvslByRef,omitempty"`

	// Copy of the transfer out confirmation to reverse.
	ReversalByTransferOutConfirmationDetails *iso20022.TransferOut6 `xml:"RvslByTrfOutConfDtls,omitempty"`

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

Scope An executing party, eg, a transfer agent, sends the ReversalOfTransferOutConfirmation message to the instructing party, eg, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, eg, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV02) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV02) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV02) AddPoolReference ¶

func (*ReversalOfTransferOutConfirmationV02) AddPreviousReference ¶

func (*ReversalOfTransferOutConfirmationV02) AddRelatedReference ¶

func (*ReversalOfTransferOutConfirmationV02) AddReversalByReference ¶

func (*ReversalOfTransferOutConfirmationV02) AddReversalByTransferOutConfirmationDetails ¶

func (r *ReversalOfTransferOutConfirmationV02) AddReversalByTransferOutConfirmationDetails() *iso20022.TransferOut6

type ReversalOfTransferOutConfirmationV03 ¶

type ReversalOfTransferOutConfirmationV03 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Reference of the transfer out confirmation to be reversed.
	ReversalByReference *iso20022.TransferReference2 `xml:"RvslByRef,omitempty"`

	// Copy of the transfer out confirmation to reverse.
	ReversalByTransferOutConfirmationDetails *iso20022.TransferOut8 `xml:"RvslByTrfOutConfDtls,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 ReversalOfTransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV03) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV03) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV03) AddReferences ¶

func (*ReversalOfTransferOutConfirmationV03) AddReversalByReference ¶

func (*ReversalOfTransferOutConfirmationV03) AddReversalByTransferOutConfirmationDetails ¶

func (r *ReversalOfTransferOutConfirmationV03) AddReversalByTransferOutConfirmationDetails() *iso20022.TransferOut8

type ReversalOfTransferOutConfirmationV04 ¶

type ReversalOfTransferOutConfirmationV04 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal1Choice `xml:"Rvsl"`

	// 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 ReversalOfTransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV04) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV04) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV04) AddReferences ¶

func (*ReversalOfTransferOutConfirmationV04) AddReversal ¶

type ReversalOfTransferOutConfirmationV05 ¶

type ReversalOfTransferOutConfirmationV05 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal3Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 ReversalOfTransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV05) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV05) AddMarketPracticeVersion ¶

func (*ReversalOfTransferOutConfirmationV05) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV05) AddReferences ¶

func (*ReversalOfTransferOutConfirmationV05) AddReversal ¶

type ReversalOfTransferOutConfirmationV06 ¶

type ReversalOfTransferOutConfirmationV06 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal5Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 ReversalOfTransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV06) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV06) AddMarketPracticeVersion ¶

func (*ReversalOfTransferOutConfirmationV06) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV06) AddReferences ¶

func (*ReversalOfTransferOutConfirmationV06) AddReversal ¶

type ReversalOfTransferOutConfirmationV07 ¶

type ReversalOfTransferOutConfirmationV07 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References20 `xml:"Refs,omitempty"`

	// Choice between reversal by reference or by reversal details.
	Reversal *iso20022.Reversal8Choice `xml:"Rvsl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An executing party, for example, a transfer agent, sends the ReversalOfTransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to cancel a previously sent TransferOutConfirmation message. Usage The ReversalOfTransferOutConfirmation message is used to reverse a previously sent TransferOutConfirmation. There are two ways to specify the reversal of the transfer out confirmation. Either: - the business references, for example, TransferReference, TransferConfirmationIdentification, of the transfer confirmation are quoted, or, - all the details of the transfer confirmation (this includes TransferReference and TransferConfirmationIdentification) are quoted but this is not recommended. The message identification of the TransferOutConfirmation message in which the transfer out confirmation was conveyed may also be quoted in PreviousReference. The message identification of the TransferOutInstruction message in which the transfer out instruction was conveyed may also be quoted in RelatedReference.

func (*ReversalOfTransferOutConfirmationV07) AddCopyDetails ¶

func (*ReversalOfTransferOutConfirmationV07) AddMarketPracticeVersion ¶

func (*ReversalOfTransferOutConfirmationV07) AddMessageIdentification ¶

func (*ReversalOfTransferOutConfirmationV07) AddReferences ¶

func (*ReversalOfTransferOutConfirmationV07) AddReversal ¶

type SecuritiesFinancingConfirmation002V06 ¶

type SecuritiesFinancingConfirmation002V06 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters12 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters26 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails58 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount46 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails30 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails104 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties29 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingConfirmation002V06) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmation002V06) AddCashParties ¶

func (*SecuritiesFinancingConfirmation002V06) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmation002V06) AddDeliveringSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingConfirmation002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesFinancingConfirmation002V06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingConfirmation002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingConfirmation002V06) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmation002V06) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmation002V06) AddOtherBusinessParties() *iso20022.OtherParties29

func (*SecuritiesFinancingConfirmation002V06) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmation002V06) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount46

func (*SecuritiesFinancingConfirmation002V06) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmation002V06) AddReceivingSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingConfirmation002V06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmation002V06) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmation002V06) AddSettlementParameters ¶

func (*SecuritiesFinancingConfirmation002V06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmation002V06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction12

func (*SecuritiesFinancingConfirmation002V06) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmation002V06) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmation002V06) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmation002V07 ¶

type SecuritiesFinancingConfirmation002V07 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters19 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters26 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails58 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount62 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails30 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails104 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties29 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingConfirmation002V07) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmation002V07) AddCashParties ¶

func (*SecuritiesFinancingConfirmation002V07) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmation002V07) AddDeliveringSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingConfirmation002V07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesFinancingConfirmation002V07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingConfirmation002V07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingConfirmation002V07) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmation002V07) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmation002V07) AddOtherBusinessParties() *iso20022.OtherParties29

func (*SecuritiesFinancingConfirmation002V07) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmation002V07) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount62

func (*SecuritiesFinancingConfirmation002V07) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmation002V07) AddReceivingSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingConfirmation002V07) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmation002V07) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmation002V07) AddSettlementParameters ¶

func (*SecuritiesFinancingConfirmation002V07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmation002V07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction12

func (*SecuritiesFinancingConfirmation002V07) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmation002V07) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmation002V07) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV01 ¶

type SecuritiesFinancingConfirmationV01 struct {

	// Information that unambiguously identifies a SecuritiesFinancingConfirmation message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters3 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters2 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails6 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount6 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails3 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails9 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

SCOPE A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

USAGE The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate) - provide a third party with a copy of a message for information (the sub-function of the message is Copy) - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate).

ISO 15022 - 20022 COEXISTENCE This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingConfirmationV01) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV01) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV01) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV01) AddDeliveringSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesFinancingConfirmationV01) AddExtension ¶

func (*SecuritiesFinancingConfirmationV01) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV01) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes8

func (*SecuritiesFinancingConfirmationV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingConfirmationV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesFinancingConfirmationV01) AddIdentification ¶

func (*SecuritiesFinancingConfirmationV01) AddMessageOriginator ¶

func (*SecuritiesFinancingConfirmationV01) AddMessageRecipient ¶

func (*SecuritiesFinancingConfirmationV01) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV01) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV01) AddOtherBusinessParties() *iso20022.OtherParties2

func (*SecuritiesFinancingConfirmationV01) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV01) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount6

func (*SecuritiesFinancingConfirmationV01) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV01) AddReceivingSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesFinancingConfirmationV01) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV01) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV01) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV01) AddSettlementParameters() *iso20022.SettlementDetails9

func (*SecuritiesFinancingConfirmationV01) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV01) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction1

func (*SecuritiesFinancingConfirmationV01) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV01) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV02 ¶

type SecuritiesFinancingConfirmationV02 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters3 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters2 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails6 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount18 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails3 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails30 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties7 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties9 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingConfirmationV02) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV02) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV02) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV02) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV02) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV02) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes20

func (*SecuritiesFinancingConfirmationV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingConfirmationV02) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV02) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV02) AddOtherBusinessParties() *iso20022.OtherParties9

func (*SecuritiesFinancingConfirmationV02) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV02) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount18

func (*SecuritiesFinancingConfirmationV02) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV02) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV02) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV02) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV02) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV02) AddSettlementParameters() *iso20022.SettlementDetails30

func (*SecuritiesFinancingConfirmationV02) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV02) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingConfirmationV02) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV02) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV02) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV03 ¶

type SecuritiesFinancingConfirmationV03 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters3 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters12 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails6 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount18 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails60 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties7 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingConfirmationV03) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV03) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV03) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV03) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV03) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV03) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingConfirmationV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingConfirmationV03) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV03) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV03) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingConfirmationV03) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV03) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount18

func (*SecuritiesFinancingConfirmationV03) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV03) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV03) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV03) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV03) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV03) AddSettlementParameters() *iso20022.SettlementDetails60

func (*SecuritiesFinancingConfirmationV03) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV03) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingConfirmationV03) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV03) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV03) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV04 ¶

type SecuritiesFinancingConfirmationV04 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters3 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters18 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails6 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount18 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails60 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be:

- a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants

- an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or

- a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingConfirmationV04) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV04) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV04) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV04) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV04) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV04) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingConfirmationV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingConfirmationV04) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV04) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV04) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingConfirmationV04) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV04) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount18

func (*SecuritiesFinancingConfirmationV04) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV04) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV04) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV04) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV04) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV04) AddSettlementParameters() *iso20022.SettlementDetails60

func (*SecuritiesFinancingConfirmationV04) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV04) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingConfirmationV04) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV04) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV04) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV05 ¶

type SecuritiesFinancingConfirmationV05 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters3 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters18 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails38 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount18 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails71 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection36 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be:

- a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants

- an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or

- a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingConfirmationV05) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV05) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV05) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV05) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV05) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV05) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingConfirmationV05) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingConfirmationV05) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV05) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV05) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingConfirmationV05) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV05) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount18

func (*SecuritiesFinancingConfirmationV05) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV05) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingConfirmationV05) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV05) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV05) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV05) AddSettlementParameters() *iso20022.SettlementDetails71

func (*SecuritiesFinancingConfirmationV05) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV05) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingConfirmationV05) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV05) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV05) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV06 ¶

type SecuritiesFinancingConfirmationV06 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters10 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters24 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails55 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount40 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails28 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails96 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties27 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingConfirmationV06) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV06) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV06) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV06) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingConfirmationV06) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV06) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes64

func (*SecuritiesFinancingConfirmationV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingConfirmationV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingConfirmationV06) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV06) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV06) AddOtherBusinessParties() *iso20022.OtherParties27

func (*SecuritiesFinancingConfirmationV06) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV06) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount40

func (*SecuritiesFinancingConfirmationV06) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV06) AddReceivingSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingConfirmationV06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV06) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV06) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV06) AddSettlementParameters() *iso20022.SettlementDetails96

func (*SecuritiesFinancingConfirmationV06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesFinancingConfirmationV06) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV06) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV06) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingConfirmationV07 ¶

type SecuritiesFinancingConfirmationV07 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionIdentificationDetails *iso20022.TransactionTypeAndAdditionalParameters16 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters24 `xml:"AddtlParams,omitempty"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails55 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount40 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails28 `xml:"SctiesFincgDtls,omitempty"`

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

	// 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.SettlementDetails96 `xml:"SttlmParams,omitempty"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties27 `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 A securities financing transaction account servicer sends a SecuritiesFinancingConfirmation to an account owner to confirm or advise of the partial or full settlement of the opening or closing leg of a securities financing transaction.

The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingConfirmationV07) AddAdditionalParameters ¶

func (*SecuritiesFinancingConfirmationV07) AddCashParties ¶

func (*SecuritiesFinancingConfirmationV07) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV07) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingConfirmationV07) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingConfirmationV07) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes64

func (*SecuritiesFinancingConfirmationV07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingConfirmationV07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingConfirmationV07) AddOtherAmounts ¶

func (*SecuritiesFinancingConfirmationV07) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingConfirmationV07) AddOtherBusinessParties() *iso20022.OtherParties27

func (*SecuritiesFinancingConfirmationV07) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingConfirmationV07) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount40

func (*SecuritiesFinancingConfirmationV07) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingConfirmationV07) AddReceivingSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingConfirmationV07) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingConfirmationV07) AddSettledAmount ¶

func (*SecuritiesFinancingConfirmationV07) AddSettlementParameters ¶

func (s *SecuritiesFinancingConfirmationV07) AddSettlementParameters() *iso20022.SettlementDetails96

func (*SecuritiesFinancingConfirmationV07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingConfirmationV07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesFinancingConfirmationV07) AddSupplementaryData ¶

func (*SecuritiesFinancingConfirmationV07) AddTradeDetails ¶

func (*SecuritiesFinancingConfirmationV07) AddTransactionIdentificationDetails ¶

type SecuritiesFinancingInstruction002V06 ¶

type SecuritiesFinancingInstruction002V06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters13 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails59 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount47 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails30 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails105 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection60 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties29 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingInstruction002V06) AddCashParties ¶

func (*SecuritiesFinancingInstruction002V06) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstruction002V06) AddDeliveringSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingInstruction002V06) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstruction002V06) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes78

func (*SecuritiesFinancingInstruction002V06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingInstruction002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingInstruction002V06) AddLinkages ¶

func (*SecuritiesFinancingInstruction002V06) AddNumberCounts ¶

func (*SecuritiesFinancingInstruction002V06) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstruction002V06) AddOpeningSettlementAmount() *iso20022.AmountAndDirection60

func (*SecuritiesFinancingInstruction002V06) AddOtherAmounts ¶

func (*SecuritiesFinancingInstruction002V06) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstruction002V06) AddOtherBusinessParties() *iso20022.OtherParties29

func (*SecuritiesFinancingInstruction002V06) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstruction002V06) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount47

func (*SecuritiesFinancingInstruction002V06) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstruction002V06) AddReceivingSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingInstruction002V06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstruction002V06) AddSettlementParameters ¶

func (*SecuritiesFinancingInstruction002V06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstruction002V06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction12

func (*SecuritiesFinancingInstruction002V06) AddSupplementaryData ¶

func (*SecuritiesFinancingInstruction002V06) AddTradeDetails ¶

func (*SecuritiesFinancingInstruction002V06) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstruction002V06) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters13

func (*SecuritiesFinancingInstruction002V06) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstruction002V06) SetTransactionIdentification(value string)

type SecuritiesFinancingInstruction002V07 ¶

type SecuritiesFinancingInstruction002V07 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters18 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails59 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount56 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails30 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails105 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection60 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties29 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingInstruction002V07) AddCashParties ¶

func (*SecuritiesFinancingInstruction002V07) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstruction002V07) AddDeliveringSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingInstruction002V07) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstruction002V07) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes78

func (*SecuritiesFinancingInstruction002V07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingInstruction002V07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingInstruction002V07) AddLinkages ¶

func (*SecuritiesFinancingInstruction002V07) AddNumberCounts ¶

func (*SecuritiesFinancingInstruction002V07) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstruction002V07) AddOpeningSettlementAmount() *iso20022.AmountAndDirection60

func (*SecuritiesFinancingInstruction002V07) AddOtherAmounts ¶

func (*SecuritiesFinancingInstruction002V07) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstruction002V07) AddOtherBusinessParties() *iso20022.OtherParties29

func (*SecuritiesFinancingInstruction002V07) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstruction002V07) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount56

func (*SecuritiesFinancingInstruction002V07) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstruction002V07) AddReceivingSettlementParties() *iso20022.SettlementParties44

func (*SecuritiesFinancingInstruction002V07) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstruction002V07) AddSettlementParameters ¶

func (*SecuritiesFinancingInstruction002V07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstruction002V07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction12

func (*SecuritiesFinancingInstruction002V07) AddSupplementaryData ¶

func (*SecuritiesFinancingInstruction002V07) AddTradeDetails ¶

func (*SecuritiesFinancingInstruction002V07) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstruction002V07) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters18

func (*SecuritiesFinancingInstruction002V07) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstruction002V07) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV01 ¶

type SecuritiesFinancingInstructionV01 struct {

	// Information that unambiguously identifies a SecuritiesFinancingTransaction (unique per piece of collateral) and a SecuritiesFinancingInstruction message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactionAndDocumentIdentification1 `xml:"Id"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters1 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails3 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount1 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails1 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails3 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection2 `xml:"OpngSttlmAmt,omitempty"`

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

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingInstructionV01) AddCashParties ¶

func (*SecuritiesFinancingInstructionV01) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV01) AddDeliveringSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesFinancingInstructionV01) AddExtension ¶

func (*SecuritiesFinancingInstructionV01) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV01) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes8

func (*SecuritiesFinancingInstructionV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingInstructionV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesFinancingInstructionV01) AddIdentification ¶

func (*SecuritiesFinancingInstructionV01) AddLinkages ¶

func (*SecuritiesFinancingInstructionV01) AddMessageOriginator ¶

func (*SecuritiesFinancingInstructionV01) AddMessageRecipient ¶

func (*SecuritiesFinancingInstructionV01) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV01) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV01) AddOpeningSettlementAmount() *iso20022.AmountAndDirection2

func (*SecuritiesFinancingInstructionV01) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV01) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV01) AddOtherBusinessParties() *iso20022.OtherParties2

func (*SecuritiesFinancingInstructionV01) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV01) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount1

func (*SecuritiesFinancingInstructionV01) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV01) AddReceivingSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesFinancingInstructionV01) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV01) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV01) AddSettlementParameters() *iso20022.SettlementDetails3

func (*SecuritiesFinancingInstructionV01) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV01) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction1

func (*SecuritiesFinancingInstructionV01) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV01) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV01) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters1

type SecuritiesFinancingInstructionV02 ¶

type SecuritiesFinancingInstructionV02 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters1 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails3 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount17 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails1 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails31 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties7 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection2 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties9 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingInstructionV02) AddCashParties ¶

func (*SecuritiesFinancingInstructionV02) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV02) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV02) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV02) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes20

func (*SecuritiesFinancingInstructionV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingInstructionV02) AddLinkages ¶

func (*SecuritiesFinancingInstructionV02) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV02) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV02) AddOpeningSettlementAmount() *iso20022.AmountAndDirection2

func (*SecuritiesFinancingInstructionV02) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV02) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV02) AddOtherBusinessParties() *iso20022.OtherParties9

func (*SecuritiesFinancingInstructionV02) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV02) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount17

func (*SecuritiesFinancingInstructionV02) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV02) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV02) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV02) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV02) AddSettlementParameters() *iso20022.SettlementDetails31

func (*SecuritiesFinancingInstructionV02) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV02) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingInstructionV02) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV02) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV02) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV02) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters1

func (*SecuritiesFinancingInstructionV02) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV02) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV03 ¶

type SecuritiesFinancingInstructionV03 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters1 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails3 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails62 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties7 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection2 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingInstructionV03) AddCashParties ¶

func (*SecuritiesFinancingInstructionV03) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV03) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV03) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV03) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingInstructionV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingInstructionV03) AddLinkages ¶

func (*SecuritiesFinancingInstructionV03) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV03) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV03) AddOpeningSettlementAmount() *iso20022.AmountAndDirection2

func (*SecuritiesFinancingInstructionV03) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV03) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV03) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingInstructionV03) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV03) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount25

func (*SecuritiesFinancingInstructionV03) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV03) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV03) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV03) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV03) AddSettlementParameters() *iso20022.SettlementDetails62

func (*SecuritiesFinancingInstructionV03) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV03) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingInstructionV03) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV03) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV03) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV03) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters1

func (*SecuritiesFinancingInstructionV03) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV03) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV04 ¶

type SecuritiesFinancingInstructionV04 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters1 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails3 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails62 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection2 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingInstructionV04) AddCashParties ¶

func (*SecuritiesFinancingInstructionV04) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV04) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV04) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV04) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingInstructionV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingInstructionV04) AddLinkages ¶

func (*SecuritiesFinancingInstructionV04) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV04) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV04) AddOpeningSettlementAmount() *iso20022.AmountAndDirection2

func (*SecuritiesFinancingInstructionV04) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV04) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV04) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingInstructionV04) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV04) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount25

func (*SecuritiesFinancingInstructionV04) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV04) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV04) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV04) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV04) AddSettlementParameters() *iso20022.SettlementDetails62

func (*SecuritiesFinancingInstructionV04) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV04) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingInstructionV04) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV04) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV04) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV04) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters1

func (*SecuritiesFinancingInstructionV04) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV04) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV05 ¶

type SecuritiesFinancingInstructionV05 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters1 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails37 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails11 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails72 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection36 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties19 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingInstructionV05) AddCashParties ¶

func (*SecuritiesFinancingInstructionV05) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV05) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV05) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV05) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes35

func (*SecuritiesFinancingInstructionV05) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingInstructionV05) AddLinkages ¶

func (*SecuritiesFinancingInstructionV05) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV05) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV05) AddOpeningSettlementAmount() *iso20022.AmountAndDirection36

func (*SecuritiesFinancingInstructionV05) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV05) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV05) AddOtherBusinessParties() *iso20022.OtherParties19

func (*SecuritiesFinancingInstructionV05) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV05) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount25

func (*SecuritiesFinancingInstructionV05) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV05) AddReceivingSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingInstructionV05) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV05) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV05) AddSettlementParameters() *iso20022.SettlementDetails72

func (*SecuritiesFinancingInstructionV05) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV05) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction3

func (*SecuritiesFinancingInstructionV05) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV05) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV05) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV05) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters1

func (*SecuritiesFinancingInstructionV05) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV05) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV06 ¶

type SecuritiesFinancingInstructionV06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters9 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails56 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails28 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails97 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection46 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties27 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingInstructionV06) AddCashParties ¶

func (*SecuritiesFinancingInstructionV06) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV06) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingInstructionV06) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV06) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes64

func (*SecuritiesFinancingInstructionV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingInstructionV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingInstructionV06) AddLinkages ¶

func (*SecuritiesFinancingInstructionV06) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV06) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV06) AddOpeningSettlementAmount() *iso20022.AmountAndDirection46

func (*SecuritiesFinancingInstructionV06) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV06) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV06) AddOtherBusinessParties() *iso20022.OtherParties27

func (*SecuritiesFinancingInstructionV06) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV06) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount39

func (*SecuritiesFinancingInstructionV06) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV06) AddReceivingSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingInstructionV06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV06) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV06) AddSettlementParameters() *iso20022.SettlementDetails97

func (*SecuritiesFinancingInstructionV06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesFinancingInstructionV06) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV06) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV06) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV06) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters9

func (*SecuritiesFinancingInstructionV06) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV06) SetTransactionIdentification(value string)

type SecuritiesFinancingInstructionV07 ¶

type SecuritiesFinancingInstructionV07 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing) and other parameters.
	TransactionTypeAndAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters15 `xml:"TxTpAndAddtlParams"`

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

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

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails56 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// Details for the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails28 `xml:"SctiesFincgDtls"`

	// 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.SettlementDetails97 `xml:"SttlmParams,omitempty"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection46 `xml:"OpngSttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties27 `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 An account owner sends a SecuritiesFinancingInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction to allow the account servicer to manage the settlement and follow-up of the opening and closing leg of the transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingInstructionV07) AddCashParties ¶

func (*SecuritiesFinancingInstructionV07) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingInstructionV07) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingInstructionV07) AddFinancialInstrumentAttributes ¶

func (s *SecuritiesFinancingInstructionV07) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes64

func (*SecuritiesFinancingInstructionV07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingInstructionV07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingInstructionV07) AddLinkages ¶

func (*SecuritiesFinancingInstructionV07) AddNumberCounts ¶

func (*SecuritiesFinancingInstructionV07) AddOpeningSettlementAmount ¶

func (s *SecuritiesFinancingInstructionV07) AddOpeningSettlementAmount() *iso20022.AmountAndDirection46

func (*SecuritiesFinancingInstructionV07) AddOtherAmounts ¶

func (*SecuritiesFinancingInstructionV07) AddOtherBusinessParties ¶

func (s *SecuritiesFinancingInstructionV07) AddOtherBusinessParties() *iso20022.OtherParties27

func (*SecuritiesFinancingInstructionV07) AddQuantityAndAccountDetails ¶

func (s *SecuritiesFinancingInstructionV07) AddQuantityAndAccountDetails() *iso20022.QuantityAndAccount39

func (*SecuritiesFinancingInstructionV07) AddReceivingSettlementParties ¶

func (s *SecuritiesFinancingInstructionV07) AddReceivingSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingInstructionV07) AddSecuritiesFinancingDetails ¶

func (*SecuritiesFinancingInstructionV07) AddSettlementParameters ¶

func (s *SecuritiesFinancingInstructionV07) AddSettlementParameters() *iso20022.SettlementDetails97

func (*SecuritiesFinancingInstructionV07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesFinancingInstructionV07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesFinancingInstructionV07) AddSupplementaryData ¶

func (*SecuritiesFinancingInstructionV07) AddTradeDetails ¶

func (*SecuritiesFinancingInstructionV07) AddTransactionTypeAndAdditionalParameters ¶

func (s *SecuritiesFinancingInstructionV07) AddTransactionTypeAndAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters15

func (*SecuritiesFinancingInstructionV07) SetTransactionIdentification ¶

func (s *SecuritiesFinancingInstructionV07) SetTransactionIdentification(value string)

type SecuritiesFinancingModificationInstruction002V05 ¶

type SecuritiesFinancingModificationInstruction002V05 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters14 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails12 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount48 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails32 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails106 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection66 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingModificationInstruction002V05) AddDeliveringSettlementParties ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingModificationInstruction002V05) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingModificationInstruction002V05) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstruction002V05) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstruction002V05) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters14

type SecuritiesFinancingModificationInstruction002V06 ¶

type SecuritiesFinancingModificationInstruction002V06 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters20 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails12 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount61 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails32 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails106 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection66 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingModificationInstruction002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingModificationInstruction002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesFinancingModificationInstruction002V06) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstruction002V06) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstruction002V06) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters20

type SecuritiesFinancingModificationInstructionV01 ¶

type SecuritiesFinancingModificationInstructionV01 struct {

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

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters2 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount7 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails1 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails3 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection10 `xml:"OpngSttlmAmt,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingModificationInstructionV01) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV01) AddDeliveringSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesFinancingModificationInstructionV01) AddExtension ¶

func (*SecuritiesFinancingModificationInstructionV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingModificationInstructionV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesFinancingModificationInstructionV01) AddIdentification ¶

func (*SecuritiesFinancingModificationInstructionV01) AddMessageOriginator ¶

func (*SecuritiesFinancingModificationInstructionV01) AddMessageRecipient ¶

func (*SecuritiesFinancingModificationInstructionV01) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV01) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV01) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV01) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV01) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV01) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV01) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters2

type SecuritiesFinancingModificationInstructionV02 ¶

type SecuritiesFinancingModificationInstructionV02 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters7 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount16 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails1 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails3 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection10 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingModificationInstructionV02) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV02) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingModificationInstructionV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingModificationInstructionV02) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV02) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV02) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV02) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV02) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstructionV02) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV02) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV02) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters7

type SecuritiesFinancingModificationInstructionV03 ¶

type SecuritiesFinancingModificationInstructionV03 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters7 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount16 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails19 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails62 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection10 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingModificationInstructionV03) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV03) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingModificationInstructionV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingModificationInstructionV03) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV03) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV03) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV03) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV03) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstructionV03) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV03) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV03) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters7

type SecuritiesFinancingModificationInstructionV04 ¶

type SecuritiesFinancingModificationInstructionV04 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters7 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount16 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails19 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails72 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection10 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingModificationInstructionV04) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV04) AddDeliveringSettlementParties() *iso20022.SettlementParties10

func (*SecuritiesFinancingModificationInstructionV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesFinancingModificationInstructionV04) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV04) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV04) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV04) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV04) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstructionV04) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV04) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV04) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters7

type SecuritiesFinancingModificationInstructionV05 ¶

type SecuritiesFinancingModificationInstructionV05 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters11 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount38 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails27 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails97 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection49 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingModificationInstructionV05) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV05) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingModificationInstructionV05) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingModificationInstructionV05) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingModificationInstructionV05) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV05) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV05) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV05) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV05) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstructionV05) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV05) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV05) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters11

type SecuritiesFinancingModificationInstructionV06 ¶

type SecuritiesFinancingModificationInstructionV06 struct {

	// Securities financing transaction identification information, type (repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing), modification information and other parameters.
	TransactionTypeAndModificationAdditionalParameters *iso20022.TransactionTypeAndAdditionalParameters17 `xml:"TxTpAndModAddtlParams"`

	// Details of the securities financing deal.
	TradeDetails *iso20022.SecuritiesTradeDetails5 `xml:"TradDtls"`

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount38 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingAdditionalDetails *iso20022.SecuritiesFinancingTransactionDetails27 `xml:"SctiesFincgAddtlDtls"`

	// 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.SettlementDetails97 `xml:"SttlmParams,omitempty"`

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

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

	// Total amount of money to be paid or received in exchange for the securities at the opening of a securities financing transaction.
	OpeningSettlementAmount *iso20022.AmountAndDirection49 `xml:"OpngSttlmAmt,omitempty"`

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

Scope An account owner sends a SecuritiesFinancingModificationInstruction to a securities financing transaction account servicer to notify the securities financing transaction account servicer of an update in the details of a repurchase agreement, reverse repurchase agreement, securities lending or securities borrowing transaction that does not impact the original transaction securities quantity. Such a change may be: - the providing of closing details not available at the time of the sending of the Securities Financing Instruction, for example, termination date for an open repo, - the providing of a new rate, for example, a repo rate, - the rollover of a position extending the closing or maturity date. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of securities financing transactions to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingModificationInstructionV06) AddDeliveringSettlementParties ¶

func (s *SecuritiesFinancingModificationInstructionV06) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesFinancingModificationInstructionV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesFinancingModificationInstructionV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesFinancingModificationInstructionV06) AddOpeningSettlementAmount ¶

func (*SecuritiesFinancingModificationInstructionV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesFinancingModificationInstructionV06) AddReceivingSettlementParties ¶

func (*SecuritiesFinancingModificationInstructionV06) AddSecuritiesFinancingAdditionalDetails ¶

func (*SecuritiesFinancingModificationInstructionV06) AddSettlementParameters ¶

func (*SecuritiesFinancingModificationInstructionV06) AddSupplementaryData ¶

func (*SecuritiesFinancingModificationInstructionV06) AddTradeDetails ¶

func (*SecuritiesFinancingModificationInstructionV06) AddTransactionTypeAndModificationAdditionalParameters ¶

func (s *SecuritiesFinancingModificationInstructionV06) AddTransactionTypeAndModificationAdditionalParameters() *iso20022.TransactionTypeAndAdditionalParameters17

type SecuritiesFinancingStatusAdvice002V06 ¶

type SecuritiesFinancingStatusAdvice002V06 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications35 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus57Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus29Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus29Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus21Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus9Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails33 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingStatusAdvice002V06) AddInferredMatchingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdvice002V06) AddTransactionIdentification ¶

type SecuritiesFinancingStatusAdvice002V07 ¶

type SecuritiesFinancingStatusAdvice002V07 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications35 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus57Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus29Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus29Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus21Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus9Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails36 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingStatusAdvice002V07) AddInferredMatchingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdvice002V07) AddTransactionIdentification ¶

type SecuritiesFinancingStatusAdviceV01 ¶

type SecuritiesFinancingStatusAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesFinancingStatusAdvice message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications1 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus3Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus3Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus3Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus2Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails2 `xml:"TxDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingStatusAdviceV01) AddExtension ¶

func (*SecuritiesFinancingStatusAdviceV01) AddIdentification ¶

func (*SecuritiesFinancingStatusAdviceV01) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV01) AddInferredMatchingStatus() *iso20022.MatchingStatus3Choice

func (*SecuritiesFinancingStatusAdviceV01) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV01) AddMessageOriginator ¶

func (*SecuritiesFinancingStatusAdviceV01) AddMessageRecipient ¶

func (*SecuritiesFinancingStatusAdviceV01) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV01) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV01) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV01) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV01) AddTransactionIdentification ¶

func (s *SecuritiesFinancingStatusAdviceV01) AddTransactionIdentification() *iso20022.TransactionIdentifications1

type SecuritiesFinancingStatusAdviceV02 ¶

type SecuritiesFinancingStatusAdviceV02 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications1 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus3Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus3Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus3Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus2Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails8 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingStatusAdviceV02) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV02) AddInferredMatchingStatus() *iso20022.MatchingStatus3Choice

func (*SecuritiesFinancingStatusAdviceV02) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV02) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV02) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV02) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV02) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV02) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV02) AddTransactionIdentification ¶

func (s *SecuritiesFinancingStatusAdviceV02) AddTransactionIdentification() *iso20022.TransactionIdentifications1

type SecuritiesFinancingStatusAdviceV03 ¶

type SecuritiesFinancingStatusAdviceV03 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications1 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus21Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus12Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus12Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus10Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus5Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails17 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingStatusAdviceV03) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV03) AddInferredMatchingStatus() *iso20022.MatchingStatus12Choice

func (*SecuritiesFinancingStatusAdviceV03) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV03) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV03) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV03) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV03) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV03) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV03) AddTransactionIdentification ¶

func (s *SecuritiesFinancingStatusAdviceV03) AddTransactionIdentification() *iso20022.TransactionIdentifications1

type SecuritiesFinancingStatusAdviceV04 ¶

type SecuritiesFinancingStatusAdviceV04 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications1 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus38Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus20Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus20Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus10Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus5Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails21 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingStatusAdviceV04) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV04) AddInferredMatchingStatus() *iso20022.MatchingStatus20Choice

func (*SecuritiesFinancingStatusAdviceV04) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV04) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV04) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV04) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV04) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV04) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV04) AddTransactionIdentification ¶

func (s *SecuritiesFinancingStatusAdviceV04) AddTransactionIdentification() *iso20022.TransactionIdentifications1

type SecuritiesFinancingStatusAdviceV05 ¶

type SecuritiesFinancingStatusAdviceV05 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications1 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus38Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus20Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus20Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus10Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus5Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails24 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesFinancingStatusAdviceV05) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV05) AddInferredMatchingStatus() *iso20022.MatchingStatus20Choice

func (*SecuritiesFinancingStatusAdviceV05) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV05) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV05) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV05) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV05) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV05) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV05) AddTransactionIdentification ¶

func (s *SecuritiesFinancingStatusAdviceV05) AddTransactionIdentification() *iso20022.TransactionIdentifications1

type SecuritiesFinancingStatusAdviceV06 ¶

type SecuritiesFinancingStatusAdviceV06 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications32 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus51Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus26Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus26Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus18Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus7Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails26 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingStatusAdviceV06) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV06) AddInferredMatchingStatus() *iso20022.MatchingStatus26Choice

func (*SecuritiesFinancingStatusAdviceV06) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV06) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV06) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV06) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV06) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV06) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV06) AddTransactionIdentification ¶

type SecuritiesFinancingStatusAdviceV07 ¶

type SecuritiesFinancingStatusAdviceV07 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications32 `xml:"TxId"`

	// Processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus51Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus26Choice `xml:"MtchgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus26Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus18Choice `xml:"SttlmSts,omitempty"`

	// Provides the status of the repurchase agreement call request.
	RepoCallRequestStatus *iso20022.RepoCallRequestStatus7Choice `xml:"RepoCallReqSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.SecuritiesFinancingTransactionDetails35 `xml:"TxDtls,omitempty"`

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

Scope An securities financing transaction account servicer sends a SecuritiesFinancingStatusAdvice to an account owner to advise the status of a securities financing transaction previously instructed by the account owner. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure managing securities financing transactions on behalf of their participants - an agent (sub-custodian) managing securities financing transactions on behalf of their global custodian customer, or - a custodian managing securities financing transactions on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesFinancingStatusAdviceV07) AddInferredMatchingStatus ¶

func (s *SecuritiesFinancingStatusAdviceV07) AddInferredMatchingStatus() *iso20022.MatchingStatus26Choice

func (*SecuritiesFinancingStatusAdviceV07) AddMatchingStatus ¶

func (*SecuritiesFinancingStatusAdviceV07) AddProcessingStatus ¶

func (*SecuritiesFinancingStatusAdviceV07) AddRepoCallRequestStatus ¶

func (*SecuritiesFinancingStatusAdviceV07) AddSettlementStatus ¶

func (*SecuritiesFinancingStatusAdviceV07) AddSupplementaryData ¶

func (*SecuritiesFinancingStatusAdviceV07) AddTransactionDetails ¶

func (*SecuritiesFinancingStatusAdviceV07) AddTransactionIdentification ¶

type SecuritiesSettlementAllegementRemovalAdvice002V04 ¶

type SecuritiesSettlementAllegementRemovalAdvice002V04 struct {

	// Provides transaction type and identification information.
	AccountServicerTransactionIdentification *iso20022.SettlementTypeAndIdentification22 `xml:"AcctSvcrTxId"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification16 `xml:"MktInfrstrctrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails83 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementAllegementRemovalAdvice to an account owner to acknowledge that a previously sent allegement is no longer outstanding, because the alleged party sent its instruction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddAccountOwner ¶

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddAccountServicerTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdvice002V04) AddAccountServicerTransactionIdentification() *iso20022.SettlementTypeAndIdentification22

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdvice002V04) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification16

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddSupplementaryData ¶

func (*SecuritiesSettlementAllegementRemovalAdvice002V04) AddTransactionDetails ¶

type SecuritiesSettlementAllegementRemovalAdviceV01 ¶

type SecuritiesSettlementAllegementRemovalAdviceV01 struct {

	// Information that unambiguously identifies a securities settlement transaction and a SecuritiesSettlementAllegementRemovalAdvice message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Details of the transaction.
	Details *iso20022.TransactionDetails13 `xml:"Dtls"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementAllegementRemovalAdvice to an account owner to acknowledge that a previously sent allegement is no longer outstanding, because the alleged party sent its instruction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementAllegementRemovalAdviceV01) AddDetails ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV01) AddExtension ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV01) AddIdentification ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV01) AddMessageOriginator ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV01) AddMessageRecipient ¶

type SecuritiesSettlementAllegementRemovalAdviceV02 ¶

type SecuritiesSettlementAllegementRemovalAdviceV02 struct {

	// Provides transaction type and identification information.
	AccountServicerTransactionIdentification *iso20022.SettlementTypeAndIdentification3 `xml:"AcctSvcrTxId"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails28 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementAllegementRemovalAdvice to an account owner to acknowledge that a previously sent allegement is no longer outstanding, because the alleged party sent its instruction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddAccountOwner ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddAccountServicerTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV02) AddAccountServicerTransactionIdentification() *iso20022.SettlementTypeAndIdentification3

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV02) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddSafekeepingAccount ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddSupplementaryData ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV02) AddTransactionDetails ¶

type SecuritiesSettlementAllegementRemovalAdviceV03 ¶

type SecuritiesSettlementAllegementRemovalAdviceV03 struct {

	// Provides transaction type and identification information.
	AccountServicerTransactionIdentification *iso20022.SettlementTypeAndIdentification3 `xml:"AcctSvcrTxId"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails29 `xml:"TxDtls,omitempty"`

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

This version is identical to the previous version. It was created automatically during the 2011/2012 maintenance cycle, at the same time as new versions of other Settlement and Reconciliation messages that were truly impacted by change requests. This should not have been the case. In future releases, SWIFT will ensure that a new version of a message is not created if identical to the previous version. Scope An account servicer sends a SecuritiesSettlementAllegementRemovalAdvice to an account owner to acknowledge that a previously sent allegement is no longer outstanding, because the alleged party sent its instruction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddAccountOwner ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddAccountServicerTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV03) AddAccountServicerTransactionIdentification() *iso20022.SettlementTypeAndIdentification3

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV03) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddSafekeepingAccount ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddSupplementaryData ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV03) AddTransactionDetails ¶

type SecuritiesSettlementAllegementRemovalAdviceV04 ¶

type SecuritiesSettlementAllegementRemovalAdviceV04 struct {

	// Provides transaction type and identification information.
	AccountServicerTransactionIdentification *iso20022.SettlementTypeAndIdentification18 `xml:"AcctSvcrTxId"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification14 `xml:"MktInfrstrctrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails74 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementAllegementRemovalAdvice to an account owner to acknowledge that a previously sent allegement is no longer outstanding, because the alleged party sent its instruction. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddAccountOwner ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddAccountServicerTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV04) AddAccountServicerTransactionIdentification() *iso20022.SettlementTypeAndIdentification18

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementAllegementRemovalAdviceV04) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification14

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddSupplementaryData ¶

func (*SecuritiesSettlementAllegementRemovalAdviceV04) AddTransactionDetails ¶

type SecuritiesSettlementConditionModificationStatusAdvice002V07 ¶

type SecuritiesSettlementConditionModificationStatusAdvice002V07 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification16 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails16 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus58Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdvice002V07) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV01 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementConditionModificationStatusAdvice message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification13Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails1 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus5Choice `xml:"PrcgSts"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage A SecuritiesSettlementConditionsModificatioRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate) - provide a third party with a copy of a message for information (the sub-function of the message is Copy) - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddExtension ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddIdentification ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddMessageOriginator ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddMessageRecipient ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV01) AddSafekeepingAccount ¶

type SecuritiesSettlementConditionModificationStatusAdviceV02 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV02 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails6 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus14Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV02) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV03 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV03 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails8 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus18Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV03) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV04 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV04 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails11 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus18Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV04) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV05 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV05 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails13 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus18Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV05) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV06 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV06 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification1 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails13 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus44Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV06) AddSupplementaryData ¶

type SecuritiesSettlementConditionModificationStatusAdviceV07 ¶

type SecuritiesSettlementConditionModificationStatusAdviceV07 struct {

	// Identification of the SecuritiesSettlementConditionsModificationRequest.
	RequestReference *iso20022.Identification14 `xml:"ReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	RequestDetails *iso20022.RequestDetails15 `xml:"ReqDtls,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus50Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesSettlementConditionsModificationStatusAdvice to an account owner to advise the status of a modification request previously instructed by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage A SecuritiesSettlementConditionsModificationRequest may contain requests on multiple transactions. However, one SecuritiesSettlementConditionsModificationStatusAdvice must be sent per transaction modified unless the SecuritiesSettlementConditionsModificationRequest is rejected as a whole. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddAccountOwner ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddProcessingStatus ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddRequestDetails ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddRequestReference ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionModificationStatusAdviceV07) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequest002V06 ¶

type SecuritiesSettlementConditionsModificationRequest002V06 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails16 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

func (*SecuritiesSettlementConditionsModificationRequest002V06) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequest002V06) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequest002V06) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequest002V06) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequest002V06) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequest002V07 ¶

type SecuritiesSettlementConditionsModificationRequest002V07 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification119 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails16 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

func (*SecuritiesSettlementConditionsModificationRequest002V07) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequest002V07) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequest002V07) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequest002V07) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequest002V07) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV01 ¶

type SecuritiesSettlementConditionsModificationRequestV01 struct {

	// Information that unambiguously identifies a SettlementConditionModification transaction and a SecuritiesSettlementConditionsModificationRequest message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification13Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails1 `xml:"ReqDtls"`

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information. The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionsModificationRequestV01) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddExtension ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddIdentification ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddMessageOriginator ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddMessageRecipient ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV01) AddSafekeepingAccount ¶

type SecuritiesSettlementConditionsModificationRequestV02 ¶

type SecuritiesSettlementConditionsModificationRequestV02 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails6 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information. The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionsModificationRequestV02) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV02) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV02) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV02) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV02) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV03 ¶

type SecuritiesSettlementConditionsModificationRequestV03 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails8 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information. The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionsModificationRequestV03) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV03) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV03) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV03) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV03) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV04 ¶

type SecuritiesSettlementConditionsModificationRequestV04 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails11 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information. The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionsModificationRequestV04) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV04) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV04) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV04) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV05 ¶

type SecuritiesSettlementConditionsModificationRequestV05 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails13 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementConditionsModificationRequestV05) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV05) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV05) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV05) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV05) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV06 ¶

type SecuritiesSettlementConditionsModificationRequestV06 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails15 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

func (*SecuritiesSettlementConditionsModificationRequestV06) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV06) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV06) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV06) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV06) AddSupplementaryData ¶

type SecuritiesSettlementConditionsModificationRequestV07 ¶

type SecuritiesSettlementConditionsModificationRequestV07 struct {

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Details of the request.
	RequestDetails []*iso20022.RequestDetails15 `xml:"ReqDtls"`

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

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

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.

The account owner/servicer relationship may be: - a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement: - a global custodian which has an account with its local agent (sub-custodian), or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

In markets where this applies (eg, securities market infrastructures with no pre-settlement matching process), it is used by a party to approve, cancel or reject a transaction instructed by the counterparty.

This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.

func (*SecuritiesSettlementConditionsModificationRequestV07) AddAccountOwner ¶

func (*SecuritiesSettlementConditionsModificationRequestV07) AddAdditionalInformation ¶

func (*SecuritiesSettlementConditionsModificationRequestV07) AddRequestDetails ¶

func (*SecuritiesSettlementConditionsModificationRequestV07) AddSafekeepingAccount ¶

func (*SecuritiesSettlementConditionsModificationRequestV07) AddSupplementaryData ¶

type SecuritiesSettlementTransactionAllegementNotification002V05 ¶

type SecuritiesSettlementTransactionAllegementNotification002V05 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters15 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification16 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount49 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails34 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails108 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties32 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection71 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties31 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotification002V05) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification16

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V05) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotification002V05) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotification002V06 ¶

type SecuritiesSettlementTransactionAllegementNotification002V06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters15 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification16 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount58 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails34 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails131 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties32 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection71 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties31 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotification002V06) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification16

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotification002V06) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotification002V06) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotificationV01 ¶

type SecuritiesSettlementTransactionAllegementNotificationV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransaction and a SecuritiesSettlementTransactionAllegementNotification message as known by the account servicer.
	Identification *iso20022.TransactionAndDocumentIdentification1 `xml:"Id"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters2 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount3 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails1 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails5 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddExtension ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV01) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV01) AddTradeDetails ¶

type SecuritiesSettlementTransactionAllegementNotificationV02 ¶

type SecuritiesSettlementTransactionAllegementNotificationV02 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters2 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount13 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails7 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails25 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties11 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection22 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties11 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV02) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV02) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV02) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotificationV03 ¶

type SecuritiesSettlementTransactionAllegementNotificationV03 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters2 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount27 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails7 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails49 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties11 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection22 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties11 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV03) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV03) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV03) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotificationV04 ¶

type SecuritiesSettlementTransactionAllegementNotificationV04 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters2 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification1 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount27 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails7 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails49 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties11 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection22 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties11 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV04) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV04) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV04) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotificationV05 ¶

type SecuritiesSettlementTransactionAllegementNotificationV05 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters12 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification14 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount42 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails29 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails99 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties25 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection48 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties28 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV05) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification14

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV05) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV05) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionAllegementNotificationV06 ¶

type SecuritiesSettlementTransactionAllegementNotificationV06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters12 `xml:"SttlmTpAndAddtlParams"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Identification14 `xml:"MktInfrstrctrTxId,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount42 `xml:"QtyAndAcctDtls"`

	// Details of the closing of the securities financing transaction.
	SecuritiesFinancingDetails *iso20022.SecuritiesFinancingTransactionDetails29 `xml:"SctiesFincgDtls,omitempty"`

	// 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.SettlementDetails125 `xml:"SttlmParams"`

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

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

	// Specifies cash parties in the framework of a corporate action event.
	CashParties *iso20022.CashParties25 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection48 `xml:"SttlmAmt,omitempty"`

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

	// Other business parties relevant to the transaction.
	OtherBusinessParties *iso20022.OtherParties28 `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 An account servicer sends a SecuritiesSettlementTransactionAllegementNotification to an account owner to advise the account owner that a counterparty has alleged an instruction against the account owner's account at the account servicer and that the account servicer could not find the corresponding instruction of the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddCashParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV06) AddMarketInfrastructureTransactionIdentification() *iso20022.Identification14

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddSecuritiesFinancingDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionAllegementNotificationV06) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionAllegementNotificationV06) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionConfirmation002V06 ¶

type SecuritiesSettlementTransactionConfirmation002V06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages50 `xml:"Lnkgs,omitempty"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters27 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount51 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails110 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionConfirmation002V06) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmation002V06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionConfirmation002V06) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionConfirmation002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesSettlementTransactionConfirmation002V06) AddLinkages ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmation002V07 ¶

type SecuritiesSettlementTransactionConfirmation002V07 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages50 `xml:"Lnkgs,omitempty"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters31 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount57 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails134 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionConfirmation002V07) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmation002V07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionConfirmation002V07) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionConfirmation002V07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesSettlementTransactionConfirmation002V07) AddLinkages ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmation002V07) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV01 ¶

type SecuritiesSettlementTransactionConfirmationV01 struct {

	// Information that unambiguously identifies an SecuritiesSettlementTransactionConfirmation message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification1 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters2 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount2 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails6 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionConfirmationV01) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV01) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionConfirmationV01) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionConfirmationV01) AddDeliveringSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesSettlementTransactionConfirmationV01) AddExtension ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionConfirmationV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesSettlementTransactionConfirmationV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV01) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction1

func (*SecuritiesSettlementTransactionConfirmationV01) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV01) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV02 ¶

type SecuritiesSettlementTransactionConfirmationV02 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification9 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters2 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount15 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails24 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionConfirmationV02) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV02) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionConfirmationV02) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionConfirmationV02) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV02) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionConfirmationV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV02) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV03 ¶

type SecuritiesSettlementTransactionConfirmationV03 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters12 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount28 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails45 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionConfirmationV03) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV03) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionConfirmationV03) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionConfirmationV03) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV03) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionConfirmationV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV03) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV04 ¶

type SecuritiesSettlementTransactionConfirmationV04 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters17 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount28 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails45 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionConfirmationV04) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV04) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionConfirmationV04) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionConfirmationV04) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV04) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionConfirmationV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV04) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV05 ¶

type SecuritiesSettlementTransactionConfirmationV05 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters17 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount28 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails70 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection36 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionConfirmationV05) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV05) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionConfirmationV05) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionConfirmationV05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV05) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionConfirmationV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV05) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV06 ¶

type SecuritiesSettlementTransactionConfirmationV06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages41 `xml:"Lnkgs,omitempty"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters22 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount41 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails90 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionConfirmationV06) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionConfirmationV06) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionConfirmationV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionConfirmationV06) AddLinkages ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesSettlementTransactionConfirmationV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionConfirmationV07 ¶

type SecuritiesSettlementTransactionConfirmationV07 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages41 `xml:"Lnkgs,omitempty"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters29 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount41 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails128 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionConfirmation to an account owner to confirm the partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionConfirmationV07) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionConfirmationV07) AddCashParties ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionConfirmationV07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionConfirmationV07) AddLinkages ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionConfirmationV07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesSettlementTransactionConfirmationV07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionConfirmationV07) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionCounterpartyResponse002V02 ¶

type SecuritiesSettlementTransactionCounterpartyResponse002V02 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentification7 `xml:"TxId"`

	// Provides the response status related to an allegement or a counterparty's instruction.
	ResponseStatus *iso20022.ResponseStatus8Choice `xml:"RspnSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails92 `xml:"TxDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionCounterpartyResponse to advise the account servicer that: - the allegement received is either rejected (that is counterparty's transaction is unknown) or accepted (i.e. either the allegement was passed to the client or the transaction is know with or without mismatches) - the modification or cancellation request sent by the counterparty for a matched transaction is affirmed or not. The account servicer will therefore proceed or not with the counterparty's request to modify or cancel the transaction. The account servicer may be a central securities depository or another settlement market infrastructure acting on behalf of their participants The account owner may be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionCounterpartyResponse002V02) AddResponseStatus ¶

func (*SecuritiesSettlementTransactionCounterpartyResponse002V02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionCounterpartyResponse002V02) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionCounterpartyResponse002V02) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionCounterpartyResponseV01 ¶

type SecuritiesSettlementTransactionCounterpartyResponseV01 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentification2 `xml:"TxId"`

	// Provides the response status related to an allegement or a counterparty's instruction.
	ResponseStatus *iso20022.ResponseStatus3Choice `xml:"RspnSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails40 `xml:"TxDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionCounterpartyResponse to advise the account servicer that: - the allegement received is either rejected (that is counterparty's transaction is unknown) or accepted (i.e. either the allegement was passed to the client or the transaction is know with or without mismatches) - the modification or cancellation request sent by the counterparty for a matched transaction is affirmed or not. The account servicer will therefore proceed or not with the counterparty's request to modify or cancel the transaction. The account servicer may be a central securities depository or another settlement market infrastructure acting on behalf of their participants The account owner may be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionCounterpartyResponseV01) AddResponseStatus ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV01) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV01) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV01) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionCounterpartyResponseV02 ¶

type SecuritiesSettlementTransactionCounterpartyResponseV02 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentification6 `xml:"TxId"`

	// Provides the response status related to an allegement or a counterparty's instruction.
	ResponseStatus *iso20022.ResponseStatus6Choice `xml:"RspnSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails82 `xml:"TxDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionCounterpartyResponse to advise the account servicer that: - the allegement received is either rejected (that is counterparty's transaction is unknown) or accepted (i.e. either the allegement was passed to the client or the transaction is know with or without mismatches) - the modification or cancellation request sent by the counterparty for a matched transaction is affirmed or not. The account servicer will therefore proceed or not with the counterparty's request to modify or cancel the transaction. The account servicer may be a central securities depository or another settlement market infrastructure acting on behalf of their participants The account owner may be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionCounterpartyResponseV02) AddResponseStatus ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV02) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionCounterpartyResponseV02) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionGenerationNotification002V06 ¶

type SecuritiesSettlementTransactionGenerationNotification002V06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount47 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails111 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection60 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason6 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason29 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotification002V06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotification002V07 ¶

type SecuritiesSettlementTransactionGenerationNotification002V07 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount56 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails137 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection60 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason6 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason29 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotification002V07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotification002V07) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV01 ¶

type SecuritiesSettlementTransactionGenerationNotificationV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransaction and a SecuritiesSettlementTransactionGenerationNotification message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification1 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount1 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails1 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason1 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason3 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV01) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddExtension ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV01) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV02 ¶

type SecuritiesSettlementTransactionGenerationNotificationV02 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification10 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount17 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails22 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason1 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason3 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV02) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV02) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV03 ¶

type SecuritiesSettlementTransactionGenerationNotificationV03 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails42 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason1 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason12 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV03) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV03) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV04 ¶

type SecuritiesSettlementTransactionGenerationNotificationV04 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails42 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason1 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason12 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV04) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV04) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV05 ¶

type SecuritiesSettlementTransactionGenerationNotificationV05 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails67 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection36 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason3 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason19 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV05) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV05) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV06 ¶

type SecuritiesSettlementTransactionGenerationNotificationV06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails101 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection46 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason5 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason28 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionGenerationNotificationV07 ¶

type SecuritiesSettlementTransactionGenerationNotificationV07 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails []*iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails120 `xml:"SttlmParams"`

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection46 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Specifies the reason why the transaction was generated.
	GeneratedReason []*iso20022.GeneratedReason5 `xml:"GnrtdRsn,omitempty"`

	// Status and reason of the transaction.
	StatusAndReason *iso20022.StatusAndReason28 `xml:"StsAndRsn,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionGenerationNotification to an account owner to advise the account owner of a securities settlement transaction that has been generated/created by the account servicer for the account owner. The reason for creation can range from the automatic transformation of pending settlement instructions following a corporate event to the recovery of an account owner transactions' database initiated by its account servicer. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionGenerationNotificationV07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddCashParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddGeneratedReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddLinkages ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddStatusAndReason ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionGenerationNotificationV07) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionInstruction002V06 ¶

type SecuritiesSettlementTransactionInstruction002V06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters16 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount47 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails112 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection60 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionInstruction002V06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstruction002V06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionInstruction002V06) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionInstruction002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesSettlementTransactionInstruction002V06) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstruction002V06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V06) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstruction002V06) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstruction002V07 ¶

type SecuritiesSettlementTransactionInstruction002V07 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters20 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount56 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails132 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties30 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection60 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionInstruction002V07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstruction002V07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionInstruction002V07) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionInstruction002V07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*SecuritiesSettlementTransactionInstruction002V07) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstruction002V07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstruction002V07) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstruction002V07) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV01 ¶

type SecuritiesSettlementTransactionInstructionV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransaction and a SecuritiesSettlementTransactionInstruction message as known by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.TransactionAndDocumentIdentification1 `xml:"Id"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters1 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount1 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails1 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionInstructionV01) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV01) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionInstructionV01) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV01) AddDeliveringSettlementParties() *iso20022.SettlementParties5

func (*SecuritiesSettlementTransactionInstructionV01) AddExtension ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesSettlementTransactionInstructionV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV01) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV01) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction1

func (*SecuritiesSettlementTransactionInstructionV01) AddTradeDetails ¶

type SecuritiesSettlementTransactionInstructionV02 ¶

type SecuritiesSettlementTransactionInstructionV02 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters1 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount17 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails22 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionInstructionV02) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV02) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionInstructionV02) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV02) AddDeliveringSettlementParties() *iso20022.SettlementParties11

func (*SecuritiesSettlementTransactionInstructionV02) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionInstructionV02) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV02) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionInstructionV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV02) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV02) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV02) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV03 ¶

type SecuritiesSettlementTransactionInstructionV03 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters1 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails42 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties8 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionInstructionV03) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV03) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionInstructionV03) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV03) AddDeliveringSettlementParties() *iso20022.SettlementParties11

func (*SecuritiesSettlementTransactionInstructionV03) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionInstructionV03) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV03) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionInstructionV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV03) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV03) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV03) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV04 ¶

type SecuritiesSettlementTransactionInstructionV04 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters9 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails42 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection2 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionInstructionV04) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV04) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionInstructionV04) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV04) AddDeliveringSettlementParties() *iso20022.SettlementParties11

func (*SecuritiesSettlementTransactionInstructionV04) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionInstructionV04) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV04) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionInstructionV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV04) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV04) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV04) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV05 ¶

type SecuritiesSettlementTransactionInstructionV05 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters9 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount25 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails67 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties17 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection36 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionInstructionV05) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV05) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionInstructionV05) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV05) AddDeliveringSettlementParties() *iso20022.SettlementParties11

func (*SecuritiesSettlementTransactionInstructionV05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionInstructionV05) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV05) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction4

func (*SecuritiesSettlementTransactionInstructionV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV05) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV05) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV06 ¶

type SecuritiesSettlementTransactionInstructionV06 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters11 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails93 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection46 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionInstructionV06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionInstructionV06) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV06) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesSettlementTransactionInstructionV06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionInstructionV06) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV06) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesSettlementTransactionInstructionV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV06) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV06) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionInstructionV07 ¶

type SecuritiesSettlementTransactionInstructionV07 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Provides settlement type and identification information.
	SettlementTypeAndAdditionalParameters *iso20022.SettlementTypeAndAdditionalParameters19 `xml:"SttlmTpAndAddtlParams"`

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

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

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount39 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails119 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties26 `xml:"CshPties,omitempty"`

	// Total amount of money to be paid or received in exchange for the securities.
	SettlementAmount *iso20022.AmountAndDirection46 `xml:"SttlmAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account owner sends a SecuritiesSettlementTransactionInstruction to an account servicer to instruct the receipt or delivery of financial instruments with or without payment, physically or by book-entry. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manages a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct the settlement of transactions to a central securities depository or another settlement market infrastructure.

Usage The instruction may be linked to other settlement instructions, for example, for a turnaround or back-to-back, or other transactions, for example, foreign exchange deal, using the linkage functionality. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionInstructionV07) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV07) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionInstructionV07) AddCashParties ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddDeliveringSettlementParties ¶

func (s *SecuritiesSettlementTransactionInstructionV07) AddDeliveringSettlementParties() *iso20022.SettlementParties36

func (*SecuritiesSettlementTransactionInstructionV07) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV07) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionInstructionV07) AddLinkages ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddNumberCounts ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddSettlementAmount ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddSettlementTypeAndAdditionalParameters ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddStandingSettlementInstructionDetails ¶

func (s *SecuritiesSettlementTransactionInstructionV07) AddStandingSettlementInstructionDetails() *iso20022.StandingSettlementInstruction11

func (*SecuritiesSettlementTransactionInstructionV07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionInstructionV07) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionInstructionV07) SetTransactionIdentification ¶

func (s *SecuritiesSettlementTransactionInstructionV07) SetTransactionIdentification(value string)

type SecuritiesSettlementTransactionModificationRequest002V04 ¶

type SecuritiesSettlementTransactionModificationRequest002V04 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails85 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType22Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequest002V04) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequest002V04) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequest002V05 ¶

type SecuritiesSettlementTransactionModificationRequest002V05 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails101 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType26Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequest002V05) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequest002V05) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	ModificationRequestReference *iso20022.Identification16 `xml:"ModReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications37 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ModificationProcessingStatus *iso20022.ModificationProcessingStatus8Choice `xml:"ModPrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails84 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be: - a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants - an custodian acting as an accounting and/or settlement agent.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddAccountOwner ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddModificationProcessingStatus ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddModificationRequestReference ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdvice002V04) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV01 ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV01 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	ModificationRequestReference *iso20022.Identification1 `xml:"ModReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications18 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ModificationProcessingStatus *iso20022.ModificationProcessingStatus2Choice `xml:"ModPrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails45 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be: - a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants - an custodian acting as an accounting and/or settlement agent.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddAccountOwner ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddModificationProcessingStatus ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddModificationRequestReference ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddSafekeepingAccount ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV01) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV02 ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV02 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	ModificationRequestReference *iso20022.Identification1 `xml:"ModReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications25 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ModificationProcessingStatus *iso20022.ModificationProcessingStatus2Choice `xml:"ModPrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails45 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be: - a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants - an custodian acting as an accounting and/or settlement agent.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddAccountOwner ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddModificationProcessingStatus ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddModificationRequestReference ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddSafekeepingAccount ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV02) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV03 ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV03 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	ModificationRequestReference *iso20022.Identification1 `xml:"ModReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications25 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ModificationProcessingStatus *iso20022.ModificationProcessingStatus4Choice `xml:"ModPrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails45 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be: - a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants - an custodian acting as an accounting and/or settlement agent.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddAccountOwner ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddModificationProcessingStatus ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddModificationRequestReference ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddSafekeepingAccount ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV03) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV04 ¶

type SecuritiesSettlementTransactionModificationRequestStatusAdviceV04 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	ModificationRequestReference *iso20022.Identification14 `xml:"ModReqRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications33 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ModificationProcessingStatus *iso20022.ModificationProcessingStatus7Choice `xml:"ModPrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails81 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionModificationRequestStatusAdvice to an account owner to advise the status of a SecuritiesSettlementModificationRequest message previously sent by the account owner. The account servicer may be: - a central securities depository or another settlement market infrastructure managing securities settlement transactions on behalf of their participants - an custodian acting as an accounting and/or settlement agent.

Usage The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddAccountOwner ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddModificationProcessingStatus ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddModificationRequestReference ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddSafekeepingAccount ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestStatusAdviceV04) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionModificationRequestV01 ¶

type SecuritiesSettlementTransactionModificationRequestV01 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails41 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType5Choice `xml:"UpdTp"`
}

Scope An account owner sends a SecuritiesSettlementTransactionModificationRequest to an account servicer to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction. The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent. Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestV01) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestV01) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequestV02 ¶

type SecuritiesSettlementTransactionModificationRequestV02 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails41 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType9Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be:

- a central securities depository participant which has an account with a central securities depository or a market infrastructure

- an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestV02) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestV02) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequestV03 ¶

type SecuritiesSettlementTransactionModificationRequestV03 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails64 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType11Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionModificationRequestV03) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestV03) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequestV04 ¶

type SecuritiesSettlementTransactionModificationRequestV04 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails76 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType14Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequestV04) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestV04) AddUpdateType ¶

type SecuritiesSettlementTransactionModificationRequestV05 ¶

type SecuritiesSettlementTransactionModificationRequestV05 struct {

	// Identifies the details of the transaction that is being modified.
	ModifiedTransactionDetails *iso20022.TransactionDetails76 `xml:"ModfdTxDtls"`

	// Specifies the type of update requested.
	UpdateType []*iso20022.UpdateType25Choice `xml:"UpdTp"`
}

Scope This message is sent by an account owner to an account servicer.

The account owner will generally be: - a central securities depository participant which has an account with a central securities depository or a market infrastructure - an investment manager which has an account with a custodian acting as accounting and/or settlement agent.

It is used to request the modification of non core business data (matching or non-matching) information in a pending or settled instruction. It can also be used for the enrichment of an incomplete transaction.

Usage The modification must only contain the data to be modified. The message may also be used to: - re-send a message sent by the account owner to the account servicer, - provide a third party with a copy of a message being sent by the account owner for information, - re-send to a third party a copy of a message being sent by the account owner for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionModificationRequestV05) AddModifiedTransactionDetails ¶

func (*SecuritiesSettlementTransactionModificationRequestV05) AddUpdateType ¶

type SecuritiesSettlementTransactionReversalAdvice002V05 ¶

type SecuritiesSettlementTransactionReversalAdvice002V05 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification16 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters28 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount51 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails110 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties32 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdvice002V05) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V05) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdvice002V06 ¶

type SecuritiesSettlementTransactionReversalAdvice002V06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification24 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification16 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters32 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification20 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount57 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails134 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties32 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection60 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters5 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdvice002V06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters5

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddFinancialInstrumentIdentification ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdvice002V06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV01 ¶

type SecuritiesSettlementTransactionReversalAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransactionReversalAdvice message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification1 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification1 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters4 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification11 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount2 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails6 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties3 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV01) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddExtension ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV01) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV02 ¶

type SecuritiesSettlementTransactionReversalAdviceV02 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification9 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification1 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters4 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount15 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails26 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties9 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV02) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV02) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV03 ¶

type SecuritiesSettlementTransactionReversalAdviceV03 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification1 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters14 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount28 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails45 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties9 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection2 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV03) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV03) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV04 ¶

type SecuritiesSettlementTransactionReversalAdviceV04 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification15 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification1 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters14 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification14 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount28 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails70 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties9 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection36 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters1 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV04) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters1

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddFinancialInstrumentIdentification ¶

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

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV04) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV05 ¶

type SecuritiesSettlementTransactionReversalAdviceV05 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification14 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters23 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount41 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails90 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties25 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV05) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV05) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV05) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionReversalAdviceV06 ¶

type SecuritiesSettlementTransactionReversalAdviceV06 struct {

	// Provides transaction type and identification information.
	TransactionIdentificationDetails *iso20022.SettlementTypeAndIdentification19 `xml:"TxIdDtls"`

	// Reference to the unambiguous identification of the confirmation as per the account servicer.
	ConfirmationReference *iso20022.Identification14 `xml:"ConfRef"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters30 `xml:"AddtlParams,omitempty"`

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

	// Financial instrument representing a sum of rights of the investor vis-a-vis the issuer.
	FinancialInstrumentIdentification *iso20022.SecurityIdentification19 `xml:"FinInstrmId"`

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

	// Details related to the account and quantity involved in the transaction.
	QuantityAndAccountDetails *iso20022.QuantityAndAccount41 `xml:"QtyAndAcctDtls"`

	// 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.SettlementDetails128 `xml:"SttlmParams"`

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

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

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

	// Cash parties involved in the transaction if different for the securities settlement parties.
	CashParties *iso20022.CashParties25 `xml:"CshPties,omitempty"`

	// Amount effectively settled and which will be credited to/debited from the account owner's cash account. It may differ from the instructed settlement amount based on market tolerance level.
	SettledAmount *iso20022.AmountAndDirection46 `xml:"SttldAmt,omitempty"`

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

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

	// Provides information required for the registration or physical settlement.
	AdditionalPhysicalOrRegistrationDetails *iso20022.RegistrationParameters4 `xml:"AddtlPhysOrRegnDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionReversalAdvice to an account owner to reverse the confirmation of a partial or full delivery or receipt of financial instruments, free or against of payment, physically or by book-entry. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddAdditionalParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddAdditionalPhysicalOrRegistrationDetails ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV06) AddAdditionalPhysicalOrRegistrationDetails() *iso20022.RegistrationParameters4

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddCashParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddConfirmationReference ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddDeliveringSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddFinancialInstrumentAttributes ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddFinancialInstrumentIdentification ¶

func (s *SecuritiesSettlementTransactionReversalAdviceV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddOtherAmounts ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddOtherBusinessParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddQuantityAndAccountDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddReceivingSettlementParties ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddSettledAmount ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddSettlementParameters ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddStandingSettlementInstructionDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddTradeDetails ¶

func (*SecuritiesSettlementTransactionReversalAdviceV06) AddTransactionIdentificationDetails ¶

type SecuritiesSettlementTransactionStatusAdvice002V07 ¶

type SecuritiesSettlementTransactionStatusAdvice002V07 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications38 `xml:"TxId"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages50 `xml:"Lnkgs,omitempty"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus63Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus32Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus32Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus22Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails87 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddLinkages ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V07) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdvice002V08 ¶

type SecuritiesSettlementTransactionStatusAdvice002V08 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications38 `xml:"TxId"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages50 `xml:"Lnkgs,omitempty"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus63Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus32Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus32Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus22Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails100 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddLinkages ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdvice002V08) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV01 ¶

type SecuritiesSettlementTransactionStatusAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransactionStatusAdvice message as know by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications2 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus1Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus2Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus2Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails5 `xml:"TxDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddExtension ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddIdentification ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddMessageOriginator ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddMessageRecipient ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV01) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV02 ¶

type SecuritiesSettlementTransactionStatusAdviceV02 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications9 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus1Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus2Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus2Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails22 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV02) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV03 ¶

type SecuritiesSettlementTransactionStatusAdviceV03 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications16 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus19Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus7Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus7Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus7Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails36 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV03) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV04 ¶

type SecuritiesSettlementTransactionStatusAdviceV04 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications16 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus19Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus7Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus7Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus7Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails53 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV04) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV05 ¶

type SecuritiesSettlementTransactionStatusAdviceV05 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications16 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus37Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus19Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus19Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus7Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails61 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV05) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV06 ¶

type SecuritiesSettlementTransactionStatusAdviceV06 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications16 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus37Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus19Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus19Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus7Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails70 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV06) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV07 ¶

type SecuritiesSettlementTransactionStatusAdviceV07 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications31 `xml:"TxId"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages41 `xml:"Lnkgs,omitempty"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus48Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus24Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus24Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus17Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails79 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddLinkages ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV07) AddTransactionIdentification ¶

type SecuritiesSettlementTransactionStatusAdviceV08 ¶

type SecuritiesSettlementTransactionStatusAdviceV08 struct {

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications31 `xml:"TxId"`

	// Link to another transaction - provided for information only.
	Linkages *iso20022.Linkages41 `xml:"Lnkgs,omitempty"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.ProcessingStatus48Choice `xml:"PrcgSts,omitempty"`

	// Provides the matching status of an instruction as per the account servicer based on an allegement. At this time no matching took place on the market (at the CSD/ICSD).
	InferredMatchingStatus *iso20022.MatchingStatus24Choice `xml:"IfrrdMtchgSts,omitempty"`

	// Provides the matching status of the instruction.
	MatchingStatus *iso20022.MatchingStatus24Choice `xml:"MtchgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus17Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails97 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends a SecuritiesSettlementTransactionStatusAdvice to an account owner to advise the status of a securities settlement transaction instruction previously sent by the account owner or the status of a settlement transaction existing in the books of the servicer for the account of the owner. The status may be a processing, pending processing, internal matching, matching and/or settlement status. The status advice may be sent as a response to the request of the account owner or not. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddInferredMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddLinkages ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddMatchingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddProcessingStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddSettlementStatus ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddSupplementaryData ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddTransactionDetails ¶

func (*SecuritiesSettlementTransactionStatusAdviceV08) AddTransactionIdentification ¶

type SecuritiesStatusOrStatementQueryStatusAdvice002V04 ¶

type SecuritiesStatusOrStatementQueryStatusAdvice002V04 struct {

	// Unambiguous identification of the query as per the account owner.
	QueryDetails *iso20022.DocumentIdentification48 `xml:"QryDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	StatusOrStatementRequested *iso20022.StatusOrStatement8Choice `xml:"StsOrStmtReqd,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus64Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddAccountOwner ¶

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddProcessingStatus ¶

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddQueryDetails ¶

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddSafekeepingAccount ¶

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddStatusOrStatementRequested ¶

func (*SecuritiesStatusOrStatementQueryStatusAdvice002V04) AddSupplementaryData ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV01 ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesStatusOrStatementQueryStatusAdvice message as know by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Unambiguous identification of the query as per the account owner.
	QueryReference *iso20022.Identification1 `xml:"QryRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification13Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	StatusOrStatementRequested *iso20022.StatusOrStatement1Choice `xml:"StsOrStmtReqd,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus4Choice `xml:"PrcgSts"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddAccountOwner ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddExtension ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddIdentification ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddMessageOriginator ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddMessageRecipient ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddProcessingStatus ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddQueryReference ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddSafekeepingAccount ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV01) AddStatusOrStatementRequested ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV02 ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV02 struct {

	// Unambiguous identification of the query as per the account owner.
	QueryReference *iso20022.Identification1 `xml:"QryRef"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	StatusOrStatementRequested *iso20022.StatusOrStatement3Choice `xml:"StsOrStmtReqd,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus4Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddAccountOwner ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddProcessingStatus ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddQueryReference ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddSafekeepingAccount ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddStatusOrStatementRequested ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV02) AddSupplementaryData ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV03 ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV03 struct {

	// Unambiguous identification of the query as per the account owner.
	QueryDetails *iso20022.DocumentIdentification24 `xml:"QryDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	StatusOrStatementRequested *iso20022.StatusOrStatement5Choice `xml:"StsOrStmtReqd,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus22Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddAccountOwner ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddProcessingStatus ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddQueryDetails ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddSafekeepingAccount ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddStatusOrStatementRequested ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV03) AddSupplementaryData ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV04 ¶

type SecuritiesStatusOrStatementQueryStatusAdviceV04 struct {

	// Unambiguous identification of the query as per the account owner.
	QueryDetails *iso20022.DocumentIdentification30 `xml:"QryDtls"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct,omitempty"`

	// Details of the request.
	StatusOrStatementRequested *iso20022.StatusOrStatement7Choice `xml:"StsOrStmtReqd,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus55Choice `xml:"PrcgSts"`

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

Scope An account servicer sends a SecuritiesStatusOrStatementQueryStatusAdvice to an account owner to advise the status of a status query or statement query previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddAccountOwner ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddProcessingStatus ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddQueryDetails ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddSafekeepingAccount ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddStatusOrStatementRequested ¶

func (*SecuritiesStatusOrStatementQueryStatusAdviceV04) AddSupplementaryData ¶

type SecuritiesTransactionCancellationRequest002V05 ¶

type SecuritiesTransactionCancellationRequest002V05 struct {

	// Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account).
	AccountOwnerTransactionIdentification *iso20022.References60Choice `xml:"AcctOwnrTxId"`

	// Unambiguous identification of the transaction as known by the account servicer.
	AccountServicerTransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"AcctSvcrTxId,omitempty"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"MktInfrstrctrTxId,omitempty"`

	// Message Reference identifying the Processor of the transaction.
	ProcessorTransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"PrcrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount30 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails83 `xml:"TxDtls,omitempty"`

	// Specifies the reason of the cancellation.
	CancellationReason *iso20022.CancellationReason19 `xml:"CxlRsn,omitempty"`

	// Specifies whether an associated FX should be cancelled.
	FXCancellation *iso20022.FXCancellation4Choice `xml:"FxCxl,omitempty"`

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

Scope An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure.

Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionCancellationRequest002V05) AddAccountOwner ¶

func (*SecuritiesTransactionCancellationRequest002V05) AddAccountOwnerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequest002V05) AddAccountOwnerTransactionIdentification() *iso20022.References60Choice

func (*SecuritiesTransactionCancellationRequest002V05) AddCancellationReason ¶

func (*SecuritiesTransactionCancellationRequest002V05) AddFXCancellation ¶

func (*SecuritiesTransactionCancellationRequest002V05) AddSafekeepingAccount ¶

func (*SecuritiesTransactionCancellationRequest002V05) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequest002V05) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequest002V05) SetAccountServicerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequest002V05) SetAccountServicerTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequest002V05) SetMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequest002V05) SetMarketInfrastructureTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequest002V05) SetProcessorTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequest002V05) SetProcessorTransactionIdentification(value string)

type SecuritiesTransactionCancellationRequestStatusAdvice002V05 ¶

type SecuritiesTransactionCancellationRequestStatusAdvice002V05 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification16 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications39 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus65Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails88 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionCancellationRequestStatusAdvice002V05) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdvice002V05) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdvice002V05) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestStatusAdvice002V05) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdvice002V05) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV01 ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV01 struct {

	// Information that unambiguously identifies a SecuritiesTransactionCancellationRequestStatusAdvice message as know by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification1 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications4 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus2Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails4 `xml:"TxDtls,omitempty"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddExtension ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddIdentification ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddMessageOriginator ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddMessageRecipient ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV01) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV02 ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV02 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification1 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications11 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus13Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails30 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer. using the relevant elements in the Business Application Header. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestStatusAdviceV02) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV02) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV02) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV02) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV02) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV03 ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV03 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification1 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications17 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus20Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails30 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestStatusAdviceV03) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV03) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV03) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV03) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV03) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV04 ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV04 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification1 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications17 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus45Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails30 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestStatusAdviceV04) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV04) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV04) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV04) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV04) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV05 ¶

type SecuritiesTransactionCancellationRequestStatusAdviceV05 struct {

	// Reference to the unambiguous identification of the cancellation request as per the account owner.
	CancellationRequestReference *iso20022.Identification14 `xml:"CxlReqRef"`

	// Unambiguous identification of the transaction as known by the account servicer.
	TransactionIdentification *iso20022.TransactionIdentifications30 `xml:"TxId,omitempty"`

	// Provides details on the processing status of the request.
	ProcessingStatus *iso20022.ProcessingStatus54Choice `xml:"PrcgSts"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails80 `xml:"TxDtls,omitempty"`

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

Scope An account servicer sends an SecuritiesTransactionCancellationRequestStatusAdvice to an account owner to advise the status of a securities transaction cancellation request previously sent by the account owner. The account servicer/owner relationship may be: - a central securities depository or another settlement market infrastructure acting on behalf of their participants - an agent (sub-custodian) acting on behalf of their global custodian customer, or - a custodian acting on behalf of an investment management institution or a broker/dealer.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionCancellationRequestStatusAdviceV05) AddCancellationRequestReference ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV05) AddProcessingStatus ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV05) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV05) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestStatusAdviceV05) AddTransactionIdentification ¶

type SecuritiesTransactionCancellationRequestV01 ¶

type SecuritiesTransactionCancellationRequestV01 struct {

	// Information that unambiguously identifies a SecuritiesTransactionCancellationRequest message as know by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Details of the transaction.
	Details *iso20022.TransactionDetails11 `xml:"Dtls"`

	// Party that originated the message, if other than the sender
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure. Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestV01) AddDetails ¶

func (*SecuritiesTransactionCancellationRequestV01) AddExtension ¶

func (*SecuritiesTransactionCancellationRequestV01) AddIdentification ¶

func (*SecuritiesTransactionCancellationRequestV01) AddMessageOriginator ¶

func (*SecuritiesTransactionCancellationRequestV01) AddMessageRecipient ¶

type SecuritiesTransactionCancellationRequestV02 ¶

type SecuritiesTransactionCancellationRequestV02 struct {

	// Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account).
	AccountOwnerTransactionIdentification *iso20022.References2Choice `xml:"AcctOwnrTxId"`

	// Unambiguous identification of the transaction as known by the account servicer.
	AccountServicerTransactionIdentification *iso20022.Max35Text `xml:"AcctSvcrTxId,omitempty"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Max35Text `xml:"MktInfrstrctrTxId,omitempty"`

	// Message Reference identifying the Processor of the transaction.
	ProcessorTransactionIdentification *iso20022.Max35Text `xml:"PrcrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails29 `xml:"TxDtls,omitempty"`

	// Specifies whether an associated FX should be cancelled.
	FXCancellation *iso20022.FXCancellation1Choice `xml:"FxCxl,omitempty"`

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

Scope An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure. Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification. The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestV02) AddAccountOwner ¶

func (*SecuritiesTransactionCancellationRequestV02) AddAccountOwnerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV02) AddAccountOwnerTransactionIdentification() *iso20022.References2Choice

func (*SecuritiesTransactionCancellationRequestV02) AddFXCancellation ¶

func (*SecuritiesTransactionCancellationRequestV02) AddSafekeepingAccount ¶

func (*SecuritiesTransactionCancellationRequestV02) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestV02) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestV02) SetAccountServicerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV02) SetAccountServicerTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV02) SetMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV02) SetMarketInfrastructureTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV02) SetProcessorTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV02) SetProcessorTransactionIdentification(value string)

type SecuritiesTransactionCancellationRequestV03 ¶

type SecuritiesTransactionCancellationRequestV03 struct {

	// Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account).
	AccountOwnerTransactionIdentification *iso20022.References2Choice `xml:"AcctOwnrTxId"`

	// Unambiguous identification of the transaction as known by the account servicer.
	AccountServicerTransactionIdentification *iso20022.Max35Text `xml:"AcctSvcrTxId,omitempty"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Max35Text `xml:"MktInfrstrctrTxId,omitempty"`

	// Message Reference identifying the Processor of the transaction.
	ProcessorTransactionIdentification *iso20022.Max35Text `xml:"PrcrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails29 `xml:"TxDtls,omitempty"`

	// Specifies whether an associated FX should be cancelled.
	FXCancellation *iso20022.FXCancellation1Choice `xml:"FxCxl,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 version is identical to the previous version. It was created automatically during the 2011/2012 maintenance cycle, at the same time as new versions of other Settlement and Reconciliation messages that were truly impacted by change requests. This should not have been the case. In future releases, SWIFT will ensure that a new version of a message is not created if identical to the previous version. An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure.

Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestV03) AddAccountOwner ¶

func (*SecuritiesTransactionCancellationRequestV03) AddAccountOwnerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV03) AddAccountOwnerTransactionIdentification() *iso20022.References2Choice

func (*SecuritiesTransactionCancellationRequestV03) AddFXCancellation ¶

func (*SecuritiesTransactionCancellationRequestV03) AddSafekeepingAccount ¶

func (*SecuritiesTransactionCancellationRequestV03) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestV03) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestV03) SetAccountServicerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV03) SetAccountServicerTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV03) SetMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV03) SetMarketInfrastructureTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV03) SetProcessorTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV03) SetProcessorTransactionIdentification(value string)

type SecuritiesTransactionCancellationRequestV04 ¶

type SecuritiesTransactionCancellationRequestV04 struct {

	// Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account).
	AccountOwnerTransactionIdentification *iso20022.References2Choice `xml:"AcctOwnrTxId"`

	// Unambiguous identification of the transaction as known by the account servicer.
	AccountServicerTransactionIdentification *iso20022.Max35Text `xml:"AcctSvcrTxId,omitempty"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Max35Text `xml:"MktInfrstrctrTxId,omitempty"`

	// Message Reference identifying the Processor of the transaction.
	ProcessorTransactionIdentification *iso20022.Max35Text `xml:"PrcrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails28 `xml:"TxDtls,omitempty"`

	// Specifies whether an associated FX should be cancelled.
	FXCancellation *iso20022.FXCancellation1Choice `xml:"FxCxl,omitempty"`

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

Scope

An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure.

Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionCancellationRequestV04) AddAccountOwner ¶

func (*SecuritiesTransactionCancellationRequestV04) AddAccountOwnerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV04) AddAccountOwnerTransactionIdentification() *iso20022.References2Choice

func (*SecuritiesTransactionCancellationRequestV04) AddFXCancellation ¶

func (*SecuritiesTransactionCancellationRequestV04) AddSafekeepingAccount ¶

func (*SecuritiesTransactionCancellationRequestV04) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestV04) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestV04) SetAccountServicerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV04) SetAccountServicerTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV04) SetMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV04) SetMarketInfrastructureTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV04) SetProcessorTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV04) SetProcessorTransactionIdentification(value string)

type SecuritiesTransactionCancellationRequestV05 ¶

type SecuritiesTransactionCancellationRequestV05 struct {

	// Unambiguous identification of the transaction as known by the account owner (or the instructing party managing the account).
	AccountOwnerTransactionIdentification *iso20022.References45Choice `xml:"AcctOwnrTxId"`

	// Unambiguous identification of the transaction as known by the account servicer.
	AccountServicerTransactionIdentification *iso20022.Max35Text `xml:"AcctSvcrTxId,omitempty"`

	// Identification of a transaction assigned by a market infrastructure other than a central securities depository, for example, Target2-Securities.
	MarketInfrastructureTransactionIdentification *iso20022.Max35Text `xml:"MktInfrstrctrTxId,omitempty"`

	// Message Reference identifying the Processor of the transaction.
	ProcessorTransactionIdentification *iso20022.Max35Text `xml:"PrcrTxId,omitempty"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount19 `xml:"SfkpgAcct"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.TransactionDetails74 `xml:"TxDtls,omitempty"`

	// Specifies the reason of the cancellation.
	CancellationReason *iso20022.CancellationReason13 `xml:"CxlRsn,omitempty"`

	// Specifies whether an associated FX should be cancelled.
	FXCancellation *iso20022.FXCancellation3Choice `xml:"FxCxl,omitempty"`

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

Scope An account owner sends a SecuritiesTransactionCancellationRequest to an account servicer to request the cancellation of a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository ot another settlement market infrastructure.

Usage The transaction may be: - a securities settlement transaction - an intra-position movement - a securities financing transaction The instruction cannot be: - a securities settlement conditions modification (another transaction processing command should be sent to reverse a processing change previously requested). - a securities financing modification The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionCancellationRequestV05) AddAccountOwner ¶

func (*SecuritiesTransactionCancellationRequestV05) AddAccountOwnerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV05) AddAccountOwnerTransactionIdentification() *iso20022.References45Choice

func (*SecuritiesTransactionCancellationRequestV05) AddCancellationReason ¶

func (*SecuritiesTransactionCancellationRequestV05) AddFXCancellation ¶

func (*SecuritiesTransactionCancellationRequestV05) AddSafekeepingAccount ¶

func (*SecuritiesTransactionCancellationRequestV05) AddSupplementaryData ¶

func (*SecuritiesTransactionCancellationRequestV05) AddTransactionDetails ¶

func (*SecuritiesTransactionCancellationRequestV05) SetAccountServicerTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV05) SetAccountServicerTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV05) SetMarketInfrastructureTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV05) SetMarketInfrastructureTransactionIdentification(value string)

func (*SecuritiesTransactionCancellationRequestV05) SetProcessorTransactionIdentification ¶

func (s *SecuritiesTransactionCancellationRequestV05) SetProcessorTransactionIdentification(value string)

type SecuritiesTransactionStatusQuery002V04 ¶

type SecuritiesTransactionStatusQuery002V04 struct {

	// Description of the status advise requested.
	StatusAdviceRequested *iso20022.DocumentNumber15 `xml:"StsAdvcReqd"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification109 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount27 `xml:"SfkpgAcct"`

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

Scope An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionStatusQuery002V04) AddAccountOwner ¶

func (*SecuritiesTransactionStatusQuery002V04) AddSafekeepingAccount ¶

func (*SecuritiesTransactionStatusQuery002V04) AddStatusAdviceRequested ¶

func (s *SecuritiesTransactionStatusQuery002V04) AddStatusAdviceRequested() *iso20022.DocumentNumber15

func (*SecuritiesTransactionStatusQuery002V04) AddSupplementaryData ¶

type SecuritiesTransactionStatusQueryV01 ¶

type SecuritiesTransactionStatusQueryV01 struct {

	// Information that unambiguously identifies a SecuritiesTransactionStatusQuery message as know by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Description of the status advise requested.
	StatusAdviceRequested *iso20022.DocumentNumber2 `xml:"StsAdvcReqd"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification13Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

	// Party that originated the message, if other than the sender.
	MessageOriginator *iso20022.PartyIdentification10Choice `xml:"MsgOrgtr,omitempty"`

	// Party that is the final destination of the message, if other than the receiver.
	MessageRecipient *iso20022.PartyIdentification10Choice `xml:"MsgRcpt,omitempty"`

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

Scope An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent (the sub-function of the message is Duplicate), - provide a third party with a copy of a message for information (the sub-function of the message is Copy), - re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionStatusQueryV01) AddAccountOwner ¶

func (*SecuritiesTransactionStatusQueryV01) AddExtension ¶

func (*SecuritiesTransactionStatusQueryV01) AddIdentification ¶

func (*SecuritiesTransactionStatusQueryV01) AddMessageOriginator ¶

func (*SecuritiesTransactionStatusQueryV01) AddMessageRecipient ¶

func (*SecuritiesTransactionStatusQueryV01) AddSafekeepingAccount ¶

func (*SecuritiesTransactionStatusQueryV01) AddStatusAdviceRequested ¶

func (s *SecuritiesTransactionStatusQueryV01) AddStatusAdviceRequested() *iso20022.DocumentNumber2

type SecuritiesTransactionStatusQueryV02 ¶

type SecuritiesTransactionStatusQueryV02 struct {

	// Description of the status advise requested.
	StatusAdviceRequested *iso20022.DocumentNumber5 `xml:"StsAdvcReqd"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

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

Scope An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure. Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information. using the relevant elements in the Business Application Header. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionStatusQueryV02) AddAccountOwner ¶

func (*SecuritiesTransactionStatusQueryV02) AddSafekeepingAccount ¶

func (*SecuritiesTransactionStatusQueryV02) AddStatusAdviceRequested ¶

func (s *SecuritiesTransactionStatusQueryV02) AddStatusAdviceRequested() *iso20022.DocumentNumber5

func (*SecuritiesTransactionStatusQueryV02) AddSupplementaryData ¶

type SecuritiesTransactionStatusQueryV03 ¶

type SecuritiesTransactionStatusQueryV03 struct {

	// Description of the status advise requested.
	StatusAdviceRequested *iso20022.DocumentNumber9 `xml:"StsAdvcReqd"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification36Choice `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount13 `xml:"SfkpgAcct"`

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

Scope This version is identical to the previous version. It was created automatically during the 2011/2012 maintenance cycle, at the same time as new versions of other Settlement and Reconciliation messages that were truly impacted by change requests. This should not have been the case. In future releases, SWIFT will ensure that a new version of a message is not created if identical to the previous version. An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

func (*SecuritiesTransactionStatusQueryV03) AddAccountOwner ¶

func (*SecuritiesTransactionStatusQueryV03) AddSafekeepingAccount ¶

func (*SecuritiesTransactionStatusQueryV03) AddStatusAdviceRequested ¶

func (s *SecuritiesTransactionStatusQueryV03) AddStatusAdviceRequested() *iso20022.DocumentNumber9

func (*SecuritiesTransactionStatusQueryV03) AddSupplementaryData ¶

type SecuritiesTransactionStatusQueryV04 ¶

type SecuritiesTransactionStatusQueryV04 struct {

	// Description of the status advise requested.
	StatusAdviceRequested *iso20022.DocumentNumber12 `xml:"StsAdvcReqd"`

	// Party that legally owns the account.
	AccountOwner *iso20022.PartyIdentification98 `xml:"AcctOwnr,omitempty"`

	// Account to or from which a securities entry is made.
	SafekeepingAccount *iso20022.SecuritiesAccount24 `xml:"SfkpgAcct"`

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

Scope An account owner sends a SecuritiesTransactionStatusQuery to an account servicer to request a status on a securities transaction. The account owner/servicer relationship may be: - a global custodian which has an account with a local custodian, or - an investment management institution which manage a fund account opened at a custodian, or - a broker which has an account with a custodian, or - a central securities depository participant which has an account with a central securities depository, or - a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure, or - a central counterparty or a stock exchange or a trade matching utility which need to instruct to a central securities depository or another settlement market infrastructure.

Usage The message may also be used to: - re-send a message previously sent, - provide a third party with a copy of a message for information, - re-send to a third party a copy of a message for information using the relevant elements in the Business Application Header.

func (*SecuritiesTransactionStatusQueryV04) AddAccountOwner ¶

func (*SecuritiesTransactionStatusQueryV04) AddSafekeepingAccount ¶

func (*SecuritiesTransactionStatusQueryV04) AddStatusAdviceRequested ¶

func (s *SecuritiesTransactionStatusQueryV04) AddStatusAdviceRequested() *iso20022.DocumentNumber12

func (*SecuritiesTransactionStatusQueryV04) AddSupplementaryData ¶

type TransferCancellationStatusReport ¶

type TransferCancellationStatusReport struct {

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

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

	// Status of the transfer cancellation instruction.
	StatusReport *iso20022.CancellationStatusAndReason `xml:"StsRpt"`
}

Scope The TransferCancellationStatusReport message is sent by an executing party to the instructing party. The message gives the status of a transfer cancellation instruction that was previously sent by the instructing party. Usage The TransferCancellationStatusReport message is sent by an executing party to the instructing party. The message can be used to report that either - the cancellation has been acted upon or - the cancellation is rejected. In both cases, the reason must be specified using either a code or unstructured information.

func (*TransferCancellationStatusReport) AddOtherReference ¶

func (*TransferCancellationStatusReport) AddRelatedReference ¶

func (*TransferCancellationStatusReport) AddStatusReport ¶

type TransferCancellationStatusReportV02 ¶

type TransferCancellationStatusReportV02 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 the linked message sent in a proprietary way or the reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Status of the transfer cancellation instruction.
	StatusReport *iso20022.CancellationStatusAndReason2 `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 An executing party, eg, a transfer agent, sends the TransferCancellationStatusReport message to the instructing party, eg, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction. Usage The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request. The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported: - the transfer cancellation is accepted, or, - the transfer cancellation has been sent to the next party, or, - the transfer cancellation is complete and the reason for the status, - the transfer cancellation pending and the reason for the status, - the transfer cancellation is rejected and the reason for the status.

func (*TransferCancellationStatusReportV02) AddExtension ¶

func (*TransferCancellationStatusReportV02) AddMessageIdentification ¶

func (*TransferCancellationStatusReportV02) AddOtherReference ¶

func (*TransferCancellationStatusReportV02) AddRelatedReference ¶

func (*TransferCancellationStatusReportV02) AddStatusReport ¶

type TransferCancellationStatusReportV03 ¶

type TransferCancellationStatusReportV03 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference2 `xml:"CtrPtyRef,omitempty"`

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

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

	// Status of the transfer cancellation instruction.
	StatusReport *iso20022.CancellationStatusAndReason2 `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 An executing party, for example, a transfer agent, sends the TransferCancellationStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction. Usage The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request. The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported: - the transfer cancellation is accepted, or, - the transfer cancellation has been sent to the next party, or, - the transfer cancellation is complete and the reason for the status, - the transfer cancellation pending and the reason for the status, - the transfer cancellation is rejected and the reason for the status.

func (*TransferCancellationStatusReportV03) AddCounterpartyReference ¶

func (t *TransferCancellationStatusReportV03) AddCounterpartyReference() *iso20022.AdditionalReference2

func (*TransferCancellationStatusReportV03) AddExtension ¶

func (*TransferCancellationStatusReportV03) AddMessageIdentification ¶

func (*TransferCancellationStatusReportV03) AddOtherReference ¶

func (*TransferCancellationStatusReportV03) AddRelatedReference ¶

func (*TransferCancellationStatusReportV03) AddStatusReport ¶

type TransferCancellationStatusReportV04 ¶

type TransferCancellationStatusReportV04 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference2 `xml:"CtrPtyRef,omitempty"`

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

	// Status of the transfer cancellation instruction.
	StatusReport *iso20022.CancellationStatusAndReason2 `xml:"StsRpt"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferCancellationStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction. Usage The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request. The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported: - the transfer cancellation is accepted, or, - the transfer cancellation has been sent to the next party, or, - the transfer cancellation is complete and the reason for the status, - the transfer cancellation pending and the reason for the status, - the transfer cancellation is rejected and the reason for the status.

func (*TransferCancellationStatusReportV04) AddCounterpartyReference ¶

func (t *TransferCancellationStatusReportV04) AddCounterpartyReference() *iso20022.AdditionalReference2

func (*TransferCancellationStatusReportV04) AddExtension ¶

func (*TransferCancellationStatusReportV04) AddMarketPracticeVersion ¶

func (*TransferCancellationStatusReportV04) AddMessageIdentification ¶

func (*TransferCancellationStatusReportV04) AddReference ¶

func (*TransferCancellationStatusReportV04) AddStatusReport ¶

type TransferCancellationStatusReportV05 ¶

type TransferCancellationStatusReportV05 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference7 `xml:"CtrPtyRef,omitempty"`

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

	// Status of the transfer cancellation instruction.
	StatusReport *iso20022.CancellationStatusAndReason3 `xml:"StsRpt"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferCancellationStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer cancellation instruction. Usage The TransferCancellationStatusReport message is used to report on the status of a transfer in or transfer out cancellation request. The reference of the transfer instruction for which the cancellation status is reported is identified in TransferReference. The message identification of the transfer cancellation request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. The message identification of the transfer instruction request message in which the transfer instruction was conveyed may also be quoted in RelatedReference. One of the following statuses can be reported: - the transfer cancellation is accepted, or, - the transfer cancellation has been sent to the next party, or, - the transfer cancellation is complete and the reason for the status, - the transfer cancellation pending and the reason for the status, - the transfer cancellation is rejected and the reason for the status.

func (*TransferCancellationStatusReportV05) AddCounterpartyReference ¶

func (t *TransferCancellationStatusReportV05) AddCounterpartyReference() *iso20022.AdditionalReference7

func (*TransferCancellationStatusReportV05) AddExtension ¶

func (*TransferCancellationStatusReportV05) AddMarketPracticeVersion ¶

func (*TransferCancellationStatusReportV05) AddMessageIdentification ¶

func (*TransferCancellationStatusReportV05) AddReference ¶

func (*TransferCancellationStatusReportV05) AddStatusReport ¶

type TransferInCancellationInstruction ¶

type TransferInCancellationInstruction struct {

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

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

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

	// The transfer in request message to cancel.
	TransferInToBeCancelled *iso20022.TransferIn2 `xml:"TrfInToBeCanc,omitempty"`
}

Scope TheTransferInCancellationInstruction message is sent by an instructing party, or an instructing party's designated agent, to the executing party. This message is used to request the cancellation of a TransferInInstruction that was previously sent by the instructing party. Usage TheTransferInCancellationInstruction message is sent by an instructing party to request cancellation of a previously sent TransferInInstruction. This message must contain the reference of the message to be cancelled. The message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*TransferInCancellationInstruction) AddPoolReference ¶

func (*TransferInCancellationInstruction) AddPreviousReference ¶

func (*TransferInCancellationInstruction) AddRelatedReference ¶

func (*TransferInCancellationInstruction) AddTransferInToBeCancelled ¶

func (t *TransferInCancellationInstruction) AddTransferInToBeCancelled() *iso20022.TransferIn2

type TransferInCancellationRequestV02 ¶

type TransferInCancellationRequestV02 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 sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

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

	// Reference of the transfer to be cancelled.
	CancellationByReference *iso20022.TransferReference1 `xml:"CxlByRef,omitempty"`

	// The transfer in request message to cancel.
	CancellationByTransferInDetails *iso20022.TransferIn3 `xml:"CxlByTrfInDtls,omitempty"`

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

Scope An instructing party, eg, a transfer agent, sends the TransferInCancellationRequest message to the executing party, eg, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV02) AddCancellationByReference ¶

func (t *TransferInCancellationRequestV02) AddCancellationByReference() *iso20022.TransferReference1

func (*TransferInCancellationRequestV02) AddCancellationByTransferInDetails ¶

func (t *TransferInCancellationRequestV02) AddCancellationByTransferInDetails() *iso20022.TransferIn3

func (*TransferInCancellationRequestV02) AddCopyDetails ¶

func (*TransferInCancellationRequestV02) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV02) AddPoolReference ¶

func (*TransferInCancellationRequestV02) AddPreviousReference ¶

func (*TransferInCancellationRequestV02) AddRelatedReference ¶

type TransferInCancellationRequestV03 ¶

type TransferInCancellationRequestV03 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Reference of the transfer to be cancelled.
	CancellationByReference *iso20022.TransferReference1 `xml:"CxlByRef,omitempty"`

	// The transfer in request message to cancel.
	CancellationByTransferInDetails *iso20022.TransferIn5 `xml:"CxlByTrfInDtls,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, a transfer agent, sends the TransferInCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV03) AddCancellationByReference ¶

func (t *TransferInCancellationRequestV03) AddCancellationByReference() *iso20022.TransferReference1

func (*TransferInCancellationRequestV03) AddCancellationByTransferInDetails ¶

func (t *TransferInCancellationRequestV03) AddCancellationByTransferInDetails() *iso20022.TransferIn5

func (*TransferInCancellationRequestV03) AddCopyDetails ¶

func (*TransferInCancellationRequestV03) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV03) AddReferences ¶

type TransferInCancellationRequestV04 ¶

type TransferInCancellationRequestV04 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation *iso20022.Cancellation2Choice `xml:"Cxl"`

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

Scope An instructing party, for example, a transfer agent, sends the TransferInCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV04) AddCancellation ¶

func (*TransferInCancellationRequestV04) AddCopyDetails ¶

func (*TransferInCancellationRequestV04) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV04) AddReferences ¶

type TransferInCancellationRequestV05 ¶

type TransferInCancellationRequestV05 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation5Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a transfer agent, sends the TransferInCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV05) AddCancellation ¶

func (*TransferInCancellationRequestV05) AddCopyDetails ¶

func (*TransferInCancellationRequestV05) AddMarketPracticeVersion ¶

func (t *TransferInCancellationRequestV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInCancellationRequestV05) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV05) AddReferences ¶

type TransferInCancellationRequestV06 ¶

type TransferInCancellationRequestV06 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation9Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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, a transfer agent, sends the TransferInCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV06) AddCancellation ¶

func (*TransferInCancellationRequestV06) AddCopyDetails ¶

func (*TransferInCancellationRequestV06) AddMarketPracticeVersion ¶

func (t *TransferInCancellationRequestV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInCancellationRequestV06) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV06) AddReferences ¶

type TransferInCancellationRequestV07 ¶

type TransferInCancellationRequestV07 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References20 `xml:"Refs,omitempty"`

	// Function of the transfer-in, that is, whether the message is used as a request to cancel a previously sent instruction or as a cancellation of a previously sent advice and request for information. The absence of Function indicates the message is a request to cancel a previously sent instruction.
	Function *iso20022.TransferInFunction1Code `xml:"Fctn,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation10Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An instructing party, for example, a transfer agent, sends the TransferInCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferInInstruction. Usage The TransferInCancellationRequest message is used to request cancellation of a previously sent TransferInInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferInInstruction message in which the transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferInInstruction message by quoting its message identification in PreviousReference.

func (*TransferInCancellationRequestV07) AddCancellation ¶

func (*TransferInCancellationRequestV07) AddCopyDetails ¶

func (*TransferInCancellationRequestV07) AddMarketPracticeVersion ¶

func (t *TransferInCancellationRequestV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInCancellationRequestV07) AddMessageIdentification ¶

func (t *TransferInCancellationRequestV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInCancellationRequestV07) AddReferences ¶

func (*TransferInCancellationRequestV07) SetFunction ¶

func (t *TransferInCancellationRequestV07) SetFunction(value string)

type TransferInConfirmation ¶

type TransferInConfirmation struct {

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

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

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer4 `xml:"TrfDtls"`

	// Information related to the financial instrument received.
	FinancialInstrumentDetails *iso20022.FinancialInstrument3 `xml:"FinInstrmDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount10 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation2 `xml:"SttlmDtls"`

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

Scope TheTransferInConfirmation message is sent by an executing party to the instructing party or the instructing party's designated agent. This message is used to confirm the receipt of a financial instrument, free of payment, at a given date, from a specified party. This message can also be used to confirm the transfer a financial instrument from an own account or from a third party. Usage TheTransferInConfirmation message is used by an executing party to confirm to the instructing party receipt of a financial instrument, either from another account owned by the instructing party or from a third party.

func (*TransferInConfirmation) AddAccountDetails ¶

func (t *TransferInConfirmation) AddAccountDetails() *iso20022.InvestmentAccount10

func (*TransferInConfirmation) AddExtension ¶

func (t *TransferInConfirmation) AddExtension() *iso20022.Extension1

func (*TransferInConfirmation) AddFinancialInstrumentDetails ¶

func (t *TransferInConfirmation) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument3

func (*TransferInConfirmation) AddPoolReference ¶

func (t *TransferInConfirmation) AddPoolReference() *iso20022.AdditionalReference2

func (*TransferInConfirmation) AddPreviousReference ¶

func (t *TransferInConfirmation) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmation) AddRelatedReference ¶

func (t *TransferInConfirmation) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmation) AddSettlementDetails ¶

func (t *TransferInConfirmation) AddSettlementDetails() *iso20022.DeliverInformation2

func (*TransferInConfirmation) AddTransferDetails ¶

func (t *TransferInConfirmation) AddTransferDetails() *iso20022.Transfer4

type TransferInConfirmationV02 ¶

type TransferInConfirmationV02 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.AdditionalReference2 `xml:"RltdRef,omitempty"`

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

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer7 `xml:"TrfDtls"`

	// Information related to the financial instrument received.
	FinancialInstrumentDetails *iso20022.FinancialInstrument13 `xml:"FinInstrmDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation4 `xml:"SttlmDtls"`

	// 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, eg, a transfer agent, sends the TransferInConfirmation message to the instructing party, eg, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV02) AddAccountDetails ¶

func (t *TransferInConfirmationV02) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInConfirmationV02) AddCopyDetails ¶

func (*TransferInConfirmationV02) AddExtension ¶

func (t *TransferInConfirmationV02) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV02) AddFinancialInstrumentDetails ¶

func (t *TransferInConfirmationV02) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument13

func (*TransferInConfirmationV02) AddMessageIdentification ¶

func (t *TransferInConfirmationV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV02) AddPoolReference ¶

func (*TransferInConfirmationV02) AddPreviousReference ¶

func (t *TransferInConfirmationV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV02) AddRelatedReference ¶

func (t *TransferInConfirmationV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV02) AddSettlementDetails ¶

func (t *TransferInConfirmationV02) AddSettlementDetails() *iso20022.DeliverInformation4

func (*TransferInConfirmationV02) AddTransferDetails ¶

func (t *TransferInConfirmationV02) AddTransferDetails() *iso20022.Transfer7

type TransferInConfirmationV03 ¶

type TransferInConfirmationV03 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer18 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation6 `xml:"SttlmDtls"`

	// 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 TransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV03) AddAccountDetails ¶

func (t *TransferInConfirmationV03) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInConfirmationV03) AddCopyDetails ¶

func (*TransferInConfirmationV03) AddExtension ¶

func (t *TransferInConfirmationV03) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV03) AddMessageIdentification ¶

func (t *TransferInConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV03) AddPoolReference ¶

func (*TransferInConfirmationV03) AddPreviousReference ¶

func (t *TransferInConfirmationV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV03) AddRelatedReference ¶

func (t *TransferInConfirmationV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV03) AddSettlementDetails ¶

func (t *TransferInConfirmationV03) AddSettlementDetails() *iso20022.DeliverInformation6

func (*TransferInConfirmationV03) AddTransferDetails ¶

func (t *TransferInConfirmationV03) AddTransferDetails() *iso20022.Transfer18

func (*TransferInConfirmationV03) SetMasterReference ¶

func (t *TransferInConfirmationV03) SetMasterReference(value string)

type TransferInConfirmationV04 ¶

type TransferInConfirmationV04 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer26 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation11 `xml:"SttlmDtls,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 TransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV04) AddAccountDetails ¶

func (t *TransferInConfirmationV04) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInConfirmationV04) AddCopyDetails ¶

func (*TransferInConfirmationV04) AddExtension ¶

func (t *TransferInConfirmationV04) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV04) AddMessageIdentification ¶

func (t *TransferInConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV04) AddPoolReference ¶

func (*TransferInConfirmationV04) AddPreviousReference ¶

func (t *TransferInConfirmationV04) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV04) AddRelatedReference ¶

func (t *TransferInConfirmationV04) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV04) AddSettlementDetails ¶

func (t *TransferInConfirmationV04) AddSettlementDetails() *iso20022.DeliverInformation11

func (*TransferInConfirmationV04) AddTransferDetails ¶

func (t *TransferInConfirmationV04) AddTransferDetails() *iso20022.Transfer26

func (*TransferInConfirmationV04) SetMasterReference ¶

func (t *TransferInConfirmationV04) SetMasterReference(value string)

type TransferInConfirmationV05 ¶

type TransferInConfirmationV05 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer29 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation12 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV05) AddAccountDetails ¶

func (t *TransferInConfirmationV05) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferInConfirmationV05) AddCopyDetails ¶

func (*TransferInConfirmationV05) AddExtension ¶

func (t *TransferInConfirmationV05) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV05) AddMarketPracticeVersion ¶

func (t *TransferInConfirmationV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInConfirmationV05) AddMessageIdentification ¶

func (t *TransferInConfirmationV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV05) AddPoolReference ¶

func (*TransferInConfirmationV05) AddPreviousReference ¶

func (t *TransferInConfirmationV05) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV05) AddRelatedReference ¶

func (t *TransferInConfirmationV05) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV05) AddSettlementDetails ¶

func (t *TransferInConfirmationV05) AddSettlementDetails() *iso20022.DeliverInformation12

func (*TransferInConfirmationV05) AddTransferDetails ¶

func (t *TransferInConfirmationV05) AddTransferDetails() *iso20022.Transfer29

func (*TransferInConfirmationV05) SetMasterReference ¶

func (t *TransferInConfirmationV05) SetMasterReference(value string)

type TransferInConfirmationV06 ¶

type TransferInConfirmationV06 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer29 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation14 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV06) AddAccountDetails ¶

func (t *TransferInConfirmationV06) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferInConfirmationV06) AddCopyDetails ¶

func (*TransferInConfirmationV06) AddExtension ¶

func (t *TransferInConfirmationV06) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV06) AddMarketPracticeVersion ¶

func (t *TransferInConfirmationV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInConfirmationV06) AddMessageIdentification ¶

func (t *TransferInConfirmationV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV06) AddPoolReference ¶

func (*TransferInConfirmationV06) AddPreviousReference ¶

func (t *TransferInConfirmationV06) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV06) AddRelatedReference ¶

func (t *TransferInConfirmationV06) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInConfirmationV06) AddSettlementDetails ¶

func (t *TransferInConfirmationV06) AddSettlementDetails() *iso20022.DeliverInformation14

func (*TransferInConfirmationV06) AddTransferDetails ¶

func (t *TransferInConfirmationV06) AddTransferDetails() *iso20022.Transfer29

func (*TransferInConfirmationV06) SetMasterReference ¶

func (t *TransferInConfirmationV06) SetMasterReference(value string)

type TransferInConfirmationV07 ¶

type TransferInConfirmationV07 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.AdditionalReference6 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference6 `xml:"PrvsRef,omitempty"`

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

	// Function of the transfer in, that is, whether the transfer in message is used as a confirmation or as or an advice. The absence of Function indicates the message is a confirmation.
	Function *iso20022.TransferInFunction2Code `xml:"Fctn,omitempty"`

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer33 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument was received.
	AccountDetails *iso20022.InvestmentAccount56 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation17 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

	// 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 An executing party, for example, a transfer agent, sends the TransferInConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the receipt of a financial instrument, free of payment, on a given date, from a specified party. This message may also be used to confirm the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. This message may also be used as an advice, that is, the message is used to provide account information. Usage The TransferInConfirmation message is used to confirm receipt of a financial instrument, either from another account owned by the instructing party or from a third party. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferInInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferInConfirmationV07) AddAccountDetails ¶

func (t *TransferInConfirmationV07) AddAccountDetails() *iso20022.InvestmentAccount56

func (*TransferInConfirmationV07) AddCopyDetails ¶

func (*TransferInConfirmationV07) AddExtension ¶

func (t *TransferInConfirmationV07) AddExtension() *iso20022.Extension1

func (*TransferInConfirmationV07) AddMarketPracticeVersion ¶

func (t *TransferInConfirmationV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInConfirmationV07) AddMessageIdentification ¶

func (t *TransferInConfirmationV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInConfirmationV07) AddPoolReference ¶

func (*TransferInConfirmationV07) AddPreviousReference ¶

func (t *TransferInConfirmationV07) AddPreviousReference() *iso20022.AdditionalReference6

func (*TransferInConfirmationV07) AddRelatedReference ¶

func (t *TransferInConfirmationV07) AddRelatedReference() *iso20022.AdditionalReference6

func (*TransferInConfirmationV07) AddSettlementDetails ¶

func (t *TransferInConfirmationV07) AddSettlementDetails() *iso20022.DeliverInformation17

func (*TransferInConfirmationV07) AddTransferDetails ¶

func (t *TransferInConfirmationV07) AddTransferDetails() *iso20022.Transfer33

func (*TransferInConfirmationV07) SetFunction ¶

func (t *TransferInConfirmationV07) SetFunction(value string)

func (*TransferInConfirmationV07) SetMasterReference ¶

func (t *TransferInConfirmationV07) SetMasterReference(value string)

type TransferInInstruction ¶

type TransferInInstruction struct {

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

	// Reference of the linked message which was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer3 `xml:"TrfDtls"`

	// Information related to the financial instrument to be received.
	FinancialInstrumentDetails *iso20022.FinancialInstrument3 `xml:"FinInstrmDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount10 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation1 `xml:"SttlmDtls"`

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

Scope The TransferInInstruction message is sent by an instructing party, or an instructing party's designated agent, to the executing party. This message is used to instruct the receipt of a financial instrument, free of payment, at a given date, from a specified party. This message may also be used to instruct the receipt of a financial instrument from an own account or from a third party. Usage The TransferInInstruction message is used by an instructing party to instruct the executing party to receive a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstruction) AddAccountDetails ¶

func (t *TransferInInstruction) AddAccountDetails() *iso20022.InvestmentAccount10

func (*TransferInInstruction) AddExtension ¶

func (t *TransferInInstruction) AddExtension() *iso20022.Extension1

func (*TransferInInstruction) AddFinancialInstrumentDetails ¶

func (t *TransferInInstruction) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument3

func (*TransferInInstruction) AddPoolReference ¶

func (t *TransferInInstruction) AddPoolReference() *iso20022.AdditionalReference2

func (*TransferInInstruction) AddPreviousReference ¶

func (t *TransferInInstruction) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstruction) AddRelatedReference ¶

func (t *TransferInInstruction) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstruction) AddSettlementDetails ¶

func (t *TransferInInstruction) AddSettlementDetails() *iso20022.DeliverInformation1

func (*TransferInInstruction) AddTransferDetails ¶

func (t *TransferInInstruction) AddTransferDetails() *iso20022.Transfer3

type TransferInInstructionV02 ¶

type TransferInInstructionV02 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message which was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer5 `xml:"TrfDtls"`

	// Information related to the financial instrument to be received.
	FinancialInstrumentDetails *iso20022.FinancialInstrument13 `xml:"FinInstrmDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation3 `xml:"SttlmDtls"`

	// 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, eg, an investment manager or its authorised representative, sends the TransferInInstruction message to the executing party, eg, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV02) AddAccountDetails ¶

func (t *TransferInInstructionV02) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInInstructionV02) AddCopyDetails ¶

func (t *TransferInInstructionV02) AddCopyDetails() *iso20022.CopyInformation2

func (*TransferInInstructionV02) AddExtension ¶

func (t *TransferInInstructionV02) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV02) AddFinancialInstrumentDetails ¶

func (t *TransferInInstructionV02) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument13

func (*TransferInInstructionV02) AddMessageIdentification ¶

func (t *TransferInInstructionV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV02) AddPoolReference ¶

func (*TransferInInstructionV02) AddPreviousReference ¶

func (t *TransferInInstructionV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV02) AddRelatedReference ¶

func (t *TransferInInstructionV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV02) AddSettlementDetails ¶

func (t *TransferInInstructionV02) AddSettlementDetails() *iso20022.DeliverInformation3

func (*TransferInInstructionV02) AddTransferDetails ¶

func (t *TransferInInstructionV02) AddTransferDetails() *iso20022.Transfer5

type TransferInInstructionV03 ¶

type TransferInInstructionV03 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer15 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation5 `xml:"SttlmDtls"`

	// 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 TransferInInstruction message to the executing party, for example, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV03) AddAccountDetails ¶

func (t *TransferInInstructionV03) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInInstructionV03) AddCopyDetails ¶

func (t *TransferInInstructionV03) AddCopyDetails() *iso20022.CopyInformation2

func (*TransferInInstructionV03) AddExtension ¶

func (t *TransferInInstructionV03) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV03) AddMessageIdentification ¶

func (t *TransferInInstructionV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV03) AddPoolReference ¶

func (*TransferInInstructionV03) AddPreviousReference ¶

func (t *TransferInInstructionV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV03) AddRelatedReference ¶

func (t *TransferInInstructionV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV03) AddSettlementDetails ¶

func (t *TransferInInstructionV03) AddSettlementDetails() *iso20022.DeliverInformation5

func (*TransferInInstructionV03) AddTransferDetails ¶

func (t *TransferInInstructionV03) AddTransferDetails() *iso20022.Transfer15

func (*TransferInInstructionV03) SetMasterReference ¶

func (t *TransferInInstructionV03) SetMasterReference(value string)

type TransferInInstructionV04 ¶

type TransferInInstructionV04 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer21 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation9 `xml:"SttlmDtls,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 TransferInInstruction message to the executing party, for example, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV04) AddAccountDetails ¶

func (t *TransferInInstructionV04) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferInInstructionV04) AddCopyDetails ¶

func (t *TransferInInstructionV04) AddCopyDetails() *iso20022.CopyInformation2

func (*TransferInInstructionV04) AddExtension ¶

func (t *TransferInInstructionV04) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV04) AddMessageIdentification ¶

func (t *TransferInInstructionV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV04) AddPoolReference ¶

func (*TransferInInstructionV04) AddPreviousReference ¶

func (t *TransferInInstructionV04) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV04) AddRelatedReference ¶

func (t *TransferInInstructionV04) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV04) AddSettlementDetails ¶

func (t *TransferInInstructionV04) AddSettlementDetails() *iso20022.DeliverInformation9

func (*TransferInInstructionV04) AddTransferDetails ¶

func (t *TransferInInstructionV04) AddTransferDetails() *iso20022.Transfer21

func (*TransferInInstructionV04) SetMasterReference ¶

func (t *TransferInInstructionV04) SetMasterReference(value string)

type TransferInInstructionV05 ¶

type TransferInInstructionV05 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer21 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation13 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInInstruction message to the executing party, for example, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV05) AddAccountDetails ¶

func (t *TransferInInstructionV05) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferInInstructionV05) AddCopyDetails ¶

func (t *TransferInInstructionV05) AddCopyDetails() *iso20022.CopyInformation2

func (*TransferInInstructionV05) AddExtension ¶

func (t *TransferInInstructionV05) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV05) AddMarketPracticeVersion ¶

func (t *TransferInInstructionV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInInstructionV05) AddMessageIdentification ¶

func (t *TransferInInstructionV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV05) AddPoolReference ¶

func (*TransferInInstructionV05) AddPreviousReference ¶

func (t *TransferInInstructionV05) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV05) AddRelatedReference ¶

func (t *TransferInInstructionV05) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV05) AddSettlementDetails ¶

func (t *TransferInInstructionV05) AddSettlementDetails() *iso20022.DeliverInformation13

func (*TransferInInstructionV05) AddTransferDetails ¶

func (t *TransferInInstructionV05) AddTransferDetails() *iso20022.Transfer21

func (*TransferInInstructionV05) SetMasterReference ¶

func (t *TransferInInstructionV05) SetMasterReference(value string)

type TransferInInstructionV06 ¶

type TransferInInstructionV06 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer21 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation15 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInInstruction message to the executing party, for example, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV06) AddAccountDetails ¶

func (t *TransferInInstructionV06) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferInInstructionV06) AddCopyDetails ¶

func (t *TransferInInstructionV06) AddCopyDetails() *iso20022.CopyInformation2

func (*TransferInInstructionV06) AddExtension ¶

func (t *TransferInInstructionV06) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV06) AddMarketPracticeVersion ¶

func (t *TransferInInstructionV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInInstructionV06) AddMessageIdentification ¶

func (t *TransferInInstructionV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV06) AddPoolReference ¶

func (*TransferInInstructionV06) AddPreviousReference ¶

func (t *TransferInInstructionV06) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV06) AddRelatedReference ¶

func (t *TransferInInstructionV06) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferInInstructionV06) AddSettlementDetails ¶

func (t *TransferInInstructionV06) AddSettlementDetails() *iso20022.DeliverInformation15

func (*TransferInInstructionV06) AddTransferDetails ¶

func (t *TransferInInstructionV06) AddTransferDetails() *iso20022.Transfer21

func (*TransferInInstructionV06) SetMasterReference ¶

func (t *TransferInInstructionV06) SetMasterReference(value string)

type TransferInInstructionV07 ¶

type TransferInInstructionV07 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.AdditionalReference6 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference6 `xml:"PrvsRef,omitempty"`

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

	// Function of the transfer in, that is, whether the transfer in message is used as an instruction or an advice and request for information. The absence of Function indicates the message is an instruction.
	Function *iso20022.TransferInFunction1Code `xml:"Fctn,omitempty"`

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer32 `xml:"TrfDtls"`

	// Information related to the account into which the financial instrument is to be received.
	AccountDetails *iso20022.InvestmentAccount56 `xml:"AcctDtls"`

	// Information related to the delivering side of the transfer.
	SettlementDetails *iso20022.DeliverInformation16 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

	// 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 An instructing party, for example, an investment manager or its authorised representative, sends the TransferInInstruction message to the executing party, for example, a transfer agent, to instruct the receipt of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the receipt of a financial instrument, free of payment, from another of the instructing parties own accounts or from a third party. This message may also be used as an advice and request, that is, the message is used to inform the receiver to expect an unsolicited transfer in confirmation and to request account information for the transfer. Usage The TransferInInstruction message is used to instruct the receipt of a financial instrument from another account, either owned by the instructing party or by a third party.

func (*TransferInInstructionV07) AddAccountDetails ¶

func (t *TransferInInstructionV07) AddAccountDetails() *iso20022.InvestmentAccount56

func (*TransferInInstructionV07) AddCopyDetails ¶

func (t *TransferInInstructionV07) AddCopyDetails() *iso20022.CopyInformation4

func (*TransferInInstructionV07) AddExtension ¶

func (t *TransferInInstructionV07) AddExtension() *iso20022.Extension1

func (*TransferInInstructionV07) AddMarketPracticeVersion ¶

func (t *TransferInInstructionV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferInInstructionV07) AddMessageIdentification ¶

func (t *TransferInInstructionV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferInInstructionV07) AddPoolReference ¶

func (*TransferInInstructionV07) AddPreviousReference ¶

func (t *TransferInInstructionV07) AddPreviousReference() *iso20022.AdditionalReference6

func (*TransferInInstructionV07) AddRelatedReference ¶

func (t *TransferInInstructionV07) AddRelatedReference() *iso20022.AdditionalReference6

func (*TransferInInstructionV07) AddSettlementDetails ¶

func (t *TransferInInstructionV07) AddSettlementDetails() *iso20022.DeliverInformation16

func (*TransferInInstructionV07) AddTransferDetails ¶

func (t *TransferInInstructionV07) AddTransferDetails() *iso20022.Transfer32

func (*TransferInInstructionV07) SetFunction ¶

func (t *TransferInInstructionV07) SetFunction(value string)

func (*TransferInInstructionV07) SetMasterReference ¶

func (t *TransferInInstructionV07) SetMasterReference(value string)

type TransferInstructionStatusReport ¶

type TransferInstructionStatusReport struct {

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

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

	// Status of the transfer instruction.
	StatusReport *iso20022.TransferStatusAndReason `xml:"StsRpt"`
}

Scope The TransferInstructionStatusReport message is sent by an instructing party to the executing party. The instructing party may be an investor, a transfer agent, or an intermediary, etc. The executing party may be a transfer agent, or an intermediary, etc. This message gives the status of a transfer instruction, and can be used from the time the executing party receives the transfer instruction until its execution. Usage The TransferInstructionStatusReport message is sent by an executing party to the instructing party. The message can be used to report one of the following - the status of the transfer instruction (using a code)or - the repair status or - the unmatched status or - the rejection status or - the pending settlement status. Further information about repair, unmatched, rejected or pending settlement statuses must be specified using either codes or unstructured information.

func (*TransferInstructionStatusReport) AddOtherReference ¶

func (*TransferInstructionStatusReport) AddRelatedReference ¶

func (*TransferInstructionStatusReport) AddStatusReport ¶

type TransferInstructionStatusReportV02 ¶

type TransferInstructionStatusReportV02 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 the reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Status of the transfer instruction.
	StatusReport *iso20022.TransferStatusAndReason2 `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 An executing party, eg, a transfer agent, sends the TransferInstructionStatusReport message to the instructing party, eg, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction. Usage The TransferInstructionStatusReport message is used to report on the status of a transfer in or transfer out instruction. The reference of the transfer instruction for which the status is reported is identified in TransferReference. The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. 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 matched status, or, - a settled status, or, - a pending settlement status and the reason for the status, or, - an unmatched status and the reason for the status, or, - an in-repair status and the reason for the status, or, - a rejected status and the reason for the status, or, - a failed settlement status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancellation pending status and the reason for the status.

func (*TransferInstructionStatusReportV02) AddExtension ¶

func (*TransferInstructionStatusReportV02) AddMessageIdentification ¶

func (*TransferInstructionStatusReportV02) AddOtherReference ¶

func (*TransferInstructionStatusReportV02) AddRelatedReference ¶

func (*TransferInstructionStatusReportV02) AddStatusReport ¶

type TransferInstructionStatusReportV03 ¶

type TransferInstructionStatusReportV03 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference2 `xml:"CtrPtyRef,omitempty"`

	// 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 the reference of a system.
	OtherReference []*iso20022.AdditionalReference3 `xml:"OthrRef,omitempty"`

	// Status of the transfer instruction.
	StatusReport *iso20022.TransferStatusAndReason2 `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 An executing party, for example, a transfer agent, sends the TransferInstructionStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction. Usage The TransferInstructionStatusReport message is used to report on the status of a transfer in or transfer out instruction. The reference of the transfer instruction for which the status is reported is identified in TransferReference. The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. 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 matched status, or, - a settled status, or, - a pending settlement status and the reason for the status, or, - an unmatched status and the reason for the status, or, - an in-repair status and the reason for the status, or, - a rejected status and the reason for the status, or, - a failed settlement status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancellation pending status and the reason for the status.

func (*TransferInstructionStatusReportV03) AddCounterpartyReference ¶

func (t *TransferInstructionStatusReportV03) AddCounterpartyReference() *iso20022.AdditionalReference2

func (*TransferInstructionStatusReportV03) AddExtension ¶

func (*TransferInstructionStatusReportV03) AddMessageIdentification ¶

func (*TransferInstructionStatusReportV03) AddOtherReference ¶

func (*TransferInstructionStatusReportV03) AddRelatedReference ¶

func (*TransferInstructionStatusReportV03) AddStatusReport ¶

type TransferInstructionStatusReportV04 ¶

type TransferInstructionStatusReportV04 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference2 `xml:"CtrPtyRef,omitempty"`

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

	// Status of the transfer instruction.
	StatusReport *iso20022.TransferStatusAndReason3 `xml:"StsRpt"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInstructionStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction. Usage The TransferInstructionStatusReport message is used to report on the status of a transfer in or transfer out instruction. The reference of the transfer instruction for which the status is reported is identified in TransferReference. The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. 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 matched status, or, - a settled status, or, - a pending settlement status and the reason for the status, or, - an unmatched status and the reason for the status, or, - an in-repair status and the reason for the status, or, - a rejected status and the reason for the status, or, - a failed settlement status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancellation pending status and the reason for the status.

func (*TransferInstructionStatusReportV04) AddCounterpartyReference ¶

func (t *TransferInstructionStatusReportV04) AddCounterpartyReference() *iso20022.AdditionalReference2

func (*TransferInstructionStatusReportV04) AddExtension ¶

func (*TransferInstructionStatusReportV04) AddMarketPracticeVersion ¶

func (*TransferInstructionStatusReportV04) AddMessageIdentification ¶

func (*TransferInstructionStatusReportV04) AddReference ¶

func (*TransferInstructionStatusReportV04) AddStatusReport ¶

type TransferInstructionStatusReportV05 ¶

type TransferInstructionStatusReportV05 struct {

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

	// Unambiguous identification of the transfer allocated by the counterparty.
	CounterpartyReference *iso20022.AdditionalReference7 `xml:"CtrPtyRef,omitempty"`

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

	// Status of the transfer instruction.
	StatusReport *iso20022.TransferStatusAndReason4 `xml:"StsRpt"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferInstructionStatusReport message to the instructing party, for example, an investment manager or one of its authorised representatives to provide the status of a previously received transfer instruction. Usage The TransferInstructionStatusReport message is used to report on the status of a transfer in or transfer out instruction. The reference of the transfer instruction for which the status is reported is identified in TransferReference. The message identification of the transfer instruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference. 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 matched status, or, - a settled status, or, - a pending settlement status and the reason for the status, or, - an unmatched status and the reason for the status, or, - an in-repair status and the reason for the status, or, - a rejected status and the reason for the status, or, - a failed settlement status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancelled status and the reason for the status, or, - a cancellation pending status and the reason for the status.

func (*TransferInstructionStatusReportV05) AddCounterpartyReference ¶

func (t *TransferInstructionStatusReportV05) AddCounterpartyReference() *iso20022.AdditionalReference7

func (*TransferInstructionStatusReportV05) AddExtension ¶

func (*TransferInstructionStatusReportV05) AddMarketPracticeVersion ¶

func (*TransferInstructionStatusReportV05) AddMessageIdentification ¶

func (*TransferInstructionStatusReportV05) AddReference ¶

func (*TransferInstructionStatusReportV05) AddStatusReport ¶

type TransferOutCancellationInstruction ¶

type TransferOutCancellationInstruction struct {

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

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

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

	//
	TransferOutToBeCancelled *iso20022.TransferOut2 `xml:"TrfOutToBeCanc,omitempty"`
}

Scope The TransferOutCancellationInstruction message is sent by an instructing party or an instructing party's designated agent to the executing party. This message is used to request the cancellation of a TransferOutInstruction that was previously sent by the instructing party. Usage The TransferOutCancellationInstruction message is sent by an instructing party to request cancellation of a previously sent TransferOutInstruction. This message must contain the reference of the message to be cancelled. The message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*TransferOutCancellationInstruction) AddPoolReference ¶

func (*TransferOutCancellationInstruction) AddPreviousReference ¶

func (*TransferOutCancellationInstruction) AddRelatedReference ¶

func (*TransferOutCancellationInstruction) AddTransferOutToBeCancelled ¶

func (t *TransferOutCancellationInstruction) AddTransferOutToBeCancelled() *iso20022.TransferOut2

type TransferOutCancellationRequestV02 ¶

type TransferOutCancellationRequestV02 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 sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

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

	// Reference of the transfer to be cancelled.
	CancellationByReference *iso20022.TransferReference1 `xml:"CxlByRef,omitempty"`

	// The transfer out request message to cancel.
	CancellationByTransferOutDetails *iso20022.TransferOut5 `xml:"CxlByTrfOutDtls,omitempty"`

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

Scope An instructing party, eg, an investment manager or its authorised representative, sends the TransferOutCancellationRequest message to the executing party, eg, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV02) AddCancellationByReference ¶

func (t *TransferOutCancellationRequestV02) AddCancellationByReference() *iso20022.TransferReference1

func (*TransferOutCancellationRequestV02) AddCancellationByTransferOutDetails ¶

func (t *TransferOutCancellationRequestV02) AddCancellationByTransferOutDetails() *iso20022.TransferOut5

func (*TransferOutCancellationRequestV02) AddCopyDetails ¶

func (*TransferOutCancellationRequestV02) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV02) AddPoolReference ¶

func (*TransferOutCancellationRequestV02) AddPreviousReference ¶

func (*TransferOutCancellationRequestV02) AddRelatedReference ¶

type TransferOutCancellationRequestV03 ¶

type TransferOutCancellationRequestV03 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Reference of the transfer to be cancelled.
	CancellationByReference *iso20022.TransferReference1 `xml:"CxlByRef,omitempty"`

	// The transfer out request message to cancel.
	CancellationByTransferOutDetails *iso20022.TransferOut7 `xml:"CxlByTrfOutDtls,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 TransferOutCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV03) AddCancellationByReference ¶

func (t *TransferOutCancellationRequestV03) AddCancellationByReference() *iso20022.TransferReference1

func (*TransferOutCancellationRequestV03) AddCancellationByTransferOutDetails ¶

func (t *TransferOutCancellationRequestV03) AddCancellationByTransferOutDetails() *iso20022.TransferOut7

func (*TransferOutCancellationRequestV03) AddCopyDetails ¶

func (*TransferOutCancellationRequestV03) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV03) AddReferences ¶

type TransferOutCancellationRequestV04 ¶

type TransferOutCancellationRequestV04 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References11 `xml:"Refs"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation *iso20022.Cancellation1Choice `xml:"Cxl"`

	// 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 TransferOutCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV04) AddCancellation ¶

func (*TransferOutCancellationRequestV04) AddCopyDetails ¶

func (*TransferOutCancellationRequestV04) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV04) AddReferences ¶

type TransferOutCancellationRequestV05 ¶

type TransferOutCancellationRequestV05 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation4Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV05) AddCancellation ¶

func (*TransferOutCancellationRequestV05) AddCopyDetails ¶

func (*TransferOutCancellationRequestV05) AddMarketPracticeVersion ¶

func (t *TransferOutCancellationRequestV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutCancellationRequestV05) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV05) AddReferences ¶

type TransferOutCancellationRequestV06 ¶

type TransferOutCancellationRequestV06 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References15 `xml:"Refs,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation8Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV06) AddCancellation ¶

func (*TransferOutCancellationRequestV06) AddCopyDetails ¶

func (*TransferOutCancellationRequestV06) AddMarketPracticeVersion ¶

func (t *TransferOutCancellationRequestV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutCancellationRequestV06) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV06) AddReferences ¶

type TransferOutCancellationRequestV07 ¶

type TransferOutCancellationRequestV07 struct {

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

	// Reference to the transaction identifier issued by the counterparty. Building block may also be used to reference a previous transaction, or tie a set of messages together.
	References []*iso20022.References20 `xml:"Refs,omitempty"`

	// Choice between cancellation by reference or by transfer details.
	Cancellation []*iso20022.Cancellation12Choice `xml:"Cxl"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

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

Scope An instructing party, for example, an investment manager or its authorised representative, sends the TransferOutCancellationRequest message to the executing party, for example, a transfer agent, to request the cancellation of a previously sent TransferOutInstruction. Usage The TransferOutCancellationRequest message is used to request cancellation of a previously sent TransferOutInstruction. There are two ways to specify the transfer cancellation request. Either: - the transfer reference of the original transfer is quoted, or, - all the details of the original transfer (this includes TransferReference) are quoted but this is not recommended. The message identification of the TransferOutInstruction message in which the original transfer was conveyed may also be quoted in PreviousReference. It is also possible to request the cancellation of a TransferOutInstruction message by quoting its message identification in PreviousReference.

func (*TransferOutCancellationRequestV07) AddCancellation ¶

func (*TransferOutCancellationRequestV07) AddCopyDetails ¶

func (*TransferOutCancellationRequestV07) AddMarketPracticeVersion ¶

func (t *TransferOutCancellationRequestV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutCancellationRequestV07) AddMessageIdentification ¶

func (t *TransferOutCancellationRequestV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutCancellationRequestV07) AddReferences ¶

type TransferOutConfirmation ¶

type TransferOutConfirmation struct {

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

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

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer2 `xml:"TrfDtls"`

	// Information related to the financial instrument withdrawn.
	FinancialInstrumentDetails *iso20022.FinancialInstrument3 `xml:"FinInstrmDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount10 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation2 `xml:"SttlmDtls"`

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

Scope The TransferOutConfirmation message is sent by an executing party to the instructing party or the instructing party's designated agent. This message is used to confirm the delivery of a financial instrument, free of payment, at a given date, to a specified party. This message can be used to confirm the transfer of a financial instrument to an own account or to a third party. Usage The TransferOutConfirmation message is used by an executing party to confirm to the instructing party that the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place.

func (*TransferOutConfirmation) AddAccountDetails ¶

func (t *TransferOutConfirmation) AddAccountDetails() *iso20022.InvestmentAccount10

func (*TransferOutConfirmation) AddExtension ¶

func (t *TransferOutConfirmation) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmation) AddFinancialInstrumentDetails ¶

func (t *TransferOutConfirmation) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument3

func (*TransferOutConfirmation) AddPoolReference ¶

func (t *TransferOutConfirmation) AddPoolReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmation) AddPreviousReference ¶

func (t *TransferOutConfirmation) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmation) AddRelatedReference ¶

func (t *TransferOutConfirmation) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmation) AddSettlementDetails ¶

func (t *TransferOutConfirmation) AddSettlementDetails() *iso20022.ReceiveInformation2

func (*TransferOutConfirmation) AddTransferDetails ¶

func (t *TransferOutConfirmation) AddTransferDetails() *iso20022.Transfer2

type TransferOutConfirmationV02 ¶

type TransferOutConfirmationV02 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.AdditionalReference2 `xml:"RltdRef,omitempty"`

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

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer10 `xml:"TrfDtls"`

	// Information related to the financial instrument withdrawn.
	FinancialInstrumentDetails *iso20022.FinancialInstrument13 `xml:"FinInstrmDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation4 `xml:"SttlmDtls"`

	// 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, eg, a transfer agent, sends the TransferOutConfirmation message to the instructing party, eg, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV02) AddAccountDetails ¶

func (*TransferOutConfirmationV02) AddCopyDetails ¶

func (*TransferOutConfirmationV02) AddExtension ¶

func (t *TransferOutConfirmationV02) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV02) AddFinancialInstrumentDetails ¶

func (t *TransferOutConfirmationV02) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument13

func (*TransferOutConfirmationV02) AddMessageIdentification ¶

func (t *TransferOutConfirmationV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV02) AddPoolReference ¶

func (*TransferOutConfirmationV02) AddPreviousReference ¶

func (t *TransferOutConfirmationV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV02) AddRelatedReference ¶

func (t *TransferOutConfirmationV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV02) AddSettlementDetails ¶

func (t *TransferOutConfirmationV02) AddSettlementDetails() *iso20022.ReceiveInformation4

func (*TransferOutConfirmationV02) AddTransferDetails ¶

func (t *TransferOutConfirmationV02) AddTransferDetails() *iso20022.Transfer10

type TransferOutConfirmationV03 ¶

type TransferOutConfirmationV03 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer13 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation6 `xml:"SttlmDtls"`

	// 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 TransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV03) AddAccountDetails ¶

func (*TransferOutConfirmationV03) AddCopyDetails ¶

func (*TransferOutConfirmationV03) AddExtension ¶

func (t *TransferOutConfirmationV03) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV03) AddMessageIdentification ¶

func (t *TransferOutConfirmationV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV03) AddPoolReference ¶

func (*TransferOutConfirmationV03) AddPreviousReference ¶

func (t *TransferOutConfirmationV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV03) AddRelatedReference ¶

func (t *TransferOutConfirmationV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV03) AddSettlementDetails ¶

func (t *TransferOutConfirmationV03) AddSettlementDetails() *iso20022.ReceiveInformation6

func (*TransferOutConfirmationV03) AddTransferDetails ¶

func (t *TransferOutConfirmationV03) AddTransferDetails() *iso20022.Transfer13

func (*TransferOutConfirmationV03) SetMasterReference ¶

func (t *TransferOutConfirmationV03) SetMasterReference(value string)

type TransferOutConfirmationV04 ¶

type TransferOutConfirmationV04 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer23 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation11 `xml:"SttlmDtls,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 TransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV04) AddAccountDetails ¶

func (*TransferOutConfirmationV04) AddCopyDetails ¶

func (*TransferOutConfirmationV04) AddExtension ¶

func (t *TransferOutConfirmationV04) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV04) AddMessageIdentification ¶

func (t *TransferOutConfirmationV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV04) AddPoolReference ¶

func (*TransferOutConfirmationV04) AddPreviousReference ¶

func (t *TransferOutConfirmationV04) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV04) AddRelatedReference ¶

func (t *TransferOutConfirmationV04) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV04) AddSettlementDetails ¶

func (t *TransferOutConfirmationV04) AddSettlementDetails() *iso20022.ReceiveInformation11

func (*TransferOutConfirmationV04) AddTransferDetails ¶

func (t *TransferOutConfirmationV04) AddTransferDetails() *iso20022.Transfer23

func (*TransferOutConfirmationV04) SetMasterReference ¶

func (t *TransferOutConfirmationV04) SetMasterReference(value string)

type TransferOutConfirmationV05 ¶

type TransferOutConfirmationV05 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer28 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation12 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV05) AddAccountDetails ¶

func (*TransferOutConfirmationV05) AddCopyDetails ¶

func (*TransferOutConfirmationV05) AddExtension ¶

func (t *TransferOutConfirmationV05) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV05) AddMarketPracticeVersion ¶

func (t *TransferOutConfirmationV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutConfirmationV05) AddMessageIdentification ¶

func (t *TransferOutConfirmationV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV05) AddPoolReference ¶

func (*TransferOutConfirmationV05) AddPreviousReference ¶

func (t *TransferOutConfirmationV05) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV05) AddRelatedReference ¶

func (t *TransferOutConfirmationV05) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV05) AddSettlementDetails ¶

func (t *TransferOutConfirmationV05) AddSettlementDetails() *iso20022.ReceiveInformation12

func (*TransferOutConfirmationV05) AddTransferDetails ¶

func (t *TransferOutConfirmationV05) AddTransferDetails() *iso20022.Transfer28

func (*TransferOutConfirmationV05) SetMasterReference ¶

func (t *TransferOutConfirmationV05) SetMasterReference(value string)

type TransferOutConfirmationV06 ¶

type TransferOutConfirmationV06 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer28 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation14 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV06) AddAccountDetails ¶

func (*TransferOutConfirmationV06) AddCopyDetails ¶

func (*TransferOutConfirmationV06) AddExtension ¶

func (t *TransferOutConfirmationV06) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV06) AddMarketPracticeVersion ¶

func (t *TransferOutConfirmationV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutConfirmationV06) AddMessageIdentification ¶

func (t *TransferOutConfirmationV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV06) AddPoolReference ¶

func (*TransferOutConfirmationV06) AddPreviousReference ¶

func (t *TransferOutConfirmationV06) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV06) AddRelatedReference ¶

func (t *TransferOutConfirmationV06) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutConfirmationV06) AddSettlementDetails ¶

func (t *TransferOutConfirmationV06) AddSettlementDetails() *iso20022.ReceiveInformation14

func (*TransferOutConfirmationV06) AddTransferDetails ¶

func (t *TransferOutConfirmationV06) AddTransferDetails() *iso20022.Transfer28

func (*TransferOutConfirmationV06) SetMasterReference ¶

func (t *TransferOutConfirmationV06) SetMasterReference(value string)

type TransferOutConfirmationV07 ¶

type TransferOutConfirmationV07 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.AdditionalReference6 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference6 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer31 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument was withdrawn.
	AccountDetails *iso20022.InvestmentAccount54 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation17 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

	// 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 An executing party, for example, a transfer agent, sends the TransferOutConfirmation message to the instructing party, for example, an investment manager or its authorised representative, to confirm the delivery of a financial instrument, free of payment, on a given date, to a specified party. This message may also be used to confirm the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutConfirmation message is used to confirm the withdrawal of a financial instrument from the owner's account and its delivery to another own account, or to a third party, has taken place. The reference of the transfer confirmation is identified in TransferConfirmationReference. The reference of the original transfer instruction is specified in TransferReference. The message identification of the TransferOutInstruction message in which the transfer instruction was conveyed may also be quoted in RelatedReference.

func (*TransferOutConfirmationV07) AddAccountDetails ¶

func (*TransferOutConfirmationV07) AddCopyDetails ¶

func (*TransferOutConfirmationV07) AddExtension ¶

func (t *TransferOutConfirmationV07) AddExtension() *iso20022.Extension1

func (*TransferOutConfirmationV07) AddMarketPracticeVersion ¶

func (t *TransferOutConfirmationV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutConfirmationV07) AddMessageIdentification ¶

func (t *TransferOutConfirmationV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutConfirmationV07) AddPoolReference ¶

func (*TransferOutConfirmationV07) AddPreviousReference ¶

func (t *TransferOutConfirmationV07) AddPreviousReference() *iso20022.AdditionalReference6

func (*TransferOutConfirmationV07) AddRelatedReference ¶

func (t *TransferOutConfirmationV07) AddRelatedReference() *iso20022.AdditionalReference6

func (*TransferOutConfirmationV07) AddSettlementDetails ¶

func (t *TransferOutConfirmationV07) AddSettlementDetails() *iso20022.ReceiveInformation17

func (*TransferOutConfirmationV07) AddTransferDetails ¶

func (t *TransferOutConfirmationV07) AddTransferDetails() *iso20022.Transfer31

func (*TransferOutConfirmationV07) SetMasterReference ¶

func (t *TransferOutConfirmationV07) SetMasterReference(value string)

type TransferOutInstruction ¶

type TransferOutInstruction struct {

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

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer1 `xml:"TrfDtls"`

	// Information related to the financial instrument to be withdrawn.
	FinancialInstrumentDetails *iso20022.FinancialInstrument3 `xml:"FinInstrmDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount10 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation1 `xml:"SttlmDtls"`

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

Scope The TransferOutInstruction message is sent by an instructing party, or an instructing party's designated agent, to the executing party. This message is used to instruct the delivery of a financial instrument, free of payment, at a given date, to a specified party. This message can be used to instruct the transfer of a financial instrument to an own account or to a third party. Usage The TransferOutInstruction message is used by an instructing party to instruct the executing party to withdraw a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstruction) AddAccountDetails ¶

func (t *TransferOutInstruction) AddAccountDetails() *iso20022.InvestmentAccount10

func (*TransferOutInstruction) AddExtension ¶

func (t *TransferOutInstruction) AddExtension() *iso20022.Extension1

func (*TransferOutInstruction) AddFinancialInstrumentDetails ¶

func (t *TransferOutInstruction) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument3

func (*TransferOutInstruction) AddPoolReference ¶

func (t *TransferOutInstruction) AddPoolReference() *iso20022.AdditionalReference2

func (*TransferOutInstruction) AddPreviousReference ¶

func (t *TransferOutInstruction) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstruction) AddRelatedReference ¶

func (t *TransferOutInstruction) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstruction) AddSettlementDetails ¶

func (t *TransferOutInstruction) AddSettlementDetails() *iso20022.ReceiveInformation1

func (*TransferOutInstruction) AddTransferDetails ¶

func (t *TransferOutInstruction) AddTransferDetails() *iso20022.Transfer1

type TransferOutInstructionV02 ¶

type TransferOutInstructionV02 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// General information related to the transfer of a financial instrument.
	TransferDetails *iso20022.Transfer8 `xml:"TrfDtls"`

	// Information related to the financial instrument to be withdrawn.
	FinancialInstrumentDetails *iso20022.FinancialInstrument13 `xml:"FinInstrmDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation3 `xml:"SttlmDtls"`

	// 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, eg, an investment manager or its authorised representative, sends the TransferOutInstruction message to the executing party, eg, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV02) AddAccountDetails ¶

func (t *TransferOutInstructionV02) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferOutInstructionV02) AddCopyDetails ¶

func (*TransferOutInstructionV02) AddExtension ¶

func (t *TransferOutInstructionV02) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV02) AddFinancialInstrumentDetails ¶

func (t *TransferOutInstructionV02) AddFinancialInstrumentDetails() *iso20022.FinancialInstrument13

func (*TransferOutInstructionV02) AddMessageIdentification ¶

func (t *TransferOutInstructionV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV02) AddPoolReference ¶

func (*TransferOutInstructionV02) AddPreviousReference ¶

func (t *TransferOutInstructionV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV02) AddRelatedReference ¶

func (t *TransferOutInstructionV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV02) AddSettlementDetails ¶

func (t *TransferOutInstructionV02) AddSettlementDetails() *iso20022.ReceiveInformation3

func (*TransferOutInstructionV02) AddTransferDetails ¶

func (t *TransferOutInstructionV02) AddTransferDetails() *iso20022.Transfer8

type TransferOutInstructionV03 ¶

type TransferOutInstructionV03 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Requested date at which the instructing party places the transfer instruction.
	RequestedTransferDate *iso20022.DateFormat1Choice `xml:"ReqdTrfDt,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer11 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation5 `xml:"SttlmDtls"`

	// 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 TransferOutInstruction message to the executing party, for example, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV03) AddAccountDetails ¶

func (t *TransferOutInstructionV03) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferOutInstructionV03) AddCopyDetails ¶

func (*TransferOutInstructionV03) AddExtension ¶

func (t *TransferOutInstructionV03) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV03) AddMessageIdentification ¶

func (t *TransferOutInstructionV03) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV03) AddPoolReference ¶

func (*TransferOutInstructionV03) AddPreviousReference ¶

func (t *TransferOutInstructionV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV03) AddRelatedReference ¶

func (t *TransferOutInstructionV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV03) AddRequestedTransferDate ¶

func (t *TransferOutInstructionV03) AddRequestedTransferDate() *iso20022.DateFormat1Choice

func (*TransferOutInstructionV03) AddSettlementDetails ¶

func (t *TransferOutInstructionV03) AddSettlementDetails() *iso20022.ReceiveInformation5

func (*TransferOutInstructionV03) AddTransferDetails ¶

func (t *TransferOutInstructionV03) AddTransferDetails() *iso20022.Transfer11

func (*TransferOutInstructionV03) SetMasterReference ¶

func (t *TransferOutInstructionV03) SetMasterReference(value string)

type TransferOutInstructionV04 ¶

type TransferOutInstructionV04 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Requested date at which the instructing party places the transfer instruction.
	RequestedTransferDate *iso20022.DateFormat1Choice `xml:"ReqdTrfDt,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer19 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount22 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation9 `xml:"SttlmDtls,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 TransferOutInstruction message to the executing party, for example, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV04) AddAccountDetails ¶

func (t *TransferOutInstructionV04) AddAccountDetails() *iso20022.InvestmentAccount22

func (*TransferOutInstructionV04) AddCopyDetails ¶

func (*TransferOutInstructionV04) AddExtension ¶

func (t *TransferOutInstructionV04) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV04) AddMessageIdentification ¶

func (t *TransferOutInstructionV04) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV04) AddPoolReference ¶

func (*TransferOutInstructionV04) AddPreviousReference ¶

func (t *TransferOutInstructionV04) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV04) AddRelatedReference ¶

func (t *TransferOutInstructionV04) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV04) AddRequestedTransferDate ¶

func (t *TransferOutInstructionV04) AddRequestedTransferDate() *iso20022.DateFormat1Choice

func (*TransferOutInstructionV04) AddSettlementDetails ¶

func (t *TransferOutInstructionV04) AddSettlementDetails() *iso20022.ReceiveInformation9

func (*TransferOutInstructionV04) AddTransferDetails ¶

func (t *TransferOutInstructionV04) AddTransferDetails() *iso20022.Transfer19

func (*TransferOutInstructionV04) SetMasterReference ¶

func (t *TransferOutInstructionV04) SetMasterReference(value string)

type TransferOutInstructionV05 ¶

type TransferOutInstructionV05 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Requested date at which the instructing party places the transfer instruction.
	RequestedTransferDate *iso20022.DateFormat1Choice `xml:"ReqdTrfDt,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer27 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation13 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutInstruction message to the executing party, for example, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV05) AddAccountDetails ¶

func (t *TransferOutInstructionV05) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferOutInstructionV05) AddCopyDetails ¶

func (*TransferOutInstructionV05) AddExtension ¶

func (t *TransferOutInstructionV05) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV05) AddMarketPracticeVersion ¶

func (t *TransferOutInstructionV05) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutInstructionV05) AddMessageIdentification ¶

func (t *TransferOutInstructionV05) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV05) AddPoolReference ¶

func (*TransferOutInstructionV05) AddPreviousReference ¶

func (t *TransferOutInstructionV05) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV05) AddRelatedReference ¶

func (t *TransferOutInstructionV05) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV05) AddRequestedTransferDate ¶

func (t *TransferOutInstructionV05) AddRequestedTransferDate() *iso20022.DateFormat1Choice

func (*TransferOutInstructionV05) AddSettlementDetails ¶

func (t *TransferOutInstructionV05) AddSettlementDetails() *iso20022.ReceiveInformation13

func (*TransferOutInstructionV05) AddTransferDetails ¶

func (t *TransferOutInstructionV05) AddTransferDetails() *iso20022.Transfer27

func (*TransferOutInstructionV05) SetMasterReference ¶

func (t *TransferOutInstructionV05) SetMasterReference(value string)

type TransferOutInstructionV06 ¶

type TransferOutInstructionV06 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.AdditionalReference2 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference2 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Requested date at which the instructing party places the transfer instruction.
	RequestedTransferDate *iso20022.DateFormat1Choice `xml:"ReqdTrfDt,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer27 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount40 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation15 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,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 TransferOutInstruction message to the executing party, for example, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV06) AddAccountDetails ¶

func (t *TransferOutInstructionV06) AddAccountDetails() *iso20022.InvestmentAccount40

func (*TransferOutInstructionV06) AddCopyDetails ¶

func (*TransferOutInstructionV06) AddExtension ¶

func (t *TransferOutInstructionV06) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV06) AddMarketPracticeVersion ¶

func (t *TransferOutInstructionV06) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutInstructionV06) AddMessageIdentification ¶

func (t *TransferOutInstructionV06) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV06) AddPoolReference ¶

func (*TransferOutInstructionV06) AddPreviousReference ¶

func (t *TransferOutInstructionV06) AddPreviousReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV06) AddRelatedReference ¶

func (t *TransferOutInstructionV06) AddRelatedReference() *iso20022.AdditionalReference2

func (*TransferOutInstructionV06) AddRequestedTransferDate ¶

func (t *TransferOutInstructionV06) AddRequestedTransferDate() *iso20022.DateFormat1Choice

func (*TransferOutInstructionV06) AddSettlementDetails ¶

func (t *TransferOutInstructionV06) AddSettlementDetails() *iso20022.ReceiveInformation15

func (*TransferOutInstructionV06) AddTransferDetails ¶

func (t *TransferOutInstructionV06) AddTransferDetails() *iso20022.Transfer27

func (*TransferOutInstructionV06) SetMasterReference ¶

func (t *TransferOutInstructionV06) SetMasterReference(value string)

type TransferOutInstructionV07 ¶

type TransferOutInstructionV07 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.AdditionalReference6 `xml:"PoolRef,omitempty"`

	// Reference of the linked message that was previously sent.
	PreviousReference *iso20022.AdditionalReference6 `xml:"PrvsRef,omitempty"`

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

	// Unique and unambiguous identifier for a group of individual transfers as assigned by the instructing party. This identifier links the individual transfers together.
	MasterReference *iso20022.Max35Text `xml:"MstrRef,omitempty"`

	// Requested date at which the instructing party places the transfer instruction.
	RequestedTransferDate *iso20022.DateFormat1Choice `xml:"ReqdTrfDt,omitempty"`

	// General information related to the transfer of a financial instrument.
	TransferDetails []*iso20022.Transfer30 `xml:"TrfDtls"`

	// Information related to the account from which the financial instrument is to be withdrawn.
	AccountDetails *iso20022.InvestmentAccount54 `xml:"AcctDtls"`

	// Information related to the receiving side of the transfer.
	SettlementDetails *iso20022.ReceiveInformation16 `xml:"SttlmDtls,omitempty"`

	// Identifies the market practice to which the message conforms.
	MarketPracticeVersion *iso20022.MarketPracticeVersion1 `xml:"MktPrctcVrsn,omitempty"`

	// 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 An instructing party, for example, an investment manager or its authorised representative, sends the TransferOutInstruction message to the executing party, for example, a transfer agent, to instruct the delivery of a financial instrument, free of payment, on a given date from a specified party. This message may also be used to instruct the delivery of a financial instrument, free of payment, to another of the instructing parties own accounts or to a third party. Usage The TransferOutInstruction message is used to instruct the withdrawal of a financial instrument from one account and deliver it to either another account or to a third party.

func (*TransferOutInstructionV07) AddAccountDetails ¶

func (t *TransferOutInstructionV07) AddAccountDetails() *iso20022.InvestmentAccount54

func (*TransferOutInstructionV07) AddCopyDetails ¶

func (*TransferOutInstructionV07) AddExtension ¶

func (t *TransferOutInstructionV07) AddExtension() *iso20022.Extension1

func (*TransferOutInstructionV07) AddMarketPracticeVersion ¶

func (t *TransferOutInstructionV07) AddMarketPracticeVersion() *iso20022.MarketPracticeVersion1

func (*TransferOutInstructionV07) AddMessageIdentification ¶

func (t *TransferOutInstructionV07) AddMessageIdentification() *iso20022.MessageIdentification1

func (*TransferOutInstructionV07) AddPoolReference ¶

func (*TransferOutInstructionV07) AddPreviousReference ¶

func (t *TransferOutInstructionV07) AddPreviousReference() *iso20022.AdditionalReference6

func (*TransferOutInstructionV07) AddRelatedReference ¶

func (t *TransferOutInstructionV07) AddRelatedReference() *iso20022.AdditionalReference6

func (*TransferOutInstructionV07) AddRequestedTransferDate ¶

func (t *TransferOutInstructionV07) AddRequestedTransferDate() *iso20022.DateFormat1Choice

func (*TransferOutInstructionV07) AddSettlementDetails ¶

func (t *TransferOutInstructionV07) AddSettlementDetails() *iso20022.ReceiveInformation16

func (*TransferOutInstructionV07) AddTransferDetails ¶

func (t *TransferOutInstructionV07) AddTransferDetails() *iso20022.Transfer30

func (*TransferOutInstructionV07) SetMasterReference ¶

func (t *TransferOutInstructionV07) SetMasterReference(value string)

Source Files ¶

Jump to

Keyboard shortcuts

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