semt

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 AccountingStatementOfHoldings 

type AccountingStatementOfHoldings struct {

	// Reference to a 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"`

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

	// General information related to the accounting statement of holdings.
	StatementGeneralDetails *iso20022.Statement4 `xml:"StmtGnlDtls"`

	// The safekeeping or investment account.
	AccountDetails *iso20022.SafekeepingAccount1 `xml:"AcctDtls"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation2 `xml:"BalForAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification2 `xml:"SubAcctDtls,omitempty"`

	// Value of total holdings reported.
	TotalValues *iso20022.TotalValueInPageAndStatement `xml:"TtlVals,omitempty"`

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

Scope The AccountingStatementOfHoldings message is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a local agent acting on behalf of its global custodian customer, a custodian acting on behalf of an investment management institution or a broker/dealer, a fund administrator or fund intermediary, trustee or registrar, etc. This message provides, at a specified moment in time, valuations of the portfolio together with details of each financial instrument holding. The information in the message can be audited or un-audited. Usage The AccountingStatementOfHoldings message can be sent: - At a frequency agreed bi-laterally between the Sender and the Receiver - As a response to a request for statement sent by the account owner. The request for statement message will be developed at a later stage. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or - the sub-account level. This message can be used to report where the securities are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The AccountingStatementOfHoldings message must not be used to reconcile the books of the account owner and the account servicer. The CustodyStatementOfHoldings message is used for reconciliation purposes. The AccountingStatementOfHoldings message must not be used for trading purposes. Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.

func (*AccountingStatementOfHoldings) AddAccountDetails 

func (a *AccountingStatementOfHoldings) AddAccountDetails() *iso20022.SafekeepingAccount1

func (*AccountingStatementOfHoldings) AddBalanceForAccount 

func (a *AccountingStatementOfHoldings) AddBalanceForAccount() *iso20022.AggregateBalanceInformation2

func (*AccountingStatementOfHoldings) AddExtension 

func (a *AccountingStatementOfHoldings) AddExtension() *iso20022.Extension1

func (*AccountingStatementOfHoldings) AddMessagePagination 

func (a *AccountingStatementOfHoldings) AddMessagePagination() *iso20022.Pagination

func (*AccountingStatementOfHoldings) AddPreviousReference 

func (a *AccountingStatementOfHoldings) AddPreviousReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldings) AddRelatedReference 

func (a *AccountingStatementOfHoldings) AddRelatedReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldings) AddStatementGeneralDetails 

func (a *AccountingStatementOfHoldings) AddStatementGeneralDetails() *iso20022.Statement4

func (*AccountingStatementOfHoldings) AddSubAccountDetails 

func (a *AccountingStatementOfHoldings) AddSubAccountDetails() *iso20022.SubAccountIdentification2

func (*AccountingStatementOfHoldings) AddTotalValues 

func (a *AccountingStatementOfHoldings) AddTotalValues() *iso20022.TotalValueInPageAndStatement

type AccountingStatementOfHoldingsCancellation 

type AccountingStatementOfHoldingsCancellation struct {

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

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

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

	// The Accounting Statement of Holdings message to cancel.
	StatementToBeCancelled *iso20022.AccountingStatementOfHoldings1 `xml:"StmtToBeCanc,omitempty"`
}

Scope The AccountingStatementOfHoldingsCancellation message is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a local agent (sub-custodian) acting on behalf of its global custodian customer, a custodian acting on behalf of an investment management institution or a broker/dealer, a fund administrator or fund intermediary, trustee or registrar. This message is used to cancel a previously sent AccountingStatementOfHoldings message. Usage The AccountingStatementOfHoldingsCancellation message is sent by an account servicer to the account owner to cancel a previously sent AccountingStatementOfHoldings message. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*AccountingStatementOfHoldingsCancellation) AddMessagePagination 

func (a *AccountingStatementOfHoldingsCancellation) AddMessagePagination() *iso20022.Pagination

func (*AccountingStatementOfHoldingsCancellation) AddPreviousReference 

func (a *AccountingStatementOfHoldingsCancellation) AddPreviousReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsCancellation) AddRelatedReference 

func (a *AccountingStatementOfHoldingsCancellation) AddRelatedReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsCancellation) AddStatementToBeCancelled 

func (a *AccountingStatementOfHoldingsCancellation) AddStatementToBeCancelled() *iso20022.AccountingStatementOfHoldings1

type AccountingStatementOfHoldingsCancellationV02 

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

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

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

	// The Accounting Statement of Holdings message to cancel.
	StatementToBeCancelled *iso20022.AccountingStatementOfHoldings2 `xml:"StmtToBeCanc,omitempty"`
}

Scope An account servicer, for example, a transfer agent, sends the AccountingStatementofHoldingsCancellation message to the account owner, for example, a fund manager or an account owner's designated agent, to notify the cancellation of a previously sent AccountingStatementOfHoldings message. Usage The AccountingStatementOfHoldingsCancellation message is used to cancel a previously sent AccountingStatementOfHoldings message. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*AccountingStatementOfHoldingsCancellationV02) AddMessageIdentification 

func (a *AccountingStatementOfHoldingsCancellationV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*AccountingStatementOfHoldingsCancellationV02) AddMessagePagination 

func (a *AccountingStatementOfHoldingsCancellationV02) AddMessagePagination() *iso20022.Pagination

func (*AccountingStatementOfHoldingsCancellationV02) AddPreviousReference 

func (a *AccountingStatementOfHoldingsCancellationV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsCancellationV02) AddRelatedReference 

func (a *AccountingStatementOfHoldingsCancellationV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsCancellationV02) AddStatementToBeCancelled 

func (a *AccountingStatementOfHoldingsCancellationV02) AddStatementToBeCancelled() *iso20022.AccountingStatementOfHoldings2

type AccountingStatementOfHoldingsV02 

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

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

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

	// General information related to the accounting statement of holdings.
	StatementGeneralDetails *iso20022.Statement6 `xml:"StmtGnlDtls"`

	// The safekeeping or investment account.
	AccountDetails *iso20022.SafekeepingAccount2 `xml:"AcctDtls"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation3 `xml:"BalForAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification3 `xml:"SubAcctDtls,omitempty"`

	// Value of total holdings reported.
	TotalValues *iso20022.TotalValueInPageAndStatement `xml:"TtlVals,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 account servicer, for example, a transfer agent sends the AccountStatementOfHoldings message to the account owner, for example, a fund manager or an account owner's designated agent to provide detailed holdings of the portfolio at a specified moment in time. The message provides, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The message can be sent either audited or un-audited and may be provided on a trade date or settlement date basis. Usage The AccountingStatementOfHoldings message is used to provide valuation detail for each financial instrument held in a portfolio. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The AccountingStatementOfHoldings message should not be used for trading purposes.

func (*AccountingStatementOfHoldingsV02) AddAccountDetails 

func (a *AccountingStatementOfHoldingsV02) AddAccountDetails() *iso20022.SafekeepingAccount2

func (*AccountingStatementOfHoldingsV02) AddBalanceForAccount 

func (a *AccountingStatementOfHoldingsV02) AddBalanceForAccount() *iso20022.AggregateBalanceInformation3

func (*AccountingStatementOfHoldingsV02) AddExtension 

func (a *AccountingStatementOfHoldingsV02) AddExtension() *iso20022.Extension1

func (*AccountingStatementOfHoldingsV02) AddMessageIdentification 

func (a *AccountingStatementOfHoldingsV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*AccountingStatementOfHoldingsV02) AddMessagePagination 

func (a *AccountingStatementOfHoldingsV02) AddMessagePagination() *iso20022.Pagination

func (*AccountingStatementOfHoldingsV02) AddPreviousReference 

func (a *AccountingStatementOfHoldingsV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsV02) AddRelatedReference 

func (a *AccountingStatementOfHoldingsV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*AccountingStatementOfHoldingsV02) AddStatementGeneralDetails 

func (a *AccountingStatementOfHoldingsV02) AddStatementGeneralDetails() *iso20022.Statement6

func (*AccountingStatementOfHoldingsV02) AddSubAccountDetails 

func (a *AccountingStatementOfHoldingsV02) AddSubAccountDetails() *iso20022.SubAccountIdentification3

func (*AccountingStatementOfHoldingsV02) AddTotalValues 

func (a *AccountingStatementOfHoldingsV02) AddTotalValues() *iso20022.TotalValueInPageAndStatement

type CustodyStatementOfHoldings 

type CustodyStatementOfHoldings struct {

	// Reference to a 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"`

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

	// General information related to the custody statement of holdings.
	StatementGeneralDetails *iso20022.Statement3 `xml:"StmtGnlDtls"`

	// The safekeeping or investment account.
	AccountDetails *iso20022.SafekeepingAccount1 `xml:"AcctDtls"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation1 `xml:"BalForAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification1 `xml:"SubAcctDtls,omitempty"`

	// Value of total holdings reported.
	TotalValues *iso20022.TotalValueInPageAndStatement `xml:"TtlVals,omitempty"`

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

Scope The CustodyStatementOfHoldings message is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a local agent acting on behalf of its global custodian customer, a custodian acting on behalf of an investment management institution or a broker/dealer, a fund administrator or fund intermediary, trustee or registrar, etc. This message reports, at a specified moment in time, the quantity and identification of financial instruments that an account servicer holds for the account owner. This message is used to reconcile the books of the account owner and the account servicer for the specified account or sub-account. This message can also report availability and/or the location of security holdings to facilitate trading and minimise settlement issues. The reporting is per financial instrument, ie, when a financial instrument is held at multiple places of safekeeping, the total holding for all locations can be provided. Usage The CustodyStatementOfHoldings message can be sent: - At a frequency agreed bi-laterally between the Sender and the Receiver - As a response to a request for statement sent by the account owner. This message can reflect all outstanding holding information or may only contain changes since the previously sent statement. The CustodyStatementOfHoldings message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, this message can be used to either specify holdings at - the main account level, or - the sub-account level. This message can be also be used to report where the securities are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. This message must not be used to report audited positions. Audited positions are reported using the AccountingStatementOfHoldings message. Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.

func (*CustodyStatementOfHoldings) AddAccountDetails 

func (c *CustodyStatementOfHoldings) AddAccountDetails() *iso20022.SafekeepingAccount1

func (*CustodyStatementOfHoldings) AddBalanceForAccount 

func (c *CustodyStatementOfHoldings) AddBalanceForAccount() *iso20022.AggregateBalanceInformation1

func (*CustodyStatementOfHoldings) AddExtension 

func (c *CustodyStatementOfHoldings) AddExtension() *iso20022.Extension1

func (*CustodyStatementOfHoldings) AddMessagePagination 

func (c *CustodyStatementOfHoldings) AddMessagePagination() *iso20022.Pagination

func (*CustodyStatementOfHoldings) AddPreviousReference 

func (c *CustodyStatementOfHoldings) AddPreviousReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldings) AddRelatedReference 

func (c *CustodyStatementOfHoldings) AddRelatedReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldings) AddStatementGeneralDetails 

func (c *CustodyStatementOfHoldings) AddStatementGeneralDetails() *iso20022.Statement3

func (*CustodyStatementOfHoldings) AddSubAccountDetails 

func (c *CustodyStatementOfHoldings) AddSubAccountDetails() *iso20022.SubAccountIdentification1

func (*CustodyStatementOfHoldings) AddTotalValues 

func (c *CustodyStatementOfHoldings) AddTotalValues() *iso20022.TotalValueInPageAndStatement

type CustodyStatementOfHoldingsCancellation 

type CustodyStatementOfHoldingsCancellation struct {

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

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

	// Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages).
	MessagePagination *iso20022.Pagination `xml:"MsgPgntn"`

	// The Custody Statement of Holdings message to cancel.
	StatementToBeCancelled *iso20022.CustodyStatementOfHoldings1 `xml:"StmtToBeCanc,omitempty"`
}

Scope The CustodyStatementOfHoldingsCancellation message is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a local agent (sub-custodian) acting on behalf of its global custodian customer, a custodian acting on behalf of an investment management institution or a broker/dealer, a fund administrator or fund intermediary, trustee or registrar, etc. This message is used to cancel a previously sent CustodyStatementOfHoldings message. Usage The CustodyStatementOfHoldingsCancellation message is sent by an account servicer to the account owner to cancel a previously sent CustodyStatementOfHoldings message. This message must contain the reference of the message to be cancelled. This message may also contain details of the message to be cancelled, but this is not recommended.

func (*CustodyStatementOfHoldingsCancellation) AddMessagePagination 

func (c *CustodyStatementOfHoldingsCancellation) AddMessagePagination() *iso20022.Pagination

func (*CustodyStatementOfHoldingsCancellation) AddPreviousReference 

func (c *CustodyStatementOfHoldingsCancellation) AddPreviousReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsCancellation) AddRelatedReference 

func (c *CustodyStatementOfHoldingsCancellation) AddRelatedReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsCancellation) AddStatementToBeCancelled 

func (c *CustodyStatementOfHoldingsCancellation) AddStatementToBeCancelled() *iso20022.CustodyStatementOfHoldings1

type CustodyStatementOfHoldingsCancellationV02 

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

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

	// Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages).
	MessagePagination *iso20022.Pagination `xml:"MsgPgntn"`

	// The Custody Statement of Holdings message to cancel.
	StatementToBeCancelled *iso20022.CustodyStatementOfHoldings2 `xml:"StmtToBeCanc,omitempty"`
}

Scope An account servicer, for example, a transfer agent, sends the CustodyStatementOfHoldingsCancellation message to the account owner, for example, an investment manager or its authorised representative to cancel a previously sent CustodyStatementOfHoldings message. Usage The CustodyStatementOfHoldingsCancellation message is used to cancel a previously sent CustodyStatementOfHoldings message. This message must contain the reference of the message to be cancelled. This message may also contain details of the message to be cancelled, but this is not recommended.

func (*CustodyStatementOfHoldingsCancellationV02) AddMessageIdentification 

func (c *CustodyStatementOfHoldingsCancellationV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*CustodyStatementOfHoldingsCancellationV02) AddMessagePagination 

func (c *CustodyStatementOfHoldingsCancellationV02) AddMessagePagination() *iso20022.Pagination

func (*CustodyStatementOfHoldingsCancellationV02) AddPreviousReference 

func (c *CustodyStatementOfHoldingsCancellationV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsCancellationV02) AddRelatedReference 

func (c *CustodyStatementOfHoldingsCancellationV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsCancellationV02) AddStatementToBeCancelled 

func (c *CustodyStatementOfHoldingsCancellationV02) AddStatementToBeCancelled() *iso20022.CustodyStatementOfHoldings2

type CustodyStatementOfHoldingsV02 

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

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

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

	// General information related to the custody statement of holdings.
	StatementGeneralDetails *iso20022.Statement7 `xml:"StmtGnlDtls"`

	// The safekeeping or investment account.
	AccountDetails *iso20022.SafekeepingAccount2 `xml:"AcctDtls"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation4 `xml:"BalForAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification5 `xml:"SubAcctDtls,omitempty"`

	// Value of total holdings reported.
	TotalValues *iso20022.TotalValueInPageAndStatement `xml:"TtlVals,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 account servicer, for example, a transfer agent sends the CustodyStatementOfHoldings message to the account owner, for example, a fund manager or an account owner's designated agent to provide detailed holdings of the portfolio at a specified moment in time. The message provides, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for the account owner. The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, ie, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. Usage The CustodyStatementOfHoldings message is used to provide detailed quantity and availability information for financial instrument holdings of a portfolio. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. This message can be also be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. This message can reflect all outstanding holding information or may only contain changes since the previously sent statement. The CustodyStatementOfHoldings message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, this message can be used to either specify holdings at - the main account level, or, - the sub-account level.

func (*CustodyStatementOfHoldingsV02) AddAccountDetails 

func (c *CustodyStatementOfHoldingsV02) AddAccountDetails() *iso20022.SafekeepingAccount2

func (*CustodyStatementOfHoldingsV02) AddBalanceForAccount 

func (c *CustodyStatementOfHoldingsV02) AddBalanceForAccount() *iso20022.AggregateBalanceInformation4

func (*CustodyStatementOfHoldingsV02) AddExtension 

func (c *CustodyStatementOfHoldingsV02) AddExtension() *iso20022.Extension1

func (*CustodyStatementOfHoldingsV02) AddMessageIdentification 

func (c *CustodyStatementOfHoldingsV02) AddMessageIdentification() *iso20022.MessageIdentification1

func (*CustodyStatementOfHoldingsV02) AddMessagePagination 

func (c *CustodyStatementOfHoldingsV02) AddMessagePagination() *iso20022.Pagination

func (*CustodyStatementOfHoldingsV02) AddPreviousReference 

func (c *CustodyStatementOfHoldingsV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsV02) AddRelatedReference 

func (c *CustodyStatementOfHoldingsV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*CustodyStatementOfHoldingsV02) AddStatementGeneralDetails 

func (c *CustodyStatementOfHoldingsV02) AddStatementGeneralDetails() *iso20022.Statement7

func (*CustodyStatementOfHoldingsV02) AddSubAccountDetails 

func (c *CustodyStatementOfHoldingsV02) AddSubAccountDetails() *iso20022.SubAccountIdentification5

func (*CustodyStatementOfHoldingsV02) AddTotalValues 

func (c *CustodyStatementOfHoldingsV02) AddTotalValues() *iso20022.TotalValueInPageAndStatement

type Document00100101 

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

func (*Document00100101) AddMessage 

func (d *Document00100101) AddMessage() *SecuritiesMessageRejection

type Document00100102 

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

func (*Document00100102) AddMessage 

func (d *Document00100102) AddMessage() *SecuritiesMessageRejectionV02

type Document00100103 

type Document00100103 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:semt.001.001.03 Document"`
	Message *SecuritiesMessageRejectionV03 `xml:"SctiesMsgRjctn"`
}

func (*Document00100103) AddMessage 

func (d *Document00100103) AddMessage() *SecuritiesMessageRejectionV03

type Document00200101 

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

func (*Document00200101) AddMessage 

func (d *Document00200101) AddMessage() *CustodyStatementOfHoldings

type Document00200102 

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

func (*Document00200102) AddMessage 

func (d *Document00200102) AddMessage() *CustodyStatementOfHoldingsV02

type Document00200103 

type Document00200103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.03 Document"`
	Message *SecuritiesBalanceCustodyReportV03 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200103) AddMessage 

func (d *Document00200103) AddMessage() *SecuritiesBalanceCustodyReportV03

type Document00200104 

type Document00200104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.04 Document"`
	Message *SecuritiesBalanceCustodyReportV04 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200104) AddMessage 

func (d *Document00200104) AddMessage() *SecuritiesBalanceCustodyReportV04

type Document00200105 

type Document00200105 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.05 Document"`
	Message *SecuritiesBalanceCustodyReportV05 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200105) AddMessage 

func (d *Document00200105) AddMessage() *SecuritiesBalanceCustodyReportV05

type Document00200106 

type Document00200106 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.06 Document"`
	Message *SecuritiesBalanceCustodyReportV06 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200106) AddMessage 

func (d *Document00200106) AddMessage() *SecuritiesBalanceCustodyReportV06

type Document00200107 

type Document00200107 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.07 Document"`
	Message *SecuritiesBalanceCustodyReportV07 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200107) AddMessage 

func (d *Document00200107) AddMessage() *SecuritiesBalanceCustodyReportV07

type Document00200108 

type Document00200108 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.08 Document"`
	Message *SecuritiesBalanceCustodyReportV08 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200108) AddMessage 

func (d *Document00200108) AddMessage() *SecuritiesBalanceCustodyReportV08

type Document00200109 

type Document00200109 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.001.09 Document"`
	Message *SecuritiesBalanceCustodyReportV09 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200109) AddMessage 

func (d *Document00200109) AddMessage() *SecuritiesBalanceCustodyReportV09

type Document00200209 

type Document00200209 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.002.002.09 Document"`
	Message *SecuritiesBalanceCustodyReport002V09 `xml:"SctiesBalCtdyRpt"`
}

func (*Document00200209) AddMessage 

func (d *Document00200209) AddMessage() *SecuritiesBalanceCustodyReport002V09

type Document00300101 

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

func (*Document00300101) AddMessage 

func (d *Document00300101) AddMessage() *AccountingStatementOfHoldings

type Document00300102 

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

func (*Document00300102) AddMessage 

func (d *Document00300102) AddMessage() *AccountingStatementOfHoldingsV02

type Document00300103 

type Document00300103 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.03 Document"`
	Message *SecuritiesBalanceAccountingReportV03 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300103) AddMessage 

func (d *Document00300103) AddMessage() *SecuritiesBalanceAccountingReportV03

type Document00300104 

type Document00300104 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.04 Document"`
	Message *SecuritiesBalanceAccountingReportV04 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300104) AddMessage 

func (d *Document00300104) AddMessage() *SecuritiesBalanceAccountingReportV04

type Document00300105 

type Document00300105 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.05 Document"`
	Message *SecuritiesBalanceAccountingReportV05 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300105) AddMessage 

func (d *Document00300105) AddMessage() *SecuritiesBalanceAccountingReportV05

type Document00300106 

type Document00300106 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.06 Document"`
	Message *SecuritiesBalanceAccountingReportV06 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300106) AddMessage 

func (d *Document00300106) AddMessage() *SecuritiesBalanceAccountingReportV06

type Document00300107 

type Document00300107 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.07 Document"`
	Message *SecuritiesBalanceAccountingReportV07 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300107) AddMessage 

func (d *Document00300107) AddMessage() *SecuritiesBalanceAccountingReportV07

type Document00300108 

type Document00300108 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.08 Document"`
	Message *SecuritiesBalanceAccountingReportV08 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300108) AddMessage 

func (d *Document00300108) AddMessage() *SecuritiesBalanceAccountingReportV08

type Document00300109 

type Document00300109 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.001.09 Document"`
	Message *SecuritiesBalanceAccountingReportV09 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300109) AddMessage 

func (d *Document00300109) AddMessage() *SecuritiesBalanceAccountingReportV09

type Document00300209 

type Document00300209 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:semt.003.002.09 Document"`
	Message *SecuritiesBalanceAccountingReport002V09 `xml:"SctiesBalAcctgRpt"`
}

func (*Document00300209) AddMessage 

func (d *Document00300209) AddMessage() *SecuritiesBalanceAccountingReport002V09

type Document00400101 

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

func (*Document00400101) AddMessage 

func (d *Document00400101) AddMessage() *CustodyStatementOfHoldingsCancellation

type Document00400102 

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

func (*Document00400102) AddMessage 

func (d *Document00400102) AddMessage() *CustodyStatementOfHoldingsCancellationV02

type Document00500101 

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

func (*Document00500101) AddMessage 

func (d *Document00500101) AddMessage() *AccountingStatementOfHoldingsCancellation

type Document00500102 

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

func (*Document00500102) AddMessage 

func (d *Document00500102) AddMessage() *AccountingStatementOfHoldingsCancellationV02

type Document00600101 

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

func (*Document00600101) AddMessage 

func (d *Document00600101) AddMessage() *StatementOfInvestmentFundTransactions

type Document00600102 

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

func (*Document00600102) AddMessage 

func (d *Document00600102) AddMessage() *StatementOfInvestmentFundTransactionsV02

type Document00600103 

type Document00600103 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.006.001.03 Document"`
	Message *StatementOfInvestmentFundTransactionsV03 `xml:"StmtOfInvstmtFndTxs"`
}

func (*Document00600103) AddMessage 

func (d *Document00600103) AddMessage() *StatementOfInvestmentFundTransactionsV03

type Document00700101 

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

func (*Document00700101) AddMessage 

func (d *Document00700101) AddMessage() *StatementOfInvestmentFundTransactionsCancellation

type Document00700102 

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

func (*Document00700102) AddMessage 

func (d *Document00700102) AddMessage() *StatementOfInvestmentFundTransactionsCancellationV02

type Document00700103 

type Document00700103 struct {
	XMLName xml.Name                                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.007.001.03 Document"`
	Message *StatementOfInvestmentFundTransactionsCancellationV03 `xml:"StmtOfInvstmtFndTxsCxl"`
}

func (*Document00700103) AddMessage 

func (d *Document00700103) AddMessage() *StatementOfInvestmentFundTransactionsCancellationV03

type Document01300101 

type Document01300101 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:semt.013.001.01 Document"`
	Message *IntraPositionMovementInstructionV01 `xml:"IntraPosMvmntInstr"`
}

func (*Document01300101) AddMessage 

func (d *Document01300101) AddMessage() *IntraPositionMovementInstructionV01

type Document01300102 

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

func (*Document01300102) AddMessage 

func (d *Document01300102) AddMessage() *IntraPositionMovementInstructionV02

type Document01300103 

type Document01300103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:semt.013.001.03 Document"`
	Message *IntraPositionMovementInstructionV03 `xml:"IntraPosMvmntInstr"`
}

func (*Document01300103) AddMessage 

func (d *Document01300103) AddMessage() *IntraPositionMovementInstructionV03

type Document01300104 

type Document01300104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:semt.013.001.04 Document"`
	Message *IntraPositionMovementInstructionV04 `xml:"IntraPosMvmntInstr"`
}

func (*Document01300104) AddMessage 

func (d *Document01300104) AddMessage() *IntraPositionMovementInstructionV04

type Document01300204 

type Document01300204 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.013.002.04 Document"`
	Message *IntraPositionMovementInstruction002V04 `xml:"IntraPosMvmntInstr"`
}

func (*Document01300204) AddMessage 

func (d *Document01300204) AddMessage() *IntraPositionMovementInstruction002V04

type Document01400101 

type Document01400101 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.001.01 Document"`
	Message *IntraPositionMovementStatusAdviceV01 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400101) AddMessage 

func (d *Document01400101) AddMessage() *IntraPositionMovementStatusAdviceV01

type Document01400102 

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

func (*Document01400102) AddMessage 

func (d *Document01400102) AddMessage() *IntraPositionMovementStatusAdviceV02

type Document01400103 

type Document01400103 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.001.03 Document"`
	Message *IntraPositionMovementStatusAdviceV03 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400103) AddMessage 

func (d *Document01400103) AddMessage() *IntraPositionMovementStatusAdviceV03

type Document01400104 

type Document01400104 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.001.04 Document"`
	Message *IntraPositionMovementStatusAdviceV04 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400104) AddMessage 

func (d *Document01400104) AddMessage() *IntraPositionMovementStatusAdviceV04

type Document01400105 

type Document01400105 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.001.05 Document"`
	Message *IntraPositionMovementStatusAdviceV05 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400105) AddMessage 

func (d *Document01400105) AddMessage() *IntraPositionMovementStatusAdviceV05

type Document01400204 

type Document01400204 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.002.04 Document"`
	Message *IntraPositionMovementStatusAdvice002V04 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400204) AddMessage 

func (d *Document01400204) AddMessage() *IntraPositionMovementStatusAdvice002V04

type Document01400205 

type Document01400205 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:semt.014.002.05 Document"`
	Message *IntraPositionMovementStatusAdvice002V05 `xml:"IntraPosMvmntStsAdvc"`
}

func (*Document01400205) AddMessage 

func (d *Document01400205) AddMessage() *IntraPositionMovementStatusAdvice002V05

type Document01500101 

type Document01500101 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.001.01 Document"`
	Message *IntraPositionMovementConfirmationV01 `xml:"IntraPosMvmntConf"`
}

func (*Document01500101) AddMessage 

func (d *Document01500101) AddMessage() *IntraPositionMovementConfirmationV01

type Document01500102 

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

func (*Document01500102) AddMessage 

func (d *Document01500102) AddMessage() *IntraPositionMovementConfirmationV02

type Document01500103 

type Document01500103 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.001.03 Document"`
	Message *IntraPositionMovementConfirmationV03 `xml:"IntraPosMvmntConf"`
}

func (*Document01500103) AddMessage 

func (d *Document01500103) AddMessage() *IntraPositionMovementConfirmationV03

type Document01500104 

type Document01500104 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.001.04 Document"`
	Message *IntraPositionMovementConfirmationV04 `xml:"IntraPosMvmntConf"`
}

func (*Document01500104) AddMessage 

func (d *Document01500104) AddMessage() *IntraPositionMovementConfirmationV04

type Document01500105 

type Document01500105 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.001.05 Document"`
	Message *IntraPositionMovementConfirmationV05 `xml:"IntraPosMvmntConf"`
}

func (*Document01500105) AddMessage 

func (d *Document01500105) AddMessage() *IntraPositionMovementConfirmationV05

type Document01500106 

type Document01500106 struct {
	XMLName xml.Name                              `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.001.06 Document"`
	Message *IntraPositionMovementConfirmationV06 `xml:"IntraPosMvmntConf"`
}

func (*Document01500106) AddMessage 

func (d *Document01500106) AddMessage() *IntraPositionMovementConfirmationV06

type Document01500205 

type Document01500205 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.002.05 Document"`
	Message *IntraPositionMovementConfirmation002V05 `xml:"IntraPosMvmntConf"`
}

func (*Document01500205) AddMessage 

func (d *Document01500205) AddMessage() *IntraPositionMovementConfirmation002V05

type Document01500206 

type Document01500206 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:semt.015.002.06 Document"`
	Message *IntraPositionMovementConfirmation002V06 `xml:"IntraPosMvmntConf"`
}

func (*Document01500206) AddMessage 

func (d *Document01500206) AddMessage() *IntraPositionMovementConfirmation002V06

type Document01600101 

type Document01600101 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.001.01 Document"`
	Message *IntraPositionMovementPostingReportV01 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600101) AddMessage 

func (d *Document01600101) AddMessage() *IntraPositionMovementPostingReportV01

type Document01600102 

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

func (*Document01600102) AddMessage 

func (d *Document01600102) AddMessage() *IntraPositionMovementPostingReportV02

type Document01600103 

type Document01600103 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.001.03 Document"`
	Message *IntraPositionMovementPostingReportV03 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600103) AddMessage 

func (d *Document01600103) AddMessage() *IntraPositionMovementPostingReportV03

type Document01600104 

type Document01600104 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.001.04 Document"`
	Message *IntraPositionMovementPostingReportV04 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600104) AddMessage 

func (d *Document01600104) AddMessage() *IntraPositionMovementPostingReportV04

type Document01600105 

type Document01600105 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.001.05 Document"`
	Message *IntraPositionMovementPostingReportV05 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600105) AddMessage 

func (d *Document01600105) AddMessage() *IntraPositionMovementPostingReportV05

type Document01600106 

type Document01600106 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.001.06 Document"`
	Message *IntraPositionMovementPostingReportV06 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600106) AddMessage 

func (d *Document01600106) AddMessage() *IntraPositionMovementPostingReportV06

type Document01600205 

type Document01600205 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.002.05 Document"`
	Message *IntraPositionMovementPostingReport002V05 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600205) AddMessage 

func (d *Document01600205) AddMessage() *IntraPositionMovementPostingReport002V05

type Document01600206 

type Document01600206 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.016.002.06 Document"`
	Message *IntraPositionMovementPostingReport002V06 `xml:"IntraPosMvmntPstngRpt"`
}

func (*Document01600206) AddMessage 

func (d *Document01600206) AddMessage() *IntraPositionMovementPostingReport002V06

type Document01700101 

type Document01700101 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.01 Document"`
	Message *SecuritiesTransactionPostingReportV01 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700101) AddMessage 

func (d *Document01700101) AddMessage() *SecuritiesTransactionPostingReportV01

type Document01700102 

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

func (*Document01700102) AddMessage 

func (d *Document01700102) AddMessage() *SecuritiesTransactionPostingReportV02

type Document01700103 

type Document01700103 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.03 Document"`
	Message *SecuritiesTransactionPostingReportV03 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700103) AddMessage 

func (d *Document01700103) AddMessage() *SecuritiesTransactionPostingReportV03

type Document01700104 

type Document01700104 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.04 Document"`
	Message *SecuritiesTransactionPostingReportV04 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700104) AddMessage 

func (d *Document01700104) AddMessage() *SecuritiesTransactionPostingReportV04

type Document01700105 

type Document01700105 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.05 Document"`
	Message *SecuritiesTransactionPostingReportV05 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700105) AddMessage 

func (d *Document01700105) AddMessage() *SecuritiesTransactionPostingReportV05

type Document01700106 

type Document01700106 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.06 Document"`
	Message *SecuritiesTransactionPostingReportV06 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700106) AddMessage 

func (d *Document01700106) AddMessage() *SecuritiesTransactionPostingReportV06

type Document01700107 

type Document01700107 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.001.07 Document"`
	Message *SecuritiesTransactionPostingReportV07 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700107) AddMessage 

func (d *Document01700107) AddMessage() *SecuritiesTransactionPostingReportV07

type Document01700206 

type Document01700206 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.002.06 Document"`
	Message *SecuritiesTransactionPostingReport002V06 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700206) AddMessage 

func (d *Document01700206) AddMessage() *SecuritiesTransactionPostingReport002V06

type Document01700207 

type Document01700207 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.017.002.07 Document"`
	Message *SecuritiesTransactionPostingReport002V07 `xml:"SctiesTxPstngRpt"`
}

func (*Document01700207) AddMessage 

func (d *Document01700207) AddMessage() *SecuritiesTransactionPostingReport002V07

type Document01800101 

type Document01800101 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.01 Document"`
	Message *SecuritiesTransactionPendingReportV01 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800101) AddMessage 

func (d *Document01800101) AddMessage() *SecuritiesTransactionPendingReportV01

type Document01800102 

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

func (*Document01800102) AddMessage 

func (d *Document01800102) AddMessage() *SecuritiesTransactionPendingReportV02

type Document01800103 

type Document01800103 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.03 Document"`
	Message *SecuritiesTransactionPendingReportV03 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800103) AddMessage 

func (d *Document01800103) AddMessage() *SecuritiesTransactionPendingReportV03

type Document01800104 

type Document01800104 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.04 Document"`
	Message *SecuritiesTransactionPendingReportV04 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800104) AddMessage 

func (d *Document01800104) AddMessage() *SecuritiesTransactionPendingReportV04

type Document01800105 

type Document01800105 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.05 Document"`
	Message *SecuritiesTransactionPendingReportV05 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800105) AddMessage 

func (d *Document01800105) AddMessage() *SecuritiesTransactionPendingReportV05

type Document01800106 

type Document01800106 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.06 Document"`
	Message *SecuritiesTransactionPendingReportV06 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800106) AddMessage 

func (d *Document01800106) AddMessage() *SecuritiesTransactionPendingReportV06

type Document01800107 

type Document01800107 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.07 Document"`
	Message *SecuritiesTransactionPendingReportV07 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800107) AddMessage 

func (d *Document01800107) AddMessage() *SecuritiesTransactionPendingReportV07

type Document01800108 

type Document01800108 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.001.08 Document"`
	Message *SecuritiesTransactionPendingReportV08 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800108) AddMessage 

func (d *Document01800108) AddMessage() *SecuritiesTransactionPendingReportV08

type Document01800207 

type Document01800207 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.002.07 Document"`
	Message *SecuritiesTransactionPendingReport002V07 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800207) AddMessage 

func (d *Document01800207) AddMessage() *SecuritiesTransactionPendingReport002V07

type Document01800208 

type Document01800208 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:semt.018.002.08 Document"`
	Message *SecuritiesTransactionPendingReport002V08 `xml:"SctiesTxPdgRpt"`
}

func (*Document01800208) AddMessage 

func (d *Document01800208) AddMessage() *SecuritiesTransactionPendingReport002V08

type Document01900101 

type Document01900101 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.01 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV01 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900101) AddMessage 

func (d *Document01900101) AddMessage() *SecuritiesSettlementTransactionAllegementReportV01

type Document01900102 

type Document01900102 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.02 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV02 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900102) AddMessage 

func (d *Document01900102) AddMessage() *SecuritiesSettlementTransactionAllegementReportV02

type Document01900103 

type Document01900103 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.03 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV03 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900103) AddMessage 

func (d *Document01900103) AddMessage() *SecuritiesSettlementTransactionAllegementReportV03

type Document01900104 

type Document01900104 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.04 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV04 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900104) AddMessage 

func (d *Document01900104) AddMessage() *SecuritiesSettlementTransactionAllegementReportV04

type Document01900105 

type Document01900105 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.05 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV05 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900105) AddMessage 

func (d *Document01900105) AddMessage() *SecuritiesSettlementTransactionAllegementReportV05

type Document01900106 

type Document01900106 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.001.06 Document"`
	Message *SecuritiesSettlementTransactionAllegementReportV06 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900106) AddMessage 

func (d *Document01900106) AddMessage() *SecuritiesSettlementTransactionAllegementReportV06

type Document01900205 

type Document01900205 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.002.05 Document"`
	Message *SecuritiesSettlementTransactionAllegementReport002V05 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900205) AddMessage 

func (d *Document01900205) AddMessage() *SecuritiesSettlementTransactionAllegementReport002V05

type Document01900206 

type Document01900206 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.019.002.06 Document"`
	Message *SecuritiesSettlementTransactionAllegementReport002V06 `xml:"SctiesSttlmTxAllgmtRpt"`
}

func (*Document01900206) AddMessage 

func (d *Document01900206) AddMessage() *SecuritiesSettlementTransactionAllegementReport002V06

type Document02000101 

type Document02000101 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.001.01 Document"`
	Message *SecuritiesMessageCancellationAdviceV01 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000101) AddMessage 

func (d *Document02000101) AddMessage() *SecuritiesMessageCancellationAdviceV01

type Document02000102 

type Document02000102 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.001.02 Document"`
	Message *SecuritiesMessageCancellationAdviceV02 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000102) AddMessage 

func (d *Document02000102) AddMessage() *SecuritiesMessageCancellationAdviceV02

type Document02000103 

type Document02000103 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.001.03 Document"`
	Message *SecuritiesMessageCancellationAdviceV03 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000103) AddMessage 

func (d *Document02000103) AddMessage() *SecuritiesMessageCancellationAdviceV03

type Document02000104 

type Document02000104 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.001.04 Document"`
	Message *SecuritiesMessageCancellationAdviceV04 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000104) AddMessage 

func (d *Document02000104) AddMessage() *SecuritiesMessageCancellationAdviceV04

type Document02000105 

type Document02000105 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.001.05 Document"`
	Message *SecuritiesMessageCancellationAdviceV05 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000105) AddMessage 

func (d *Document02000105) AddMessage() *SecuritiesMessageCancellationAdviceV05

type Document02000205 

type Document02000205 struct {
	XMLName xml.Name                                   `xml:"urn:iso:std:iso:20022:tech:xsd:semt.020.002.05 Document"`
	Message *SecuritiesMessageCancellationAdvice002V05 `xml:"SctiesMsgCxlAdvc"`
}

func (*Document02000205) AddMessage 

func (d *Document02000205) AddMessage() *SecuritiesMessageCancellationAdvice002V05

type Document02100101 

type Document02100101 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.01 Document"`
	Message *SecuritiesStatementQueryV01 `xml:"SctiesStmtQry"`
}

func (*Document02100101) AddMessage 

func (d *Document02100101) AddMessage() *SecuritiesStatementQueryV01

type Document02100102 

type Document02100102 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.02 Document"`
	Message *SecuritiesStatementQueryV02 `xml:"SctiesStmtQry"`
}

func (*Document02100102) AddMessage 

func (d *Document02100102) AddMessage() *SecuritiesStatementQueryV02

type Document02100103 

type Document02100103 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.03 Document"`
	Message *SecuritiesStatementQueryV03 `xml:"SctiesStmtQry"`
}

func (*Document02100103) AddMessage 

func (d *Document02100103) AddMessage() *SecuritiesStatementQueryV03

type Document02100104 

type Document02100104 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.04 Document"`
	Message *SecuritiesStatementQueryV04 `xml:"SctiesStmtQry"`
}

func (*Document02100104) AddMessage 

func (d *Document02100104) AddMessage() *SecuritiesStatementQueryV04

type Document02100105 

type Document02100105 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.05 Document"`
	Message *SecuritiesStatementQueryV05 `xml:"SctiesStmtQry"`
}

func (*Document02100105) AddMessage 

func (d *Document02100105) AddMessage() *SecuritiesStatementQueryV05

type Document02100106 

type Document02100106 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.001.06 Document"`
	Message *SecuritiesStatementQueryV06 `xml:"SctiesStmtQry"`
}

func (*Document02100106) AddMessage 

func (d *Document02100106) AddMessage() *SecuritiesStatementQueryV06

type Document02100206 

type Document02100206 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:semt.021.002.06 Document"`
	Message *SecuritiesStatementQuery002V06 `xml:"SctiesStmtQry"`
}

func (*Document02100206) AddMessage 

func (d *Document02100206) AddMessage() *SecuritiesStatementQuery002V06

type Document02200101 

type Document02200101 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.022.001.01 Document"`
	Message *SecuritiesSettlementTransactionAuditTrailReportV01 `xml:"SctiesSttlmTxAudtTrlRpt"`
}

func (*Document02200101) AddMessage 

func (d *Document02200101) AddMessage() *SecuritiesSettlementTransactionAuditTrailReportV01

type Document02200102 

type Document02200102 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.022.001.02 Document"`
	Message *SecuritiesSettlementTransactionAuditTrailReportV02 `xml:"SctiesSttlmTxAudtTrlRpt"`
}

func (*Document02200102) AddMessage 

func (d *Document02200102) AddMessage() *SecuritiesSettlementTransactionAuditTrailReportV02

type Document02200103 

type Document02200103 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.022.001.03 Document"`
	Message *SecuritiesSettlementTransactionAuditTrailReportV03 `xml:"SctiesSttlmTxAudtTrlRpt"`
}

func (*Document02200103) AddMessage 

func (d *Document02200103) AddMessage() *SecuritiesSettlementTransactionAuditTrailReportV03

type Document02200203 

type Document02200203 struct {
	XMLName xml.Name                                               `xml:"urn:iso:std:iso:20022:tech:xsd:semt.022.002.03 Document"`
	Message *SecuritiesSettlementTransactionAuditTrailReport002V03 `xml:"SctiesSttlmTxAudtTrlRpt"`
}

func (*Document02200203) AddMessage 

func (d *Document02200203) AddMessage() *SecuritiesSettlementTransactionAuditTrailReport002V03

type Document02300101 

type Document02300101 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:semt.023.001.01 Document"`
	Message *SecuritiesEndOfProcessReportV01 `xml:"SctiesEndOfPrcRpt"`
}

func (*Document02300101) AddMessage 

func (d *Document02300101) AddMessage() *SecuritiesEndOfProcessReportV01

type Document02400101 

type Document02400101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:semt.024.001.01 Document"`
	Message *TotalPortfolioValuationReportV01 `xml:"TtlPrtflValtnRpt"`
}

func (*Document02400101) AddMessage 

func (d *Document02400101) AddMessage() *TotalPortfolioValuationReportV01

type Document04100102 

type Document04100102 struct {
	XMLName xml.Name                                `xml:"urn:iso:std:iso:20022:tech:xsd:semt.041.001.02 Document"`
	Message *SecuritiesBalanceTransparencyReportV02 `xml:"SctiesBalTrnsprncyRpt"`
}

func (*Document04100102) AddMessage 

func (d *Document04100102) AddMessage() *SecuritiesBalanceTransparencyReportV02

type Document04200101 

type Document04200101 struct {
	XMLName xml.Name                                            `xml:"urn:iso:std:iso:20022:tech:xsd:semt.042.001.01 Document"`
	Message *SecuritiesBalanceTransparencyReportStatusAdviceV01 `xml:"SctiesBalTrnsprncyRptStsAdvc"`
}

func (*Document04200101) AddMessage 

func (d *Document04200101) AddMessage() *SecuritiesBalanceTransparencyReportStatusAdviceV01

type IntraPositionMovementConfirmation002V05 

type IntraPositionMovementConfirmation002V05 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters25 `xml:"AddtlParams,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat17Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes75 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails35 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmation002V05) AddAccountOwner 

func (i *IntraPositionMovementConfirmation002V05) AddAccountOwner() *iso20022.PartyIdentification103Choice

func (*IntraPositionMovementConfirmation002V05) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmation002V05) AddAdditionalParameters() *iso20022.AdditionalParameters25

func (*IntraPositionMovementConfirmation002V05) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmation002V05) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes75

func (*IntraPositionMovementConfirmation002V05) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmation002V05) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*IntraPositionMovementConfirmation002V05) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmation002V05) AddIntraPositionDetails() *iso20022.IntraPositionDetails35

func (*IntraPositionMovementConfirmation002V05) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmation002V05) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*IntraPositionMovementConfirmation002V05) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmation002V05) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat17Choice

func (*IntraPositionMovementConfirmation002V05) AddSupplementaryData 

func (i *IntraPositionMovementConfirmation002V05) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmation002V06 

type IntraPositionMovementConfirmation002V06 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters25 `xml:"AddtlParams,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat17Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes75 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails43 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmation002V06) AddAccountOwner 

func (i *IntraPositionMovementConfirmation002V06) AddAccountOwner() *iso20022.PartyIdentification103Choice

func (*IntraPositionMovementConfirmation002V06) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmation002V06) AddAdditionalParameters() *iso20022.AdditionalParameters25

func (*IntraPositionMovementConfirmation002V06) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmation002V06) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes75

func (*IntraPositionMovementConfirmation002V06) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmation002V06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*IntraPositionMovementConfirmation002V06) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmation002V06) AddIntraPositionDetails() *iso20022.IntraPositionDetails43

func (*IntraPositionMovementConfirmation002V06) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmation002V06) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*IntraPositionMovementConfirmation002V06) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmation002V06) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat17Choice

func (*IntraPositionMovementConfirmation002V06) AddSupplementaryData 

func (i *IntraPositionMovementConfirmation002V06) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmationV01 

type IntraPositionMovementConfirmationV01 struct {

	// Information that unambiguously identifies an IntraPositionMovementConfirmation message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters3 `xml:"AddtlParams,omitempty"`

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes4 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails2 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmationV01) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*IntraPositionMovementConfirmationV01) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV01) AddAdditionalParameters() *iso20022.AdditionalParameters3

func (*IntraPositionMovementConfirmationV01) AddExtension 

func (i *IntraPositionMovementConfirmationV01) AddExtension() *iso20022.Extension2

func (*IntraPositionMovementConfirmationV01) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV01) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes4

func (*IntraPositionMovementConfirmationV01) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*IntraPositionMovementConfirmationV01) AddIdentification 

func (i *IntraPositionMovementConfirmationV01) AddIdentification() *iso20022.DocumentIdentification11

func (*IntraPositionMovementConfirmationV01) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV01) AddIntraPositionDetails() *iso20022.IntraPositionDetails2

func (*IntraPositionMovementConfirmationV01) AddMessageOriginator 

func (i *IntraPositionMovementConfirmationV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementConfirmationV01) AddMessageRecipient 

func (i *IntraPositionMovementConfirmationV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementConfirmationV01) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementConfirmationV01) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV01) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

type IntraPositionMovementConfirmationV02 

type IntraPositionMovementConfirmationV02 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters8 `xml:"AddtlParams,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"`

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes21 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails12 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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. 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 (*IntraPositionMovementConfirmationV02) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementConfirmationV02) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV02) AddAdditionalParameters() *iso20022.AdditionalParameters8

func (*IntraPositionMovementConfirmationV02) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV02) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes21

func (*IntraPositionMovementConfirmationV02) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV02) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*IntraPositionMovementConfirmationV02) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV02) AddIntraPositionDetails() *iso20022.IntraPositionDetails12

func (*IntraPositionMovementConfirmationV02) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementConfirmationV02) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV02) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

func (*IntraPositionMovementConfirmationV02) AddSupplementaryData 

func (i *IntraPositionMovementConfirmationV02) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmationV03 

type IntraPositionMovementConfirmationV03 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters10 `xml:"AddtlParams,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"`

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes36 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails22 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmationV03) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementConfirmationV03) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV03) AddAdditionalParameters() *iso20022.AdditionalParameters10

func (*IntraPositionMovementConfirmationV03) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV03) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes36

func (*IntraPositionMovementConfirmationV03) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV03) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*IntraPositionMovementConfirmationV03) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV03) AddIntraPositionDetails() *iso20022.IntraPositionDetails22

func (*IntraPositionMovementConfirmationV03) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementConfirmationV03) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV03) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

func (*IntraPositionMovementConfirmationV03) AddSupplementaryData 

func (i *IntraPositionMovementConfirmationV03) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmationV04 

type IntraPositionMovementConfirmationV04 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters10 `xml:"AddtlParams,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"`

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes36 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails27 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmationV04) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementConfirmationV04) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV04) AddAdditionalParameters() *iso20022.AdditionalParameters10

func (*IntraPositionMovementConfirmationV04) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV04) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes36

func (*IntraPositionMovementConfirmationV04) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV04) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*IntraPositionMovementConfirmationV04) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV04) AddIntraPositionDetails() *iso20022.IntraPositionDetails27

func (*IntraPositionMovementConfirmationV04) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementConfirmationV04) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV04) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

func (*IntraPositionMovementConfirmationV04) AddSupplementaryData 

func (i *IntraPositionMovementConfirmationV04) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmationV05 

type IntraPositionMovementConfirmationV05 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters21 `xml:"AddtlParams,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat10Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes63 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails34 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmationV05) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV05) AddAccountOwner() *iso20022.PartyIdentification92Choice

func (*IntraPositionMovementConfirmationV05) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV05) AddAdditionalParameters() *iso20022.AdditionalParameters21

func (*IntraPositionMovementConfirmationV05) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV05) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes63

func (*IntraPositionMovementConfirmationV05) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV05) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*IntraPositionMovementConfirmationV05) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV05) AddIntraPositionDetails() *iso20022.IntraPositionDetails34

func (*IntraPositionMovementConfirmationV05) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*IntraPositionMovementConfirmationV05) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV05) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat10Choice

func (*IntraPositionMovementConfirmationV05) AddSupplementaryData 

func (i *IntraPositionMovementConfirmationV05) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementConfirmationV06 

type IntraPositionMovementConfirmationV06 struct {

	// Additional parameters to the transaction.
	AdditionalParameters *iso20022.AdditionalParameters21 `xml:"AddtlParams,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat10Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes63 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails41 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementConfirmation to an account owner to confirm the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. 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 (*IntraPositionMovementConfirmationV06) AddAccountOwner 

func (i *IntraPositionMovementConfirmationV06) AddAccountOwner() *iso20022.PartyIdentification92Choice

func (*IntraPositionMovementConfirmationV06) AddAdditionalParameters 

func (i *IntraPositionMovementConfirmationV06) AddAdditionalParameters() *iso20022.AdditionalParameters21

func (*IntraPositionMovementConfirmationV06) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementConfirmationV06) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes63

func (*IntraPositionMovementConfirmationV06) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementConfirmationV06) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*IntraPositionMovementConfirmationV06) AddIntraPositionDetails 

func (i *IntraPositionMovementConfirmationV06) AddIntraPositionDetails() *iso20022.IntraPositionDetails41

func (*IntraPositionMovementConfirmationV06) AddSafekeepingAccount 

func (i *IntraPositionMovementConfirmationV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*IntraPositionMovementConfirmationV06) AddSafekeepingPlace 

func (i *IntraPositionMovementConfirmationV06) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat10Choice

func (*IntraPositionMovementConfirmationV06) AddSupplementaryData 

func (i *IntraPositionMovementConfirmationV06) AddSupplementaryData() *iso20022.SupplementaryData1

type IntraPositionMovementInstruction002V04 

type IntraPositionMovementInstruction002V04 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.RestrictedFINXMax16Text `xml:"TxId"`

	// Identification assigned by the account servicer to unambiguously identify a corporate action event.
	CorporateActionEventIdentification *iso20022.Identification16 `xml:"CorpActnEvtId,omitempty"`

	// 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.Linkages42 `xml:"Lnkgs,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat17Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes75 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails36 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementInstruction to an account servicer to instruct the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. The account owner/servicer relationship may be: - 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 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. 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 (*IntraPositionMovementInstruction002V04) AddAccountOwner 

func (i *IntraPositionMovementInstruction002V04) AddAccountOwner() *iso20022.PartyIdentification103Choice

func (*IntraPositionMovementInstruction002V04) AddCorporateActionEventIdentification 

func (i *IntraPositionMovementInstruction002V04) AddCorporateActionEventIdentification() *iso20022.Identification16

func (*IntraPositionMovementInstruction002V04) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementInstruction002V04) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes75

func (*IntraPositionMovementInstruction002V04) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementInstruction002V04) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification20

func (*IntraPositionMovementInstruction002V04) AddIntraPositionDetails 

func (i *IntraPositionMovementInstruction002V04) AddIntraPositionDetails() *iso20022.IntraPositionDetails36

func (*IntraPositionMovementInstruction002V04) AddLinkages 

func (i *IntraPositionMovementInstruction002V04) AddLinkages() *iso20022.Linkages42

func (*IntraPositionMovementInstruction002V04) AddNumberCounts 

func (i *IntraPositionMovementInstruction002V04) AddNumberCounts() *iso20022.NumberCount1Choice

func (*IntraPositionMovementInstruction002V04) AddSafekeepingAccount 

func (i *IntraPositionMovementInstruction002V04) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*IntraPositionMovementInstruction002V04) AddSafekeepingPlace 

func (i *IntraPositionMovementInstruction002V04) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat17Choice

func (*IntraPositionMovementInstruction002V04) AddSupplementaryData 

func (i *IntraPositionMovementInstruction002V04) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementInstruction002V04) SetTransactionIdentification 

func (i *IntraPositionMovementInstruction002V04) SetTransactionIdentification(value string)

type IntraPositionMovementInstructionV01 

type IntraPositionMovementInstructionV01 struct {

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

	// Identification assigned by the account servicer to unambiguously identify a corporate action event.
	CorporateActionEventIdentification *iso20022.Identification1 `xml:"CorpActnEvtId,omitempty"`

	// Link to another transaction that must be processed after, before or at the same time.
	Linkages *iso20022.Linkages2 `xml:"Lnkgs,omitempty"`

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes4 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails1 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementInstruction to an account servicer to instruct the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. The account owner/servicer relationship may be: - 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 - 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. 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 (*IntraPositionMovementInstructionV01) AddAccountOwner 

func (i *IntraPositionMovementInstructionV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*IntraPositionMovementInstructionV01) AddCorporateActionEventIdentification 

func (i *IntraPositionMovementInstructionV01) AddCorporateActionEventIdentification() *iso20022.Identification1

func (*IntraPositionMovementInstructionV01) AddExtension 

func (i *IntraPositionMovementInstructionV01) AddExtension() *iso20022.Extension2

func (*IntraPositionMovementInstructionV01) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementInstructionV01) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes4

func (*IntraPositionMovementInstructionV01) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementInstructionV01) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification11

func (*IntraPositionMovementInstructionV01) AddIdentification 

func (i *IntraPositionMovementInstructionV01) AddIdentification() *iso20022.TransactionAndDocumentIdentification1

func (*IntraPositionMovementInstructionV01) AddIntraPositionDetails 

func (i *IntraPositionMovementInstructionV01) AddIntraPositionDetails() *iso20022.IntraPositionDetails1

func (*IntraPositionMovementInstructionV01) AddLinkages 

func (i *IntraPositionMovementInstructionV01) AddLinkages() *iso20022.Linkages2

func (*IntraPositionMovementInstructionV01) AddMessageOriginator 

func (i *IntraPositionMovementInstructionV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementInstructionV01) AddMessageRecipient 

func (i *IntraPositionMovementInstructionV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementInstructionV01) AddSafekeepingAccount 

func (i *IntraPositionMovementInstructionV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementInstructionV01) AddSafekeepingPlace 

func (i *IntraPositionMovementInstructionV01) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

type IntraPositionMovementInstructionV02 

type IntraPositionMovementInstructionV02 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Identification assigned by the account servicer to unambiguously identify a corporate action event.
	CorporateActionEventIdentification *iso20022.Identification1 `xml:"CorpActnEvtId,omitempty"`

	// Link to another transaction that must be processed after, before or at the same time.
	Linkages *iso20022.Linkages8 `xml:"Lnkgs,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"`

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes21 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails11 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementInstruction to an account servicer to instruct the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. The account owner/servicer relationship may be: - 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 - 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. 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 (*IntraPositionMovementInstructionV02) AddAccountOwner 

func (i *IntraPositionMovementInstructionV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementInstructionV02) AddCorporateActionEventIdentification 

func (i *IntraPositionMovementInstructionV02) AddCorporateActionEventIdentification() *iso20022.Identification1

func (*IntraPositionMovementInstructionV02) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementInstructionV02) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes21

func (*IntraPositionMovementInstructionV02) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementInstructionV02) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*IntraPositionMovementInstructionV02) AddIntraPositionDetails 

func (i *IntraPositionMovementInstructionV02) AddIntraPositionDetails() *iso20022.IntraPositionDetails11

func (*IntraPositionMovementInstructionV02) AddLinkages 

func (i *IntraPositionMovementInstructionV02) AddLinkages() *iso20022.Linkages8

func (*IntraPositionMovementInstructionV02) AddSafekeepingAccount 

func (i *IntraPositionMovementInstructionV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementInstructionV02) AddSafekeepingPlace 

func (i *IntraPositionMovementInstructionV02) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

func (*IntraPositionMovementInstructionV02) AddSupplementaryData 

func (i *IntraPositionMovementInstructionV02) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementInstructionV02) SetTransactionIdentification 

func (i *IntraPositionMovementInstructionV02) SetTransactionIdentification(value string)

type IntraPositionMovementInstructionV03 

type IntraPositionMovementInstructionV03 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Identification assigned by the account servicer to unambiguously identify a corporate action event.
	CorporateActionEventIdentification *iso20022.Identification1 `xml:"CorpActnEvtId,omitempty"`

	// 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.Linkages19 `xml:"Lnkgs,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"`

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat3Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes36 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails21 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementInstruction to an account servicer to instruct the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. The account owner/servicer relationship may be: - 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 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. 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 (*IntraPositionMovementInstructionV03) AddAccountOwner 

func (i *IntraPositionMovementInstructionV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementInstructionV03) AddCorporateActionEventIdentification 

func (i *IntraPositionMovementInstructionV03) AddCorporateActionEventIdentification() *iso20022.Identification1

func (*IntraPositionMovementInstructionV03) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementInstructionV03) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes36

func (*IntraPositionMovementInstructionV03) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementInstructionV03) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification14

func (*IntraPositionMovementInstructionV03) AddIntraPositionDetails 

func (i *IntraPositionMovementInstructionV03) AddIntraPositionDetails() *iso20022.IntraPositionDetails21

func (*IntraPositionMovementInstructionV03) AddLinkages 

func (i *IntraPositionMovementInstructionV03) AddLinkages() *iso20022.Linkages19

func (*IntraPositionMovementInstructionV03) AddNumberCounts 

func (i *IntraPositionMovementInstructionV03) AddNumberCounts() *iso20022.NumberCount1Choice

func (*IntraPositionMovementInstructionV03) AddSafekeepingAccount 

func (i *IntraPositionMovementInstructionV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementInstructionV03) AddSafekeepingPlace 

func (i *IntraPositionMovementInstructionV03) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat3Choice

func (*IntraPositionMovementInstructionV03) AddSupplementaryData 

func (i *IntraPositionMovementInstructionV03) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementInstructionV03) SetTransactionIdentification 

func (i *IntraPositionMovementInstructionV03) SetTransactionIdentification(value string)

type IntraPositionMovementInstructionV04 

type IntraPositionMovementInstructionV04 struct {

	// Unambiguous identification of the transaction as know by the instructing party.
	TransactionIdentification *iso20022.Max35Text `xml:"TxId"`

	// Identification assigned by the account servicer to unambiguously identify a corporate action event.
	CorporateActionEventIdentification *iso20022.Identification14 `xml:"CorpActnEvtId,omitempty"`

	// 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.Linkages36 `xml:"Lnkgs,omitempty"`

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

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

	// Place where the securities are safe-kept, physically or notionally.  This place can be, for example, a local custodian, a Central Securities Depository (CSD) or an International Central Securities Depository (ICSD).
	SafekeepingPlace *iso20022.SafekeepingPlaceFormat10Choice `xml:"SfkpgPlc,omitempty"`

	// 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.FinancialInstrumentAttributes63 `xml:"FinInstrmAttrbts,omitempty"`

	// Intra-position movement transaction details.
	IntraPositionDetails *iso20022.IntraPositionDetails33 `xml:"IntraPosDtls"`

	// 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 IntraPositionMovementInstruction to an account servicer to instruct the movement of securities within its holding from one sub-balance to another, for example, blocking of securities. The account owner/servicer relationship may be: - 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 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. 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 (*IntraPositionMovementInstructionV04) AddAccountOwner 

func (i *IntraPositionMovementInstructionV04) AddAccountOwner() *iso20022.PartyIdentification92Choice

func (*IntraPositionMovementInstructionV04) AddCorporateActionEventIdentification 

func (i *IntraPositionMovementInstructionV04) AddCorporateActionEventIdentification() *iso20022.Identification14

func (*IntraPositionMovementInstructionV04) AddFinancialInstrumentAttributes 

func (i *IntraPositionMovementInstructionV04) AddFinancialInstrumentAttributes() *iso20022.FinancialInstrumentAttributes63

func (*IntraPositionMovementInstructionV04) AddFinancialInstrumentIdentification 

func (i *IntraPositionMovementInstructionV04) AddFinancialInstrumentIdentification() *iso20022.SecurityIdentification19

func (*IntraPositionMovementInstructionV04) AddIntraPositionDetails 

func (i *IntraPositionMovementInstructionV04) AddIntraPositionDetails() *iso20022.IntraPositionDetails33

func (*IntraPositionMovementInstructionV04) AddLinkages 

func (i *IntraPositionMovementInstructionV04) AddLinkages() *iso20022.Linkages36

func (*IntraPositionMovementInstructionV04) AddNumberCounts 

func (i *IntraPositionMovementInstructionV04) AddNumberCounts() *iso20022.NumberCount1Choice

func (*IntraPositionMovementInstructionV04) AddSafekeepingAccount 

func (i *IntraPositionMovementInstructionV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*IntraPositionMovementInstructionV04) AddSafekeepingPlace 

func (i *IntraPositionMovementInstructionV04) AddSafekeepingPlace() *iso20022.SafekeepingPlaceFormat10Choice

func (*IntraPositionMovementInstructionV04) AddSupplementaryData 

func (i *IntraPositionMovementInstructionV04) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementInstructionV04) SetTransactionIdentification 

func (i *IntraPositionMovementInstructionV04) SetTransactionIdentification(value string)

type IntraPositionMovementPostingReport002V05 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement49 `xml:"StmtGnlDtls"`

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

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

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails22 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, that is, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReport002V05) AddAccountOwner 

func (i *IntraPositionMovementPostingReport002V05) AddAccountOwner() *iso20022.PartyIdentification103Choice

func (*IntraPositionMovementPostingReport002V05) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReport002V05) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails22

func (*IntraPositionMovementPostingReport002V05) AddPagination 

func (i *IntraPositionMovementPostingReport002V05) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReport002V05) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReport002V05) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*IntraPositionMovementPostingReport002V05) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReport002V05) AddStatementGeneralDetails() *iso20022.Statement49

type IntraPositionMovementPostingReport002V06 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement49 `xml:"StmtGnlDtls"`

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

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

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails26 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, that is, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReport002V06) AddAccountOwner 

func (i *IntraPositionMovementPostingReport002V06) AddAccountOwner() *iso20022.PartyIdentification103Choice

func (*IntraPositionMovementPostingReport002V06) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReport002V06) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails26

func (*IntraPositionMovementPostingReport002V06) AddPagination 

func (i *IntraPositionMovementPostingReport002V06) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReport002V06) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReport002V06) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*IntraPositionMovementPostingReport002V06) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReport002V06) AddStatementGeneralDetails() *iso20022.Statement49

type IntraPositionMovementPostingReportV01 

type IntraPositionMovementPostingReportV01 struct {

	// Information that unambiguously identifies an IntraPositionMovementPostingReport message as known by the account servicer.
	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"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement15 `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"`

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails1 `xml:"FinInstrm,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 an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, ie, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReportV01) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*IntraPositionMovementPostingReportV01) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV01) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails1

func (*IntraPositionMovementPostingReportV01) AddIdentification 

func (i *IntraPositionMovementPostingReportV01) AddIdentification() *iso20022.DocumentIdentification11

func (*IntraPositionMovementPostingReportV01) AddMessageOriginator 

func (i *IntraPositionMovementPostingReportV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementPostingReportV01) AddMessageRecipient 

func (i *IntraPositionMovementPostingReportV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementPostingReportV01) AddPagination 

func (i *IntraPositionMovementPostingReportV01) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV01) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementPostingReportV01) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV01) AddStatementGeneralDetails() *iso20022.Statement15

type IntraPositionMovementPostingReportV02 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement15 `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"`

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails6 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, ie, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReportV02) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementPostingReportV02) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV02) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails6

func (*IntraPositionMovementPostingReportV02) AddPagination 

func (i *IntraPositionMovementPostingReportV02) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV02) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementPostingReportV02) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV02) AddStatementGeneralDetails() *iso20022.Statement15

type IntraPositionMovementPostingReportV03 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement15 `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"`

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails10 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, ie, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReportV03) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementPostingReportV03) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV03) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails10

func (*IntraPositionMovementPostingReportV03) AddPagination 

func (i *IntraPositionMovementPostingReportV03) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV03) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementPostingReportV03) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV03) AddStatementGeneralDetails() *iso20022.Statement15

type IntraPositionMovementPostingReportV04 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement15 `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"`

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails14 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, that is, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 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 (*IntraPositionMovementPostingReportV04) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*IntraPositionMovementPostingReportV04) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV04) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails14

func (*IntraPositionMovementPostingReportV04) AddPagination 

func (i *IntraPositionMovementPostingReportV04) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV04) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*IntraPositionMovementPostingReportV04) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV04) AddStatementGeneralDetails() *iso20022.Statement15

type IntraPositionMovementPostingReportV05 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement43 `xml:"StmtGnlDtls"`

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

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

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails21 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, that is, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReportV05) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV05) AddAccountOwner() *iso20022.PartyIdentification92Choice

func (*IntraPositionMovementPostingReportV05) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV05) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails21

func (*IntraPositionMovementPostingReportV05) AddPagination 

func (i *IntraPositionMovementPostingReportV05) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV05) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*IntraPositionMovementPostingReportV05) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV05) AddStatementGeneralDetails() *iso20022.Statement43

type IntraPositionMovementPostingReportV06 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement43 `xml:"StmtGnlDtls"`

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

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

	// Reporting per financial instrument.
	FinancialInstrument []*iso20022.FinancialInstrumentDetails24 `xml:"FinInstrm,omitempty"`
}

Scope An account servicer sends an IntraPositionMovementPostingReport to an account owner to provide the details of increases and decreases in securities with a given status within a holding, that is, intra-position transfers, which occurred during a specified period, for all or selected securities in a specified safekeeping account which the account servicer holds for 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 (*IntraPositionMovementPostingReportV06) AddAccountOwner 

func (i *IntraPositionMovementPostingReportV06) AddAccountOwner() *iso20022.PartyIdentification92Choice

func (*IntraPositionMovementPostingReportV06) AddFinancialInstrument 

func (i *IntraPositionMovementPostingReportV06) AddFinancialInstrument() *iso20022.FinancialInstrumentDetails24

func (*IntraPositionMovementPostingReportV06) AddPagination 

func (i *IntraPositionMovementPostingReportV06) AddPagination() *iso20022.Pagination

func (*IntraPositionMovementPostingReportV06) AddSafekeepingAccount 

func (i *IntraPositionMovementPostingReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*IntraPositionMovementPostingReportV06) AddStatementGeneralDetails 

func (i *IntraPositionMovementPostingReportV06) AddStatementGeneralDetails() *iso20022.Statement43

type IntraPositionMovementStatusAdvice002V04 

type IntraPositionMovementStatusAdvice002V04 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications34 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus6Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus20Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails38 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdvice002V04) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdvice002V04) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus6Choice

func (*IntraPositionMovementStatusAdvice002V04) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdvice002V04) AddSettlementStatus() *iso20022.SettlementStatus20Choice

func (*IntraPositionMovementStatusAdvice002V04) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdvice002V04) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdvice002V04) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdvice002V04) AddTransactionDetails() *iso20022.IntraPositionDetails38

func (*IntraPositionMovementStatusAdvice002V04) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdvice002V04) AddTransactionIdentification() *iso20022.TransactionIdentifications34

type IntraPositionMovementStatusAdvice002V05 

type IntraPositionMovementStatusAdvice002V05 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications34 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus6Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus20Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails42 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdvice002V05) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdvice002V05) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus6Choice

func (*IntraPositionMovementStatusAdvice002V05) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdvice002V05) AddSettlementStatus() *iso20022.SettlementStatus20Choice

func (*IntraPositionMovementStatusAdvice002V05) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdvice002V05) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdvice002V05) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdvice002V05) AddTransactionDetails() *iso20022.IntraPositionDetails42

func (*IntraPositionMovementStatusAdvice002V05) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdvice002V05) AddTransactionIdentification() *iso20022.TransactionIdentifications34

type IntraPositionMovementStatusAdviceV01 

type IntraPositionMovementStatusAdviceV01 struct {

	// Information that unambiguously identifies an IntraPositionMovementStatusAdvice message as known by the account servicer.
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications3 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus1Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails4 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdviceV01) AddExtension 

func (i *IntraPositionMovementStatusAdviceV01) AddExtension() *iso20022.Extension2

func (*IntraPositionMovementStatusAdviceV01) AddIdentification 

func (i *IntraPositionMovementStatusAdviceV01) AddIdentification() *iso20022.DocumentIdentification11

func (*IntraPositionMovementStatusAdviceV01) AddMessageOriginator 

func (i *IntraPositionMovementStatusAdviceV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementStatusAdviceV01) AddMessageRecipient 

func (i *IntraPositionMovementStatusAdviceV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*IntraPositionMovementStatusAdviceV01) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdviceV01) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus1Choice

func (*IntraPositionMovementStatusAdviceV01) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdviceV01) AddSettlementStatus() *iso20022.SettlementStatus2Choice

func (*IntraPositionMovementStatusAdviceV01) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdviceV01) AddTransactionDetails() *iso20022.IntraPositionDetails4

func (*IntraPositionMovementStatusAdviceV01) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdviceV01) AddTransactionIdentification() *iso20022.TransactionIdentifications3

type IntraPositionMovementStatusAdviceV02 

type IntraPositionMovementStatusAdviceV02 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications10 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus1Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus2Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails9 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdviceV02) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdviceV02) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus1Choice

func (*IntraPositionMovementStatusAdviceV02) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdviceV02) AddSettlementStatus() *iso20022.SettlementStatus2Choice

func (*IntraPositionMovementStatusAdviceV02) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdviceV02) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdviceV02) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdviceV02) AddTransactionDetails() *iso20022.IntraPositionDetails9

func (*IntraPositionMovementStatusAdviceV02) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdviceV02) AddTransactionIdentification() *iso20022.TransactionIdentifications10

type IntraPositionMovementStatusAdviceV03 

type IntraPositionMovementStatusAdviceV03 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications15 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus3Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus9Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails19 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdviceV03) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdviceV03) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus3Choice

func (*IntraPositionMovementStatusAdviceV03) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdviceV03) AddSettlementStatus() *iso20022.SettlementStatus9Choice

func (*IntraPositionMovementStatusAdviceV03) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdviceV03) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdviceV03) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdviceV03) AddTransactionDetails() *iso20022.IntraPositionDetails19

func (*IntraPositionMovementStatusAdviceV03) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdviceV03) AddTransactionIdentification() *iso20022.TransactionIdentifications15

type IntraPositionMovementStatusAdviceV04 

type IntraPositionMovementStatusAdviceV04 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications29 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus5Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus16Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails31 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdviceV04) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdviceV04) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus5Choice

func (*IntraPositionMovementStatusAdviceV04) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdviceV04) AddSettlementStatus() *iso20022.SettlementStatus16Choice

func (*IntraPositionMovementStatusAdviceV04) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdviceV04) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdviceV04) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdviceV04) AddTransactionDetails() *iso20022.IntraPositionDetails31

func (*IntraPositionMovementStatusAdviceV04) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdviceV04) AddTransactionIdentification() *iso20022.TransactionIdentifications29

type IntraPositionMovementStatusAdviceV05 

type IntraPositionMovementStatusAdviceV05 struct {

	// Unambiguous identification of a transaction as per the account owner (or the instructing party managing the account).
	TransactionIdentification *iso20022.TransactionIdentifications29 `xml:"TxId"`

	// Provides details on the processing status of the transaction.
	ProcessingStatus *iso20022.IntraPositionProcessingStatus5Choice `xml:"PrcgSts,omitempty"`

	// Provides the status of settlement of a transaction.
	SettlementStatus *iso20022.SettlementStatus16Choice `xml:"SttlmSts,omitempty"`

	// Identifies the details of the transaction.
	TransactionDetails *iso20022.IntraPositionDetails39 `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 IntraPositionMovementStatusAdvice to an account owner to advise the status of a intra-position movement instruction 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 (*IntraPositionMovementStatusAdviceV05) AddProcessingStatus 

func (i *IntraPositionMovementStatusAdviceV05) AddProcessingStatus() *iso20022.IntraPositionProcessingStatus5Choice

func (*IntraPositionMovementStatusAdviceV05) AddSettlementStatus 

func (i *IntraPositionMovementStatusAdviceV05) AddSettlementStatus() *iso20022.SettlementStatus16Choice

func (*IntraPositionMovementStatusAdviceV05) AddSupplementaryData 

func (i *IntraPositionMovementStatusAdviceV05) AddSupplementaryData() *iso20022.SupplementaryData1

func (*IntraPositionMovementStatusAdviceV05) AddTransactionDetails 

func (i *IntraPositionMovementStatusAdviceV05) AddTransactionDetails() *iso20022.IntraPositionDetails39

func (*IntraPositionMovementStatusAdviceV05) AddTransactionIdentification 

func (i *IntraPositionMovementStatusAdviceV05) AddTransactionIdentification() *iso20022.TransactionIdentifications29

type SecuritiesBalanceAccountingReport002V09 

type SecuritiesBalanceAccountingReport002V09 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 report.
	StatementGeneralDetails *iso20022.Statement51 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification111 `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary37 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation32 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification45 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement4 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement4 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReport002V09) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReport002V09) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement4

func (*SecuritiesBalanceAccountingReport002V09) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReport002V09) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesBalanceAccountingReport002V09) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReport002V09) AddAccountServicer() *iso20022.PartyIdentification111

func (*SecuritiesBalanceAccountingReport002V09) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReport002V09) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement4

func (*SecuritiesBalanceAccountingReport002V09) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReport002V09) AddBalanceForAccount() *iso20022.AggregateBalanceInformation32

func (*SecuritiesBalanceAccountingReport002V09) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReport002V09) AddIntermediaryInformation() *iso20022.Intermediary37

func (*SecuritiesBalanceAccountingReport002V09) AddPagination 

func (s *SecuritiesBalanceAccountingReport002V09) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReport002V09) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReport002V09) AddSafekeepingAccount() *iso20022.SecuritiesAccount33

func (*SecuritiesBalanceAccountingReport002V09) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReport002V09) AddStatementGeneralDetails() *iso20022.Statement51

func (*SecuritiesBalanceAccountingReport002V09) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReport002V09) AddSubAccountDetails() *iso20022.SubAccountIdentification45

type SecuritiesBalanceAccountingReportV03 

type SecuritiesBalanceAccountingReportV03 struct {

	// Information that uniquely identifies the SecuritiesBalanceAccountReport message as known by the account servicer. When the report has multiple pages, one message equals one page. Therefore, Identification uniquely identifies the page.
	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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification10Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary2 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation8 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification10 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,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 SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV03) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV03) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV03) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV03) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesBalanceAccountingReportV03) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV03) AddAccountServicer() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceAccountingReportV03) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV03) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV03) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV03) AddBalanceForAccount() *iso20022.AggregateBalanceInformation8

func (*SecuritiesBalanceAccountingReportV03) AddIdentification 

func (s *SecuritiesBalanceAccountingReportV03) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesBalanceAccountingReportV03) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV03) AddIntermediaryInformation() *iso20022.Intermediary2

func (*SecuritiesBalanceAccountingReportV03) AddMessageOriginator 

func (s *SecuritiesBalanceAccountingReportV03) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceAccountingReportV03) AddMessageRecipient 

func (s *SecuritiesBalanceAccountingReportV03) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceAccountingReportV03) AddPagination 

func (s *SecuritiesBalanceAccountingReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV03) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV03) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV03) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV03) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV03) AddSubAccountDetails() *iso20022.SubAccountIdentification10

type SecuritiesBalanceAccountingReportV04 

type SecuritiesBalanceAccountingReportV04 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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary21 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation13 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification16 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV04) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV04) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV04) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceAccountingReportV04) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV04) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceAccountingReportV04) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV04) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV04) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV04) AddBalanceForAccount() *iso20022.AggregateBalanceInformation13

func (*SecuritiesBalanceAccountingReportV04) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV04) AddIntermediaryInformation() *iso20022.Intermediary21

func (*SecuritiesBalanceAccountingReportV04) AddPagination 

func (s *SecuritiesBalanceAccountingReportV04) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV04) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV04) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV04) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV04) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV04) AddSubAccountDetails() *iso20022.SubAccountIdentification16

type SecuritiesBalanceAccountingReportV05 

type SecuritiesBalanceAccountingReportV05 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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary21 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation17 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification23 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV05) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV05) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV05) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV05) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceAccountingReportV05) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV05) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceAccountingReportV05) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV05) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV05) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV05) AddBalanceForAccount() *iso20022.AggregateBalanceInformation17

func (*SecuritiesBalanceAccountingReportV05) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV05) AddIntermediaryInformation() *iso20022.Intermediary21

func (*SecuritiesBalanceAccountingReportV05) AddPagination 

func (s *SecuritiesBalanceAccountingReportV05) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV05) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV05) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV05) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV05) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV05) AddSubAccountDetails() *iso20022.SubAccountIdentification23

type SecuritiesBalanceAccountingReportV06 

type SecuritiesBalanceAccountingReportV06 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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation22 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification29 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV06) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV06) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV06) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV06) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceAccountingReportV06) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV06) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceAccountingReportV06) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV06) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV06) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV06) AddBalanceForAccount() *iso20022.AggregateBalanceInformation22

func (*SecuritiesBalanceAccountingReportV06) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV06) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceAccountingReportV06) AddPagination 

func (s *SecuritiesBalanceAccountingReportV06) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV06) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV06) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV06) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV06) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV06) AddSubAccountDetails() *iso20022.SubAccountIdentification29

type SecuritiesBalanceAccountingReportV07 

type SecuritiesBalanceAccountingReportV07 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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation22 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification29 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV07) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV07) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV07) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV07) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceAccountingReportV07) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV07) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceAccountingReportV07) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV07) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV07) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV07) AddBalanceForAccount() *iso20022.AggregateBalanceInformation22

func (*SecuritiesBalanceAccountingReportV07) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV07) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceAccountingReportV07) AddPagination 

func (s *SecuritiesBalanceAccountingReportV07) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV07) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV07) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV07) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV07) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV07) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV07) AddSubAccountDetails() *iso20022.SubAccountIdentification29

type SecuritiesBalanceAccountingReportV08 

type SecuritiesBalanceAccountingReportV08 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 report.
	StatementGeneralDetails *iso20022.Statement20 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation26 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification38 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV08) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV08) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV08) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV08) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceAccountingReportV08) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV08) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceAccountingReportV08) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV08) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV08) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV08) AddBalanceForAccount() *iso20022.AggregateBalanceInformation26

func (*SecuritiesBalanceAccountingReportV08) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV08) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceAccountingReportV08) AddPagination 

func (s *SecuritiesBalanceAccountingReportV08) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV08) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV08) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceAccountingReportV08) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV08) AddStatementGeneralDetails() *iso20022.Statement20

func (*SecuritiesBalanceAccountingReportV08) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV08) AddSubAccountDetails() *iso20022.SubAccountIdentification38

type SecuritiesBalanceAccountingReportV09 

type SecuritiesBalanceAccountingReportV09 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 report.
	StatementGeneralDetails *iso20022.Statement40 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	AccountServicer *iso20022.PartyIdentification100 `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary32 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation31 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification43 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AcctBaseCcyTtlAmts,omitempty"`

	// Total valuation amounts provided in another currency than the base currency of the account.
	AlternateReportingCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement2 `xml:"AltrnRptgCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceAccountingReport to an account owner to provide, at a moment in time, valuations of the portfolio together with details of each financial instrument holding. The account servicer/owner relationship may be: - an accounting agent acting on behalf of an account owner, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message can be sent either audited or un-audited and may be provided on a trade date, contractual or settlement date basis. This message can only be used to list the holdings of a single (master) account. However, it is possible to break down these holdings into one or several sub-accounts. Therefore, the message can be used to either specify holdings at - the main account level, or, - the sub-account level. This message can be used to report where the financial instruments are safe-kept, physically or notionally. If a security is held in more than one safekeeping place, this can also be indicated. The SecuritiesBalanceAccountingReport message should not be used for trading purposes. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceAccountingReportV09) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV09) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV09) AddAccountOwner 

func (s *SecuritiesBalanceAccountingReportV09) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesBalanceAccountingReportV09) AddAccountServicer 

func (s *SecuritiesBalanceAccountingReportV09) AddAccountServicer() *iso20022.PartyIdentification100

func (*SecuritiesBalanceAccountingReportV09) AddAlternateReportingCurrencyTotalAmounts 

func (s *SecuritiesBalanceAccountingReportV09) AddAlternateReportingCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement2

func (*SecuritiesBalanceAccountingReportV09) AddBalanceForAccount 

func (s *SecuritiesBalanceAccountingReportV09) AddBalanceForAccount() *iso20022.AggregateBalanceInformation31

func (*SecuritiesBalanceAccountingReportV09) AddIntermediaryInformation 

func (s *SecuritiesBalanceAccountingReportV09) AddIntermediaryInformation() *iso20022.Intermediary32

func (*SecuritiesBalanceAccountingReportV09) AddPagination 

func (s *SecuritiesBalanceAccountingReportV09) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceAccountingReportV09) AddSafekeepingAccount 

func (s *SecuritiesBalanceAccountingReportV09) AddSafekeepingAccount() *iso20022.SecuritiesAccount26

func (*SecuritiesBalanceAccountingReportV09) AddStatementGeneralDetails 

func (s *SecuritiesBalanceAccountingReportV09) AddStatementGeneralDetails() *iso20022.Statement40

func (*SecuritiesBalanceAccountingReportV09) AddSubAccountDetails 

func (s *SecuritiesBalanceAccountingReportV09) AddSubAccountDetails() *iso20022.SubAccountIdentification43

type SecuritiesBalanceCustodyReport002V09 

type SecuritiesBalanceCustodyReport002V09 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 report.
	StatementGeneralDetails *iso20022.Statement52 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification111 `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary37 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation33 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification46 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement3 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer.

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 (*SecuritiesBalanceCustodyReport002V09) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReport002V09) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement3

func (*SecuritiesBalanceCustodyReport002V09) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReport002V09) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesBalanceCustodyReport002V09) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReport002V09) AddAccountServicer() *iso20022.PartyIdentification111

func (*SecuritiesBalanceCustodyReport002V09) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReport002V09) AddBalanceForAccount() *iso20022.AggregateBalanceInformation33

func (*SecuritiesBalanceCustodyReport002V09) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReport002V09) AddIntermediaryInformation() *iso20022.Intermediary37

func (*SecuritiesBalanceCustodyReport002V09) AddPagination 

func (s *SecuritiesBalanceCustodyReport002V09) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReport002V09) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReport002V09) AddSafekeepingAccount() *iso20022.SecuritiesAccount33

func (*SecuritiesBalanceCustodyReport002V09) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReport002V09) AddStatementGeneralDetails() *iso20022.Statement52

func (*SecuritiesBalanceCustodyReport002V09) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReport002V09) AddSubAccountDetails() *iso20022.SubAccountIdentification46

type SecuritiesBalanceCustodyReportV03 

type SecuritiesBalanceCustodyReportV03 struct {

	// Information that uniquely identifies the SecuritiesBalanceCustodyReport message as known by the account servicer. When the report has multiple pages, one message equals one page. Therefore, Identification uniquely identifies the page.
	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 report.
	StatementGeneralDetails *iso20022.Statement21 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification10Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary2 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation9 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification11 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,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 SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV03) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV03) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV03) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV03) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesBalanceCustodyReportV03) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV03) AddAccountServicer() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceCustodyReportV03) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV03) AddBalanceForAccount() *iso20022.AggregateBalanceInformation9

func (*SecuritiesBalanceCustodyReportV03) AddIdentification 

func (s *SecuritiesBalanceCustodyReportV03) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesBalanceCustodyReportV03) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV03) AddIntermediaryInformation() *iso20022.Intermediary2

func (*SecuritiesBalanceCustodyReportV03) AddMessageOriginator 

func (s *SecuritiesBalanceCustodyReportV03) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceCustodyReportV03) AddMessageRecipient 

func (s *SecuritiesBalanceCustodyReportV03) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesBalanceCustodyReportV03) AddPagination 

func (s *SecuritiesBalanceCustodyReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV03) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV03) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV03) AddStatementGeneralDetails() *iso20022.Statement21

func (*SecuritiesBalanceCustodyReportV03) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV03) AddSubAccountDetails() *iso20022.SubAccountIdentification11

type SecuritiesBalanceCustodyReportV04 

type SecuritiesBalanceCustodyReportV04 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 report.
	StatementGeneralDetails *iso20022.Statement21 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary21 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation12 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification17 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV04) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV04) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV04) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceCustodyReportV04) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV04) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceCustodyReportV04) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV04) AddBalanceForAccount() *iso20022.AggregateBalanceInformation12

func (*SecuritiesBalanceCustodyReportV04) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV04) AddIntermediaryInformation() *iso20022.Intermediary21

func (*SecuritiesBalanceCustodyReportV04) AddPagination 

func (s *SecuritiesBalanceCustodyReportV04) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV04) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV04) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV04) AddStatementGeneralDetails() *iso20022.Statement21

func (*SecuritiesBalanceCustodyReportV04) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV04) AddSubAccountDetails() *iso20022.SubAccountIdentification17

type SecuritiesBalanceCustodyReportV05 

type SecuritiesBalanceCustodyReportV05 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 report.
	StatementGeneralDetails *iso20022.Statement33 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary21 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation16 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification22 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent. Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV05) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV05) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV05) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV05) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceCustodyReportV05) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV05) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceCustodyReportV05) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV05) AddBalanceForAccount() *iso20022.AggregateBalanceInformation16

func (*SecuritiesBalanceCustodyReportV05) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV05) AddIntermediaryInformation() *iso20022.Intermediary21

func (*SecuritiesBalanceCustodyReportV05) AddPagination 

func (s *SecuritiesBalanceCustodyReportV05) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV05) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV05) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV05) AddStatementGeneralDetails() *iso20022.Statement33

func (*SecuritiesBalanceCustodyReportV05) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV05) AddSubAccountDetails() *iso20022.SubAccountIdentification22

type SecuritiesBalanceCustodyReportV06 

type SecuritiesBalanceCustodyReportV06 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 report.
	StatementGeneralDetails *iso20022.Statement33 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation21 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification28 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV06) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV06) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV06) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV06) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceCustodyReportV06) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV06) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceCustodyReportV06) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV06) AddBalanceForAccount() *iso20022.AggregateBalanceInformation21

func (*SecuritiesBalanceCustodyReportV06) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV06) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceCustodyReportV06) AddPagination 

func (s *SecuritiesBalanceCustodyReportV06) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV06) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV06) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV06) AddStatementGeneralDetails() *iso20022.Statement33

func (*SecuritiesBalanceCustodyReportV06) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV06) AddSubAccountDetails() *iso20022.SubAccountIdentification28

type SecuritiesBalanceCustodyReportV07 

type SecuritiesBalanceCustodyReportV07 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 report.
	StatementGeneralDetails *iso20022.Statement33 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation21 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification28 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV07) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV07) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV07) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV07) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceCustodyReportV07) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV07) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceCustodyReportV07) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV07) AddBalanceForAccount() *iso20022.AggregateBalanceInformation21

func (*SecuritiesBalanceCustodyReportV07) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV07) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceCustodyReportV07) AddPagination 

func (s *SecuritiesBalanceCustodyReportV07) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV07) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV07) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV07) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV07) AddStatementGeneralDetails() *iso20022.Statement33

func (*SecuritiesBalanceCustodyReportV07) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV07) AddSubAccountDetails() *iso20022.SubAccountIdentification28

type SecuritiesBalanceCustodyReportV08 

type SecuritiesBalanceCustodyReportV08 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 report.
	StatementGeneralDetails *iso20022.Statement33 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification49Choice `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary23 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation25 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification37 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer. 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 (*SecuritiesBalanceCustodyReportV08) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV08) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV08) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV08) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesBalanceCustodyReportV08) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV08) AddAccountServicer() *iso20022.PartyIdentification49Choice

func (*SecuritiesBalanceCustodyReportV08) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV08) AddBalanceForAccount() *iso20022.AggregateBalanceInformation25

func (*SecuritiesBalanceCustodyReportV08) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV08) AddIntermediaryInformation() *iso20022.Intermediary23

func (*SecuritiesBalanceCustodyReportV08) AddPagination 

func (s *SecuritiesBalanceCustodyReportV08) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV08) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV08) AddSafekeepingAccount() *iso20022.SecuritiesAccount11

func (*SecuritiesBalanceCustodyReportV08) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV08) AddStatementGeneralDetails() *iso20022.Statement33

func (*SecuritiesBalanceCustodyReportV08) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV08) AddSubAccountDetails() *iso20022.SubAccountIdentification37

type SecuritiesBalanceCustodyReportV09 

type SecuritiesBalanceCustodyReportV09 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 report.
	StatementGeneralDetails *iso20022.Statement45 `xml:"StmtGnlDtls"`

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

	// Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
	//
	AccountServicer *iso20022.PartyIdentification100 `xml:"AcctSvcr,omitempty"`

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

	// Information about the party that provides services relating to financial products to investors, for example, advice on products and placement of orders for the investment fund.
	IntermediaryInformation []*iso20022.Intermediary32 `xml:"IntrmyInf,omitempty"`

	// Net position of a segregated holding, in a single security, within the overall position held in a securities account.
	BalanceForAccount []*iso20022.AggregateBalanceInformation30 `xml:"BalForAcct,omitempty"`

	// Sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification42 `xml:"SubAcctDtls,omitempty"`

	// Total valuation amounts provided in the base currency of the account.
	AccountBaseCurrencyTotalAmounts *iso20022.TotalValueInPageAndStatement1 `xml:"AcctBaseCcyTtlAmts,omitempty"`
}

Scope An account servicer sends a SecuritiesBalanceCustodyReport to an account owner to provide, at a moment in time, the quantity and identification of the financial instruments that the account servicer holds for 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, or - 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, or - a transfer agent acting on behalf of a fund manager or an account owner's designated agent.

Usage The message can also include availability and the location of holdings to facilitate trading and minimise settlement issues. The message reports all information per financial instrument, that is, when a financial instrument is held at multiple places of safekeeping, the total holdings for all locations can be provided. The message should be sent at a frequency agreed bi-laterally between the account servicer and the account owner. The message may be provided on a trade date, contractual or settlement date basis. There may be one or more intermediary parties, for example, an intermediary or a concentrator between the account owner and account servicer.

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 (*SecuritiesBalanceCustodyReportV09) AddAccountBaseCurrencyTotalAmounts 

func (s *SecuritiesBalanceCustodyReportV09) AddAccountBaseCurrencyTotalAmounts() *iso20022.TotalValueInPageAndStatement1

func (*SecuritiesBalanceCustodyReportV09) AddAccountOwner 

func (s *SecuritiesBalanceCustodyReportV09) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesBalanceCustodyReportV09) AddAccountServicer 

func (s *SecuritiesBalanceCustodyReportV09) AddAccountServicer() *iso20022.PartyIdentification100

func (*SecuritiesBalanceCustodyReportV09) AddBalanceForAccount 

func (s *SecuritiesBalanceCustodyReportV09) AddBalanceForAccount() *iso20022.AggregateBalanceInformation30

func (*SecuritiesBalanceCustodyReportV09) AddIntermediaryInformation 

func (s *SecuritiesBalanceCustodyReportV09) AddIntermediaryInformation() *iso20022.Intermediary32

func (*SecuritiesBalanceCustodyReportV09) AddPagination 

func (s *SecuritiesBalanceCustodyReportV09) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceCustodyReportV09) AddSafekeepingAccount 

func (s *SecuritiesBalanceCustodyReportV09) AddSafekeepingAccount() *iso20022.SecuritiesAccount26

func (*SecuritiesBalanceCustodyReportV09) AddStatementGeneralDetails 

func (s *SecuritiesBalanceCustodyReportV09) AddStatementGeneralDetails() *iso20022.Statement45

func (*SecuritiesBalanceCustodyReportV09) AddSubAccountDetails 

func (s *SecuritiesBalanceCustodyReportV09) AddSubAccountDetails() *iso20022.SubAccountIdentification42

type SecuritiesBalanceTransparencyReportStatusAdviceV01 

type SecuritiesBalanceTransparencyReportStatusAdviceV01 struct {

	// Unique and unambiguous identification of the status advice message.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Identification of the party that is the sender of the status advice message.
	SenderIdentification *iso20022.PartyIdentification100 `xml:"SndrId"`

	// Identification of the party that is the receiver of the status advice message.
	ReceiverIdentification *iso20022.PartyIdentification100 `xml:"RcvrId,omitempty"`

	// Reference of the statement for which the status advice has been issued.
	RelatedStatement *iso20022.StatementReference1 `xml:"RltdStmt"`

	// Status of the referenced statement.
	Status *iso20022.ReportItemStatus1Choice `xml:"Sts"`

	// Number of items for each identical transaction status.
	NumberOfItemsPerStatus []*iso20022.NumberOfItemsPerStatus1 `xml:"NbOfItmsPerSts,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, such as a custodian, central securities depository, international securities depository or transfer agent, sends the SecuritiesBalanceTransparencyReportStatusAdvice message in response to a SecuritiesBalanceTransparencyReport, to accept or reject the statement of holdings as sent in a SecuritiesBalanceTransparencyReport.

USAGE The SecuritiesBalanceTransparencyReportStatusAdvice is used to accept (Accepted), partially accept (Accepted With Exception) or reject (Rejected) a previously received SecuritiesBalanceTransparencyReport.

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddMessageIdentification 

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

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddNumberOfItemsPerStatus 

func (s *SecuritiesBalanceTransparencyReportStatusAdviceV01) AddNumberOfItemsPerStatus() *iso20022.NumberOfItemsPerStatus1

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddReceiverIdentification 

func (s *SecuritiesBalanceTransparencyReportStatusAdviceV01) AddReceiverIdentification() *iso20022.PartyIdentification100

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddRelatedStatement 

func (s *SecuritiesBalanceTransparencyReportStatusAdviceV01) AddRelatedStatement() *iso20022.StatementReference1

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddSenderIdentification 

func (s *SecuritiesBalanceTransparencyReportStatusAdviceV01) AddSenderIdentification() *iso20022.PartyIdentification100

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddStatus 

func (s *SecuritiesBalanceTransparencyReportStatusAdviceV01) AddStatus() *iso20022.ReportItemStatus1Choice

func (*SecuritiesBalanceTransparencyReportStatusAdviceV01) AddSupplementaryData 

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

type SecuritiesBalanceTransparencyReportV02 

type SecuritiesBalanceTransparencyReportV02 struct {

	// Unique and unambiguous identification of the message. When the report has multiple pages, one message equals one page. Therefore, the MessageIdentification uniquely identifies the page.
	MessageIdentification *iso20022.MessageIdentification1 `xml:"MsgId"`

	// Identification of the party that is the sender of the message.
	SenderIdentification *iso20022.PartyIdentification100 `xml:"SndrId"`

	// Identification of the party that is the receiver of the message.
	ReceiverIdentification *iso20022.PartyIdentification100 `xml:"RcvrId,omitempty"`

	// 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 statement.
	StatementGeneralDetails *iso20022.Statement59 `xml:"StmtGnlDtls"`

	// Details of the account, account sub-levels and the holdings.
	SafekeepingAccountAndHoldings []*iso20022.SafekeepingAccount7 `xml:"SfkpgAcctAndHldgs,omitempty"`

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

Scope The SecuritiesBalanceTransparencyReport message is sent by an account servicer, such as a custodian, central securities depository or international central securities depository, to the account owner to provide holdings information for the accounts that it services, to disclose underlying details of holdings on an omnibus account that the sender owns or operates at the receiver. The receiver may also be a custodian, central securities depository, international central securities depository, and the ultimate receiver may be a registrar, transfer agent, fund company, official agent of the reported instrument(s) and/or other parties. The SecuritiesBalanceTransparencyReport message provides transparency of holdings through layers of custody chains in a consolidated statement, to allow for an efficient gathering of investor data, which, in turn, may be used to measure marketing effectiveness, validation of compliance with prospectuses and regulatory requirements, and the calculation of trailer fees and other retrocessions. Usage The SecuritiesBalanceTransparencyReport message is used to provide aggregated holdings information and a breakdown of holdings information. A sender of the SecuritiesBalanceTransparencyReport message will identify its own safekeeping account (for example, an omnibus account in the ledger of the receiver) and holdings information at the level of account(s) for which the sender is the account servicer (that is, in the ledger of the sender). When relevant, the sender will aggregate its holdings information with holdings information of one or more sub levels and sub-sub levels of accounts, that is, with holdings information the sender has received from the owner(s) of the account(s) for which the sender is the account servicer. A sender of the SecuritiesBalanceTransparencyReport message may also use it to send statements to its account owning customers, and these can be enrichments of statements that the respective account owners have previously provided to the sender. Ultimately, the statement reaches the relevant fund company, for example, the transfer agent, that may use it for obtaining information about the custodians, distributors and commercial agreement references associated with holdings on an omnibus account at the ultimate place of safekeeping, for example, a central securities depository (CSD) or a register of shareholders. When the message is sent by the owner of the account specified in SafekeepingAccountAndHoldings/AccountIdentification, the message will disclose holding details of the underlying owner(s) of the sender’s holdings with the receiver. This direction is commonly referred to as ‘downstream’. When the sender is the account servicer of an account owned by the receiver, for example, the account in AccountSubLevel1/AccountIdentification or AccountSubLevel2/AccountIdentification, the message is providing a statement of the receiver’s holdings with sender. This direction is commonly referred to as ‘upstream’, and the safekeeping account should identify the ultimate place of safekeeping (for example, an account in a transfer agent's register of shareholders).

func (*SecuritiesBalanceTransparencyReportV02) AddMessageIdentification 

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

func (*SecuritiesBalanceTransparencyReportV02) AddPagination 

func (s *SecuritiesBalanceTransparencyReportV02) AddPagination() *iso20022.Pagination

func (*SecuritiesBalanceTransparencyReportV02) AddReceiverIdentification 

func (s *SecuritiesBalanceTransparencyReportV02) AddReceiverIdentification() *iso20022.PartyIdentification100

func (*SecuritiesBalanceTransparencyReportV02) AddSafekeepingAccountAndHoldings 

func (s *SecuritiesBalanceTransparencyReportV02) AddSafekeepingAccountAndHoldings() *iso20022.SafekeepingAccount7

func (*SecuritiesBalanceTransparencyReportV02) AddSenderIdentification 

func (s *SecuritiesBalanceTransparencyReportV02) AddSenderIdentification() *iso20022.PartyIdentification100

func (*SecuritiesBalanceTransparencyReportV02) AddStatementGeneralDetails 

func (s *SecuritiesBalanceTransparencyReportV02) AddStatementGeneralDetails() *iso20022.Statement59

func (*SecuritiesBalanceTransparencyReportV02) AddSupplementaryData 

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

type SecuritiesEndOfProcessReportV01 

type SecuritiesEndOfProcessReportV01 struct {

	// Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages).
	Pagination []*iso20022.Pagination `xml:"Pgntn,omitempty"`

	// Notifies the type of report transmitted.
	ReportGeneralDetails *iso20022.Report3 `xml:"RptGnlDtls"`

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

	// Party that identifies the underlying investor.
	Investor []*iso20022.PartyIdentificationAndAccount79 `xml:"Invstr,omitempty"`

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

Scope Sent by an executing party or an instructing party to the custodian or an affirming party to notify that all the necessary SecuritiesTradeConfirmation message or any other notification of the process have been sent. It may also be sent through Central Matching Utility (CMU). The instructing party is typically the investment manager or an intermediary system/vendor communicating on behalf of the investment manager. The executing party is typically the broker/dealer or an intermediary system/vendor communicating on behalf of the broker/dealer. The custodian or an affirming party is typically the custodian, trustee, financial institution, intermediary system/vendor communicating on behalf of them, or their agent. The ISO 20022 Business Application Header must be used Usage Initiator: Executing Party, CMU or Instructing Party Respondent: Custodian or an affirming party does not need to respond.

func (*SecuritiesEndOfProcessReportV01) AddConfirmationParties 

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

func (*SecuritiesEndOfProcessReportV01) AddInvestor 

func (s *SecuritiesEndOfProcessReportV01) AddInvestor() *iso20022.PartyIdentificationAndAccount79

func (*SecuritiesEndOfProcessReportV01) AddPagination 

func (s *SecuritiesEndOfProcessReportV01) AddPagination() *iso20022.Pagination

func (*SecuritiesEndOfProcessReportV01) AddReportGeneralDetails 

func (s *SecuritiesEndOfProcessReportV01) AddReportGeneralDetails() *iso20022.Report3

func (*SecuritiesEndOfProcessReportV01) AddSupplementaryData 

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

type SecuritiesMessageCancellationAdvice002V05 

type SecuritiesMessageCancellationAdvice002V05 struct {

	// Reference to the message advised to be cancelled by the account servicer
	Reference *iso20022.References53Choice `xml:"Ref"`

	// 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 servicer sends a SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - a allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification

The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdvice002V05) AddAccountOwner 

func (s *SecuritiesMessageCancellationAdvice002V05) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesMessageCancellationAdvice002V05) AddReference 

func (s *SecuritiesMessageCancellationAdvice002V05) AddReference() *iso20022.References53Choice

func (*SecuritiesMessageCancellationAdvice002V05) AddSafekeepingAccount 

func (s *SecuritiesMessageCancellationAdvice002V05) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesMessageCancellationAdvice002V05) AddSupplementaryData 

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

type SecuritiesMessageCancellationAdviceV01 

type SecuritiesMessageCancellationAdviceV01 struct {

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

	// Details of the transaction.
	Details *iso20022.TransactionDetails12 `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 SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - an allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdviceV01) AddDetails 

func (s *SecuritiesMessageCancellationAdviceV01) AddDetails() *iso20022.TransactionDetails12

func (*SecuritiesMessageCancellationAdviceV01) AddExtension 

func (s *SecuritiesMessageCancellationAdviceV01) AddExtension() *iso20022.Extension2

func (*SecuritiesMessageCancellationAdviceV01) AddIdentification 

func (s *SecuritiesMessageCancellationAdviceV01) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesMessageCancellationAdviceV01) AddMessageOriginator 

func (s *SecuritiesMessageCancellationAdviceV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesMessageCancellationAdviceV01) AddMessageRecipient 

func (s *SecuritiesMessageCancellationAdviceV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

type SecuritiesMessageCancellationAdviceV02 

type SecuritiesMessageCancellationAdviceV02 struct {

	// Reference to the message advised to be cancelled by the account servicer
	Reference *iso20022.References18Choice `xml:"Ref"`

	// 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 servicer sends a SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - an allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdviceV02) AddAccountOwner 

func (s *SecuritiesMessageCancellationAdviceV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesMessageCancellationAdviceV02) AddReference 

func (s *SecuritiesMessageCancellationAdviceV02) AddReference() *iso20022.References18Choice

func (*SecuritiesMessageCancellationAdviceV02) AddSafekeepingAccount 

func (s *SecuritiesMessageCancellationAdviceV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesMessageCancellationAdviceV02) AddSupplementaryData 

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

type SecuritiesMessageCancellationAdviceV03 

type SecuritiesMessageCancellationAdviceV03 struct {

	// Reference to the message advised to be cancelled by the account servicer
	Reference *iso20022.References18Choice `xml:"Ref"`

	// 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 servicer sends a SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - an allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdviceV03) AddAccountOwner 

func (s *SecuritiesMessageCancellationAdviceV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesMessageCancellationAdviceV03) AddReference 

func (s *SecuritiesMessageCancellationAdviceV03) AddReference() *iso20022.References18Choice

func (*SecuritiesMessageCancellationAdviceV03) AddSafekeepingAccount 

func (s *SecuritiesMessageCancellationAdviceV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesMessageCancellationAdviceV03) AddSupplementaryData 

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

type SecuritiesMessageCancellationAdviceV04 

type SecuritiesMessageCancellationAdviceV04 struct {

	// Reference to the message advised to be cancelled by the account servicer
	Reference *iso20022.References37Choice `xml:"Ref"`

	// 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 servicer sends a SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - a allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdviceV04) AddAccountOwner 

func (s *SecuritiesMessageCancellationAdviceV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesMessageCancellationAdviceV04) AddReference 

func (s *SecuritiesMessageCancellationAdviceV04) AddReference() *iso20022.References37Choice

func (*SecuritiesMessageCancellationAdviceV04) AddSafekeepingAccount 

func (s *SecuritiesMessageCancellationAdviceV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesMessageCancellationAdviceV04) AddSupplementaryData 

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

type SecuritiesMessageCancellationAdviceV05 

type SecuritiesMessageCancellationAdviceV05 struct {

	// Reference to the message advised to be cancelled by the account servicer
	Reference *iso20022.References43Choice `xml:"Ref"`

	// 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 servicer sends a SecuritiesMessageCancellationAdvice to an account owner to inform of the cancellation of a securities message previously sent by an 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 previously sent message may be: - a securities settlement transaction confirmation - a report (transactions, pending transactions, allegements, accounting and custody securities balance) - a allegement notification (when sent by mistake or because the counterparty cancelled its instruction) - a portfolio transfer notification - an intra-position movement confirmation - a transaction generation notification

The previously sent message cannot be a status advice message (any). If a status advice should not have been sent, a new status advice with the correct status should be sent, not a cancellation advice. 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 (*SecuritiesMessageCancellationAdviceV05) AddAccountOwner 

func (s *SecuritiesMessageCancellationAdviceV05) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesMessageCancellationAdviceV05) AddReference 

func (s *SecuritiesMessageCancellationAdviceV05) AddReference() *iso20022.References43Choice

func (*SecuritiesMessageCancellationAdviceV05) AddSafekeepingAccount 

func (s *SecuritiesMessageCancellationAdviceV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesMessageCancellationAdviceV05) AddSupplementaryData 

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

type SecuritiesMessageRejection 

type SecuritiesMessageRejection struct {

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

	// Reason to reject the message.
	Reason *iso20022.RejectionReason1 `xml:"Rsn"`
}

Scope The SecuritiesMessageRejection message is sent by an executing party to the instructing party. Typically, this message is sent by an account servicer to the account owner. This message is used to reject a previously received message on which action cannot be taken. Usage The SecuritiesMessageRejection message can be sent for the following reasons: - the executing party does not recognise the linked reference, so the executing party cannot process the message - the instructing party should not have sent the message. This could be because the Receiver does not expect the message, eg, there is no SLA in place between the Sender and the Receiver. The SecuritiesMessageRejection message must not be used to reject an instruction message that cannot be processed for business reasons, eg, if information is missing in an instruction message or because securities are not available for settlement.

func (*SecuritiesMessageRejection) AddReason 

func (s *SecuritiesMessageRejection) AddReason() *iso20022.RejectionReason1

func (*SecuritiesMessageRejection) AddRelatedReference 

func (s *SecuritiesMessageRejection) AddRelatedReference() *iso20022.AdditionalReference2

type SecuritiesMessageRejectionV02 

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

	// Reason to reject the message.
	Reason *iso20022.RejectionReason3 `xml:"Rsn"`
}

Scope An account servicer, for example, a registrar, transfer agent or custodian bank, sends the SecuritiesMessageRejection message to the account owner, for example, an investor or its authorised agent, to reject a previously received message on which action cannot be taken. The message may also be sent by an executing party, for example, transfer agent to the instructing party, for example, investment manager or its authorised representative to reject a previously received message on which action cannot be taken. Usage The SecuritiesMessageRejection message is used for the following reasons: - the executing party does not recognise the linked reference, so the executing party cannot process the message - the instructing party should not have sent the message. Reasons that a receiver does not expect a message include no SLA in place between the Sender and the Receiver. The SecuritiesMessageRejection message must not be used to reject an instruction message that cannot be processed for business reasons, for example, if information is missing in an instruction message or because securities are not available for settlement.

func (*SecuritiesMessageRejectionV02) AddMessageIdentification 

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

func (*SecuritiesMessageRejectionV02) AddReason 

func (s *SecuritiesMessageRejectionV02) AddReason() *iso20022.RejectionReason3

func (*SecuritiesMessageRejectionV02) AddRelatedReference 

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

type SecuritiesMessageRejectionV03 

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

	// Reason to reject the message.
	Reason *iso20022.RejectionReason23 `xml:"Rsn"`
}

Scope An account servicer, for example, a registrar, transfer agent or custodian bank, sends the SecuritiesMessageRejection message to the account owner, for example, an investor or its authorised agent, to reject a previously received message on which action cannot be taken. The message may also be sent by an executing party, for example, transfer agent to the instructing party, for example, investment manager or its authorised representative to reject a previously received message on which action cannot be taken. Usage The SecuritiesMessageRejection message is used for the following reasons: - the executing party does not recognise the linked reference, so the executing party cannot process the message - the instructing party should not have sent the message. Reasons that a receiver does not expect a message include no SLA in place between the Sender and the Receiver. The SecuritiesMessageRejection message must not be used to reject an instruction message that cannot be processed for business reasons, for example, if information is missing in an instruction message or because securities are not available for settlement.

func (*SecuritiesMessageRejectionV03) AddMessageIdentification 

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

func (*SecuritiesMessageRejectionV03) AddReason 

func (s *SecuritiesMessageRejectionV03) AddReason() *iso20022.RejectionReason23

func (*SecuritiesMessageRejectionV03) AddRelatedReference 

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

type SecuritiesSettlementTransactionAllegementReport002V05 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement53 `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.SecuritiesAccount27 `xml:"SfkpgAcct"`

	// Details of the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails61 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReport002V05) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReport002V05) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesSettlementTransactionAllegementReport002V05) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReport002V05) AddAllegementDetails() *iso20022.SecuritiesTradeDetails61

func (*SecuritiesSettlementTransactionAllegementReport002V05) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReport002V05) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReport002V05) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReport002V05) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesSettlementTransactionAllegementReport002V05) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReport002V05) AddStatementGeneralDetails() *iso20022.Statement53

type SecuritiesSettlementTransactionAllegementReport002V06 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement53 `xml:"StmtGnlDtls"`

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

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

	// Details of the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails69 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReport002V06) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReport002V06) AddAccountOwner() *iso20022.PartyIdentification119

func (*SecuritiesSettlementTransactionAllegementReport002V06) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReport002V06) AddAllegementDetails() *iso20022.SecuritiesTradeDetails69

func (*SecuritiesSettlementTransactionAllegementReport002V06) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReport002V06) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReport002V06) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReport002V06) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesSettlementTransactionAllegementReport002V06) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReport002V06) AddStatementGeneralDetails() *iso20022.Statement53

type SecuritiesSettlementTransactionAllegementReportV01 

type SecuritiesSettlementTransactionAllegementReportV01 struct {

	// Information that unambiguously identifies a SecuritiesSettlementTransactionAllegementReport message as know by the account servicer.
	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"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement17 `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 the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails4 `xml:"AllgmtDtls,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 SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReportV01) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesSettlementTransactionAllegementReportV01) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddAllegementDetails() *iso20022.SecuritiesTradeDetails4

func (*SecuritiesSettlementTransactionAllegementReportV01) AddIdentification 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesSettlementTransactionAllegementReportV01) AddMessageOriginator 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesSettlementTransactionAllegementReportV01) AddMessageRecipient 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesSettlementTransactionAllegementReportV01) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV01) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAllegementReportV01) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV01) AddStatementGeneralDetails() *iso20022.Statement17

type SecuritiesSettlementTransactionAllegementReportV02 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement17 `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 the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails17 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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. 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 (*SecuritiesSettlementTransactionAllegementReportV02) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesSettlementTransactionAllegementReportV02) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV02) AddAllegementDetails() *iso20022.SecuritiesTradeDetails17

func (*SecuritiesSettlementTransactionAllegementReportV02) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV02) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV02) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAllegementReportV02) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV02) AddStatementGeneralDetails() *iso20022.Statement17

type SecuritiesSettlementTransactionAllegementReportV03 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement17 `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 the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails23 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReportV03) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesSettlementTransactionAllegementReportV03) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV03) AddAllegementDetails() *iso20022.SecuritiesTradeDetails23

func (*SecuritiesSettlementTransactionAllegementReportV03) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV03) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAllegementReportV03) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV03) AddStatementGeneralDetails() *iso20022.Statement17

type SecuritiesSettlementTransactionAllegementReportV04 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement17 `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 the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails35 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReportV04) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesSettlementTransactionAllegementReportV04) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV04) AddAllegementDetails() *iso20022.SecuritiesTradeDetails35

func (*SecuritiesSettlementTransactionAllegementReportV04) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV04) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV04) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAllegementReportV04) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV04) AddStatementGeneralDetails() *iso20022.Statement17

type SecuritiesSettlementTransactionAllegementReportV05 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement39 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Details of the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails49 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReportV05) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV05) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesSettlementTransactionAllegementReportV05) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV05) AddAllegementDetails() *iso20022.SecuritiesTradeDetails49

func (*SecuritiesSettlementTransactionAllegementReportV05) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV05) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV05) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesSettlementTransactionAllegementReportV05) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV05) AddStatementGeneralDetails() *iso20022.Statement39

type SecuritiesSettlementTransactionAllegementReportV06 

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

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement39 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Details of the allegement.
	AllegementDetails []*iso20022.SecuritiesTradeDetails68 `xml:"AllgmtDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesSettlementTransactionAllegementReport to an account owner to provide, at a specified time, the status and details of pending settlement allegements, for all or selected securities in a specified safekeeping account. 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 (*SecuritiesSettlementTransactionAllegementReportV06) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAllegementReportV06) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesSettlementTransactionAllegementReportV06) AddAllegementDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV06) AddAllegementDetails() *iso20022.SecuritiesTradeDetails68

func (*SecuritiesSettlementTransactionAllegementReportV06) AddPagination 

func (s *SecuritiesSettlementTransactionAllegementReportV06) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAllegementReportV06) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAllegementReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesSettlementTransactionAllegementReportV06) AddStatementGeneralDetails 

func (s *SecuritiesSettlementTransactionAllegementReportV06) AddStatementGeneralDetails() *iso20022.Statement39

type SecuritiesSettlementTransactionAuditTrailReport002V03 

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

	// Identification of the SecuritiesStatusQuery message sent to request this report.
	QueryReference *iso20022.Identification16 `xml:"QryRef,omitempty"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications34 `xml:"TxId,omitempty"`

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

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

	//  Provides the history of status and reasons for a pending, posted or cancelled transaction.
	StatusTrail []*iso20022.StatusTrail7 `xml:"StsTrl,omitempty"`
}

Scope This message is sent by the Market Infrastructure to the CSD to advise of the history of all the statuses, modifications, replacement and cancellation of a specific transaction during its whole life cycle when the instructing party is a direct participant to the Settlement Infrastructure.

Usage The message may also be used to: - re-send a message sent by the market infrastructure to the direct participant, - provide a third party with a copy of a message being sent by the market infrastructure for information, - re-send to a third party a copy of a message being sent by the market infrastructure for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddPagination 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddQueryReference 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddQueryReference() *iso20022.Identification16

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddStatusTrail 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddStatusTrail() *iso20022.StatusTrail7

func (*SecuritiesSettlementTransactionAuditTrailReport002V03) AddTransactionIdentification 

func (s *SecuritiesSettlementTransactionAuditTrailReport002V03) AddTransactionIdentification() *iso20022.TransactionIdentifications34

type SecuritiesSettlementTransactionAuditTrailReportV01 

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

	// Identification of the SecuritiesStatusQuery message sent to request this report.
	QueryReference *iso20022.Identification1 `xml:"QryRef,omitempty"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications15 `xml:"TxId,omitempty"`

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

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

	//  Provides the history of status and reasons for a pending, posted or cancelled transaction.
	StatusTrail []*iso20022.StatusTrail2 `xml:"StsTrl,omitempty"`
}

Scope

This message is sent by the Market Infrastructure to the CSD to advise of the history of all the statuses, modifications, replacement and cancellation of a specific transaction during its whole life cycle when the instructing party is a direct participant to the Settlement Infrastructure.

Usage

The message may also be used to:

- re-send a message sent by the market infrastructure to the direct participant,

- provide a third party with a copy of a message being sent by the market infrastructure for information,

- re-send to a third party a copy of a message being sent by the market infrastructure 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 (*SecuritiesSettlementTransactionAuditTrailReportV01) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesSettlementTransactionAuditTrailReportV01) AddPagination 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAuditTrailReportV01) AddQueryReference 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddQueryReference() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAuditTrailReportV01) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAuditTrailReportV01) AddStatusTrail 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddStatusTrail() *iso20022.StatusTrail2

func (*SecuritiesSettlementTransactionAuditTrailReportV01) AddTransactionIdentification 

func (s *SecuritiesSettlementTransactionAuditTrailReportV01) AddTransactionIdentification() *iso20022.TransactionIdentifications15

type SecuritiesSettlementTransactionAuditTrailReportV02 

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

	// Identification of the SecuritiesStatusQuery message sent to request this report.
	QueryReference *iso20022.Identification1 `xml:"QryRef,omitempty"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications15 `xml:"TxId,omitempty"`

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

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

	//  Provides the history of status and reasons for a pending, posted or cancelled transaction.
	StatusTrail []*iso20022.StatusTrail4 `xml:"StsTrl,omitempty"`
}

Scope

This message is sent by the Market Infrastructure to the CSD to advise of the history of all the statuses, modifications, replacement and cancellation of a specific transaction during its whole life cycle when the instructing party is a direct participant to the Settlement Infrastructure.

Usage

The message may also be used to:

- re-send a message sent by the market infrastructure to the direct participant,

- provide a third party with a copy of a message being sent by the market infrastructure for information,

- re-send to a third party a copy of a message being sent by the market infrastructure 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 (*SecuritiesSettlementTransactionAuditTrailReportV02) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesSettlementTransactionAuditTrailReportV02) AddPagination 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAuditTrailReportV02) AddQueryReference 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddQueryReference() *iso20022.Identification1

func (*SecuritiesSettlementTransactionAuditTrailReportV02) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesSettlementTransactionAuditTrailReportV02) AddStatusTrail 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddStatusTrail() *iso20022.StatusTrail4

func (*SecuritiesSettlementTransactionAuditTrailReportV02) AddTransactionIdentification 

func (s *SecuritiesSettlementTransactionAuditTrailReportV02) AddTransactionIdentification() *iso20022.TransactionIdentifications15

type SecuritiesSettlementTransactionAuditTrailReportV03 

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

	// Identification of the SecuritiesStatusQuery message sent to request this report.
	QueryReference *iso20022.Identification14 `xml:"QryRef,omitempty"`

	// Provides unambiguous transaction identification information.
	TransactionIdentification *iso20022.TransactionIdentifications29 `xml:"TxId,omitempty"`

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

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

	//  Provides the history of status and reasons for a pending, posted or cancelled transaction.
	StatusTrail []*iso20022.StatusTrail6 `xml:"StsTrl,omitempty"`
}

Scope This message is sent by the Market Infrastructure to the CSD to advise of the history of all the statuses, modifications, replacement and cancellation of a specific transaction during its whole life cycle when the instructing party is a direct participant to the Settlement Infrastructure.

Usage The message may also be used to: - re-send a message sent by the market infrastructure to the direct participant, - provide a third party with a copy of a message being sent by the market infrastructure for information, - re-send to a third party a copy of a message being sent by the market infrastructure for information using the relevant elements in the Business Application Header.

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddAccountOwner 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddPagination 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddQueryReference 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddQueryReference() *iso20022.Identification14

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddSafekeepingAccount 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddStatusTrail 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddStatusTrail() *iso20022.StatusTrail6

func (*SecuritiesSettlementTransactionAuditTrailReportV03) AddTransactionIdentification 

func (s *SecuritiesSettlementTransactionAuditTrailReportV03) AddTransactionIdentification() *iso20022.TransactionIdentifications29

type SecuritiesStatementQuery002V06 

type SecuritiesStatementQuery002V06 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber14 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement54 `xml:"StmtGnlDtls,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.SecuritiesAccount27 `xml:"SfkpgAcct"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters12 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQuery002V06) AddAccountOwner 

func (s *SecuritiesStatementQuery002V06) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesStatementQuery002V06) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQuery002V06) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters12

func (*SecuritiesStatementQuery002V06) AddSafekeepingAccount 

func (s *SecuritiesStatementQuery002V06) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesStatementQuery002V06) AddStatementGeneralDetails 

func (s *SecuritiesStatementQuery002V06) AddStatementGeneralDetails() *iso20022.Statement54

func (*SecuritiesStatementQuery002V06) AddStatementRequested 

func (s *SecuritiesStatementQuery002V06) AddStatementRequested() *iso20022.DocumentNumber14

func (*SecuritiesStatementQuery002V06) AddSupplementaryData 

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

type SecuritiesStatementQueryV01 

type SecuritiesStatementQueryV01 struct {

	// Information that unambiguously identifies a SecuritiesStatementQuery message as know by the account owner (or the instructing party acting on its behalf).
	Identification *iso20022.DocumentIdentification11 `xml:"Id"`

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber1 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement16 `xml:"StmtGnlDtls,omitempty"`

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

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters1 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQueryV01) AddAccountOwner 

func (s *SecuritiesStatementQueryV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesStatementQueryV01) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV01) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters1

func (*SecuritiesStatementQueryV01) AddExtension 

func (s *SecuritiesStatementQueryV01) AddExtension() *iso20022.Extension2

func (*SecuritiesStatementQueryV01) AddIdentification 

func (s *SecuritiesStatementQueryV01) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesStatementQueryV01) AddMessageOriginator 

func (s *SecuritiesStatementQueryV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesStatementQueryV01) AddMessageRecipient 

func (s *SecuritiesStatementQueryV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesStatementQueryV01) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesStatementQueryV01) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV01) AddStatementGeneralDetails() *iso20022.Statement16

func (*SecuritiesStatementQueryV01) AddStatementRequested 

func (s *SecuritiesStatementQueryV01) AddStatementRequested() *iso20022.DocumentNumber1

type SecuritiesStatementQueryV02 

type SecuritiesStatementQueryV02 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber1 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement16 `xml:"StmtGnlDtls,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"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters3 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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). 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 (*SecuritiesStatementQueryV02) AddAccountOwner 

func (s *SecuritiesStatementQueryV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesStatementQueryV02) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV02) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters3

func (*SecuritiesStatementQueryV02) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesStatementQueryV02) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV02) AddStatementGeneralDetails() *iso20022.Statement16

func (*SecuritiesStatementQueryV02) AddStatementRequested 

func (s *SecuritiesStatementQueryV02) AddStatementRequested() *iso20022.DocumentNumber1

func (*SecuritiesStatementQueryV02) AddSupplementaryData 

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

type SecuritiesStatementQueryV03 

type SecuritiesStatementQueryV03 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber1 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement16 `xml:"StmtGnlDtls,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"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters5 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQueryV03) AddAccountOwner 

func (s *SecuritiesStatementQueryV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesStatementQueryV03) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV03) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters5

func (*SecuritiesStatementQueryV03) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesStatementQueryV03) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV03) AddStatementGeneralDetails() *iso20022.Statement16

func (*SecuritiesStatementQueryV03) AddStatementRequested 

func (s *SecuritiesStatementQueryV03) AddStatementRequested() *iso20022.DocumentNumber1

func (*SecuritiesStatementQueryV03) AddSupplementaryData 

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

type SecuritiesStatementQueryV04 

type SecuritiesStatementQueryV04 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber1 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement16 `xml:"StmtGnlDtls,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"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters7 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQueryV04) AddAccountOwner 

func (s *SecuritiesStatementQueryV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesStatementQueryV04) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV04) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters7

func (*SecuritiesStatementQueryV04) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesStatementQueryV04) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV04) AddStatementGeneralDetails() *iso20022.Statement16

func (*SecuritiesStatementQueryV04) AddStatementRequested 

func (s *SecuritiesStatementQueryV04) AddStatementRequested() *iso20022.DocumentNumber1

func (*SecuritiesStatementQueryV04) AddSupplementaryData 

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

type SecuritiesStatementQueryV05 

type SecuritiesStatementQueryV05 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber1 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement16 `xml:"StmtGnlDtls,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"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters9 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQueryV05) AddAccountOwner 

func (s *SecuritiesStatementQueryV05) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesStatementQueryV05) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV05) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters9

func (*SecuritiesStatementQueryV05) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesStatementQueryV05) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV05) AddStatementGeneralDetails() *iso20022.Statement16

func (*SecuritiesStatementQueryV05) AddStatementRequested 

func (s *SecuritiesStatementQueryV05) AddStatementRequested() *iso20022.DocumentNumber1

func (*SecuritiesStatementQueryV05) AddSupplementaryData 

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

type SecuritiesStatementQueryV06 

type SecuritiesStatementQueryV06 struct {

	// Description of the statement requested.
	StatementRequested *iso20022.DocumentNumber13 `xml:"StmtReqd"`

	// General information related to report.
	StatementGeneralDetails *iso20022.Statement42 `xml:"StmtGnlDtls,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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Additional specific query criteria.
	AdditionalQueryParameters []*iso20022.AdditionalQueryParameters11 `xml:"AddtlQryParams,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 SecuritiesStatementQuery to an account servicer to request any existing securities statement. 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 (*SecuritiesStatementQueryV06) AddAccountOwner 

func (s *SecuritiesStatementQueryV06) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesStatementQueryV06) AddAdditionalQueryParameters 

func (s *SecuritiesStatementQueryV06) AddAdditionalQueryParameters() *iso20022.AdditionalQueryParameters11

func (*SecuritiesStatementQueryV06) AddSafekeepingAccount 

func (s *SecuritiesStatementQueryV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesStatementQueryV06) AddStatementGeneralDetails 

func (s *SecuritiesStatementQueryV06) AddStatementGeneralDetails() *iso20022.Statement42

func (*SecuritiesStatementQueryV06) AddStatementRequested 

func (s *SecuritiesStatementQueryV06) AddStatementRequested() *iso20022.DocumentNumber13

func (*SecuritiesStatementQueryV06) AddSupplementaryData 

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

type SecuritiesTransactionPendingReport002V07 

type SecuritiesTransactionPendingReport002V07 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 report.
	StatementGeneralDetails *iso20022.Statement55 `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.SecuritiesAccount27 `xml:"SfkpgAcct"`

	// Status information.
	Status []*iso20022.StatusAndReason30 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction49 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReport002V07) AddAccountOwner 

func (s *SecuritiesTransactionPendingReport002V07) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesTransactionPendingReport002V07) AddPagination 

func (s *SecuritiesTransactionPendingReport002V07) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReport002V07) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReport002V07) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesTransactionPendingReport002V07) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReport002V07) AddStatementGeneralDetails() *iso20022.Statement55

func (*SecuritiesTransactionPendingReport002V07) AddStatus 

func (s *SecuritiesTransactionPendingReport002V07) AddStatus() *iso20022.StatusAndReason30

func (*SecuritiesTransactionPendingReport002V07) AddTransactions 

func (s *SecuritiesTransactionPendingReport002V07) AddTransactions() *iso20022.Transaction49

type SecuritiesTransactionPendingReport002V08 

type SecuritiesTransactionPendingReport002V08 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 report.
	StatementGeneralDetails *iso20022.Statement55 `xml:"StmtGnlDtls"`

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

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

	// Status information.
	Status []*iso20022.StatusAndReason33 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction57 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReport002V08) AddAccountOwner 

func (s *SecuritiesTransactionPendingReport002V08) AddAccountOwner() *iso20022.PartyIdentification119

func (*SecuritiesTransactionPendingReport002V08) AddPagination 

func (s *SecuritiesTransactionPendingReport002V08) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReport002V08) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReport002V08) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesTransactionPendingReport002V08) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReport002V08) AddStatementGeneralDetails() *iso20022.Statement55

func (*SecuritiesTransactionPendingReport002V08) AddStatus 

func (s *SecuritiesTransactionPendingReport002V08) AddStatus() *iso20022.StatusAndReason33

func (*SecuritiesTransactionPendingReport002V08) AddTransactions 

func (s *SecuritiesTransactionPendingReport002V08) AddTransactions() *iso20022.Transaction57

type SecuritiesTransactionPendingReportV01 

type SecuritiesTransactionPendingReportV01 struct {

	// Information that uniquely identifies the SecuritiesTransactionPendingReport message as known by the account servicer. When the report has multiple pages, one message equals one page. Therefore, Identification uniquely identifies the page.
	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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason1 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction8 `xml:"Txs,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 SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV01) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesTransactionPendingReportV01) AddIdentification 

func (s *SecuritiesTransactionPendingReportV01) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesTransactionPendingReportV01) AddMessageOriginator 

func (s *SecuritiesTransactionPendingReportV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesTransactionPendingReportV01) AddMessageRecipient 

func (s *SecuritiesTransactionPendingReportV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesTransactionPendingReportV01) AddPagination 

func (s *SecuritiesTransactionPendingReportV01) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV01) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV01) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV01) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV01) AddStatus 

func (s *SecuritiesTransactionPendingReportV01) AddStatus() *iso20022.StatusAndReason1

func (*SecuritiesTransactionPendingReportV01) AddTransactions 

func (s *SecuritiesTransactionPendingReportV01) AddTransactions() *iso20022.Transaction8

type SecuritiesTransactionPendingReportV02 

type SecuritiesTransactionPendingReportV02 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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason7 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction12 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV02) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPendingReportV02) AddPagination 

func (s *SecuritiesTransactionPendingReportV02) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV02) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV02) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV02) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV02) AddStatus 

func (s *SecuritiesTransactionPendingReportV02) AddStatus() *iso20022.StatusAndReason7

func (*SecuritiesTransactionPendingReportV02) AddTransactions 

func (s *SecuritiesTransactionPendingReportV02) AddTransactions() *iso20022.Transaction12

type SecuritiesTransactionPendingReportV03 

type SecuritiesTransactionPendingReportV03 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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason9 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction19 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV03) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPendingReportV03) AddPagination 

func (s *SecuritiesTransactionPendingReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV03) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV03) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV03) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV03) AddStatus 

func (s *SecuritiesTransactionPendingReportV03) AddStatus() *iso20022.StatusAndReason9

func (*SecuritiesTransactionPendingReportV03) AddTransactions 

func (s *SecuritiesTransactionPendingReportV03) AddTransactions() *iso20022.Transaction19

type SecuritiesTransactionPendingReportV04 

type SecuritiesTransactionPendingReportV04 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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason16 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction27 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV04) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPendingReportV04) AddPagination 

func (s *SecuritiesTransactionPendingReportV04) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV04) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV04) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV04) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV04) AddStatus 

func (s *SecuritiesTransactionPendingReportV04) AddStatus() *iso20022.StatusAndReason16

func (*SecuritiesTransactionPendingReportV04) AddTransactions 

func (s *SecuritiesTransactionPendingReportV04) AddTransactions() *iso20022.Transaction27

type SecuritiesTransactionPendingReportV05 

type SecuritiesTransactionPendingReportV05 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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason18 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction34 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV05) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV05) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPendingReportV05) AddPagination 

func (s *SecuritiesTransactionPendingReportV05) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV05) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV05) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV05) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV05) AddStatus 

func (s *SecuritiesTransactionPendingReportV05) AddStatus() *iso20022.StatusAndReason18

func (*SecuritiesTransactionPendingReportV05) AddTransactions 

func (s *SecuritiesTransactionPendingReportV05) AddTransactions() *iso20022.Transaction34

type SecuritiesTransactionPendingReportV06 

type SecuritiesTransactionPendingReportV06 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 report.
	StatementGeneralDetails *iso20022.Statement14 `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"`

	// Status information.
	Status []*iso20022.StatusAndReason25 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction41 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV06) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV06) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPendingReportV06) AddPagination 

func (s *SecuritiesTransactionPendingReportV06) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV06) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPendingReportV06) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV06) AddStatementGeneralDetails() *iso20022.Statement14

func (*SecuritiesTransactionPendingReportV06) AddStatus 

func (s *SecuritiesTransactionPendingReportV06) AddStatus() *iso20022.StatusAndReason25

func (*SecuritiesTransactionPendingReportV06) AddTransactions 

func (s *SecuritiesTransactionPendingReportV06) AddTransactions() *iso20022.Transaction41

type SecuritiesTransactionPendingReportV07 

type SecuritiesTransactionPendingReportV07 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 report.
	StatementGeneralDetails *iso20022.Statement41 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Status information.
	Status []*iso20022.StatusAndReason27 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction47 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV07) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV07) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesTransactionPendingReportV07) AddPagination 

func (s *SecuritiesTransactionPendingReportV07) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV07) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV07) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesTransactionPendingReportV07) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV07) AddStatementGeneralDetails() *iso20022.Statement41

func (*SecuritiesTransactionPendingReportV07) AddStatus 

func (s *SecuritiesTransactionPendingReportV07) AddStatus() *iso20022.StatusAndReason27

func (*SecuritiesTransactionPendingReportV07) AddTransactions 

func (s *SecuritiesTransactionPendingReportV07) AddTransactions() *iso20022.Transaction47

type SecuritiesTransactionPendingReportV08 

type SecuritiesTransactionPendingReportV08 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 report.
	StatementGeneralDetails *iso20022.Statement41 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Status information.
	Status []*iso20022.StatusAndReason32 `xml:"Sts,omitempty"`

	// Details of the transactions reported.
	Transactions []*iso20022.Transaction53 `xml:"Txs,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPendingReport to an account owner to provide, as at a specified time, the details of pending increases and decreases of holdings, for all or selected securities in a specified safekeeping account, for all or selected reasons why the transaction is pending. 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 statement may also include future settlement or forward transactions which have become binding on the account owner. 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 (*SecuritiesTransactionPendingReportV08) AddAccountOwner 

func (s *SecuritiesTransactionPendingReportV08) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesTransactionPendingReportV08) AddPagination 

func (s *SecuritiesTransactionPendingReportV08) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPendingReportV08) AddSafekeepingAccount 

func (s *SecuritiesTransactionPendingReportV08) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesTransactionPendingReportV08) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPendingReportV08) AddStatementGeneralDetails() *iso20022.Statement41

func (*SecuritiesTransactionPendingReportV08) AddStatus 

func (s *SecuritiesTransactionPendingReportV08) AddStatus() *iso20022.StatusAndReason32

func (*SecuritiesTransactionPendingReportV08) AddTransactions 

func (s *SecuritiesTransactionPendingReportV08) AddTransactions() *iso20022.Transaction53

type SecuritiesTransactionPostingReport002V06 

type SecuritiesTransactionPostingReport002V06 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 report.
	StatementGeneralDetails *iso20022.Statement56 `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.SecuritiesAccount27 `xml:"SfkpgAcct"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails23 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification47 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReport002V06) AddAccountOwner 

func (s *SecuritiesTransactionPostingReport002V06) AddAccountOwner() *iso20022.PartyIdentification109

func (*SecuritiesTransactionPostingReport002V06) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReport002V06) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails23

func (*SecuritiesTransactionPostingReport002V06) AddPagination 

func (s *SecuritiesTransactionPostingReport002V06) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReport002V06) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReport002V06) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesTransactionPostingReport002V06) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReport002V06) AddStatementGeneralDetails() *iso20022.Statement56

func (*SecuritiesTransactionPostingReport002V06) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReport002V06) AddSubAccountDetails() *iso20022.SubAccountIdentification47

type SecuritiesTransactionPostingReport002V07 

type SecuritiesTransactionPostingReport002V07 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 report.
	StatementGeneralDetails *iso20022.Statement56 `xml:"StmtGnlDtls"`

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

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

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails27 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification50 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReport002V07) AddAccountOwner 

func (s *SecuritiesTransactionPostingReport002V07) AddAccountOwner() *iso20022.PartyIdentification119

func (*SecuritiesTransactionPostingReport002V07) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReport002V07) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails27

func (*SecuritiesTransactionPostingReport002V07) AddPagination 

func (s *SecuritiesTransactionPostingReport002V07) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReport002V07) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReport002V07) AddSafekeepingAccount() *iso20022.SecuritiesAccount27

func (*SecuritiesTransactionPostingReport002V07) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReport002V07) AddStatementGeneralDetails() *iso20022.Statement56

func (*SecuritiesTransactionPostingReport002V07) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReport002V07) AddSubAccountDetails() *iso20022.SubAccountIdentification50

type SecuritiesTransactionPostingReportV01 

type SecuritiesTransactionPostingReportV01 struct {

	// Information that uniquely identifies the SecuritiesTransactionPostingReport message as known by the account servicer. When the report has multiple pages, one message equals one page. Therefore, Identification uniquely identifies the page.
	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 report.
	StatementGeneralDetails *iso20022.Statement11 `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"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails2 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification9 `xml:"SubAcctDtls,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 SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV01) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV01) AddAccountOwner() *iso20022.PartyIdentification13Choice

func (*SecuritiesTransactionPostingReportV01) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV01) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails2

func (*SecuritiesTransactionPostingReportV01) AddIdentification 

func (s *SecuritiesTransactionPostingReportV01) AddIdentification() *iso20022.DocumentIdentification11

func (*SecuritiesTransactionPostingReportV01) AddMessageOriginator 

func (s *SecuritiesTransactionPostingReportV01) AddMessageOriginator() *iso20022.PartyIdentification10Choice

func (*SecuritiesTransactionPostingReportV01) AddMessageRecipient 

func (s *SecuritiesTransactionPostingReportV01) AddMessageRecipient() *iso20022.PartyIdentification10Choice

func (*SecuritiesTransactionPostingReportV01) AddPagination 

func (s *SecuritiesTransactionPostingReportV01) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV01) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV01) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPostingReportV01) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV01) AddStatementGeneralDetails() *iso20022.Statement11

func (*SecuritiesTransactionPostingReportV01) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV01) AddSubAccountDetails() *iso20022.SubAccountIdentification9

type SecuritiesTransactionPostingReportV02 

type SecuritiesTransactionPostingReportV02 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 report.
	StatementGeneralDetails *iso20022.Statement11 `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"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails5 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification15 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV02) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV02) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPostingReportV02) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV02) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails5

func (*SecuritiesTransactionPostingReportV02) AddPagination 

func (s *SecuritiesTransactionPostingReportV02) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV02) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV02) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPostingReportV02) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV02) AddStatementGeneralDetails() *iso20022.Statement11

func (*SecuritiesTransactionPostingReportV02) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV02) AddSubAccountDetails() *iso20022.SubAccountIdentification15

type SecuritiesTransactionPostingReportV03 

type SecuritiesTransactionPostingReportV03 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 report.
	StatementGeneralDetails *iso20022.Statement11 `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"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails9 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification21 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV03) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV03) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPostingReportV03) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV03) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails9

func (*SecuritiesTransactionPostingReportV03) AddPagination 

func (s *SecuritiesTransactionPostingReportV03) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV03) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV03) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPostingReportV03) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV03) AddStatementGeneralDetails() *iso20022.Statement11

func (*SecuritiesTransactionPostingReportV03) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV03) AddSubAccountDetails() *iso20022.SubAccountIdentification21

type SecuritiesTransactionPostingReportV04 

type SecuritiesTransactionPostingReportV04 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 report.
	StatementGeneralDetails *iso20022.Statement11 `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"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails13 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification30 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV04) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV04) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPostingReportV04) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV04) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails13

func (*SecuritiesTransactionPostingReportV04) AddPagination 

func (s *SecuritiesTransactionPostingReportV04) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV04) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV04) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPostingReportV04) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV04) AddStatementGeneralDetails() *iso20022.Statement11

func (*SecuritiesTransactionPostingReportV04) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV04) AddSubAccountDetails() *iso20022.SubAccountIdentification30

type SecuritiesTransactionPostingReportV05 

type SecuritiesTransactionPostingReportV05 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 report.
	StatementGeneralDetails *iso20022.Statement11 `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"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails17 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification34 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV05) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV05) AddAccountOwner() *iso20022.PartyIdentification36Choice

func (*SecuritiesTransactionPostingReportV05) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV05) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails17

func (*SecuritiesTransactionPostingReportV05) AddPagination 

func (s *SecuritiesTransactionPostingReportV05) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV05) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV05) AddSafekeepingAccount() *iso20022.SecuritiesAccount13

func (*SecuritiesTransactionPostingReportV05) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV05) AddStatementGeneralDetails() *iso20022.Statement11

func (*SecuritiesTransactionPostingReportV05) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV05) AddSubAccountDetails() *iso20022.SubAccountIdentification34

type SecuritiesTransactionPostingReportV06 

type SecuritiesTransactionPostingReportV06 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 report.
	StatementGeneralDetails *iso20022.Statement44 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails20 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification44 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV06) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV06) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesTransactionPostingReportV06) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV06) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails20

func (*SecuritiesTransactionPostingReportV06) AddPagination 

func (s *SecuritiesTransactionPostingReportV06) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV06) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV06) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesTransactionPostingReportV06) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV06) AddStatementGeneralDetails() *iso20022.Statement44

func (*SecuritiesTransactionPostingReportV06) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV06) AddSubAccountDetails() *iso20022.SubAccountIdentification44

type SecuritiesTransactionPostingReportV07 

type SecuritiesTransactionPostingReportV07 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 report.
	StatementGeneralDetails *iso20022.Statement44 `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.SecuritiesAccount24 `xml:"SfkpgAcct"`

	// Reporting per financial instrument.
	FinancialInstrumentDetails []*iso20022.FinancialInstrumentDetails25 `xml:"FinInstrmDtls,omitempty"`

	// Details at sub-account level.
	SubAccountDetails []*iso20022.SubAccountIdentification49 `xml:"SubAcctDtls,omitempty"`
}

Scope An account servicer sends a SecuritiesTransactionPostingReport to an account owner to provide the details of increases and decreases of holdings which occurred during a specified period, for all or selected securities in the specified safekeeping account or sub-safekeeping account which the account servicer holds for 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 This message may be used as a trade date based or a settlement date based statement. 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 (*SecuritiesTransactionPostingReportV07) AddAccountOwner 

func (s *SecuritiesTransactionPostingReportV07) AddAccountOwner() *iso20022.PartyIdentification98

func (*SecuritiesTransactionPostingReportV07) AddFinancialInstrumentDetails 

func (s *SecuritiesTransactionPostingReportV07) AddFinancialInstrumentDetails() *iso20022.FinancialInstrumentDetails25

func (*SecuritiesTransactionPostingReportV07) AddPagination 

func (s *SecuritiesTransactionPostingReportV07) AddPagination() *iso20022.Pagination

func (*SecuritiesTransactionPostingReportV07) AddSafekeepingAccount 

func (s *SecuritiesTransactionPostingReportV07) AddSafekeepingAccount() *iso20022.SecuritiesAccount24

func (*SecuritiesTransactionPostingReportV07) AddStatementGeneralDetails 

func (s *SecuritiesTransactionPostingReportV07) AddStatementGeneralDetails() *iso20022.Statement44

func (*SecuritiesTransactionPostingReportV07) AddSubAccountDetails 

func (s *SecuritiesTransactionPostingReportV07) AddSubAccountDetails() *iso20022.SubAccountIdentification49

type StatementOfInvestmentFundTransactions 

type StatementOfInvestmentFundTransactions struct {

	// Reference to a 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"`

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

	// General information related to the investment fund statement of transactions.
	StatementGeneralDetails *iso20022.Statement5 `xml:"StmtGnlDtls"`

	// Information related to an investment account.
	InvestmentAccountDetails *iso20022.InvestmentAccount12 `xml:"InvstmtAcctDtls"`

	// Creation/cancellation of investment units on the books of the fund or its designated agent, as a result of executing an investment fund order.
	TransactionOnAccount []*iso20022.InvestmentFundTransactionsByFund1 `xml:"TxOnAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification4 `xml:"SubAcctDtls,omitempty"`

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

Scope The StatementOfInvestmentFundTransactions is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a fund administrator or fund intermediary, trustee or registrar. This message provides the details of increases and decreases of holdings which occurred during a specified period. This message can also be used for information purposes, eg, tax information. Usage The StatementOfInvestmentFundTransactions message can be sent: - At a frequency agreed bi-laterally between the Sender and the Receiver and/or - As a response to a request for statement sent by the account owner. The StatementOfInvestmentFundTransactions message can only be used to list the transactions of a single (master) account. However, it is possible to break down these transactions into one or several sub-accounts. Therefore, the message can be used to either specify transactions at - the main account level, or - the sub-account level. This message must not be used in place of confirmation messages. Since a SWIFT message as sent is restricted to the maximum input message length, several messages may be needed to accommodate all the information.

func (*StatementOfInvestmentFundTransactions) AddExtension 

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

func (*StatementOfInvestmentFundTransactions) AddInvestmentAccountDetails 

func (s *StatementOfInvestmentFundTransactions) AddInvestmentAccountDetails() *iso20022.InvestmentAccount12

func (*StatementOfInvestmentFundTransactions) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactions) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactions) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactions) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactions) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactions) AddStatementGeneralDetails 

func (s *StatementOfInvestmentFundTransactions) AddStatementGeneralDetails() *iso20022.Statement5

func (*StatementOfInvestmentFundTransactions) AddSubAccountDetails 

func (s *StatementOfInvestmentFundTransactions) AddSubAccountDetails() *iso20022.SubAccountIdentification4

func (*StatementOfInvestmentFundTransactions) AddTransactionOnAccount 

func (s *StatementOfInvestmentFundTransactions) AddTransactionOnAccount() *iso20022.InvestmentFundTransactionsByFund1

type StatementOfInvestmentFundTransactionsCancellation 

type StatementOfInvestmentFundTransactionsCancellation struct {

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

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

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

	// The Statement of Investment Fund Transactions message to cancel.
	StatementToBeCancelled *iso20022.StatementOfInvestmentFundTransactions1 `xml:"StmtToBeCanc,omitempty"`
}

Scope The StatementOfInvestmentFundTransactionsCancellation message is sent by an account servicer to the account owner or the account owner's designated agent. The account servicer may be a fund administrator or fund intermediary, trustee or registrar, etc. This message is used to cancel a previously sent StatementOfInvestmentFundTransactions message. Usage The StatementOfInvestmentFundTransactionsCancellation message is sent by an account servicer to the account owner to cancel a previously sent StatementOfInvestmentFundTransactions message. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*StatementOfInvestmentFundTransactionsCancellation) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactionsCancellation) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactionsCancellation) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellation) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactionsCancellation) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellation) AddStatementToBeCancelled 

func (s *StatementOfInvestmentFundTransactionsCancellation) AddStatementToBeCancelled() *iso20022.StatementOfInvestmentFundTransactions1

type StatementOfInvestmentFundTransactionsCancellationV02 

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

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

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

	// The Statement of Investment Fund Transactions message to cancel.
	StatementToBeCancelled *iso20022.StatementOfInvestmentFundTransactions2 `xml:"StmtToBeCanc,omitempty"`
}

Scope An account servicer, for example, a transfer agent sends the StatementOfInvestmentFundTransactionsCancellation message to the account owner, for example, an investment manager or its authorised representative to cancel a previously sent StatementOfInvestmentFundTransactions message. Usage The StatementOfInvestmentFundTransactionsCancellation message is used to cancel a previously sent StatementOfInvestmentFundTransactions message. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*StatementOfInvestmentFundTransactionsCancellationV02) AddMessageIdentification 

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

func (*StatementOfInvestmentFundTransactionsCancellationV02) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactionsCancellationV02) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactionsCancellationV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellationV02) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactionsCancellationV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellationV02) AddStatementToBeCancelled 

func (s *StatementOfInvestmentFundTransactionsCancellationV02) AddStatementToBeCancelled() *iso20022.StatementOfInvestmentFundTransactions2

type StatementOfInvestmentFundTransactionsCancellationV03 

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

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

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

	// The Statement of Investment Fund Transactions message to cancel.
	StatementToBeCancelled *iso20022.StatementOfInvestmentFundTransactions3 `xml:"StmtToBeCanc,omitempty"`
}

Scope An account servicer, for example, a transfer agent sends the StatementOfInvestmentFundTransactionsCancellation message to the account owner, for example, an investment manager or its authorised representative to cancel a previously sent StatementOfInvestmentFundTransactions message. Usage The StatementOfInvestmentFundTransactionsCancellation message is used to cancel a previously sent StatementOfInvestmentFundTransactions message. This message must contain the reference of the message to be cancelled. This message may also contain all the details of the message to be cancelled, but this is not recommended.

func (*StatementOfInvestmentFundTransactionsCancellationV03) AddMessageIdentification 

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

func (*StatementOfInvestmentFundTransactionsCancellationV03) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactionsCancellationV03) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactionsCancellationV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellationV03) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactionsCancellationV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsCancellationV03) AddStatementToBeCancelled 

func (s *StatementOfInvestmentFundTransactionsCancellationV03) AddStatementToBeCancelled() *iso20022.StatementOfInvestmentFundTransactions3

type StatementOfInvestmentFundTransactionsV02 

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

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

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

	// General information related to the investment fund statement of transactions.
	StatementGeneralDetails *iso20022.Statement8 `xml:"StmtGnlDtls"`

	// Information related to an investment account.
	InvestmentAccountDetails *iso20022.InvestmentAccount25 `xml:"InvstmtAcctDtls"`

	// Creation/cancellation of investment units on the books of the fund or its designated agent, as a result of executing an investment fund order.
	TransactionOnAccount []*iso20022.InvestmentFundTransactionsByFund2 `xml:"TxOnAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification6 `xml:"SubAcctDtls,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 account servicer, for example, a transfer agent sends the StatementOfInvestmentFundTransactions message to the account owner, for example, an investment manager or its authorised representative to provide detailed transactions (increases and decreases) of holdings which occurred during a specified period of time. Usage The StatementOfInvestmentFundTransactions message is used to list the holdings transactions of a single (master) account or several sub-accounts. This message should be used at a frequency agreed bi-laterally between the account servicer and the account owner. This message must not be used in place of confirmation messages.

func (*StatementOfInvestmentFundTransactionsV02) AddExtension 

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

func (*StatementOfInvestmentFundTransactionsV02) AddInvestmentAccountDetails 

func (s *StatementOfInvestmentFundTransactionsV02) AddInvestmentAccountDetails() *iso20022.InvestmentAccount25

func (*StatementOfInvestmentFundTransactionsV02) AddMessageIdentification 

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

func (*StatementOfInvestmentFundTransactionsV02) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactionsV02) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactionsV02) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsV02) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactionsV02) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsV02) AddStatementGeneralDetails 

func (s *StatementOfInvestmentFundTransactionsV02) AddStatementGeneralDetails() *iso20022.Statement8

func (*StatementOfInvestmentFundTransactionsV02) AddSubAccountDetails 

func (s *StatementOfInvestmentFundTransactionsV02) AddSubAccountDetails() *iso20022.SubAccountIdentification6

func (*StatementOfInvestmentFundTransactionsV02) AddTransactionOnAccount 

func (s *StatementOfInvestmentFundTransactionsV02) AddTransactionOnAccount() *iso20022.InvestmentFundTransactionsByFund2

type StatementOfInvestmentFundTransactionsV03 

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

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

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

	// General information related to the investment fund statement of transactions.
	StatementGeneralDetails *iso20022.Statement8 `xml:"StmtGnlDtls"`

	// Information related to an investment account.
	InvestmentAccountDetails *iso20022.InvestmentAccount43 `xml:"InvstmtAcctDtls"`

	// Creation/cancellation of investment units on the books of the fund or its designated agent, as a result of executing an investment fund order.
	TransactionOnAccount []*iso20022.InvestmentFundTransactionsByFund3 `xml:"TxOnAcct,omitempty"`

	// The sub-account of the safekeeping or investment account.
	SubAccountDetails []*iso20022.SubAccountIdentification36 `xml:"SubAcctDtls,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 account servicer, for example, a transfer agent sends the StatementOfInvestmentFundTransactions message to the account owner, for example, an investment manager or its authorised representative to provide detailed transactions (increases and decreases) of holdings which occurred during a specified period of time. Usage The StatementOfInvestmentFundTransactions message is used to list the holdings transactions of a single (master) account or several sub-accounts. This message should be used at a frequency agreed bi-laterally between the account servicer and the account owner. This message must not be used in place of confirmation messages.

func (*StatementOfInvestmentFundTransactionsV03) AddExtension 

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

func (*StatementOfInvestmentFundTransactionsV03) AddInvestmentAccountDetails 

func (s *StatementOfInvestmentFundTransactionsV03) AddInvestmentAccountDetails() *iso20022.InvestmentAccount43

func (*StatementOfInvestmentFundTransactionsV03) AddMessageIdentification 

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

func (*StatementOfInvestmentFundTransactionsV03) AddMessagePagination 

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

func (*StatementOfInvestmentFundTransactionsV03) AddPreviousReference 

func (s *StatementOfInvestmentFundTransactionsV03) AddPreviousReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsV03) AddRelatedReference 

func (s *StatementOfInvestmentFundTransactionsV03) AddRelatedReference() *iso20022.AdditionalReference2

func (*StatementOfInvestmentFundTransactionsV03) AddStatementGeneralDetails 

func (s *StatementOfInvestmentFundTransactionsV03) AddStatementGeneralDetails() *iso20022.Statement8

func (*StatementOfInvestmentFundTransactionsV03) AddSubAccountDetails 

func (s *StatementOfInvestmentFundTransactionsV03) AddSubAccountDetails() *iso20022.SubAccountIdentification36

func (*StatementOfInvestmentFundTransactionsV03) AddTransactionOnAccount 

func (s *StatementOfInvestmentFundTransactionsV03) AddTransactionOnAccount() *iso20022.InvestmentFundTransactionsByFund3

type TotalPortfolioValuationReportV01 

type TotalPortfolioValuationReportV01 struct {

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

	// General information related to the total portfolio valuation report.
	ReportGeneralDetails *iso20022.Report4 `xml:"RptGnlDtls"`

	// Details of the account. The account may represent an investment portfolio or a fund.
	AccountDetails *iso20022.SecuritiesAccount21 `xml:"AcctDtls"`

	// Valuation information of the portfolio. In some markets a fund of funds or an investment fund is regarded as a portfolio.
	TotalPortfolioValuation *iso20022.TotalPortfolioValuation1 `xml:"TtlPrtflValtn"`

	// Balance breakdown information.
	Balance *iso20022.PortfolioBalance1 `xml:"Bal,omitempty"`

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

Scope An account servicer sends a TotalPortfolioValuationReport to an account owner to provide detailed valuation information for a portfolio. Usage The TotalPortfolioValuationReport will be sent by the account servicer to the account owner on an agreed basis. The report may also be requested using a SecuritiesStatementQuery. The TotalPortfolioValuationReport is used to report on a portfolio without Investment Funds; or to report on a portfolio when an investment fund is regarded as a portfolio containing, only one or multiple investment funds The TotalPortfolioValuationReport may also be used to: - re-send a message previously sent (the CopyDuplicate value is DUPL), - provide a third party with a copy of a message for information (the CopyDuplicate value is COPY), - re-send to a third party a copy of a message for information (the CopyDuplicate value is CODU).

func (*TotalPortfolioValuationReportV01) AddAccountDetails 

func (t *TotalPortfolioValuationReportV01) AddAccountDetails() *iso20022.SecuritiesAccount21

func (*TotalPortfolioValuationReportV01) AddBalance 

func (t *TotalPortfolioValuationReportV01) AddBalance() *iso20022.PortfolioBalance1

func (*TotalPortfolioValuationReportV01) AddPagination 

func (t *TotalPortfolioValuationReportV01) AddPagination() *iso20022.Pagination

func (*TotalPortfolioValuationReportV01) AddReportGeneralDetails 

func (t *TotalPortfolioValuationReportV01) AddReportGeneralDetails() *iso20022.Report4

func (*TotalPortfolioValuationReportV01) AddSupplementaryData 

func (t *TotalPortfolioValuationReportV01) AddSupplementaryData() *iso20022.SupplementaryData1

func (*TotalPortfolioValuationReportV01) AddTotalPortfolioValuation 

func (t *TotalPortfolioValuationReportV01) AddTotalPortfolioValuation() *iso20022.TotalPortfolioValuation1

Source Files

View all Source files

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL
go.dev uses cookies from Google to deliver and enhance the quality of its services and to analyze traffic. Learn more.