tsmt

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 AcknowledgementV03 

type AcknowledgementV03 struct {

	// Identifies the acknowledgement message.
	AcknowledgementIdentification *iso20022.MessageIdentification1 `xml:"AckId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId,omitempty"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts,omitempty"`

	// Reference to the transaction for the financial institution that is the sender of the acknowledged message.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the acknowledged message.
	AcknowledgedMessageReference *iso20022.MessageIdentification1 `xml:"AckdMsgRef"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The Acknowledgement message is sent by the matching application to the party from which it received a message. This message is used to acknowledge the receipt of a message by the matching application. Usage The Acknowledgement message can be sent to a party from which the matching application received a message to acknowledge the receipt of that message. The message is sent when the matching application does not send any other message in response to a received message.

func (*AcknowledgementV03) AddAcknowledgedMessageReference 

func (a *AcknowledgementV03) AddAcknowledgedMessageReference() *iso20022.MessageIdentification1

func (*AcknowledgementV03) AddAcknowledgementIdentification 

func (a *AcknowledgementV03) AddAcknowledgementIdentification() *iso20022.MessageIdentification1

func (*AcknowledgementV03) AddEstablishedBaselineIdentification 

func (a *AcknowledgementV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*AcknowledgementV03) AddRequestForAction 

func (a *AcknowledgementV03) AddRequestForAction() *iso20022.PendingActivity2

func (*AcknowledgementV03) AddTransactionIdentification 

func (a *AcknowledgementV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*AcknowledgementV03) AddTransactionStatus 

func (a *AcknowledgementV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*AcknowledgementV03) AddUserTransactionReference 

func (a *AcknowledgementV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type ActionReminderV03 

type ActionReminderV03 struct {

	// Identifies the reminder message.
	ReminderIdentification *iso20022.MessageIdentification1 `xml:"RmndrId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Identifies the message for which an action is required.
	MessageRequiringAction *iso20022.MessageIdentification1 `xml:"MsgReqrngActn"`

	// Next processing step required.
	PendingRequestForAction *iso20022.PendingActivity2 `xml:"PdgReqForActn"`
}

Scope The ActionReminder message is sent by the matching application to a party involved in a transaction that it is expecting to take an action. This message is used to remind a party of an action that it is expected to take. Usage The ActionReminder message can be sent by the matching application to remind a party that it is waiting for - the submission of a transaction initiation message (BaselineReSubmission message), or - the acceptance or rejection of mis-matched data sets (MisMatchAcceptance or MisMatchRejection message), or - the acceptance or rejection of an amendment request (AmendmentAcceptance or AmendmentRejection message), or - the acceptance or rejection of a status change request (StatusChangeRequestAcceptance or StatusChangeRequestRejection message), or - the acceptance or rejection of a status extension request (StatusExtensionAcceptance or StatusExtensionRejection message). - or - the acceptance or rejection of a request to accept role and baseline (RoleAndBaselineAcceptance or RoleAndBaselineRejection message).

func (*ActionReminderV03) AddEstablishedBaselineIdentification 

func (a *ActionReminderV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*ActionReminderV03) AddMessageRequiringAction 

func (a *ActionReminderV03) AddMessageRequiringAction() *iso20022.MessageIdentification1

func (*ActionReminderV03) AddPendingRequestForAction 

func (a *ActionReminderV03) AddPendingRequestForAction() *iso20022.PendingActivity2

func (*ActionReminderV03) AddReminderIdentification 

func (a *ActionReminderV03) AddReminderIdentification() *iso20022.MessageIdentification1

func (*ActionReminderV03) AddTransactionIdentification 

func (a *ActionReminderV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*ActionReminderV03) AddTransactionStatus 

func (a *ActionReminderV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*ActionReminderV03) AddUserTransactionReference 

func (a *ActionReminderV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type ActivityReportRequestV03 

type ActivityReportRequestV03 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Specifies the entities of the submitter for which the activities have to be reported.
	EntitiesToBeReported []*iso20022.BICIdentification1 `xml:"NttiesToBeRptd,omitempty"`

	// Specifies the period for which activities have to be reported.
	ReportPeriod *iso20022.DateTimePeriodDetails1 `xml:"RptPrd"`
}

Scope The ActivityReportRequest message is sent by any party involved in a transaction to the matching application. This message is used to request a report on all transactions for which an activity has taken place within a given time span. Usage The ActivityReportRequest message can be sent - at a pre-determined time. The message requests a report on all transactions that the requester is involved in and for which an activity has taken place within the last 24 hours. - on demand. The message requests a report on all transactions that the requester is involved in and for which an activity has taken place within a time span specified by the requester.

func (*ActivityReportRequestV03) AddEntitiesToBeReported 

func (a *ActivityReportRequestV03) AddEntitiesToBeReported() *iso20022.BICIdentification1

func (*ActivityReportRequestV03) AddReportPeriod 

func (a *ActivityReportRequestV03) AddReportPeriod() *iso20022.DateTimePeriodDetails1

func (*ActivityReportRequestV03) AddRequestIdentification 

func (a *ActivityReportRequestV03) AddRequestIdentification() *iso20022.MessageIdentification1

type ActivityReportSetUpRequestV02 

type ActivityReportSetUpRequestV02 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Specifies the parameters to calculate the local reporting time.
	UTCOffset *iso20022.UTCOffset1 `xml:"UTCOffset"`
}

Scope The ActivityReportSetUpRequest message is sent by any party involved in a transaction to the matching application. The ActivityReportSetUpRequest message can be sent to request the reset of the pre-determined time at which the daily production of the activity report should take place. Usage This message is sent to the matching application by a bank, in order to set the UTC offset specifying the hour when the matching application will generate every day an activity report covering the last 24 hours and send it. By default, this offset is equal to 0.

func (*ActivityReportSetUpRequestV02) AddRequestIdentification 

func (a *ActivityReportSetUpRequestV02) AddRequestIdentification() *iso20022.MessageIdentification1

func (*ActivityReportSetUpRequestV02) AddUTCOffset 

func (a *ActivityReportSetUpRequestV02) AddUTCOffset() *iso20022.UTCOffset1

type ActivityReportV03 

type ActivityReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the previous message requesting the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef,omitempty"`

	// Describes the events that occurred for one transaction.
	Report []*iso20022.ActivityReportItems2 `xml:"Rpt,omitempty"`
}

Scope The ActivityReport message is sent by the matching application to the requester of an activity report. This message is used to report on all transactions for which an activity has taken place within a given time span. Usage The ActivityReport message can be sent - at a pre-determined time every 24 hours. The message reports on all transactions that the requester is involved in and for which an activity has taken place within the last 24 hours. - on demand in response to an ActivityReportRequest message. The message reports on all transactions that the requester is involved in and for which an activity has taken place within a time span specified by the requester in the ActivityReportRequest message.

func (*ActivityReportV03) AddRelatedMessageReference 

func (a *ActivityReportV03) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*ActivityReportV03) AddReport 

func (a *ActivityReportV03) AddReport() *iso20022.ActivityReportItems2

func (*ActivityReportV03) AddReportIdentification 

func (a *ActivityReportV03) AddReportIdentification() *iso20022.MessageIdentification1

type ActivityReportV04 

type ActivityReportV04 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the previous message requesting the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef,omitempty"`

	// Describes the events that occurred for one transaction.
	Report []*iso20022.ActivityReportItems3 `xml:"Rpt,omitempty"`
}

Scope The ActivityReport message is sent by the matching application to the requester of an activity report. This message is used to report on all transactions for which an activity has taken place within a given time span. Usage The ActivityReport message can be sent - at a pre-determined time every 24 hours. The message reports on all transactions that the requester is involved in and for which an activity has taken place within the last 24 hours. - on demand in response to an ActivityReportRequest message. The message reports on all transactions that the requester is involved in and for which an activity has taken place within a time span specified by the requester in the ActivityReportRequest message.

func (*ActivityReportV04) AddRelatedMessageReference 

func (a *ActivityReportV04) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*ActivityReportV04) AddReport 

func (a *ActivityReportV04) AddReport() *iso20022.ActivityReportItems3

func (*ActivityReportV04) AddReportIdentification 

func (a *ActivityReportV04) AddReportIdentification() *iso20022.MessageIdentification1

type AmendmentAcceptanceNotificationV03 

type AmendmentAcceptanceNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the delta report that contained the amendment.
	DeltaReportReference *iso20022.MessageIdentification1 `xml:"DltaRptRef"`

	// Sequence number of the accepted baseline amendment.
	AcceptedAmendmentNumber *iso20022.Count1 `xml:"AccptdAmdmntNb"`

	// Party that has accepted the amendment.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The AmendmentAcceptanceNotification message is sent by the matching application to the requester of an amendment. This message is used to notify the acceptance of an amendment request. Usage The AmendmentAcceptanceNotification message can be sent by the matching application to pass on information about the acceptance of an amendment request that it has obtained through the receipt of an AmendmentAcceptance message. In order to pass on information about the rejection of an amendment request the matching application sends an AmendmentRejectionNotification message.

func (*AmendmentAcceptanceNotificationV03) AddAcceptedAmendmentNumber 

func (a *AmendmentAcceptanceNotificationV03) AddAcceptedAmendmentNumber() *iso20022.Count1

func (*AmendmentAcceptanceNotificationV03) AddDeltaReportReference 

func (a *AmendmentAcceptanceNotificationV03) AddDeltaReportReference() *iso20022.MessageIdentification1

func (*AmendmentAcceptanceNotificationV03) AddEstablishedBaselineIdentification 

func (a *AmendmentAcceptanceNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*AmendmentAcceptanceNotificationV03) AddInitiator 

func (a *AmendmentAcceptanceNotificationV03) AddInitiator() *iso20022.BICIdentification1

func (*AmendmentAcceptanceNotificationV03) AddNotificationIdentification 

func (a *AmendmentAcceptanceNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*AmendmentAcceptanceNotificationV03) AddRequestForAction 

func (a *AmendmentAcceptanceNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*AmendmentAcceptanceNotificationV03) AddTransactionIdentification 

func (a *AmendmentAcceptanceNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*AmendmentAcceptanceNotificationV03) AddTransactionStatus 

func (a *AmendmentAcceptanceNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*AmendmentAcceptanceNotificationV03) AddUserTransactionReference 

func (a *AmendmentAcceptanceNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type AmendmentAcceptanceV02 

type AmendmentAcceptanceV02 struct {

	// Identifies the acceptance message.
	AcceptanceIdentification *iso20022.MessageIdentification1 `xml:"AccptncId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the identification of the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Reference to the identification of the delta report that contained the amendment.
	DeltaReportReference *iso20022.MessageIdentification1 `xml:"DltaRptRef"`

	// Sequence number of the accepted baseline amendment.
	AcceptedAmendmentNumber *iso20022.Count1 `xml:"AccptdAmdmntNb"`
}

Scope The AmendmentAcceptance message is sent by the party requested to accept or reject an amendment to the matching application. The message is used to accept an amendment request. Usage The AmendmentAcceptance message can be sent by the party requested to accept or reject an amendment to inform that it accepts the requested amendment. The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message. The rejection of an amendment request can be achieved by sending an AmendmentRejection message.

func (*AmendmentAcceptanceV02) AddAcceptanceIdentification 

func (a *AmendmentAcceptanceV02) AddAcceptanceIdentification() *iso20022.MessageIdentification1

func (*AmendmentAcceptanceV02) AddAcceptedAmendmentNumber 

func (a *AmendmentAcceptanceV02) AddAcceptedAmendmentNumber() *iso20022.Count1

func (*AmendmentAcceptanceV02) AddDeltaReportReference 

func (a *AmendmentAcceptanceV02) AddDeltaReportReference() *iso20022.MessageIdentification1

func (*AmendmentAcceptanceV02) AddSubmitterTransactionReference 

func (a *AmendmentAcceptanceV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*AmendmentAcceptanceV02) AddTransactionIdentification 

func (a *AmendmentAcceptanceV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type AmendmentRejectionNotificationV03 

type AmendmentRejectionNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique Identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the delta report that contained the amendment.
	DeltaReportReference *iso20022.MessageIdentification1 `xml:"DltaRptRef"`

	// Sequence number of the rejected baseline amendment.
	RejectedAmendmentNumber *iso20022.Count1 `xml:"RjctdAmdmntNb"`

	// Party that has rejected the amendment.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Specifies the reaons for rejecting the amendment.
	RejectionReason *iso20022.RejectionReason1Choice `xml:"RjctnRsn"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The AmendmentRejectionNotification message is sent by the matching application to the requester of an amendment. This message is used to notify the rejection of an amendment request. Usage The AmendmentRejectionNotification message can be sent by the matching application to pass on information about the rejection of an amendment request that it has obtained through the receipt of an AmendmentRejection message. In order to pass on information about the acceptance of an amendment request the matching application sends an AmendmentAcceptanceNotification message.

func (*AmendmentRejectionNotificationV03) AddDeltaReportReference 

func (a *AmendmentRejectionNotificationV03) AddDeltaReportReference() *iso20022.MessageIdentification1

func (*AmendmentRejectionNotificationV03) AddEstablishedBaselineIdentification 

func (a *AmendmentRejectionNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*AmendmentRejectionNotificationV03) AddInitiator 

func (a *AmendmentRejectionNotificationV03) AddInitiator() *iso20022.BICIdentification1

func (*AmendmentRejectionNotificationV03) AddNotificationIdentification 

func (a *AmendmentRejectionNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*AmendmentRejectionNotificationV03) AddRejectedAmendmentNumber 

func (a *AmendmentRejectionNotificationV03) AddRejectedAmendmentNumber() *iso20022.Count1

func (*AmendmentRejectionNotificationV03) AddRejectionReason 

func (a *AmendmentRejectionNotificationV03) AddRejectionReason() *iso20022.RejectionReason1Choice

func (*AmendmentRejectionNotificationV03) AddRequestForAction 

func (a *AmendmentRejectionNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*AmendmentRejectionNotificationV03) AddTransactionIdentification 

func (a *AmendmentRejectionNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*AmendmentRejectionNotificationV03) AddTransactionStatus 

func (a *AmendmentRejectionNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*AmendmentRejectionNotificationV03) AddUserTransactionReference 

func (a *AmendmentRejectionNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type AmendmentRejectionV02 

type AmendmentRejectionV02 struct {

	// Identifies the rejection message.
	RejectionIdentification *iso20022.MessageIdentification1 `xml:"RjctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Reference to the identification of the delta report that contained the amendment.
	DeltaReportReference *iso20022.MessageIdentification1 `xml:"DltaRptRef"`

	// Sequence number of the rejected baseline amendment.
	RejectedAmendmentNumber *iso20022.Count1 `xml:"RjctdAmdmntNb"`

	// Specifies the reaons for rejecting the amendment.
	RejectionReason *iso20022.RejectionReason1Choice `xml:"RjctnRsn"`
}

Scope The AmendmentRejection message is sent by the party requested to accept or reject an amendment to the matching application. This message is used to reject an amendment request. Usage The AmendmentRejection message can be sent by the party requested to accept or reject an amendment to inform that it rejects the requested amendment. The message can be sent in response to a FullPushThroughReport and DeltaReport message conveying the details of a BaselineAmendmentRequest message. The acceptance of an amendment request can be achieved by sending an AmendmentAcceptance message.

func (*AmendmentRejectionV02) AddDeltaReportReference 

func (a *AmendmentRejectionV02) AddDeltaReportReference() *iso20022.MessageIdentification1

func (*AmendmentRejectionV02) AddRejectedAmendmentNumber 

func (a *AmendmentRejectionV02) AddRejectedAmendmentNumber() *iso20022.Count1

func (*AmendmentRejectionV02) AddRejectionIdentification 

func (a *AmendmentRejectionV02) AddRejectionIdentification() *iso20022.MessageIdentification1

func (*AmendmentRejectionV02) AddRejectionReason 

func (a *AmendmentRejectionV02) AddRejectionReason() *iso20022.RejectionReason1Choice

func (*AmendmentRejectionV02) AddSubmitterTransactionReference 

func (a *AmendmentRejectionV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*AmendmentRejectionV02) AddTransactionIdentification 

func (a *AmendmentRejectionV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineAmendmentRequestV03 

type BaselineAmendmentRequestV03 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline3 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineAmendmentRequest message is sent by a primary party involved in a transaction to the matching application. The message is used to request the amendment of an established baseline. Usage The BaselineAmendmentRequest message may only be sent if the transaction is in the state Established or Active. The BaselineAmendmentRequest message can be sent to the matching application by one of the primary parties involved in a transaction established in the push-through mode to request the amendment of an established baseline. The matching application acknowledges the receipt of the amendment request by sending a DeltaReport message to the submitter of the BaselineAmendmentRequest message. It passes on the newly proposed baseline to the counterparty by sending a FullPushThroughReport message, a DeltaReport message and a pre-calculated BaselineReport message. The counterparty is expected to either accept or reject the amendment request by submitting an AmendmentAcceptance or AmendmentRejection message. or The BaselineAmendmentRequest message can be sent by the party involved in a transaction established in the lodge mode to the matching application to amend an established baseline. The matching application amends the baseline according to the BaselineAmendmentRequest message and confirms the execution of the request by sending a DeltaReport and calculated BaselineReport message to the requester of the amendment.

func (*BaselineAmendmentRequestV03) AddBaseline 

func (b *BaselineAmendmentRequestV03) AddBaseline() *iso20022.Baseline3

func (*BaselineAmendmentRequestV03) AddBuyerBankContactPerson 

func (b *BaselineAmendmentRequestV03) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV03) AddBuyerContactPerson 

func (b *BaselineAmendmentRequestV03) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV03) AddOtherBankContactPerson 

func (b *BaselineAmendmentRequestV03) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineAmendmentRequestV03) AddRequestIdentification 

func (b *BaselineAmendmentRequestV03) AddRequestIdentification() *iso20022.MessageIdentification1

func (*BaselineAmendmentRequestV03) AddSellerBankContactPerson 

func (b *BaselineAmendmentRequestV03) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV03) AddSellerContactPerson 

func (b *BaselineAmendmentRequestV03) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV03) AddSubmitterTransactionReference 

func (b *BaselineAmendmentRequestV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineAmendmentRequestV03) AddTransactionIdentification 

func (b *BaselineAmendmentRequestV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineAmendmentRequestV04 

type BaselineAmendmentRequestV04 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline4 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineAmendmentRequest message is sent by a primary party involved in a transaction to the matching application. The message is used to request the amendment of an established baseline. Usage The BaselineAmendmentRequest message may only be sent if the transaction is in the state Established or Active. The BaselineAmendmentRequest message can be sent to the matching application by one of the primary parties involved in a transaction established in the push-through mode to request the amendment of an established baseline. The matching application acknowledges the receipt of the amendment request by sending a DeltaReport message to the submitter of the BaselineAmendmentRequest message. It passes on the newly proposed baseline to the counterparty by sending a FullPushThroughReport message, a DeltaReport message and a pre-calculated BaselineReport message. The counterparty is expected to either accept or reject the amendment request by submitting an AmendmentAcceptance or AmendmentRejection message. or The BaselineAmendmentRequest message can be sent by the party involved in a transaction established in the lodge mode to the matching application to amend an established baseline. The matching application amends the baseline according to the BaselineAmendmentRequest message and confirms the execution of the request by sending a DeltaReport and calculated BaselineReport message to the requester of the amendment.

func (*BaselineAmendmentRequestV04) AddBaseline 

func (b *BaselineAmendmentRequestV04) AddBaseline() *iso20022.Baseline4

func (*BaselineAmendmentRequestV04) AddBuyerBankContactPerson 

func (b *BaselineAmendmentRequestV04) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV04) AddBuyerContactPerson 

func (b *BaselineAmendmentRequestV04) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV04) AddOtherBankContactPerson 

func (b *BaselineAmendmentRequestV04) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineAmendmentRequestV04) AddRequestIdentification 

func (b *BaselineAmendmentRequestV04) AddRequestIdentification() *iso20022.MessageIdentification1

func (*BaselineAmendmentRequestV04) AddSellerBankContactPerson 

func (b *BaselineAmendmentRequestV04) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV04) AddSellerContactPerson 

func (b *BaselineAmendmentRequestV04) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV04) AddSubmitterTransactionReference 

func (b *BaselineAmendmentRequestV04) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineAmendmentRequestV04) AddTransactionIdentification 

func (b *BaselineAmendmentRequestV04) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineAmendmentRequestV05 

type BaselineAmendmentRequestV05 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline5 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineAmendmentRequest message is sent by a primary party involved in a transaction to the matching application. The message is used to request the amendment of an established baseline. Usage The BaselineAmendmentRequest message may only be sent if the transaction is in the state Established or Active. The BaselineAmendmentRequest message can be sent to the matching application by one of the primary parties involved in a transaction established in the push-through mode to request the amendment of an established baseline. The matching application acknowledges the receipt of the amendment request by sending a DeltaReport message to the submitter of the BaselineAmendmentRequest message. It passes on the newly proposed baseline to the counterparty by sending a FullPushThroughReport message, a DeltaReport message and a pre-calculated BaselineReport message. The counterparty is expected to either accept or reject the amendment request by submitting an AmendmentAcceptance or AmendmentRejection message. or The BaselineAmendmentRequest message can be sent by the party involved in a transaction established in the lodge mode to the matching application to amend an established baseline. The matching application amends the baseline according to the BaselineAmendmentRequest message and confirms the execution of the request by sending a DeltaReport and calculated BaselineReport message to the requester of the amendment.

func (*BaselineAmendmentRequestV05) AddBaseline 

func (b *BaselineAmendmentRequestV05) AddBaseline() *iso20022.Baseline5

func (*BaselineAmendmentRequestV05) AddBuyerBankContactPerson 

func (b *BaselineAmendmentRequestV05) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV05) AddBuyerContactPerson 

func (b *BaselineAmendmentRequestV05) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV05) AddOtherBankContactPerson 

func (b *BaselineAmendmentRequestV05) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineAmendmentRequestV05) AddRequestIdentification 

func (b *BaselineAmendmentRequestV05) AddRequestIdentification() *iso20022.MessageIdentification1

func (*BaselineAmendmentRequestV05) AddSellerBankContactPerson 

func (b *BaselineAmendmentRequestV05) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV05) AddSellerContactPerson 

func (b *BaselineAmendmentRequestV05) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineAmendmentRequestV05) AddSubmitterTransactionReference 

func (b *BaselineAmendmentRequestV05) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineAmendmentRequestV05) AddTransactionIdentification 

func (b *BaselineAmendmentRequestV05) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineMatchReportV03 

type BaselineMatchReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that buys goods or services, or a financial instrument.
	Buyer *iso20022.PartyIdentification26 `xml:"Buyr"`

	// Party that sells goods or services, or a financial instrument.
	Seller *iso20022.PartyIdentification26 `xml:"Sellr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Specifies the number of matching trials for a baseline.
	BaselineEstablishmentTrials *iso20022.Limit1 `xml:"BaselnEstblishmtTrils"`

	// Identifies the two baselines compared in this report.
	ComparedDocumentReference []*iso20022.DocumentIdentification4 `xml:"CmpardDocRef"`

	// Description of the differences between the two proposed baselines
	Report *iso20022.MisMatchReport3 `xml:"Rpt"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The BaselineMatchReport message is sent by the matching application to the parties involved in the establishment of a transaction. The message is used to inform about either the successful establishment of a transaction (baseline) or the mis-matches found between two baseline initiation messages. Usage The BaselineMatchReport message can be sent by the matching application to - the parties involved in the establishment of a transaction in the push-through mode, that is the senders of InitialBaselineSubmission and BaselineReSubmission messages including the instruction push-through. In the outlined scenario the message is used to inform either about the successful establishment of a transaction in the matching application or about mis-matches found between two baseline initiation messages,or - the party establishing a transaction in the lodge mode, that is the sender of an InitialBaselineSubmission message including the instruction lodge. In the outlined scenario the message is used to inform about the successful establishment of a transaction in the matching application.

func (*BaselineMatchReportV03) AddBaselineEstablishmentTrials 

func (b *BaselineMatchReportV03) AddBaselineEstablishmentTrials() *iso20022.Limit1

func (*BaselineMatchReportV03) AddBuyer 

func (b *BaselineMatchReportV03) AddBuyer() *iso20022.PartyIdentification26

func (*BaselineMatchReportV03) AddBuyerBank 

func (b *BaselineMatchReportV03) AddBuyerBank() *iso20022.BICIdentification1

func (*BaselineMatchReportV03) AddComparedDocumentReference 

func (b *BaselineMatchReportV03) AddComparedDocumentReference() *iso20022.DocumentIdentification4

func (*BaselineMatchReportV03) AddEstablishedBaselineIdentification 

func (b *BaselineMatchReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*BaselineMatchReportV03) AddReport 

func (b *BaselineMatchReportV03) AddReport() *iso20022.MisMatchReport3

func (*BaselineMatchReportV03) AddReportIdentification 

func (b *BaselineMatchReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*BaselineMatchReportV03) AddRequestForAction 

func (b *BaselineMatchReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*BaselineMatchReportV03) AddSeller 

func (b *BaselineMatchReportV03) AddSeller() *iso20022.PartyIdentification26

func (*BaselineMatchReportV03) AddSellerBank 

func (b *BaselineMatchReportV03) AddSellerBank() *iso20022.BICIdentification1

func (*BaselineMatchReportV03) AddTransactionIdentification 

func (b *BaselineMatchReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*BaselineMatchReportV03) AddTransactionStatus 

func (b *BaselineMatchReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*BaselineMatchReportV03) AddUserTransactionReference 

func (b *BaselineMatchReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type BaselineReSubmissionV03 

type BaselineReSubmissionV03 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline3 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineReSubmission message is sent by either the counterparty or the initiator of a transaction (baseline) to the matching application. This message is used by the counterparty to respond on the registration of a push-through transaction in the matching application or by the initiator or counterparty to re-send earlier mis-matched baseline information. Usage The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a FullPushThroughReport message received from the matching application conveying the details of an InitialBaselineSubmission message. The objective of the BaselineReSubmission message sent in the outlined scenario is to achieve a successful match of two baseline initiation messages in order to establish a transaction in the matching application. or The BaselineReSubmission message can be sent by the initiator of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct an InitialBaselineSubmission or BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application. or The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct a BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application.

func (*BaselineReSubmissionV03) AddBaseline 

func (b *BaselineReSubmissionV03) AddBaseline() *iso20022.Baseline3

func (*BaselineReSubmissionV03) AddBuyerBankContactPerson 

func (b *BaselineReSubmissionV03) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV03) AddBuyerContactPerson 

func (b *BaselineReSubmissionV03) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV03) AddOtherBankContactPerson 

func (b *BaselineReSubmissionV03) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineReSubmissionV03) AddSellerBankContactPerson 

func (b *BaselineReSubmissionV03) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV03) AddSellerContactPerson 

func (b *BaselineReSubmissionV03) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV03) AddSubmissionIdentification 

func (b *BaselineReSubmissionV03) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*BaselineReSubmissionV03) AddSubmitterTransactionReference 

func (b *BaselineReSubmissionV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineReSubmissionV03) AddTransactionIdentification 

func (b *BaselineReSubmissionV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineReSubmissionV04 

type BaselineReSubmissionV04 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline4 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank or buyer's bank.
	BankContactPerson *iso20022.BankContactPerson1Choice `xml:"BkCtctPrsn"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineReSubmission message is sent by either the counterparty or the initiator of a transaction (baseline) to the matching application. This message is used by the counterparty to respond on the registration of a push-through transaction in the matching application or by the initiator or counterparty to re-send earlier mis-matched baseline information. Usage The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a FullPushThroughReport message received from the matching application conveying the details of an InitialBaselineSubmission message. The objective of the BaselineReSubmission message sent in the outlined scenario is to achieve a successful match of two baseline initiation messages in order to establish a transaction in the matching application. or The BaselineReSubmission message can be sent by the initiator of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct an InitialBaselineSubmission or BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application. or The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct a BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application.

func (*BaselineReSubmissionV04) AddBankContactPerson 

func (b *BaselineReSubmissionV04) AddBankContactPerson() *iso20022.BankContactPerson1Choice

func (*BaselineReSubmissionV04) AddBaseline 

func (b *BaselineReSubmissionV04) AddBaseline() *iso20022.Baseline4

func (*BaselineReSubmissionV04) AddBuyerContactPerson 

func (b *BaselineReSubmissionV04) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV04) AddOtherBankContactPerson 

func (b *BaselineReSubmissionV04) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineReSubmissionV04) AddSellerContactPerson 

func (b *BaselineReSubmissionV04) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV04) AddSubmissionIdentification 

func (b *BaselineReSubmissionV04) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*BaselineReSubmissionV04) AddSubmitterTransactionReference 

func (b *BaselineReSubmissionV04) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineReSubmissionV04) AddTransactionIdentification 

func (b *BaselineReSubmissionV04) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineReSubmissionV05 

type BaselineReSubmissionV05 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline5 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank or buyer's bank.
	BankContactPerson *iso20022.BankContactPerson1Choice `xml:"BkCtctPrsn"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The BaselineReSubmission message is sent by either the counterparty or the initiator of a transaction (baseline) to the matching application. This message is used by the counterparty to respond on the registration of a push-through transaction in the matching application or by the initiator or counterparty to re-send earlier mis-matched baseline information. Usage The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a FullPushThroughReport message received from the matching application conveying the details of an InitialBaselineSubmission message. The objective of the BaselineReSubmission message sent in the outlined scenario is to achieve a successful match of two baseline initiation messages in order to establish a transaction in the matching application. or The BaselineReSubmission message can be sent by the initiator of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct an InitialBaselineSubmission or BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application. or The BaselineReSubmission message can be sent by the counterparty of a transaction to the matching application in response to a BaselineMatchReport message indicating mis-matches. The objective of the BaselineReSubmission message sent in the outlined scenario is to correct a BaselineReSubmission message submitted earlier in order to achieve the establishment of a transaction in the matching application.

func (*BaselineReSubmissionV05) AddBankContactPerson 

func (b *BaselineReSubmissionV05) AddBankContactPerson() *iso20022.BankContactPerson1Choice

func (*BaselineReSubmissionV05) AddBaseline 

func (b *BaselineReSubmissionV05) AddBaseline() *iso20022.Baseline5

func (*BaselineReSubmissionV05) AddBuyerContactPerson 

func (b *BaselineReSubmissionV05) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV05) AddOtherBankContactPerson 

func (b *BaselineReSubmissionV05) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*BaselineReSubmissionV05) AddSellerContactPerson 

func (b *BaselineReSubmissionV05) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*BaselineReSubmissionV05) AddSubmissionIdentification 

func (b *BaselineReSubmissionV05) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*BaselineReSubmissionV05) AddSubmitterTransactionReference 

func (b *BaselineReSubmissionV05) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*BaselineReSubmissionV05) AddTransactionIdentification 

func (b *BaselineReSubmissionV05) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type BaselineReportV03 

type BaselineReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the related message at the origin of the report or sent at the same time than the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef,omitempty"`

	// Type of baseline report.
	ReportType *iso20022.ReportType2 `xml:"RptTp"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification6 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that buys goods or services, or a financial instrument.
	Buyer *iso20022.PartyIdentification26 `xml:"Buyr"`

	// Party that sells goods or services, or a financial instrument.
	Seller *iso20022.PartyIdentification26 `xml:"Sellr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Information on the goods
	ReportedLineItem *iso20022.LineItem8 `xml:"RptdLineItm"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The BaselineReport message is sent by the matching application to the parties involved in an amendment request or to the parties involved in a data set match. The message is used to report either a pre-calculation or final calculation of the dynamic part of an established baseline. Usage The BaselineReport message can be sent by the matching application to the parties involved in an amendment request for a transaction established in the push-through mode. In the outlined scenario, the message is sent - to the party requested to accept or reject an amendment request after the matching application has received a BaselineAmendmentRequest message. The message informs about the provisional status of the dynamic part of the baseline. - to the requester and the accepter of an amendment request after the matching application has received an AmendmentAcceptance message conveying the acceptance of the amendment request. The message informs about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the party which has sent an amendment request for a transaction established in the lodge mode. In the outlined scenario the message is used to inform about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the parties involved in a data set match. In the outlined scenario, the message is sent - to the submitter of the data set(s) in the case of a data set match for a transaction established in the lodge mode. - to the submitter of the data set(s) and to the counterparty in case of a data set match for a transaction established in the push-through mode.The message can be sent after a successful data-set match or after the acceptance of mis-matched data sets to inform about the actual status of the dynamic part of the baseline.

func (*BaselineReportV03) AddBuyer 

func (b *BaselineReportV03) AddBuyer() *iso20022.PartyIdentification26

func (*BaselineReportV03) AddBuyerBank 

func (b *BaselineReportV03) AddBuyerBank() *iso20022.BICIdentification1

func (*BaselineReportV03) AddEstablishedBaselineIdentification 

func (b *BaselineReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification6

func (*BaselineReportV03) AddRelatedMessageReference 

func (b *BaselineReportV03) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*BaselineReportV03) AddReportIdentification 

func (b *BaselineReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*BaselineReportV03) AddReportType 

func (b *BaselineReportV03) AddReportType() *iso20022.ReportType2

func (*BaselineReportV03) AddReportedLineItem 

func (b *BaselineReportV03) AddReportedLineItem() *iso20022.LineItem8

func (*BaselineReportV03) AddRequestForAction 

func (b *BaselineReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*BaselineReportV03) AddSeller 

func (b *BaselineReportV03) AddSeller() *iso20022.PartyIdentification26

func (*BaselineReportV03) AddSellerBank 

func (b *BaselineReportV03) AddSellerBank() *iso20022.BICIdentification1

func (*BaselineReportV03) AddTransactionIdentification 

func (b *BaselineReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*BaselineReportV03) AddTransactionStatus 

func (b *BaselineReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*BaselineReportV03) AddUserTransactionReference 

func (b *BaselineReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type BaselineReportV04 

type BaselineReportV04 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the related message at the origin of the report or sent at the same time than the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef,omitempty"`

	// Type of baseline report.
	ReportType *iso20022.ReportType2 `xml:"RptTp"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification6 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that buys goods or services, or a financial instrument.
	Buyer *iso20022.PartyIdentification26 `xml:"Buyr"`

	// Party that sells goods or services, or a financial instrument.
	Seller *iso20022.PartyIdentification26 `xml:"Sellr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Information on the goods
	ReportedLineItem *iso20022.LineItem14 `xml:"RptdLineItm"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The BaselineReport message is sent by the matching application to the parties involved in an amendment request or to the parties involved in a data set match. The message is used to report either a pre-calculation or final calculation of the dynamic part of an established baseline. Usage The BaselineReport message can be sent by the matching application to the parties involved in an amendment request for a transaction established in the push-through mode. In the outlined scenario, the message is sent - to the party requested to accept or reject an amendment request after the matching application has received a BaselineAmendmentRequest message. The message informs about the provisional status of the dynamic part of the baseline. - to the requester and the accepter of an amendment request after the matching application has received an AmendmentAcceptance message conveying the acceptance of the amendment request. The message informs about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the party which has sent an amendment request for a transaction established in the lodge mode. In the outlined scenario the message is used to inform about the actual status of the dynamic part of the baseline. or The BaselineReport message can be sent by the matching application to the parties involved in a data set match. In the outlined scenario, the message is sent - to the submitter of the data set(s) in the case of a data set match for a transaction established in the lodge mode. - to the submitter of the data set(s) and to the counterparty in case of a data set match for a transaction established in the push-through mode.The message can be sent after a successful data-set match or after the acceptance of mis-matched data sets to inform about the actual status of the dynamic part of the baseline.

func (*BaselineReportV04) AddBuyer 

func (b *BaselineReportV04) AddBuyer() *iso20022.PartyIdentification26

func (*BaselineReportV04) AddBuyerBank 

func (b *BaselineReportV04) AddBuyerBank() *iso20022.BICIdentification1

func (*BaselineReportV04) AddEstablishedBaselineIdentification 

func (b *BaselineReportV04) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification6

func (*BaselineReportV04) AddRelatedMessageReference 

func (b *BaselineReportV04) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*BaselineReportV04) AddReportIdentification 

func (b *BaselineReportV04) AddReportIdentification() *iso20022.MessageIdentification1

func (*BaselineReportV04) AddReportType 

func (b *BaselineReportV04) AddReportType() *iso20022.ReportType2

func (*BaselineReportV04) AddReportedLineItem 

func (b *BaselineReportV04) AddReportedLineItem() *iso20022.LineItem14

func (*BaselineReportV04) AddRequestForAction 

func (b *BaselineReportV04) AddRequestForAction() *iso20022.PendingActivity2

func (*BaselineReportV04) AddSeller 

func (b *BaselineReportV04) AddSeller() *iso20022.PartyIdentification26

func (*BaselineReportV04) AddSellerBank 

func (b *BaselineReportV04) AddSellerBank() *iso20022.BICIdentification1

func (*BaselineReportV04) AddTransactionIdentification 

func (b *BaselineReportV04) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*BaselineReportV04) AddTransactionStatus 

func (b *BaselineReportV04) AddTransactionStatus() *iso20022.TransactionStatus4

func (*BaselineReportV04) AddUserTransactionReference 

func (b *BaselineReportV04) AddUserTransactionReference() *iso20022.DocumentIdentification5

type DataSetMatchReportV03 

type DataSetMatchReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that buys goods or services, or a financial instrument.
	Buyer *iso20022.PartyIdentification26 `xml:"Buyr"`

	// Party that sells goods or services, or a financial instrument.
	Seller *iso20022.PartyIdentification26 `xml:"Sellr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Identifies the documents compared in this report.
	ComparedDocumentReference []*iso20022.DocumentIdentification10 `xml:"CmpardDocRef"`

	// Specifies whether the data set was submitted for match or pre-match.
	SubmissionType *iso20022.ReportType3 `xml:"SubmissnTp"`

	// Description of the differences between the data set(s) and the baseline.
	Report *iso20022.MisMatchReport3 `xml:"Rpt"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The DataSetMatchReport message is sent by the matching application to the parties involved in a data set match. This message is used to either - inform about the successful match of data sets submitted with the instruction match or pre-match (DataSetSubmission message) and the related baseline,or - inform about mis-matches found between data sets submitted with the instruction match or pre-match (DataSetSubmission message) and the related baseline. Usage The DataSetMatchReport message can be sent by the matching application to the party requesting a data set pre-match for a transaction established in the push-through mode. In the outlined scenario, the DataSetMatchReport message will either inform about the successful pre-match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline. or The DataSetMatchReport message can be sent by the matching application to the parties involved in a data set match for a transaction established in the push-through mode. In the outlined scenario, the DataSetMatchReport message will either inform about the successful match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline. or The DataSetMatchReport message can be sent by the matching application to the party requesting a data set match or pre-match for a transaction established in the lodge mode. In the outlined scenario, the DataSetMatchReport will either inform about the successful match or list the mis-matches between the data set(s) conveyed with the DataSetSubmission message and the related baseline.

func (*DataSetMatchReportV03) AddBuyer 

func (d *DataSetMatchReportV03) AddBuyer() *iso20022.PartyIdentification26

func (*DataSetMatchReportV03) AddBuyerBank 

func (d *DataSetMatchReportV03) AddBuyerBank() *iso20022.BICIdentification1

func (*DataSetMatchReportV03) AddComparedDocumentReference 

func (d *DataSetMatchReportV03) AddComparedDocumentReference() *iso20022.DocumentIdentification10

func (*DataSetMatchReportV03) AddEstablishedBaselineIdentification 

func (d *DataSetMatchReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*DataSetMatchReportV03) AddReport 

func (d *DataSetMatchReportV03) AddReport() *iso20022.MisMatchReport3

func (*DataSetMatchReportV03) AddReportIdentification 

func (d *DataSetMatchReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*DataSetMatchReportV03) AddRequestForAction 

func (d *DataSetMatchReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*DataSetMatchReportV03) AddSeller 

func (d *DataSetMatchReportV03) AddSeller() *iso20022.PartyIdentification26

func (*DataSetMatchReportV03) AddSellerBank 

func (d *DataSetMatchReportV03) AddSellerBank() *iso20022.BICIdentification1

func (*DataSetMatchReportV03) AddSubmissionType 

func (d *DataSetMatchReportV03) AddSubmissionType() *iso20022.ReportType3

func (*DataSetMatchReportV03) AddTransactionIdentification 

func (d *DataSetMatchReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*DataSetMatchReportV03) AddTransactionStatus 

func (d *DataSetMatchReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*DataSetMatchReportV03) AddUserTransactionReference 

func (d *DataSetMatchReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type DataSetSubmissionV03 

type DataSetSubmissionV03 struct {

	// Identifies the submitted information.
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences3 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// Specifies the instruction given by the submitter.
	Instruction *iso20022.InstructionType3 `xml:"Instr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that is submitted to the matching application for processing.
	CommercialDataSet *iso20022.CommercialDataSet3 `xml:"ComrclDataSet,omitempty"`

	// Transport information that is submitted to the matching application for processing.
	TransportDataSet *iso20022.TransportDataSet3 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that is submitted to the matching application for processing.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that is submitted to the matching application for processing.
	CertificateDataSet []*iso20022.CertificateDataSet1 `xml:"CertDataSet,omitempty"`

	// Other certificate information that is submitted to the matching application for processing.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet1 `xml:"OthrCertDataSet,omitempty"`
}

Scope The DataSetSubmission message is sent by a party involved in the transaction to the matching application. This message is used to trigger either a match or a pre-match of the information submitted with the message. Usage The DataSetSubmission message can be sent by either party with the instruction pre-match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to the requester of the data set pre-match by sending a DataSetMatchReport message. or The DataSetSubmission message can be sent by the party specified in the baseline as data set submitter with the instruction match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to - the parties involved in a transaction established in the push-through mode, or - the initiator of a transaction established in the lodge mode. The DataSetSubmission message can be used to submit multiple data sets for multiple transactions (baselines) at the same time. However, all transactions (baselines) covered by the message must be for the same parties, that is transaction initiator and counterparty, as well as for the same buyer and seller. The DataSetSubmission message consists of data reflecting trade information related to the purchasing agreement covered by the transaction(s), for example shipment date, invoice amount.

func (*DataSetSubmissionV03) AddBuyerBank 

func (d *DataSetSubmissionV03) AddBuyerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV03) AddCertificateDataSet 

func (d *DataSetSubmissionV03) AddCertificateDataSet() *iso20022.CertificateDataSet1

func (*DataSetSubmissionV03) AddCommercialDataSet 

func (d *DataSetSubmissionV03) AddCommercialDataSet() *iso20022.CommercialDataSet3

func (*DataSetSubmissionV03) AddCommonSubmissionReference 

func (d *DataSetSubmissionV03) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*DataSetSubmissionV03) AddInstruction 

func (d *DataSetSubmissionV03) AddInstruction() *iso20022.InstructionType3

func (*DataSetSubmissionV03) AddInsuranceDataSet 

func (d *DataSetSubmissionV03) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*DataSetSubmissionV03) AddOtherCertificateDataSet 

func (d *DataSetSubmissionV03) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet1

func (*DataSetSubmissionV03) AddRelatedTransactionReferences 

func (d *DataSetSubmissionV03) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences3

func (*DataSetSubmissionV03) AddSellerBank 

func (d *DataSetSubmissionV03) AddSellerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV03) AddSubmissionIdentification 

func (d *DataSetSubmissionV03) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*DataSetSubmissionV03) AddTransportDataSet 

func (d *DataSetSubmissionV03) AddTransportDataSet() *iso20022.TransportDataSet3

type DataSetSubmissionV04 

type DataSetSubmissionV04 struct {

	// Identifies the submitted information.
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences3 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// Specifies the instruction given by the submitter.
	Instruction *iso20022.InstructionType3 `xml:"Instr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that is submitted to the matching application for processing.
	CommercialDataSet *iso20022.CommercialDataSet4 `xml:"ComrclDataSet,omitempty"`

	// Transport information that is submitted to the matching application for processing.
	TransportDataSet *iso20022.TransportDataSet4 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that is submitted to the matching application for processing.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that is submitted to the matching application for processing.
	CertificateDataSet []*iso20022.CertificateDataSet2 `xml:"CertDataSet,omitempty"`

	// Other certificate information that is submitted to the matching application for processing.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet1 `xml:"OthrCertDataSet,omitempty"`
}

Scope The DataSetSubmission message is sent by a party involved in the transaction to the matching application. This message is used to trigger either a match or a pre-match of the information submitted with the message. Usage The DataSetSubmission message can be sent by either party with the instruction pre-match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to the requester of the data set pre-match by sending a DataSetMatchReport message. or The DataSetSubmission message can be sent by the party specified in the baseline as data set submitter with the instruction match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to - the parties involved in a transaction established in the push-through mode, or - the initiator of a transaction established in the lodge mode. The DataSetSubmission message can be used to submit multiple data sets for multiple transactions (baselines) at the same time. However, all transactions (baselines) covered by the message must be for the same parties, that is transaction initiator and counterparty, as well as for the same buyer and seller. The DataSetSubmission message consists of data reflecting trade information related to the purchasing agreement covered by the transaction(s), for example shipment date, invoice amount.

func (*DataSetSubmissionV04) AddBuyerBank 

func (d *DataSetSubmissionV04) AddBuyerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV04) AddCertificateDataSet 

func (d *DataSetSubmissionV04) AddCertificateDataSet() *iso20022.CertificateDataSet2

func (*DataSetSubmissionV04) AddCommercialDataSet 

func (d *DataSetSubmissionV04) AddCommercialDataSet() *iso20022.CommercialDataSet4

func (*DataSetSubmissionV04) AddCommonSubmissionReference 

func (d *DataSetSubmissionV04) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*DataSetSubmissionV04) AddInstruction 

func (d *DataSetSubmissionV04) AddInstruction() *iso20022.InstructionType3

func (*DataSetSubmissionV04) AddInsuranceDataSet 

func (d *DataSetSubmissionV04) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*DataSetSubmissionV04) AddOtherCertificateDataSet 

func (d *DataSetSubmissionV04) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet1

func (*DataSetSubmissionV04) AddRelatedTransactionReferences 

func (d *DataSetSubmissionV04) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences3

func (*DataSetSubmissionV04) AddSellerBank 

func (d *DataSetSubmissionV04) AddSellerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV04) AddSubmissionIdentification 

func (d *DataSetSubmissionV04) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*DataSetSubmissionV04) AddTransportDataSet 

func (d *DataSetSubmissionV04) AddTransportDataSet() *iso20022.TransportDataSet4

type DataSetSubmissionV05 

type DataSetSubmissionV05 struct {

	// Identifies the submitted information.
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences3 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// Specifies the instruction given by the submitter.
	Instruction *iso20022.InstructionType3 `xml:"Instr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that is submitted to the matching application for processing.
	CommercialDataSet *iso20022.CommercialDataSet5 `xml:"ComrclDataSet,omitempty"`

	// Transport information that is submitted to the matching application for processing.
	TransportDataSet *iso20022.TransportDataSet5 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that is submitted to the matching application for processing.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that is submitted to the matching application for processing.
	CertificateDataSet []*iso20022.CertificateDataSet2 `xml:"CertDataSet,omitempty"`

	// Other certificate information that is submitted to the matching application for processing.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet2 `xml:"OthrCertDataSet,omitempty"`
}

Scope The DataSetSubmission message is sent by a party involved in the transaction to the matching application. This message is used to trigger either a match or a pre-match of the information submitted with the message. Usage The DataSetSubmission message can be sent by either party with the instruction pre-match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to the requester of the data set pre-match by sending a DataSetMatchReport message. or The DataSetSubmission message can be sent by the party specified in the baseline as data set submitter with the instruction match. In the outlined scenario, the matching application will compare the data set(s) conveyed by the DataSetSubmission message with the established baseline and report the matching result to - the parties involved in a transaction established in the push-through mode, or - the initiator of a transaction established in the lodge mode. The DataSetSubmission message can be used to submit multiple data sets for multiple transactions (baselines) at the same time. However, all transactions (baselines) covered by the message must be for the same parties, that is transaction initiator and counterparty, as well as for the same buyer and seller. The DataSetSubmission message consists of data reflecting trade information related to the purchasing agreement covered by the transaction(s), for example shipment date, invoice amount.

func (*DataSetSubmissionV05) AddBuyerBank 

func (d *DataSetSubmissionV05) AddBuyerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV05) AddCertificateDataSet 

func (d *DataSetSubmissionV05) AddCertificateDataSet() *iso20022.CertificateDataSet2

func (*DataSetSubmissionV05) AddCommercialDataSet 

func (d *DataSetSubmissionV05) AddCommercialDataSet() *iso20022.CommercialDataSet5

func (*DataSetSubmissionV05) AddCommonSubmissionReference 

func (d *DataSetSubmissionV05) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*DataSetSubmissionV05) AddInstruction 

func (d *DataSetSubmissionV05) AddInstruction() *iso20022.InstructionType3

func (*DataSetSubmissionV05) AddInsuranceDataSet 

func (d *DataSetSubmissionV05) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*DataSetSubmissionV05) AddOtherCertificateDataSet 

func (d *DataSetSubmissionV05) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet2

func (*DataSetSubmissionV05) AddRelatedTransactionReferences 

func (d *DataSetSubmissionV05) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences3

func (*DataSetSubmissionV05) AddSellerBank 

func (d *DataSetSubmissionV05) AddSellerBank() *iso20022.BICIdentification1

func (*DataSetSubmissionV05) AddSubmissionIdentification 

func (d *DataSetSubmissionV05) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*DataSetSubmissionV05) AddTransportDataSet 

func (d *DataSetSubmissionV05) AddTransportDataSet() *iso20022.TransportDataSet5

type DeltaReportV03 

type DeltaReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Sequence number of the proposed baseline amendment.
	AmendmentNumber *iso20022.Count1 `xml:"AmdmntNb"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that buys goods or services, or a financial instrument.
	Buyer *iso20022.PartyIdentification26 `xml:"Buyr"`

	// Party that sells goods or services, or a financial instrument.
	Seller *iso20022.PartyIdentification26 `xml:"Sellr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Reference to the identification of the baseline included in the amendment request.
	SubmitterProposedBaselineReference *iso20022.DocumentIdentification1 `xml:"SubmitrPropsdBaselnRef"`

	// Detailed comparison between the currently established baseline elements and the proposed ones.
	UpdatedElement []*iso20022.ComparisonResult2 `xml:"UpdtdElmt"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The DeltaReport message is sent by the matching application to the parties involved in the request of a baseline amendment. The message is used to list the differences between the established and the newly proposed baseline. Usage The DeltaReport message can be sent by the matching application to - the parties involved in the amendment of a baseline that has been established in the push-through mode. In the outlined scenario the message is sent to the requester of the amendment to acknowledge the receipt of the request and to list the differences between the established and the newly proposed baseline and to the counterparty to list the differences between the established and the newly proposed baseline and to request the acceptance or rejection of the amendment request, or - the party that has requested the amendment of a baseline established in the lodge mode. In the outlined scenario the message is used to confirm the changes to the baseline and to list the differences between the amended baseline and the baseline established earlier.

func (*DeltaReportV03) AddAmendmentNumber 

func (d *DeltaReportV03) AddAmendmentNumber() *iso20022.Count1

func (*DeltaReportV03) AddBuyer 

func (d *DeltaReportV03) AddBuyer() *iso20022.PartyIdentification26

func (*DeltaReportV03) AddBuyerBank 

func (d *DeltaReportV03) AddBuyerBank() *iso20022.BICIdentification1

func (*DeltaReportV03) AddEstablishedBaselineIdentification 

func (d *DeltaReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*DeltaReportV03) AddReportIdentification 

func (d *DeltaReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*DeltaReportV03) AddRequestForAction 

func (d *DeltaReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*DeltaReportV03) AddSeller 

func (d *DeltaReportV03) AddSeller() *iso20022.PartyIdentification26

func (*DeltaReportV03) AddSellerBank 

func (d *DeltaReportV03) AddSellerBank() *iso20022.BICIdentification1

func (*DeltaReportV03) AddSubmitterProposedBaselineReference 

func (d *DeltaReportV03) AddSubmitterProposedBaselineReference() *iso20022.DocumentIdentification1

func (*DeltaReportV03) AddTransactionIdentification 

func (d *DeltaReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*DeltaReportV03) AddTransactionStatus 

func (d *DeltaReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*DeltaReportV03) AddUpdatedElement 

func (d *DeltaReportV03) AddUpdatedElement() *iso20022.ComparisonResult2

func (*DeltaReportV03) AddUserTransactionReference 

func (d *DeltaReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type Document00100103 

type Document00100103 struct {
	XMLName xml.Name            `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.001.001.03 Document"`
	Message *AcknowledgementV03 `xml:"Ack"`
}

func (*Document00100103) AddMessage 

func (d *Document00100103) AddMessage() *AcknowledgementV03

type Document00200103 

type Document00200103 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.002.001.03 Document"`
	Message *ActivityReportV03 `xml:"ActvtyRpt"`
}

func (*Document00200103) AddMessage 

func (d *Document00200103) AddMessage() *ActivityReportV03

type Document00200104 

type Document00200104 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.002.001.04 Document"`
	Message *ActivityReportV04 `xml:"ActvtyRpt"`
}

func (*Document00200104) AddMessage 

func (d *Document00200104) AddMessage() *ActivityReportV04

type Document00300103 

type Document00300103 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.003.001.03 Document"`
	Message *ActivityReportRequestV03 `xml:"ActvtyReqRpt"`
}

func (*Document00300103) AddMessage 

func (d *Document00300103) AddMessage() *ActivityReportRequestV03

type Document00400102 

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

func (*Document00400102) AddMessage 

func (d *Document00400102) AddMessage() *ActivityReportSetUpRequestV02

type Document00500102 

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

func (*Document00500102) AddMessage 

func (d *Document00500102) AddMessage() *AmendmentAcceptanceV02

type Document00600103 

type Document00600103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.006.001.03 Document"`
	Message *AmendmentAcceptanceNotificationV03 `xml:"AmdmntAccptncNtfctn"`
}

func (*Document00600103) AddMessage 

func (d *Document00600103) AddMessage() *AmendmentAcceptanceNotificationV03

type Document00700102 

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

func (*Document00700102) AddMessage 

func (d *Document00700102) AddMessage() *AmendmentRejectionV02

type Document00800103 

type Document00800103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.008.001.03 Document"`
	Message *AmendmentRejectionNotificationV03 `xml:"AmdmntRjctnNtfctn"`
}

func (*Document00800103) AddMessage 

func (d *Document00800103) AddMessage() *AmendmentRejectionNotificationV03

type Document00900103 

type Document00900103 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.009.001.03 Document"`
	Message *BaselineAmendmentRequestV03 `xml:"BaselnAmdmntReq"`
}

func (*Document00900103) AddMessage 

func (d *Document00900103) AddMessage() *BaselineAmendmentRequestV03

type Document00900104 

type Document00900104 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.009.001.04 Document"`
	Message *BaselineAmendmentRequestV04 `xml:"BaselnAmdmntReq"`
}

func (*Document00900104) AddMessage 

func (d *Document00900104) AddMessage() *BaselineAmendmentRequestV04

type Document00900105 

type Document00900105 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.009.001.05 Document"`
	Message *BaselineAmendmentRequestV05 `xml:"BaselnAmdmntReq"`
}

func (*Document00900105) AddMessage 

func (d *Document00900105) AddMessage() *BaselineAmendmentRequestV05

type Document01000103 

type Document01000103 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.010.001.03 Document"`
	Message *BaselineMatchReportV03 `xml:"BaselnMtchRpt"`
}

func (*Document01000103) AddMessage 

func (d *Document01000103) AddMessage() *BaselineMatchReportV03

type Document01100103 

type Document01100103 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.011.001.03 Document"`
	Message *BaselineReportV03 `xml:"BaselnRpt"`
}

func (*Document01100103) AddMessage 

func (d *Document01100103) AddMessage() *BaselineReportV03

type Document01100104 

type Document01100104 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.011.001.04 Document"`
	Message *BaselineReportV04 `xml:"BaselnRpt"`
}

func (*Document01100104) AddMessage 

func (d *Document01100104) AddMessage() *BaselineReportV04

type Document01200103 

type Document01200103 struct {
	XMLName xml.Name                 `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.012.001.03 Document"`
	Message *BaselineReSubmissionV03 `xml:"BaselnReSubmissn"`
}

func (*Document01200103) AddMessage 

func (d *Document01200103) AddMessage() *BaselineReSubmissionV03

type Document01200104 

type Document01200104 struct {
	XMLName xml.Name                 `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.012.001.04 Document"`
	Message *BaselineReSubmissionV04 `xml:"BaselnReSubmissn"`
}

func (*Document01200104) AddMessage 

func (d *Document01200104) AddMessage() *BaselineReSubmissionV04

type Document01200105 

type Document01200105 struct {
	XMLName xml.Name                 `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.012.001.05 Document"`
	Message *BaselineReSubmissionV05 `xml:"BaselnReSubmissn"`
}

func (*Document01200105) AddMessage 

func (d *Document01200105) AddMessage() *BaselineReSubmissionV05

type Document01300103 

type Document01300103 struct {
	XMLName xml.Name               `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.013.001.03 Document"`
	Message *DataSetMatchReportV03 `xml:"DataSetMtchRpt"`
}

func (*Document01300103) AddMessage 

func (d *Document01300103) AddMessage() *DataSetMatchReportV03

type Document01400103 

type Document01400103 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.014.001.03 Document"`
	Message *DataSetSubmissionV03 `xml:"DataSetSubmissn"`
}

func (*Document01400103) AddMessage 

func (d *Document01400103) AddMessage() *DataSetSubmissionV03

type Document01400104 

type Document01400104 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.014.001.04 Document"`
	Message *DataSetSubmissionV04 `xml:"DataSetSubmissn"`
}

func (*Document01400104) AddMessage 

func (d *Document01400104) AddMessage() *DataSetSubmissionV04

type Document01400105 

type Document01400105 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.014.001.05 Document"`
	Message *DataSetSubmissionV05 `xml:"DataSetSubmissn"`
}

func (*Document01400105) AddMessage 

func (d *Document01400105) AddMessage() *DataSetSubmissionV05

type Document01500103 

type Document01500103 struct {
	XMLName xml.Name        `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.015.001.03 Document"`
	Message *DeltaReportV03 `xml:"DltaRpt"`
}

func (*Document01500103) AddMessage 

func (d *Document01500103) AddMessage() *DeltaReportV03

type Document01600103 

type Document01600103 struct {
	XMLName xml.Name        `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.016.001.03 Document"`
	Message *ErrorReportV03 `xml:"ErrRpt"`
}

func (*Document01600103) AddMessage 

func (d *Document01600103) AddMessage() *ErrorReportV03

type Document01700103 

type Document01700103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.017.001.03 Document"`
	Message *ForwardDataSetSubmissionReportV03 `xml:"FwdDataSetSubmissnRpt"`
}

func (*Document01700103) AddMessage 

func (d *Document01700103) AddMessage() *ForwardDataSetSubmissionReportV03

type Document01700104 

type Document01700104 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.017.001.04 Document"`
	Message *ForwardDataSetSubmissionReportV04 `xml:"FwdDataSetSubmissnRpt"`
}

func (*Document01700104) AddMessage 

func (d *Document01700104) AddMessage() *ForwardDataSetSubmissionReportV04

type Document01700105 

type Document01700105 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.017.001.05 Document"`
	Message *ForwardDataSetSubmissionReportV05 `xml:"FwdDataSetSubmissnRpt"`
}

func (*Document01700105) AddMessage 

func (d *Document01700105) AddMessage() *ForwardDataSetSubmissionReportV05

type Document01800103 

type Document01800103 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.018.001.03 Document"`
	Message *FullPushThroughReportV03 `xml:"FullPushThrghRpt"`
}

func (*Document01800103) AddMessage 

func (d *Document01800103) AddMessage() *FullPushThroughReportV03

type Document01800104 

type Document01800104 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.018.001.04 Document"`
	Message *FullPushThroughReportV04 `xml:"FullPushThrghRpt"`
}

func (*Document01800104) AddMessage 

func (d *Document01800104) AddMessage() *FullPushThroughReportV04

type Document01800105 

type Document01800105 struct {
	XMLName xml.Name                  `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.018.001.05 Document"`
	Message *FullPushThroughReportV05 `xml:"FullPushThrghRpt"`
}

func (*Document01800105) AddMessage 

func (d *Document01800105) AddMessage() *FullPushThroughReportV05

type Document01900103 

type Document01900103 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.019.001.03 Document"`
	Message *InitialBaselineSubmissionV03 `xml:"InitlBaselnSubmissn"`
}

func (*Document01900103) AddMessage 

func (d *Document01900103) AddMessage() *InitialBaselineSubmissionV03

type Document01900104 

type Document01900104 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.019.001.04 Document"`
	Message *InitialBaselineSubmissionV04 `xml:"InitlBaselnSubmissn"`
}

func (*Document01900104) AddMessage 

func (d *Document01900104) AddMessage() *InitialBaselineSubmissionV04

type Document01900105 

type Document01900105 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.019.001.05 Document"`
	Message *InitialBaselineSubmissionV05 `xml:"InitlBaselnSubmissn"`
}

func (*Document01900105) AddMessage 

func (d *Document01900105) AddMessage() *InitialBaselineSubmissionV05

type Document02000102 

type Document02000102 struct {
	XMLName xml.Name               `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.020.001.02 Document"`
	Message *MisMatchAcceptanceV02 `xml:"MisMtchAccptnc"`
}

func (*Document02000102) AddMessage 

func (d *Document02000102) AddMessage() *MisMatchAcceptanceV02

type Document02100103 

type Document02100103 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.021.001.03 Document"`
	Message *MisMatchAcceptanceNotificationV03 `xml:"MisMtchAccptncNtfctn"`
}

func (*Document02100103) AddMessage 

func (d *Document02100103) AddMessage() *MisMatchAcceptanceNotificationV03

type Document02200102 

type Document02200102 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.022.001.02 Document"`
	Message *MisMatchRejectionV02 `xml:"MisMtchRjctn"`
}

func (*Document02200102) AddMessage 

func (d *Document02200102) AddMessage() *MisMatchRejectionV02

type Document02300103 

type Document02300103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.023.001.03 Document"`
	Message *MisMatchRejectionNotificationV03 `xml:"MisMtchRjctnNtfctn"`
}

func (*Document02300103) AddMessage 

func (d *Document02300103) AddMessage() *MisMatchRejectionNotificationV03

type Document02400103 

type Document02400103 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.024.001.03 Document"`
	Message *ActionReminderV03 `xml:"ActnRmndr"`
}

func (*Document02400103) AddMessage 

func (d *Document02400103) AddMessage() *ActionReminderV03

type Document02500103 

type Document02500103 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.025.001.03 Document"`
	Message *StatusChangeNotificationV03 `xml:"StsChngNtfctn"`
}

func (*Document02500103) AddMessage 

func (d *Document02500103) AddMessage() *StatusChangeNotificationV03

type Document02600102 

type Document02600102 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.026.001.02 Document"`
	Message *StatusChangeRequestV02 `xml:"StsChngReq"`
}

func (*Document02600102) AddMessage 

func (d *Document02600102) AddMessage() *StatusChangeRequestV02

type Document02700102 

type Document02700102 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.027.001.02 Document"`
	Message *StatusChangeRequestAcceptanceV02 `xml:"StsChngReqAccptnc"`
}

func (*Document02700102) AddMessage 

func (d *Document02700102) AddMessage() *StatusChangeRequestAcceptanceV02

type Document02800103 

type Document02800103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.028.001.03 Document"`
	Message *StatusChangeRequestNotificationV03 `xml:"StsChngReqNtfctn"`
}

func (*Document02800103) AddMessage 

func (d *Document02800103) AddMessage() *StatusChangeRequestNotificationV03

type Document02900102 

type Document02900102 struct {
	XMLName xml.Name                         `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.029.001.02 Document"`
	Message *StatusChangeRequestRejectionV02 `xml:"StsChngReqRjctn"`
}

func (*Document02900102) AddMessage 

func (d *Document02900102) AddMessage() *StatusChangeRequestRejectionV02

type Document03000103 

type Document03000103 struct {
	XMLName xml.Name                                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.030.001.03 Document"`
	Message *StatusChangeRequestRejectionNotificationV03 `xml:"StsChngReqRjctnNtfctn"`
}

func (*Document03000103) AddMessage 

func (d *Document03000103) AddMessage() *StatusChangeRequestRejectionNotificationV03

type Document03100103 

type Document03100103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.031.001.03 Document"`
	Message *StatusExtensionRequestAcceptanceV03 `xml:"StsXtnsnReqAccptnc"`
}

func (*Document03100103) AddMessage 

func (d *Document03100103) AddMessage() *StatusExtensionRequestAcceptanceV03

type Document03200103 

type Document03200103 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.032.001.03 Document"`
	Message *StatusExtensionNotificationV03 `xml:"StsXtnsnNtfctn"`
}

func (*Document03200103) AddMessage 

func (d *Document03200103) AddMessage() *StatusExtensionNotificationV03

type Document03300103 

type Document03300103 struct {
	XMLName xml.Name                            `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.033.001.03 Document"`
	Message *StatusExtensionRequestRejectionV03 `xml:"StsXtnsnReqRjctn"`
}

func (*Document03300103) AddMessage 

func (d *Document03300103) AddMessage() *StatusExtensionRequestRejectionV03

type Document03400103 

type Document03400103 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.034.001.03 Document"`
	Message *StatusExtensionRejectionNotificationV03 `xml:"StsXtnsnRjctnNtfctn"`
}

func (*Document03400103) AddMessage 

func (d *Document03400103) AddMessage() *StatusExtensionRejectionNotificationV03

type Document03500103 

type Document03500103 struct {
	XMLName xml.Name                   `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.035.001.03 Document"`
	Message *StatusExtensionRequestV03 `xml:"StsXtnsnReq"`
}

func (*Document03500103) AddMessage 

func (d *Document03500103) AddMessage() *StatusExtensionRequestV03

type Document03600103 

type Document03600103 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.036.001.03 Document"`
	Message *StatusExtensionRequestNotificationV03 `xml:"StsXtnsnReqNtfctn"`
}

func (*Document03600103) AddMessage 

func (d *Document03600103) AddMessage() *StatusExtensionRequestNotificationV03

type Document03700103 

type Document03700103 struct {
	XMLName xml.Name         `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.037.001.03 Document"`
	Message *StatusReportV03 `xml:"StsRpt"`
}

func (*Document03700103) AddMessage 

func (d *Document03700103) AddMessage() *StatusReportV03

type Document03800103 

type Document03800103 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.038.001.03 Document"`
	Message *StatusReportRequestV03 `xml:"StsRptReq"`
}

func (*Document03800103) AddMessage 

func (d *Document03800103) AddMessage() *StatusReportRequestV03

type Document04000103 

type Document04000103 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.040.001.03 Document"`
	Message *TimeOutNotificationV03 `xml:"TmOutNtfctn"`
}

func (*Document04000103) AddMessage 

func (d *Document04000103) AddMessage() *TimeOutNotificationV03

type Document04100103 

type Document04100103 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.041.001.03 Document"`
	Message *TransactionReportV03 `xml:"TxRpt"`
}

func (*Document04100103) AddMessage 

func (d *Document04100103) AddMessage() *TransactionReportV03

type Document04200103 

type Document04200103 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.042.001.03 Document"`
	Message *TransactionReportRequestV03 `xml:"TxRptReq"`
}

func (*Document04200103) AddMessage 

func (d *Document04200103) AddMessage() *TransactionReportRequestV03

type Document04400101 

type Document04400101 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.044.001.01 Document"`
	Message *IntentToPayNotificationV01 `xml:"InttToPayNtfctn"`
}

func (*Document04400101) AddMessage 

func (d *Document04400101) AddMessage() *IntentToPayNotificationV01

type Document04400102 

type Document04400102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.044.001.02 Document"`
	Message *IntentToPayNotificationV02 `xml:"InttToPayNtfctn"`
}

func (*Document04400102) AddMessage 

func (d *Document04400102) AddMessage() *IntentToPayNotificationV02

type Document04500101 

type Document04500101 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.045.001.01 Document"`
	Message *ForwardIntentToPayNotificationV01 `xml:"FwdInttToPayNtfctn"`
}

func (*Document04500101) AddMessage 

func (d *Document04500101) AddMessage() *ForwardIntentToPayNotificationV01

type Document04500102 

type Document04500102 struct {
	XMLName xml.Name                           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.045.001.02 Document"`
	Message *ForwardIntentToPayNotificationV02 `xml:"FwdInttToPayNtfctn"`
}

func (*Document04500102) AddMessage 

func (d *Document04500102) AddMessage() *ForwardIntentToPayNotificationV02

type Document04600101 

type Document04600101 struct {
	XMLName xml.Name              `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.046.001.01 Document"`
	Message *IntentToPayReportV01 `xml:"InttToPayRpt"`
}

func (*Document04600101) AddMessage 

func (d *Document04600101) AddMessage() *IntentToPayReportV01

type Document04700101 

type Document04700101 struct {
	XMLName xml.Name           `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.047.001.01 Document"`
	Message *SpecialRequestV01 `xml:"SpclReq"`
}

func (*Document04700101) AddMessage 

func (d *Document04700101) AddMessage() *SpecialRequestV01

type Document04800101 

type Document04800101 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.048.001.01 Document"`
	Message *SpecialNotificationV01 `xml:"SpclNtfctn"`
}

func (*Document04800101) AddMessage 

func (d *Document04800101) AddMessage() *SpecialNotificationV01

type Document04900101 

type Document04900101 struct {
	XMLName xml.Name                      `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.049.001.01 Document"`
	Message *RoleAndBaselineAcceptanceV01 `xml:"RoleAndBaselnAccptnc"`
}

func (*Document04900101) AddMessage 

func (d *Document04900101) AddMessage() *RoleAndBaselineAcceptanceV01

type Document05000101 

type Document05000101 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.050.001.01 Document"`
	Message *RoleAndBaselineRejectionV01 `xml:"RoleAndBaselnRjctn"`
}

func (*Document05000101) AddMessage 

func (d *Document05000101) AddMessage() *RoleAndBaselineRejectionV01

type Document05100101 

type Document05100101 struct {
	XMLName xml.Name                                  `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.051.001.01 Document"`
	Message *RoleAndBaselineAcceptanceNotificationV01 `xml:"RoleAndBaselnAccptncNtfctn"`
}

func (*Document05100101) AddMessage 

func (d *Document05100101) AddMessage() *RoleAndBaselineAcceptanceNotificationV01

type Document05200101 

type Document05200101 struct {
	XMLName xml.Name                                 `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.052.001.01 Document"`
	Message *RoleAndBaselineRejectionNotificationV01 `xml:"RoleAndBaselnRjctnNtfctn"`
}

func (*Document05200101) AddMessage 

func (d *Document05200101) AddMessage() *RoleAndBaselineRejectionNotificationV01

type Document05300101 

type Document05300101 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.053.001.01 Document"`
	Message *InvoicePaymentReconciliationAdviceV01 `xml:"InvcPmtRcncltnAdvc"`
}

func (*Document05300101) AddMessage 

func (d *Document05300101) AddMessage() *InvoicePaymentReconciliationAdviceV01

type Document05400101 

type Document05400101 struct {
	XMLName xml.Name                               `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.054.001.01 Document"`
	Message *InvoicePaymentReconciliationStatusV01 `xml:"InvcPmtRcncltnSts"`
}

func (*Document05400101) AddMessage 

func (d *Document05400101) AddMessage() *InvoicePaymentReconciliationStatusV01

type Document05500101 

type Document05500101 struct {
	XMLName xml.Name             `xml:"urn:iso:std:iso:20022:tech:xsd:tsmt.055.001.01 Document"`
	Message *PartyEventAdviceV01 `xml:"PtyEvtAdvc"`
}

func (*Document05500101) AddMessage 

func (d *Document05500101) AddMessage() *PartyEventAdviceV01

type ErrorReportV03 

type ErrorReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId,omitempty"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts,omitempty"`

	// Reference to the transaction for the financial institution which is the sender of the rejected message.
	UserTransactionReference *iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the rejected message.
	RejectedMessageReference *iso20022.MessageIdentification1 `xml:"RjctdMsgRef,omitempty"`

	// Specifies the total number of errors identified in the rejected message.
	NumberOfErrors *iso20022.Count1 `xml:"NbOfErrs"`

	// Describes the error that is the cause of the rejection.
	ErrorDescription []*iso20022.ValidationResult3 `xml:"ErrDesc"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ErrorReport message is sent by the matching application to the party from which it received a message. This message is used to inform about the inability of the matching application to process a received message. Usage The ErrorReport message can be sent to a party from which the matching application received a message to inform about its inability to process the received message because - the syntax of the message is incorrect,or - the message content is inconsistent,or - according to the workflow implemented in the matching application, it did not expect the received message.

func (*ErrorReportV03) AddErrorDescription 

func (e *ErrorReportV03) AddErrorDescription() *iso20022.ValidationResult3

func (*ErrorReportV03) AddEstablishedBaselineIdentification 

func (e *ErrorReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*ErrorReportV03) AddNumberOfErrors 

func (e *ErrorReportV03) AddNumberOfErrors() *iso20022.Count1

func (*ErrorReportV03) AddRejectedMessageReference 

func (e *ErrorReportV03) AddRejectedMessageReference() *iso20022.MessageIdentification1

func (*ErrorReportV03) AddReportIdentification 

func (e *ErrorReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*ErrorReportV03) AddRequestForAction 

func (e *ErrorReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*ErrorReportV03) AddTransactionIdentification 

func (e *ErrorReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*ErrorReportV03) AddTransactionStatus 

func (e *ErrorReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*ErrorReportV03) AddUserTransactionReference 

func (e *ErrorReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type ForwardDataSetSubmissionReportV03 

type ForwardDataSetSubmissionReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences4 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// The financial institution that has submitted the data sets to the matching engine.
	Submitter *iso20022.BICIdentification1 `xml:"Submitr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that has been submitted to the matching application by the other party.
	CommercialDataSet *iso20022.CommercialDataSet3 `xml:"ComrclDataSet,omitempty"`

	// Transport information that has been submitted to the matching application by the other party.
	TransportDataSet *iso20022.TransportDataSet3 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that has been submitted to the matching application by the other party.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that has been submitted to the matching application by the other party.
	CertificateDataSet []*iso20022.CertificateDataSet1 `xml:"CertDataSet,omitempty"`

	// Other certificate information that has been submitted to the matching application by the other party.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet1 `xml:"OthrCertDataSet,omitempty"`

	// Next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ForwardDataSetSubmissionReport message is sent by the matching application to the counterparty(ies) of the submitter of data sets. This message is used to pass on information related to the purchasing agreement(s) covered by the transaction(s) referred to in the message. Usage The ForwardDataSetSubmission message can be sent by the matching application to forward the details of a DataSetSubmission message that it has obtained.

func (*ForwardDataSetSubmissionReportV03) AddBuyerBank 

func (f *ForwardDataSetSubmissionReportV03) AddBuyerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV03) AddCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV03) AddCertificateDataSet() *iso20022.CertificateDataSet1

func (*ForwardDataSetSubmissionReportV03) AddCommercialDataSet 

func (f *ForwardDataSetSubmissionReportV03) AddCommercialDataSet() *iso20022.CommercialDataSet3

func (*ForwardDataSetSubmissionReportV03) AddCommonSubmissionReference 

func (f *ForwardDataSetSubmissionReportV03) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*ForwardDataSetSubmissionReportV03) AddInsuranceDataSet 

func (f *ForwardDataSetSubmissionReportV03) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*ForwardDataSetSubmissionReportV03) AddOtherCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV03) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet1

func (*ForwardDataSetSubmissionReportV03) AddRelatedTransactionReferences 

func (f *ForwardDataSetSubmissionReportV03) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences4

func (*ForwardDataSetSubmissionReportV03) AddReportIdentification 

func (f *ForwardDataSetSubmissionReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*ForwardDataSetSubmissionReportV03) AddRequestForAction 

func (f *ForwardDataSetSubmissionReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*ForwardDataSetSubmissionReportV03) AddSellerBank 

func (f *ForwardDataSetSubmissionReportV03) AddSellerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV03) AddSubmitter 

func (f *ForwardDataSetSubmissionReportV03) AddSubmitter() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV03) AddTransportDataSet 

func (f *ForwardDataSetSubmissionReportV03) AddTransportDataSet() *iso20022.TransportDataSet3

type ForwardDataSetSubmissionReportV04 

type ForwardDataSetSubmissionReportV04 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences4 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// The financial institution that has submitted the data sets to the matching engine.
	Submitter *iso20022.BICIdentification1 `xml:"Submitr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that has been submitted to the matching application by the other party.
	CommercialDataSet *iso20022.CommercialDataSet4 `xml:"ComrclDataSet,omitempty"`

	// Transport information that has been submitted to the matching application by the other party.
	TransportDataSet *iso20022.TransportDataSet4 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that has been submitted to the matching application by the other party.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that has been submitted to the matching application by the other party.
	CertificateDataSet []*iso20022.CertificateDataSet2 `xml:"CertDataSet,omitempty"`

	// Other certificate information that has been submitted to the matching application by the other party.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet1 `xml:"OthrCertDataSet,omitempty"`

	// Next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ForwardDataSetSubmissionReport message is sent by the matching application to the counterparty(ies) of the submitter of data sets. This message is used to pass on information related to the purchasing agreement(s) covered by the transaction(s) referred to in the message. Usage The ForwardDataSetSubmission message can be sent by the matching application to forward the details of a DataSetSubmission message that it has obtained.

func (*ForwardDataSetSubmissionReportV04) AddBuyerBank 

func (f *ForwardDataSetSubmissionReportV04) AddBuyerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV04) AddCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV04) AddCertificateDataSet() *iso20022.CertificateDataSet2

func (*ForwardDataSetSubmissionReportV04) AddCommercialDataSet 

func (f *ForwardDataSetSubmissionReportV04) AddCommercialDataSet() *iso20022.CommercialDataSet4

func (*ForwardDataSetSubmissionReportV04) AddCommonSubmissionReference 

func (f *ForwardDataSetSubmissionReportV04) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*ForwardDataSetSubmissionReportV04) AddInsuranceDataSet 

func (f *ForwardDataSetSubmissionReportV04) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*ForwardDataSetSubmissionReportV04) AddOtherCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV04) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet1

func (*ForwardDataSetSubmissionReportV04) AddRelatedTransactionReferences 

func (f *ForwardDataSetSubmissionReportV04) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences4

func (*ForwardDataSetSubmissionReportV04) AddReportIdentification 

func (f *ForwardDataSetSubmissionReportV04) AddReportIdentification() *iso20022.MessageIdentification1

func (*ForwardDataSetSubmissionReportV04) AddRequestForAction 

func (f *ForwardDataSetSubmissionReportV04) AddRequestForAction() *iso20022.PendingActivity2

func (*ForwardDataSetSubmissionReportV04) AddSellerBank 

func (f *ForwardDataSetSubmissionReportV04) AddSellerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV04) AddSubmitter 

func (f *ForwardDataSetSubmissionReportV04) AddSubmitter() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV04) AddTransportDataSet 

func (f *ForwardDataSetSubmissionReportV04) AddTransportDataSet() *iso20022.TransportDataSet4

type ForwardDataSetSubmissionReportV05 

type ForwardDataSetSubmissionReportV05 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Identifies the transactions that this submission relates to and provides associated information.
	RelatedTransactionReferences []*iso20022.DataSetSubmissionReferences4 `xml:"RltdTxRefs"`

	// This reference must be used for all data sets belonging to the same submission group.
	CommonSubmissionReference *iso20022.SimpleIdentificationInformation `xml:"CmonSubmissnRef"`

	// The financial institution that has submitted the data sets to the matching engine.
	Submitter *iso20022.BICIdentification1 `xml:"Submitr"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Commercial information that has been submitted to the matching application by the other party.
	CommercialDataSet *iso20022.CommercialDataSet5 `xml:"ComrclDataSet,omitempty"`

	// Transport information that has been submitted to the matching application by the other party.
	TransportDataSet *iso20022.TransportDataSet5 `xml:"TrnsprtDataSet,omitempty"`

	// Insurance information that has been submitted to the matching application by the other party.
	InsuranceDataSet *iso20022.InsuranceDataSet1 `xml:"InsrncDataSet,omitempty"`

	// Certificate information that has been submitted to the matching application by the other party.
	CertificateDataSet []*iso20022.CertificateDataSet2 `xml:"CertDataSet,omitempty"`

	// Other certificate information that has been submitted to the matching application by the other party.
	OtherCertificateDataSet []*iso20022.OtherCertificateDataSet2 `xml:"OthrCertDataSet,omitempty"`

	// Next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ForwardDataSetSubmissionReport message is sent by the matching application to the counterparty(ies) of the submitter of data sets. This message is used to pass on information related to the purchasing agreement(s) covered by the transaction(s) referred to in the message. Usage The ForwardDataSetSubmission message can be sent by the matching application to forward the details of a DataSetSubmission message that it has obtained.

func (*ForwardDataSetSubmissionReportV05) AddBuyerBank 

func (f *ForwardDataSetSubmissionReportV05) AddBuyerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV05) AddCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV05) AddCertificateDataSet() *iso20022.CertificateDataSet2

func (*ForwardDataSetSubmissionReportV05) AddCommercialDataSet 

func (f *ForwardDataSetSubmissionReportV05) AddCommercialDataSet() *iso20022.CommercialDataSet5

func (*ForwardDataSetSubmissionReportV05) AddCommonSubmissionReference 

func (f *ForwardDataSetSubmissionReportV05) AddCommonSubmissionReference() *iso20022.SimpleIdentificationInformation

func (*ForwardDataSetSubmissionReportV05) AddInsuranceDataSet 

func (f *ForwardDataSetSubmissionReportV05) AddInsuranceDataSet() *iso20022.InsuranceDataSet1

func (*ForwardDataSetSubmissionReportV05) AddOtherCertificateDataSet 

func (f *ForwardDataSetSubmissionReportV05) AddOtherCertificateDataSet() *iso20022.OtherCertificateDataSet2

func (*ForwardDataSetSubmissionReportV05) AddRelatedTransactionReferences 

func (f *ForwardDataSetSubmissionReportV05) AddRelatedTransactionReferences() *iso20022.DataSetSubmissionReferences4

func (*ForwardDataSetSubmissionReportV05) AddReportIdentification 

func (f *ForwardDataSetSubmissionReportV05) AddReportIdentification() *iso20022.MessageIdentification1

func (*ForwardDataSetSubmissionReportV05) AddRequestForAction 

func (f *ForwardDataSetSubmissionReportV05) AddRequestForAction() *iso20022.PendingActivity2

func (*ForwardDataSetSubmissionReportV05) AddSellerBank 

func (f *ForwardDataSetSubmissionReportV05) AddSellerBank() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV05) AddSubmitter 

func (f *ForwardDataSetSubmissionReportV05) AddSubmitter() *iso20022.BICIdentification1

func (*ForwardDataSetSubmissionReportV05) AddTransportDataSet 

func (f *ForwardDataSetSubmissionReportV05) AddTransportDataSet() *iso20022.TransportDataSet5

type ForwardIntentToPayNotificationV01 

type ForwardIntentToPayNotificationV01 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institutions involved in this transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Provides the details of the intention to pay.
	IntentToPay *iso20022.IntentToPay1 `xml:"InttToPay"`

	// Next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ForwardIntentToPayNotification message is forwarded by the matching application from one primary bank to the other primary bank in order to provide details about a future payment. This message contains details about an intention to pay a certain amount, on a certain date, in relation to one or several transactions known to the matching application. Usage The ForwardIntentToPayNotification message is a copy of the IntentToPayNotification message received by the matching application and forwarded to the other primary bank for information. No response is expected.

func (*ForwardIntentToPayNotificationV01) AddBuyerBank 

func (f *ForwardIntentToPayNotificationV01) AddBuyerBank() *iso20022.BICIdentification1

func (*ForwardIntentToPayNotificationV01) AddEstablishedBaselineIdentification 

func (f *ForwardIntentToPayNotificationV01) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*ForwardIntentToPayNotificationV01) AddIntentToPay 

func (f *ForwardIntentToPayNotificationV01) AddIntentToPay() *iso20022.IntentToPay1

func (*ForwardIntentToPayNotificationV01) AddNotificationIdentification 

func (f *ForwardIntentToPayNotificationV01) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*ForwardIntentToPayNotificationV01) AddRequestForAction 

func (f *ForwardIntentToPayNotificationV01) AddRequestForAction() *iso20022.PendingActivity2

func (*ForwardIntentToPayNotificationV01) AddSellerBank 

func (f *ForwardIntentToPayNotificationV01) AddSellerBank() *iso20022.BICIdentification1

func (*ForwardIntentToPayNotificationV01) AddTransactionIdentification 

func (f *ForwardIntentToPayNotificationV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*ForwardIntentToPayNotificationV01) AddTransactionStatus 

func (f *ForwardIntentToPayNotificationV01) AddTransactionStatus() *iso20022.TransactionStatus4

func (*ForwardIntentToPayNotificationV01) AddUserTransactionReference 

func (f *ForwardIntentToPayNotificationV01) AddUserTransactionReference() *iso20022.DocumentIdentification5

type ForwardIntentToPayNotificationV02 

type ForwardIntentToPayNotificationV02 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institutions involved in this transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Provides the details of the intention to pay.
	IntentToPay *iso20022.IntentToPay2 `xml:"InttToPay"`

	// Next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The ForwardIntentToPayNotification message is forwarded by the matching application from one primary bank to the other primary bank in order to provide details about a future payment. This message contains details about an intention to pay a certain amount, on a certain date, in relation to one or several transactions known to the matching application. Usage The ForwardIntentToPayNotification message is a copy of the IntentToPayNotification message received by the matching application and forwarded to the other primary bank for information. No response is expected.

func (*ForwardIntentToPayNotificationV02) AddBuyerBank 

func (f *ForwardIntentToPayNotificationV02) AddBuyerBank() *iso20022.BICIdentification1

func (*ForwardIntentToPayNotificationV02) AddEstablishedBaselineIdentification 

func (f *ForwardIntentToPayNotificationV02) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*ForwardIntentToPayNotificationV02) AddIntentToPay 

func (f *ForwardIntentToPayNotificationV02) AddIntentToPay() *iso20022.IntentToPay2

func (*ForwardIntentToPayNotificationV02) AddNotificationIdentification 

func (f *ForwardIntentToPayNotificationV02) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*ForwardIntentToPayNotificationV02) AddRequestForAction 

func (f *ForwardIntentToPayNotificationV02) AddRequestForAction() *iso20022.PendingActivity2

func (*ForwardIntentToPayNotificationV02) AddSellerBank 

func (f *ForwardIntentToPayNotificationV02) AddSellerBank() *iso20022.BICIdentification1

func (*ForwardIntentToPayNotificationV02) AddTransactionIdentification 

func (f *ForwardIntentToPayNotificationV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*ForwardIntentToPayNotificationV02) AddTransactionStatus 

func (f *ForwardIntentToPayNotificationV02) AddTransactionStatus() *iso20022.TransactionStatus4

func (*ForwardIntentToPayNotificationV02) AddUserTransactionReference 

func (f *ForwardIntentToPayNotificationV02) AddUserTransactionReference() *iso20022.DocumentIdentification5

type FullPushThroughReportV03 

type FullPushThroughReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institution which submitted the baseline.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Specifies the type of report.
	ReportPurpose *iso20022.ReportType1 `xml:"RptPurp"`

	// Specifies the commercial details of the underlying transaction.
	PushedThroughBaseline *iso20022.Baseline3 `xml:"PushdThrghBaseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The FullPushThroughReport message is sent by the matching application to a party involved in a transaction. This message is used to pass on information that the matching application has received from the submitter. The forwarded information can originate from an InitialBaselineSubmission or BaselineReSubmission or BaselineAmendmentRequest message. Usage The FullPushThroughReport message can be sent by the matching application to a party to convey - the details of an InitialBaselineSubmission message that it has obtained,or - the details of a BaselineResubmission message that it has obtained,or - the details of a BaselineAmendmentRequest message that it has obtained.

func (*FullPushThroughReportV03) AddBuyerBankContactPerson 

func (f *FullPushThroughReportV03) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV03) AddBuyerContactPerson 

func (f *FullPushThroughReportV03) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV03) AddEstablishedBaselineIdentification 

func (f *FullPushThroughReportV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*FullPushThroughReportV03) AddOtherBankContactPerson 

func (f *FullPushThroughReportV03) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*FullPushThroughReportV03) AddPushedThroughBaseline 

func (f *FullPushThroughReportV03) AddPushedThroughBaseline() *iso20022.Baseline3

func (*FullPushThroughReportV03) AddReportIdentification 

func (f *FullPushThroughReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*FullPushThroughReportV03) AddReportPurpose 

func (f *FullPushThroughReportV03) AddReportPurpose() *iso20022.ReportType1

func (*FullPushThroughReportV03) AddRequestForAction 

func (f *FullPushThroughReportV03) AddRequestForAction() *iso20022.PendingActivity2

func (*FullPushThroughReportV03) AddSellerBankContactPerson 

func (f *FullPushThroughReportV03) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV03) AddSellerContactPerson 

func (f *FullPushThroughReportV03) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV03) AddTransactionIdentification 

func (f *FullPushThroughReportV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*FullPushThroughReportV03) AddTransactionStatus 

func (f *FullPushThroughReportV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*FullPushThroughReportV03) AddUserTransactionReference 

func (f *FullPushThroughReportV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type FullPushThroughReportV04 

type FullPushThroughReportV04 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institution which submitted the baseline.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Specifies the type of report.
	ReportPurpose *iso20022.ReportType1 `xml:"RptPurp"`

	// Specifies the commercial details of the underlying transaction.
	PushedThroughBaseline *iso20022.Baseline4 `xml:"PushdThrghBaseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The FullPushThroughReport message is sent by the matching application to a party involved in a transaction. This message is used to pass on information that the matching application has received from the submitter. The forwarded information can originate from an InitialBaselineSubmission or BaselineReSubmission or BaselineAmendmentRequest message. Usage The FullPushThroughReport message can be sent by the matching application to a party to convey - the details of an InitialBaselineSubmission message that it has obtained,or - the details of a BaselineResubmission message that it has obtained,or - the details of a BaselineAmendmentRequest message that it has obtained.

func (*FullPushThroughReportV04) AddBuyerBankContactPerson 

func (f *FullPushThroughReportV04) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV04) AddBuyerContactPerson 

func (f *FullPushThroughReportV04) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV04) AddEstablishedBaselineIdentification 

func (f *FullPushThroughReportV04) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*FullPushThroughReportV04) AddOtherBankContactPerson 

func (f *FullPushThroughReportV04) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*FullPushThroughReportV04) AddPushedThroughBaseline 

func (f *FullPushThroughReportV04) AddPushedThroughBaseline() *iso20022.Baseline4

func (*FullPushThroughReportV04) AddReportIdentification 

func (f *FullPushThroughReportV04) AddReportIdentification() *iso20022.MessageIdentification1

func (*FullPushThroughReportV04) AddReportPurpose 

func (f *FullPushThroughReportV04) AddReportPurpose() *iso20022.ReportType1

func (*FullPushThroughReportV04) AddRequestForAction 

func (f *FullPushThroughReportV04) AddRequestForAction() *iso20022.PendingActivity2

func (*FullPushThroughReportV04) AddSellerBankContactPerson 

func (f *FullPushThroughReportV04) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV04) AddSellerContactPerson 

func (f *FullPushThroughReportV04) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV04) AddTransactionIdentification 

func (f *FullPushThroughReportV04) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*FullPushThroughReportV04) AddTransactionStatus 

func (f *FullPushThroughReportV04) AddTransactionStatus() *iso20022.TransactionStatus4

func (*FullPushThroughReportV04) AddUserTransactionReference 

func (f *FullPushThroughReportV04) AddUserTransactionReference() *iso20022.DocumentIdentification5

type FullPushThroughReportV05 

type FullPushThroughReportV05 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institution which submitted the baseline.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Specifies the type of report.
	ReportPurpose *iso20022.ReportType1 `xml:"RptPurp"`

	// Specifies the commercial details of the underlying transaction.
	PushedThroughBaseline *iso20022.Baseline5 `xml:"PushdThrghBaseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn,omitempty"`

	// Person to be contacted in another bank than the seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The FullPushThroughReport message is sent by the matching application to a party involved in a transaction. This message is used to pass on information that the matching application has received from the submitter. The forwarded information can originate from an InitialBaselineSubmission or BaselineReSubmission or BaselineAmendmentRequest message. Usage The FullPushThroughReport message can be sent by the matching application to a party to convey - the details of an InitialBaselineSubmission message that it has obtained,or - the details of a BaselineResubmission message that it has obtained,or - the details of a BaselineAmendmentRequest message that it has obtained.

func (*FullPushThroughReportV05) AddBuyerBankContactPerson 

func (f *FullPushThroughReportV05) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV05) AddBuyerContactPerson 

func (f *FullPushThroughReportV05) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV05) AddEstablishedBaselineIdentification 

func (f *FullPushThroughReportV05) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*FullPushThroughReportV05) AddOtherBankContactPerson 

func (f *FullPushThroughReportV05) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*FullPushThroughReportV05) AddPushedThroughBaseline 

func (f *FullPushThroughReportV05) AddPushedThroughBaseline() *iso20022.Baseline5

func (*FullPushThroughReportV05) AddReportIdentification 

func (f *FullPushThroughReportV05) AddReportIdentification() *iso20022.MessageIdentification1

func (*FullPushThroughReportV05) AddReportPurpose 

func (f *FullPushThroughReportV05) AddReportPurpose() *iso20022.ReportType1

func (*FullPushThroughReportV05) AddRequestForAction 

func (f *FullPushThroughReportV05) AddRequestForAction() *iso20022.PendingActivity2

func (*FullPushThroughReportV05) AddSellerBankContactPerson 

func (f *FullPushThroughReportV05) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV05) AddSellerContactPerson 

func (f *FullPushThroughReportV05) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*FullPushThroughReportV05) AddTransactionIdentification 

func (f *FullPushThroughReportV05) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*FullPushThroughReportV05) AddTransactionStatus 

func (f *FullPushThroughReportV05) AddTransactionStatus() *iso20022.TransactionStatus4

func (*FullPushThroughReportV05) AddUserTransactionReference 

func (f *FullPushThroughReportV05) AddUserTransactionReference() *iso20022.DocumentIdentification5

type InitialBaselineSubmissionV03 

type InitialBaselineSubmissionV03 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef"`

	// Specifies the instruction requested by the submitter by means of a code.
	Instruction *iso20022.InstructionType1 `xml:"Instr"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline3 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the buyer's bank.
	BuyerBankContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrBkCtctPrsn"`

	// Person to be contacted in the seller's bank.
	SellerBankContactPerson []*iso20022.ContactIdentification1 `xml:"SellrBkCtctPrsn"`

	// Person to be contacted in another bank than seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The InitialBaselineSubmission message is sent by the initiator of a transaction to the matching application. This message is used to initiate a transaction. Usage The InitialBaselineSubmission message can be sent by a party to register a transaction in the matching application. The message can be submitted with either lodge or push-through instruction. When the push-through instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message, stores the submitted information and informs the counterparty about the registration of the transaction by sending a FullPushThroughReport message. With the BaselineReSubmission message the counterparty responds with matching baseline information in order to establish the transaction (baseline). When the lodge instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message and stores the submitted information. No matching of the submitted baseline data with other baseline information will take place. For example the submission of an InitialBaselineSubmission message containing a lodge instruction establishes the transaction (baseline) in the matching application. The InitialBaselineSubmission message consists of data which relates to the purchasing agreement covered by the transaction, for example line item details, shipping details.

func (*InitialBaselineSubmissionV03) AddBaseline 

func (i *InitialBaselineSubmissionV03) AddBaseline() *iso20022.Baseline3

func (*InitialBaselineSubmissionV03) AddBuyerBankContactPerson 

func (i *InitialBaselineSubmissionV03) AddBuyerBankContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV03) AddBuyerContactPerson 

func (i *InitialBaselineSubmissionV03) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV03) AddInstruction 

func (i *InitialBaselineSubmissionV03) AddInstruction() *iso20022.InstructionType1

func (*InitialBaselineSubmissionV03) AddOtherBankContactPerson 

func (i *InitialBaselineSubmissionV03) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*InitialBaselineSubmissionV03) AddSellerBankContactPerson 

func (i *InitialBaselineSubmissionV03) AddSellerBankContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV03) AddSellerContactPerson 

func (i *InitialBaselineSubmissionV03) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV03) AddSubmissionIdentification 

func (i *InitialBaselineSubmissionV03) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*InitialBaselineSubmissionV03) AddSubmitterTransactionReference 

func (i *InitialBaselineSubmissionV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

type InitialBaselineSubmissionV04 

type InitialBaselineSubmissionV04 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef"`

	// Specifies the instruction requested by the submitter by means of a code.
	Instruction *iso20022.InstructionType1 `xml:"Instr"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline4 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank or buyer's bank.
	BankContactPerson *iso20022.BankContactPerson1Choice `xml:"BkCtctPrsn"`

	// Person to be contacted in another bank than seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The InitialBaselineSubmission message is sent by the initiator of a transaction to the matching application. This message is used to initiate a transaction. Usage The InitialBaselineSubmission message can be sent by a party to register a transaction in the matching application. The message can be submitted with either lodge or push-through instruction. When the push-through instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message, stores the submitted information and informs the counterparty about the registration of the transaction by sending a FullPushThroughReport message. With the BaselineReSubmission message the counterparty responds with matching baseline information in order to establish the transaction (baseline). When the lodge instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message and stores the submitted information. No matching of the submitted baseline data with other baseline information will take place. For example the submission of an InitialBaselineSubmission message containing a lodge instruction establishes the transaction (baseline) in the matching application. The InitialBaselineSubmission message consists of data which relates to the purchasing agreement covered by the transaction, for example line item details, shipping details.

func (*InitialBaselineSubmissionV04) AddBankContactPerson 

func (i *InitialBaselineSubmissionV04) AddBankContactPerson() *iso20022.BankContactPerson1Choice

func (*InitialBaselineSubmissionV04) AddBaseline 

func (i *InitialBaselineSubmissionV04) AddBaseline() *iso20022.Baseline4

func (*InitialBaselineSubmissionV04) AddBuyerContactPerson 

func (i *InitialBaselineSubmissionV04) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV04) AddInstruction 

func (i *InitialBaselineSubmissionV04) AddInstruction() *iso20022.InstructionType1

func (*InitialBaselineSubmissionV04) AddOtherBankContactPerson 

func (i *InitialBaselineSubmissionV04) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*InitialBaselineSubmissionV04) AddSellerContactPerson 

func (i *InitialBaselineSubmissionV04) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV04) AddSubmissionIdentification 

func (i *InitialBaselineSubmissionV04) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*InitialBaselineSubmissionV04) AddSubmitterTransactionReference 

func (i *InitialBaselineSubmissionV04) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

type InitialBaselineSubmissionV05 

type InitialBaselineSubmissionV05 struct {

	// Identifies the submitted information
	SubmissionIdentification *iso20022.MessageIdentification1 `xml:"SubmissnId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef"`

	// Specifies the instruction requested by the submitter by means of a code.
	Instruction *iso20022.InstructionType1 `xml:"Instr"`

	// Specifies the commercial details of the underlying transaction.
	Baseline *iso20022.Baseline5 `xml:"Baseln"`

	// Person to be contacted in the organisation of the buyer.
	BuyerContactPerson []*iso20022.ContactIdentification1 `xml:"BuyrCtctPrsn,omitempty"`

	// Person to be contacted in the organisation of the seller.
	SellerContactPerson []*iso20022.ContactIdentification1 `xml:"SellrCtctPrsn,omitempty"`

	// Person to be contacted in the seller's bank or buyer's bank.
	BankContactPerson *iso20022.BankContactPerson1Choice `xml:"BkCtctPrsn"`

	// Person to be contacted in another bank than seller or buyer's bank.
	OtherBankContactPerson []*iso20022.ContactIdentification3 `xml:"OthrBkCtctPrsn,omitempty"`
}

Scope The InitialBaselineSubmission message is sent by the initiator of a transaction to the matching application. This message is used to initiate a transaction. Usage The InitialBaselineSubmission message can be sent by a party to register a transaction in the matching application. The message can be submitted with either lodge or push-through instruction. When the push-through instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message, stores the submitted information and informs the counterparty about the registration of the transaction by sending a FullPushThroughReport message. With the BaselineReSubmission message the counterparty responds with matching baseline information in order to establish the transaction (baseline). When the lodge instruction is present, the matching application acknowledges the receipt of the message to the sender by sending an Acknowledgement message and stores the submitted information. No matching of the submitted baseline data with other baseline information will take place. For example the submission of an InitialBaselineSubmission message containing a lodge instruction establishes the transaction (baseline) in the matching application. The InitialBaselineSubmission message consists of data which relates to the purchasing agreement covered by the transaction, for example line item details, shipping details.

func (*InitialBaselineSubmissionV05) AddBankContactPerson 

func (i *InitialBaselineSubmissionV05) AddBankContactPerson() *iso20022.BankContactPerson1Choice

func (*InitialBaselineSubmissionV05) AddBaseline 

func (i *InitialBaselineSubmissionV05) AddBaseline() *iso20022.Baseline5

func (*InitialBaselineSubmissionV05) AddBuyerContactPerson 

func (i *InitialBaselineSubmissionV05) AddBuyerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV05) AddInstruction 

func (i *InitialBaselineSubmissionV05) AddInstruction() *iso20022.InstructionType1

func (*InitialBaselineSubmissionV05) AddOtherBankContactPerson 

func (i *InitialBaselineSubmissionV05) AddOtherBankContactPerson() *iso20022.ContactIdentification3

func (*InitialBaselineSubmissionV05) AddSellerContactPerson 

func (i *InitialBaselineSubmissionV05) AddSellerContactPerson() *iso20022.ContactIdentification1

func (*InitialBaselineSubmissionV05) AddSubmissionIdentification 

func (i *InitialBaselineSubmissionV05) AddSubmissionIdentification() *iso20022.MessageIdentification1

func (*InitialBaselineSubmissionV05) AddSubmitterTransactionReference 

func (i *InitialBaselineSubmissionV05) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

type IntentToPayNotificationV01 

type IntentToPayNotificationV01 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	//
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	//
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Provides the details of the intention to pay.
	IntentToPay *iso20022.IntentToPay1 `xml:"InttToPay"`
}

Scope The IntentToPayNotification message is sent by a party to the matching application in order to provide details about a future payment. This message contains details about an intention to pay a certain amount, on a certain date, in relation to one or several transactions known to the matching application. Usage The IntentToPayNotification message can be sent by a party to the transaction at any time as long as the transaction is established and not yet closed. The message is unsolicited, that is, it is not sent in response to another message.

func (*IntentToPayNotificationV01) AddBuyerBank 

func (i *IntentToPayNotificationV01) AddBuyerBank() *iso20022.BICIdentification1

func (*IntentToPayNotificationV01) AddIntentToPay 

func (i *IntentToPayNotificationV01) AddIntentToPay() *iso20022.IntentToPay1

func (*IntentToPayNotificationV01) AddNotificationIdentification 

func (i *IntentToPayNotificationV01) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*IntentToPayNotificationV01) AddSellerBank 

func (i *IntentToPayNotificationV01) AddSellerBank() *iso20022.BICIdentification1

func (*IntentToPayNotificationV01) AddSubmitterTransactionReference 

func (i *IntentToPayNotificationV01) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*IntentToPayNotificationV01) AddTransactionIdentification 

func (i *IntentToPayNotificationV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type IntentToPayNotificationV02 

type IntentToPayNotificationV02 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// The financial institution of the buyer, uniquely identified by its BIC.
	//
	BuyerBank *iso20022.BICIdentification1 `xml:"BuyrBk"`

	// The financial institution of the seller, uniquely identified by its BIC.
	//
	SellerBank *iso20022.BICIdentification1 `xml:"SellrBk"`

	// Provides the details of the intention to pay.
	IntentToPay *iso20022.IntentToPay2 `xml:"InttToPay"`
}

Scope The IntentToPayNotification message is sent by a party to the matching application in order to provide details about a future payment. This message contains details about an intention to pay a certain amount, on a certain date, in relation to one or several transactions known to the matching application. Usage The IntentToPayNotification message can be sent by a party to the transaction at any time as long as the transaction is established and not yet closed. The message is unsolicited, that is, it is not sent in response to another message.

func (*IntentToPayNotificationV02) AddBuyerBank 

func (i *IntentToPayNotificationV02) AddBuyerBank() *iso20022.BICIdentification1

func (*IntentToPayNotificationV02) AddIntentToPay 

func (i *IntentToPayNotificationV02) AddIntentToPay() *iso20022.IntentToPay2

func (*IntentToPayNotificationV02) AddNotificationIdentification 

func (i *IntentToPayNotificationV02) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*IntentToPayNotificationV02) AddSellerBank 

func (i *IntentToPayNotificationV02) AddSellerBank() *iso20022.BICIdentification1

func (*IntentToPayNotificationV02) AddSubmitterTransactionReference 

func (i *IntentToPayNotificationV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*IntentToPayNotificationV02) AddTransactionIdentification 

func (i *IntentToPayNotificationV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type IntentToPayReportV01 

type IntentToPayReportV01 struct {

	// Identifies the report message.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reports on the intention to pay per purchase order.
	ReportedItems []*iso20022.ReportLine1 `xml:"RptdItms,omitempty"`
}

Scope The IntentToPayReport message is sent by the matching application to the two primary banks after receiving an IntentToPayNotification message. This message is a report per transaction that were referenced in the IntentToPayNotice message. For each transaction, the matching application has accumulated the amounts present in all previous IntentToPayNotice messages and reports the total. Usage The IntentToPayReport message is a report that is automatically generated by the matching application following an IntentToPayNotice message. No response is expected.

func (*IntentToPayReportV01) AddReportIdentification 

func (i *IntentToPayReportV01) AddReportIdentification() *iso20022.MessageIdentification1

func (*IntentToPayReportV01) AddReportedItems 

func (i *IntentToPayReportV01) AddReportedItems() *iso20022.ReportLine1

type InvoicePaymentReconciliationAdviceV01 

type InvoicePaymentReconciliationAdviceV01 struct {

	// Set of characteristics that unambiguously identify the letter, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of payment reconciliation information.
	ReconciliationList []*iso20022.ReconciliationList1 `xml:"RcncltnList"`

	// Number of reconciliation lists as control value.
	ReconciliationCount *iso20022.Max15NumericText `xml:"RcncltnCnt,omitempty"`

	// Total number of individual items in all lists.
	ItemCount *iso20022.Max15NumericText `xml:"ItmCnt,omitempty"`

	// Total of all individual amounts included in all lists, irrespective of currencies or direction.
	ControlSum *iso20022.DecimalNumber `xml:"CtrlSum,omitempty"`

	// Referenced or related business message.
	AttachedMessage []*iso20022.EncapsulatedBusinessMessage1 `xml:"AttchdMsg,omitempty"`
}

The message InvoicePaymentReconciliationAdvice is sent by a payer to a payee to indicate attribution of payments to instalment of payment obligations in order to simplify the account netting or clearing when a lot of invoices are paid with a unique payment (for instance an SCT or an SDD). The message contains references to payment instructions, may reference other messages and may include referenced data. The message can carry digital signatures if required by context.

func (*InvoicePaymentReconciliationAdviceV01) AddAttachedMessage 

func (i *InvoicePaymentReconciliationAdviceV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (*InvoicePaymentReconciliationAdviceV01) AddHeader 

func (i *InvoicePaymentReconciliationAdviceV01) AddHeader() *iso20022.BusinessLetter1

func (*InvoicePaymentReconciliationAdviceV01) AddReconciliationList 

func (i *InvoicePaymentReconciliationAdviceV01) AddReconciliationList() *iso20022.ReconciliationList1

func (*InvoicePaymentReconciliationAdviceV01) SetControlSum 

func (i *InvoicePaymentReconciliationAdviceV01) SetControlSum(value string)

func (*InvoicePaymentReconciliationAdviceV01) SetItemCount 

func (i *InvoicePaymentReconciliationAdviceV01) SetItemCount(value string)

func (*InvoicePaymentReconciliationAdviceV01) SetReconciliationCount 

func (i *InvoicePaymentReconciliationAdviceV01) SetReconciliationCount(value string)

type InvoicePaymentReconciliationStatusV01 

type InvoicePaymentReconciliationStatusV01 struct {

	// Specifies a set of characteristics that unambiguously identify the status, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of payment reconciliation information.
	ReconciliationList []*iso20022.ReconciliationList1 `xml:"RcncltnList"`

	// Specifies the number of reconciliation lists.
	ReconciliationCount *iso20022.Max15NumericText `xml:"RcncltnCnt,omitempty"`

	// Total number of individual items in all lists.
	ItemCount *iso20022.Max15NumericText `xml:"ItmCnt,omitempty"`

	// Total of all individual amounts included in all lists, irrespective of currencies or direction.
	ControlSum *iso20022.DecimalNumber `xml:"CtrlSum,omitempty"`

	// Referenced or related business message.
	AttachedMessage []*iso20022.EncapsulatedBusinessMessage1 `xml:"AttchdMsg,omitempty"`
}

The message InvoicePaymentReconciliationStatus is sent from a payee to a payer to acknowledge attribution of payments. A payee that has received payment reconciliation information uses this message to confirm or to question common understanding of payments and instalments. The payee may include references to the corresponding items of an InvoicePaymentReconciliationAdvice message or to other messages and may include the referenced data. The message can carry digital signatures if required by context.

func (*InvoicePaymentReconciliationStatusV01) AddAttachedMessage 

func (i *InvoicePaymentReconciliationStatusV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (*InvoicePaymentReconciliationStatusV01) AddHeader 

func (i *InvoicePaymentReconciliationStatusV01) AddHeader() *iso20022.BusinessLetter1

func (*InvoicePaymentReconciliationStatusV01) AddReconciliationList 

func (i *InvoicePaymentReconciliationStatusV01) AddReconciliationList() *iso20022.ReconciliationList1

func (*InvoicePaymentReconciliationStatusV01) SetControlSum 

func (i *InvoicePaymentReconciliationStatusV01) SetControlSum(value string)

func (*InvoicePaymentReconciliationStatusV01) SetItemCount 

func (i *InvoicePaymentReconciliationStatusV01) SetItemCount(value string)

func (*InvoicePaymentReconciliationStatusV01) SetReconciliationCount 

func (i *InvoicePaymentReconciliationStatusV01) SetReconciliationCount(value string)

type MisMatchAcceptanceNotificationV03 

type MisMatchAcceptanceNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the report that contained the difference.
	DataSetMatchReportReference *iso20022.MessageIdentification1 `xml:"DataSetMtchRptRef"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The MisMatchAcceptanceNotification message is sent by the matching application to the parties involved in the transaction. This message is used to notify the acceptance of mis-matched data sets. Usage The MisMatchAcceptanceNotification message can be sent by the matching application to pass on information about the acceptance of mis-matched data sets that it has obtained through the receipt of an MisMatchAcceptance message. In order to pass on information about the rejection of mis-matched data sets the matching application sends a MisMatchRejectionNotification message.

func (*MisMatchAcceptanceNotificationV03) AddDataSetMatchReportReference 

func (m *MisMatchAcceptanceNotificationV03) AddDataSetMatchReportReference() *iso20022.MessageIdentification1

func (*MisMatchAcceptanceNotificationV03) AddEstablishedBaselineIdentification 

func (m *MisMatchAcceptanceNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*MisMatchAcceptanceNotificationV03) AddNotificationIdentification 

func (m *MisMatchAcceptanceNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*MisMatchAcceptanceNotificationV03) AddRequestForAction 

func (m *MisMatchAcceptanceNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*MisMatchAcceptanceNotificationV03) AddTransactionIdentification 

func (m *MisMatchAcceptanceNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*MisMatchAcceptanceNotificationV03) AddTransactionStatus 

func (m *MisMatchAcceptanceNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*MisMatchAcceptanceNotificationV03) AddUserTransactionReference 

func (m *MisMatchAcceptanceNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type MisMatchAcceptanceV02 

type MisMatchAcceptanceV02 struct {

	// Identifies the acceptance message.
	AcceptanceIdentification *iso20022.MessageIdentification1 `xml:"AccptncId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Reference to the identification of the report that contained the difference.
	DataSetMatchReportReference *iso20022.MessageIdentification1 `xml:"DataSetMtchRptRef"`
}

Scope The MisMatchAcceptance message is sent by the party requested to accept or reject data set mis-matches to the matching application. This message is used to accept mis-matches between data sets and the related baseline. Usage The MisMatchAcceptance message can be sent by the party requested to accept or reject data set mis-matches to inform that it accepts the data sets. The message can be sent in response to a DataSetMatchReport message conveying mis-matches. The information about the acceptance of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchAcceptanceNotification message. The rejection of mis-matched data sets can be achieved by sending a MisMatchRejection message.

func (*MisMatchAcceptanceV02) AddAcceptanceIdentification 

func (m *MisMatchAcceptanceV02) AddAcceptanceIdentification() *iso20022.MessageIdentification1

func (*MisMatchAcceptanceV02) AddDataSetMatchReportReference 

func (m *MisMatchAcceptanceV02) AddDataSetMatchReportReference() *iso20022.MessageIdentification1

func (*MisMatchAcceptanceV02) AddSubmitterTransactionReference 

func (m *MisMatchAcceptanceV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*MisMatchAcceptanceV02) AddTransactionIdentification 

func (m *MisMatchAcceptanceV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type MisMatchRejectionNotificationV03 

type MisMatchRejectionNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reference to the identification of the report that contained the difference.
	DataSetMatchReportReference *iso20022.MessageIdentification1 `xml:"DataSetMtchRptRef"`

	// Specifies the reaons for rejecting the mismatch.
	RejectionReason *iso20022.RejectionReason1Choice `xml:"RjctnRsn"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The MisMatchRejectionNotification message is sent by the matching application to the parties involved in the transaction. This message is used to notify the rejection of mis-matched data sets. Usage The MisMatchRejectionNotification message can be sent by the matching application to pass on the information about the rejection of mis-matched data sets that it has obtained through the receipt of an MisMatchRejection message. In order to pass on information about the acceptance of mis-matched data sets the matching application sends an MisMatchAcceptanceNotification message.

func (*MisMatchRejectionNotificationV03) AddDataSetMatchReportReference 

func (m *MisMatchRejectionNotificationV03) AddDataSetMatchReportReference() *iso20022.MessageIdentification1

func (*MisMatchRejectionNotificationV03) AddEstablishedBaselineIdentification 

func (m *MisMatchRejectionNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*MisMatchRejectionNotificationV03) AddNotificationIdentification 

func (m *MisMatchRejectionNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*MisMatchRejectionNotificationV03) AddRejectionReason 

func (m *MisMatchRejectionNotificationV03) AddRejectionReason() *iso20022.RejectionReason1Choice

func (*MisMatchRejectionNotificationV03) AddRequestForAction 

func (m *MisMatchRejectionNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*MisMatchRejectionNotificationV03) AddTransactionIdentification 

func (m *MisMatchRejectionNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*MisMatchRejectionNotificationV03) AddTransactionStatus 

func (m *MisMatchRejectionNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*MisMatchRejectionNotificationV03) AddUserTransactionReference 

func (m *MisMatchRejectionNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type MisMatchRejectionV02 

type MisMatchRejectionV02 struct {

	// Identifies the rejection message.
	RejectionIdentification *iso20022.MessageIdentification1 `xml:"RjctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Reference to the identification of the report that contained the difference.
	DataSetMatchReportReference *iso20022.MessageIdentification1 `xml:"DataSetMtchRptRef"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.RejectionReason1Choice `xml:"RjctnRsn"`
}

Scope The MisMatchRejection message is sent by the party requested to accept or reject data set mis-matches to the matching application. This message is used to reject mis-matches between data sets and the related baseline. Usage The MisMatchRejection message can be sent by the party requested to accept or reject data set mis-match to inform that it rejects the data set(s). The message can be sent in response to a DataSetMatchReport message conveying mis-matches. The information about the rejection of the mis-matched data sets will be forwarded by the matching application to the submitter of the data sets by a MisMatchRejectionNotification message. The acceptance of mis-matched data sets can be achieved by sending a MisMatchAcceptance message.

func (*MisMatchRejectionV02) AddDataSetMatchReportReference 

func (m *MisMatchRejectionV02) AddDataSetMatchReportReference() *iso20022.MessageIdentification1

func (*MisMatchRejectionV02) AddRejectionIdentification 

func (m *MisMatchRejectionV02) AddRejectionIdentification() *iso20022.MessageIdentification1

func (*MisMatchRejectionV02) AddRejectionReason 

func (m *MisMatchRejectionV02) AddRejectionReason() *iso20022.RejectionReason1Choice

func (*MisMatchRejectionV02) AddSubmitterTransactionReference 

func (m *MisMatchRejectionV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*MisMatchRejectionV02) AddTransactionIdentification 

func (m *MisMatchRejectionV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type PartyEventAdviceV01 

type PartyEventAdviceV01 struct {

	// Set of characteristics that unambiguously identify the event, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// Description of the event.
	EventNotice []*iso20022.EventDescription1 `xml:"EvtNtce"`

	// Number of events as control value.
	EventCount *iso20022.Max15NumericText `xml:"EvtCnt,omitempty"`

	// Referenced or related business message.
	AttachedMessage []*iso20022.EncapsulatedBusinessMessage1 `xml:"AttchdMsg,omitempty"`
}

The PartyEventAdvice message can be sent by any party to any other party. It is used for business letters containing information for which treatment is not formally defined in order to keep partners informed and to maintain business traces, for example confirmations of information exchanged out-of band such as announcing a postal letter, confirming a telephone call or the exchange of contractual information. It can also be sent to verify the technical interoperability of the communicating IT-systems. The message can reference other message and include data from referenced messages. The message can report several events. The message can carry digital signatures if required by context.

func (*PartyEventAdviceV01) AddAttachedMessage 

func (p *PartyEventAdviceV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (*PartyEventAdviceV01) AddEventNotice 

func (p *PartyEventAdviceV01) AddEventNotice() *iso20022.EventDescription1

func (*PartyEventAdviceV01) AddHeader 

func (p *PartyEventAdviceV01) AddHeader() *iso20022.BusinessLetter1

func (*PartyEventAdviceV01) SetEventCount 

func (p *PartyEventAdviceV01) SetEventCount(value string)

type RoleAndBaselineAcceptanceNotificationV01 

type RoleAndBaselineAcceptanceNotificationV01 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that has accepted.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The RoleAndBaselineAcceptanceNotification message is sent by the matching application to the primary banks to inform about role and baseline acceptance by a secondary bank. Usage The RoleAndBaselineAcceptanceNotification message is used to inform that a secondary bank has accepted the role and baseline. No response is expected.

func (*RoleAndBaselineAcceptanceNotificationV01) AddEstablishedBaselineIdentification 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*RoleAndBaselineAcceptanceNotificationV01) AddInitiator 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddInitiator() *iso20022.BICIdentification1

func (*RoleAndBaselineAcceptanceNotificationV01) AddNotificationIdentification 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*RoleAndBaselineAcceptanceNotificationV01) AddRequestForAction 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddRequestForAction() *iso20022.PendingActivity2

func (*RoleAndBaselineAcceptanceNotificationV01) AddTransactionIdentification 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*RoleAndBaselineAcceptanceNotificationV01) AddTransactionStatus 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddTransactionStatus() *iso20022.TransactionStatus4

func (*RoleAndBaselineAcceptanceNotificationV01) AddUserTransactionReference 

func (r *RoleAndBaselineAcceptanceNotificationV01) AddUserTransactionReference() *iso20022.DocumentIdentification5

type RoleAndBaselineAcceptanceV01 

type RoleAndBaselineAcceptanceV01 struct {

	// Identifies the acceptance message.
	AcceptanceIdentification *iso20022.MessageIdentification1 `xml:"AccptncId"`

	// Reference to the message that contained the baseline and is accepted.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`
}

Scope The RoleAndBaselineAcceptance message is sent by a secondary bank to the matching application if it accepts to join the transaction based on the baseline and the role that it is expected to play. Usage The RoleAndBaselineAcceptance message is sent in response to a message that is a direct request to join a transaction.

func (*RoleAndBaselineAcceptanceV01) AddAcceptanceIdentification 

func (r *RoleAndBaselineAcceptanceV01) AddAcceptanceIdentification() *iso20022.MessageIdentification1

func (*RoleAndBaselineAcceptanceV01) AddRelatedMessageReference 

func (r *RoleAndBaselineAcceptanceV01) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*RoleAndBaselineAcceptanceV01) AddTransactionIdentification 

func (r *RoleAndBaselineAcceptanceV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type RoleAndBaselineRejectionNotificationV01 

type RoleAndBaselineRejectionNotificationV01 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction that is not extended.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that has rejected.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn,omitempty"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The RoleAndBaselineRejectionNotification message is sent by the matching application to the primary banks to inform about role and baseline rejection by a secondary bank. Usage The RoleAndBaselineRejectionNotification message is used to inform that a secondary bank has rejected the role and baseline. No response is expected.

func (*RoleAndBaselineRejectionNotificationV01) AddEstablishedBaselineIdentification 

func (r *RoleAndBaselineRejectionNotificationV01) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*RoleAndBaselineRejectionNotificationV01) AddInitiator 

func (r *RoleAndBaselineRejectionNotificationV01) AddInitiator() *iso20022.BICIdentification1

func (*RoleAndBaselineRejectionNotificationV01) AddNotificationIdentification 

func (r *RoleAndBaselineRejectionNotificationV01) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*RoleAndBaselineRejectionNotificationV01) AddRejectionReason 

func (r *RoleAndBaselineRejectionNotificationV01) AddRejectionReason() *iso20022.Reason2

func (*RoleAndBaselineRejectionNotificationV01) AddRequestForAction 

func (r *RoleAndBaselineRejectionNotificationV01) AddRequestForAction() *iso20022.PendingActivity2

func (*RoleAndBaselineRejectionNotificationV01) AddTransactionIdentification 

func (r *RoleAndBaselineRejectionNotificationV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*RoleAndBaselineRejectionNotificationV01) AddTransactionStatus 

func (r *RoleAndBaselineRejectionNotificationV01) AddTransactionStatus() *iso20022.TransactionStatus4

func (*RoleAndBaselineRejectionNotificationV01) AddUserTransactionReference 

func (r *RoleAndBaselineRejectionNotificationV01) AddUserTransactionReference() *iso20022.DocumentIdentification5

type RoleAndBaselineRejectionV01 

type RoleAndBaselineRejectionV01 struct {

	// Identifies the rejection message.
	RejectionIdentification *iso20022.MessageIdentification1 `xml:"RjctnId"`

	// Reference to the message that contained the baseline and is rejected.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn,omitempty"`
}

Scope The RoleAndBaselineRejection message is sent by a secondary bank to the matching application if it rejects to join the transaction based on the baseline and the role that it is expected to play. Usage The RoleAndBaselineRejection message is sent in response to a message that is a direct request to join a transaction.

func (*RoleAndBaselineRejectionV01) AddRejectionIdentification 

func (r *RoleAndBaselineRejectionV01) AddRejectionIdentification() *iso20022.MessageIdentification1

func (*RoleAndBaselineRejectionV01) AddRejectionReason 

func (r *RoleAndBaselineRejectionV01) AddRejectionReason() *iso20022.Reason2

func (*RoleAndBaselineRejectionV01) AddRelatedMessageReference 

func (r *RoleAndBaselineRejectionV01) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*RoleAndBaselineRejectionV01) AddTransactionIdentification 

func (r *RoleAndBaselineRejectionV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type SpecialNotificationV01 

type SpecialNotificationV01 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for the financial institution that is the sender of the acknowledged message.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Party that has sent the special request.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Notification received by the matching application and forwarded to another party.
	Notification *iso20022.Notification1 `xml:"Ntfctn"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The SpecialNotification message is sent by the matching application to parties to the transaction, following the receipt of a SpecialRequest message. The SpecialRequest message is sent by a party to the transaction to the matching application if special circumstances are such that it cannot take part any longer to a specific transaction or that it cannot fulfill its role in the transaction. Usage The SpecialNotification message is sent to the parties to the transaction so that they can take appropriate action.

func (*SpecialNotificationV01) AddEstablishedBaselineIdentification 

func (s *SpecialNotificationV01) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*SpecialNotificationV01) AddInitiator 

func (s *SpecialNotificationV01) AddInitiator() *iso20022.BICIdentification1

func (*SpecialNotificationV01) AddNotification 

func (s *SpecialNotificationV01) AddNotification() *iso20022.Notification1

func (*SpecialNotificationV01) AddNotificationIdentification 

func (s *SpecialNotificationV01) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*SpecialNotificationV01) AddRequestForAction 

func (s *SpecialNotificationV01) AddRequestForAction() *iso20022.PendingActivity2

func (*SpecialNotificationV01) AddTransactionIdentification 

func (s *SpecialNotificationV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*SpecialNotificationV01) AddTransactionStatus 

func (s *SpecialNotificationV01) AddTransactionStatus() *iso20022.TransactionStatus4

func (*SpecialNotificationV01) AddUserTransactionReference 

func (s *SpecialNotificationV01) AddUserTransactionReference() *iso20022.DocumentIdentification5

type SpecialRequestV01 

type SpecialRequestV01 struct {

	// Identifies the acceptance message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the identification of the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Type and details of the notification.
	Notification *iso20022.Notification1 `xml:"Ntfctn"`
}

Scope The SpecialRequest message is sent by a party to the transaction to the matching application if special circumstances are such that it cannot take part any longer to a specific transaction or that it cannot fulfill its role in the transaction. Usage The SpecialRequest message can be sent at any time during the life time of a transaction as long as the transaction is established and not yet closed.

func (*SpecialRequestV01) AddNotification 

func (s *SpecialRequestV01) AddNotification() *iso20022.Notification1

func (*SpecialRequestV01) AddRequestIdentification 

func (s *SpecialRequestV01) AddRequestIdentification() *iso20022.MessageIdentification1

func (*SpecialRequestV01) AddSubmitterTransactionReference 

func (s *SpecialRequestV01) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*SpecialRequestV01) AddTransactionIdentification 

func (s *SpecialRequestV01) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusChangeNotificationV03 

type StatusChangeNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusChangeNotification message is sent by the matching application to the parties involved in the change of the status of a transaction. This message is used to inform about the change of a status. Usage The StatusChangeNotification message can be sent by the matching application - to the submitter of the request to change the status of a transaction to pass on the information about the acceptance of the request that it has obtained through the receipt of an StatusChangeRequestAcceptance message. - to the accepter of a request to change the status of a transaction inform about the actual status of the transaction in response to a StatusChangeRequestAcceptance message. - to either party involved in the establishment of a transaction to inform about the change of the status of the transaction to the status close. This can be done when the limit of possible attempts to establish the transaction has been reached or when unilaterally requested by one of the parties involved in the not yet established transaction. - to either party involved in a transaction to inform about the change of the status of the transaction as announced in a TimeOutNotification message sent by the matching application prior to the StatusChangeNotification message.

func (*StatusChangeNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusChangeNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusChangeNotificationV03) AddNotificationIdentification 

func (s *StatusChangeNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusChangeNotificationV03) AddRequestForAction 

func (s *StatusChangeNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusChangeNotificationV03) AddTransactionIdentification 

func (s *StatusChangeNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusChangeNotificationV03) AddTransactionStatus 

func (s *StatusChangeNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*StatusChangeNotificationV03) AddUserTransactionReference 

func (s *StatusChangeNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusChangeRequestAcceptanceV02 

type StatusChangeRequestAcceptanceV02 struct {

	// Identifies the acceptance message.
	AcceptanceIdentification *iso20022.MessageIdentification1 `xml:"AccptncId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the status accepted.
	AcceptedStatus *iso20022.TransactionStatus3 `xml:"AccptdSts"`
}

Scope The StatusChangeRequestAcceptance message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application. This message is used to inform about the acceptance of a request to change the status of a transaction. Usage The StatusChangeRequestAcceptance message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it accepts the request. The message can be sent in response to a StatusChangeRequestNotification message. The rejection of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestRejection message.

func (*StatusChangeRequestAcceptanceV02) AddAcceptanceIdentification 

func (s *StatusChangeRequestAcceptanceV02) AddAcceptanceIdentification() *iso20022.MessageIdentification1

func (*StatusChangeRequestAcceptanceV02) AddAcceptedStatus 

func (s *StatusChangeRequestAcceptanceV02) AddAcceptedStatus() *iso20022.TransactionStatus3

func (*StatusChangeRequestAcceptanceV02) AddSubmitterTransactionReference 

func (s *StatusChangeRequestAcceptanceV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusChangeRequestAcceptanceV02) AddTransactionIdentification 

func (s *StatusChangeRequestAcceptanceV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusChangeRequestNotificationV03 

type StatusChangeRequestNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Specifies the status that is proposed by the other party.
	ProposedStatusChange *iso20022.TransactionStatus3 `xml:"PropsdStsChng"`

	// Specifies the reason for the request to change status.
	RequestReason *iso20022.Reason2 `xml:"ReqRsn,omitempty"`

	// Party that has requested the status change.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusChangeRequestNotification message is sent by the matching application to the party requested to accept or reject the request of a change in the status of a transaction. This message is used to notify the request of a change in the status of a transaction. Usage The StatusChangeRequestNotification message can be sent by the matching application to pass on the information about the request of a change in the status of a transaction that it has obtained through the receipt of a StatusChangeRequest message.

func (*StatusChangeRequestNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusChangeRequestNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusChangeRequestNotificationV03) AddInitiator 

func (s *StatusChangeRequestNotificationV03) AddInitiator() *iso20022.BICIdentification1

func (*StatusChangeRequestNotificationV03) AddNotificationIdentification 

func (s *StatusChangeRequestNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusChangeRequestNotificationV03) AddProposedStatusChange 

func (s *StatusChangeRequestNotificationV03) AddProposedStatusChange() *iso20022.TransactionStatus3

func (*StatusChangeRequestNotificationV03) AddRequestForAction 

func (s *StatusChangeRequestNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusChangeRequestNotificationV03) AddRequestReason 

func (s *StatusChangeRequestNotificationV03) AddRequestReason() *iso20022.Reason2

func (*StatusChangeRequestNotificationV03) AddTransactionIdentification 

func (s *StatusChangeRequestNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusChangeRequestNotificationV03) AddTransactionStatus 

func (s *StatusChangeRequestNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*StatusChangeRequestNotificationV03) AddUserTransactionReference 

func (s *StatusChangeRequestNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusChangeRequestRejectionNotificationV03 

type StatusChangeRequestRejectionNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Specifies the status that was rejected by the other party.
	RejectedStatusChange *iso20022.TransactionStatus3 `xml:"RjctdStsChng"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusChangeRequestRejectionNotification message is sent by the matching application to the submitter of a request to change the status of a transaction. This message is used to inform about the rejection of a request to change the status of a transaction. Usage The StatusChangeRequestRejectionNotification message can be sent by the matching application to pass on information about the rejection of a request to change the status of a transaction that it has obtained through the receipt of a StatusChangeRequestRejection message. In order to pass on information about the acceptance of a request to change the status of a transaction the matching application sends a StatusChangeNotification message.

func (*StatusChangeRequestRejectionNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusChangeRequestRejectionNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusChangeRequestRejectionNotificationV03) AddNotificationIdentification 

func (s *StatusChangeRequestRejectionNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusChangeRequestRejectionNotificationV03) AddRejectedStatusChange 

func (s *StatusChangeRequestRejectionNotificationV03) AddRejectedStatusChange() *iso20022.TransactionStatus3

func (*StatusChangeRequestRejectionNotificationV03) AddRejectionReason 

func (s *StatusChangeRequestRejectionNotificationV03) AddRejectionReason() *iso20022.Reason2

func (*StatusChangeRequestRejectionNotificationV03) AddRequestForAction 

func (s *StatusChangeRequestRejectionNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusChangeRequestRejectionNotificationV03) AddTransactionIdentification 

func (s *StatusChangeRequestRejectionNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusChangeRequestRejectionNotificationV03) AddTransactionStatus 

func (s *StatusChangeRequestRejectionNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*StatusChangeRequestRejectionNotificationV03) AddUserTransactionReference 

func (s *StatusChangeRequestRejectionNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusChangeRequestRejectionV02 

type StatusChangeRequestRejectionV02 struct {

	// Identifies the rejection message.
	RejectionIdentification *iso20022.MessageIdentification1 `xml:"RjctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the status rejected.
	RejectedStatusChange *iso20022.TransactionStatus3 `xml:"RjctdStsChng"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn"`
}

Scope The StatusChangeRequestRejection message is sent by the party requested to accept or reject the request of a change in the status of a transaction to the matching application. This message is used to inform about the rejection of a request to change the status of a transaction. Usage The StatusChangeRequestRejection message can be sent by the party requested to accept or reject a request to change the status of a transaction to inform that it rejects the request. The message can be sent in response to a StatusChangeRequestNotification message. The acceptance of a request to change the status of a transaction can be achieved by sending a StatusChangeRequestAcceptance message.

func (*StatusChangeRequestRejectionV02) AddRejectedStatusChange 

func (s *StatusChangeRequestRejectionV02) AddRejectedStatusChange() *iso20022.TransactionStatus3

func (*StatusChangeRequestRejectionV02) AddRejectionIdentification 

func (s *StatusChangeRequestRejectionV02) AddRejectionIdentification() *iso20022.MessageIdentification1

func (*StatusChangeRequestRejectionV02) AddRejectionReason 

func (s *StatusChangeRequestRejectionV02) AddRejectionReason() *iso20022.Reason2

func (*StatusChangeRequestRejectionV02) AddSubmitterTransactionReference 

func (s *StatusChangeRequestRejectionV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusChangeRequestRejectionV02) AddTransactionIdentification 

func (s *StatusChangeRequestRejectionV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusChangeRequestV02 

type StatusChangeRequestV02 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Specifies the baseline status requested by the submitter by means of a code.
	RequestedStatus *iso20022.TransactionStatus3 `xml:"ReqdSts"`

	// Specifies the reason for the request to change status.
	RequestReason *iso20022.Reason2 `xml:"ReqRsn,omitempty"`
}

Scope The StatusChangeRequest message is sent by a party involved in a transaction to the matching application. This message is used to request a change in the status of a transaction. Usage The StatusChangeRequest message can be sent by either party involved in a transaction to the matching application to request a change in the status of a transaction. The matching application will pass on the request by sending a StatusChangeRequestNotification message to the counterparty which can accept or reject the request by sending a SatausChangeRequestAcceptance or StatusChangeRequestRejection message.

func (*StatusChangeRequestV02) AddRequestIdentification 

func (s *StatusChangeRequestV02) AddRequestIdentification() *iso20022.MessageIdentification1

func (*StatusChangeRequestV02) AddRequestReason 

func (s *StatusChangeRequestV02) AddRequestReason() *iso20022.Reason2

func (*StatusChangeRequestV02) AddRequestedStatus 

func (s *StatusChangeRequestV02) AddRequestedStatus() *iso20022.TransactionStatus3

func (*StatusChangeRequestV02) AddSubmitterTransactionReference 

func (s *StatusChangeRequestV02) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusChangeRequestV02) AddTransactionIdentification 

func (s *StatusChangeRequestV02) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusExtensionNotificationV03 

type StatusExtensionNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Identifies the status that is being rolled over.
	ExtendedStatus *iso20022.TransactionStatus5 `xml:"XtndedSts"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusExtensionNotification message is sent by the matching application to the parties involved in a request to extend the status of a transaction. This message is used to inform about the acceptance of a request to extend the status of a transaction. Usage The StatusExtensionNotification message can be sent by the matching application - to the submitter of a request to extend the status of a transaction to pass on information about the acceptance of the request that it has obtained through the receipt of an StatusExtensionAcceptance message. - to the accepter of a request to extend the status of a transaction to inform about the actual status of the transaction in response to a StatusExtensionAcceptance message. In order to pass on information about the rejection of a request to extend the status of a transaction the matching application sends a StatusExtensionRejectionNotification message.

func (*StatusExtensionNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusExtensionNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusExtensionNotificationV03) AddExtendedStatus 

func (s *StatusExtensionNotificationV03) AddExtendedStatus() *iso20022.TransactionStatus5

func (*StatusExtensionNotificationV03) AddNotificationIdentification 

func (s *StatusExtensionNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionNotificationV03) AddRequestForAction 

func (s *StatusExtensionNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusExtensionNotificationV03) AddTransactionIdentification 

func (s *StatusExtensionNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionNotificationV03) AddUserTransactionReference 

func (s *StatusExtensionNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusExtensionRejectionNotificationV03 

type StatusExtensionRejectionNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction that is not extended.
	NonExtendedStatus *iso20022.TransactionStatus4 `xml:"NonXtndedSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusExtensionRejectionNotification message is sent by the matching application to the submitter of a request to extend the status of a transaction. This message is used to inform about the rejection of a request to extend the status of a transaction. Usage The StatusExtensionRejectionNotification message can be sent by the matching application to pass on information about the rejection of a request to extend the status of a transaction that it has obtained through the receipt of a StatusExtensionRejection message. In order to pass on information about the acceptance of a request to extend the status of a transaction the matching application sends a StatusExtensionNotification message

func (*StatusExtensionRejectionNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusExtensionRejectionNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusExtensionRejectionNotificationV03) AddNonExtendedStatus 

func (s *StatusExtensionRejectionNotificationV03) AddNonExtendedStatus() *iso20022.TransactionStatus4

func (*StatusExtensionRejectionNotificationV03) AddNotificationIdentification 

func (s *StatusExtensionRejectionNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionRejectionNotificationV03) AddRejectionReason 

func (s *StatusExtensionRejectionNotificationV03) AddRejectionReason() *iso20022.Reason2

func (*StatusExtensionRejectionNotificationV03) AddRequestForAction 

func (s *StatusExtensionRejectionNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusExtensionRejectionNotificationV03) AddTransactionIdentification 

func (s *StatusExtensionRejectionNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionRejectionNotificationV03) AddUserTransactionReference 

func (s *StatusExtensionRejectionNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusExtensionRequestAcceptanceV03 

type StatusExtensionRequestAcceptanceV03 struct {

	// Identifies the acceptance message.
	AcceptanceIdentification *iso20022.MessageIdentification1 `xml:"AccptncId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Identifies the status for which the user accepts an extension of the validity period..
	ExtendedStatus *iso20022.TransactionStatus4 `xml:"XtndedSts"`
}

Scope The StatusExtensionRequestAcceptance message is sent by the party requested to accept or reject a request to extend the status of a transaction to the matching application. This message is used to inform about the acceptance of a request to extend the status of a transaction. Usage The StatusExtensionRequestAcceptance message can be sent by the party requested to accept or reject the request to extend the status of a transaction to inform that it accepts the request. The message can be sent in response to a StatusExtensionRequestNotification message. The rejection of a request to extend the status of a transaction can be achieved by sending a StatusExtensionRequestRejection message.

func (*StatusExtensionRequestAcceptanceV03) AddAcceptanceIdentification 

func (s *StatusExtensionRequestAcceptanceV03) AddAcceptanceIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionRequestAcceptanceV03) AddExtendedStatus 

func (s *StatusExtensionRequestAcceptanceV03) AddExtendedStatus() *iso20022.TransactionStatus4

func (*StatusExtensionRequestAcceptanceV03) AddSubmitterTransactionReference 

func (s *StatusExtensionRequestAcceptanceV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionRequestAcceptanceV03) AddTransactionIdentification 

func (s *StatusExtensionRequestAcceptanceV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusExtensionRequestNotificationV03 

type StatusExtensionRequestNotificationV03 struct {

	// Identifies the notification.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Identifies the status for which an extension of the validity period has been requested.
	StatusToBeExtended *iso20022.TransactionStatus5 `xml:"StsToBeXtnded"`

	// Party that has requested the status extension.
	Initiator *iso20022.BICIdentification1 `xml:"Initr"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The StatusExtensionRequestNotification message is sent by the matching application to the party requested to accept or reject a request to extend the status of a transaction. This message is used to notify the request to extend the status of a transaction. Usage The StatusExtensionRequestNotification message can be sent by the matching application to pass on information about the request to extend the status of a transaction that it has obtained through the receipt of a StatusExtensionRequest message.

func (*StatusExtensionRequestNotificationV03) AddEstablishedBaselineIdentification 

func (s *StatusExtensionRequestNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*StatusExtensionRequestNotificationV03) AddInitiator 

func (s *StatusExtensionRequestNotificationV03) AddInitiator() *iso20022.BICIdentification1

func (*StatusExtensionRequestNotificationV03) AddNotificationIdentification 

func (s *StatusExtensionRequestNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionRequestNotificationV03) AddRequestForAction 

func (s *StatusExtensionRequestNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*StatusExtensionRequestNotificationV03) AddStatusToBeExtended 

func (s *StatusExtensionRequestNotificationV03) AddStatusToBeExtended() *iso20022.TransactionStatus5

func (*StatusExtensionRequestNotificationV03) AddTransactionIdentification 

func (s *StatusExtensionRequestNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionRequestNotificationV03) AddUserTransactionReference 

func (s *StatusExtensionRequestNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type StatusExtensionRequestRejectionV03 

type StatusExtensionRequestRejectionV03 struct {

	// Identifies the rejection message.
	RejectionIdentification *iso20022.MessageIdentification1 `xml:"RjctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Identifies the status that the submitter does not want to be extended.
	StatusNotToBeExtended *iso20022.TransactionStatus4 `xml:"StsNotToBeXtnded"`

	// Reason why the user cannot accept the request.
	RejectionReason *iso20022.Reason2 `xml:"RjctnRsn"`
}

Scope The StatusExtensionRequestRejection message is sent by the party requested to accept or reject a request to extend the status of a transaction to the matching application. This message is used to inform about the rejection of a request to extend the status of a transaction. Usage The StatusExtensionRequestRejection message can be sent by the party requested to accept or reject the request to extend the status of a transaction to inform that it rejects the request. The message can be sent in response to a StatusExtensionRequestNotification message. The acceptance of a request to extend the status of a transaction can be achieved by sending a StatusExtensionRequestAcceptance message.

func (*StatusExtensionRequestRejectionV03) AddRejectionIdentification 

func (s *StatusExtensionRequestRejectionV03) AddRejectionIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionRequestRejectionV03) AddRejectionReason 

func (s *StatusExtensionRequestRejectionV03) AddRejectionReason() *iso20022.Reason2

func (*StatusExtensionRequestRejectionV03) AddStatusNotToBeExtended 

func (s *StatusExtensionRequestRejectionV03) AddStatusNotToBeExtended() *iso20022.TransactionStatus4

func (*StatusExtensionRequestRejectionV03) AddSubmitterTransactionReference 

func (s *StatusExtensionRequestRejectionV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionRequestRejectionV03) AddTransactionIdentification 

func (s *StatusExtensionRequestRejectionV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusExtensionRequestV03 

type StatusExtensionRequestV03 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Reference to the transaction for the requesting financial institution.
	SubmitterTransactionReference *iso20022.SimpleIdentificationInformation `xml:"SubmitrTxRef,omitempty"`

	// Identifies the status of the transaction by means of a code.
	StatusToBeExtended *iso20022.TransactionStatus5 `xml:"StsToBeXtnded"`
}

Scope The StatusExtensionRequest message is sent by either party involved in a transaction to the matching application. This message is used to request the extension of the status of a transaction. Usage The StatusExtensionRequest message can be sent by either party involved in a transaction to the matching application to request the extension of the status of a transaction. The matching application will pass on the request by sending a StatusExtensionRequestNotification message to the counterparty which can accept or reject the status extension request by sending a StatusExtensionAcceptance or StatusExtensionRejection message.

func (*StatusExtensionRequestV03) AddRequestIdentification 

func (s *StatusExtensionRequestV03) AddRequestIdentification() *iso20022.MessageIdentification1

func (*StatusExtensionRequestV03) AddStatusToBeExtended 

func (s *StatusExtensionRequestV03) AddStatusToBeExtended() *iso20022.TransactionStatus5

func (*StatusExtensionRequestV03) AddSubmitterTransactionReference 

func (s *StatusExtensionRequestV03) AddSubmitterTransactionReference() *iso20022.SimpleIdentificationInformation

func (*StatusExtensionRequestV03) AddTransactionIdentification 

func (s *StatusExtensionRequestV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

type StatusReportRequestV03 

type StatusReportRequestV03 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Specifies the entities of the submitter for which the transactions have to be reported.
	EntitiesToBeReported []*iso20022.BICIdentification1 `xml:"NttiesToBeRptd,omitempty"`
}

Scope The StatusReportRequest message is sent by a party involved in a transaction to the matching application. This message is used to request a report on the status of transactions registered in the matching application. Usage The StatusReportRequest message can be sent by either party involved in a transaction to request a report on the status and sub-statuses of all transactions that the requester is involved in. The application will respond to the request by sending a StatusReport message.

func (*StatusReportRequestV03) AddEntitiesToBeReported 

func (s *StatusReportRequestV03) AddEntitiesToBeReported() *iso20022.BICIdentification1

func (*StatusReportRequestV03) AddRequestIdentification 

func (s *StatusReportRequestV03) AddRequestIdentification() *iso20022.MessageIdentification1

type StatusReportV03 

type StatusReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the previous message requesting the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef"`

	// Describes a transaction and its status.
	ReportedItems []*iso20022.StatusReportItems2 `xml:"RptdItms,omitempty"`
}

Scope The StatusReport message is sent by the matching application to the requester of a status report. This message is used to report on the status of transactions registered in the matching application. Usage The StatusReport message can be sent by the matching application to report on the status and sub-status of all transactions that the requester of the report is involved in. The message can be sent in response to a StatusReportRequest message.

func (*StatusReportV03) AddRelatedMessageReference 

func (s *StatusReportV03) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*StatusReportV03) AddReportIdentification 

func (s *StatusReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*StatusReportV03) AddReportedItems 

func (s *StatusReportV03) AddReportedItems() *iso20022.StatusReportItems2

type TimeOutNotificationV03 

type TimeOutNotificationV03 struct {

	// Identifies the notification message.
	NotificationIdentification *iso20022.MessageIdentification1 `xml:"NtfctnId"`

	// Unique identification assigned by the matching application to the transaction.
	// This identification is to be used in any communication between the parties.
	//
	TransactionIdentification *iso20022.SimpleIdentificationInformation `xml:"TxId"`

	// Unique identification assigned by the matching application to the baseline when it is established.
	EstablishedBaselineIdentification *iso20022.DocumentIdentification3 `xml:"EstblishdBaselnId,omitempty"`

	// Identifies the status of the transaction by means of a code.
	TransactionStatus *iso20022.TransactionStatus4 `xml:"TxSts"`

	// Reference to the transaction for each financial institution which is a party to the transaction.
	UserTransactionReference []*iso20022.DocumentIdentification5 `xml:"UsrTxRef,omitempty"`

	// Describes the time-out consequences.
	TimeOutDescription *iso20022.TimeOutResult2 `xml:"TmOutDesc"`

	// Information on the next processing step required.
	RequestForAction *iso20022.PendingActivity2 `xml:"ReqForActn,omitempty"`
}

Scope The TimeOutNotification message is sent by the matching application to a party involved in a transaction. This message is used to inform that a transaction will be closed within a given span of time if no action is taken. Usage The TimeOutNotification message can be sent by the matching application to inform the parties that a transaction will be closed within a given span of time if no action is taken by either party because - no activity for the transaction has taken place within a specified span of time,or - a significant date is reached, for example latest shipment date.

func (*TimeOutNotificationV03) AddEstablishedBaselineIdentification 

func (t *TimeOutNotificationV03) AddEstablishedBaselineIdentification() *iso20022.DocumentIdentification3

func (*TimeOutNotificationV03) AddNotificationIdentification 

func (t *TimeOutNotificationV03) AddNotificationIdentification() *iso20022.MessageIdentification1

func (*TimeOutNotificationV03) AddRequestForAction 

func (t *TimeOutNotificationV03) AddRequestForAction() *iso20022.PendingActivity2

func (*TimeOutNotificationV03) AddTimeOutDescription 

func (t *TimeOutNotificationV03) AddTimeOutDescription() *iso20022.TimeOutResult2

func (*TimeOutNotificationV03) AddTransactionIdentification 

func (t *TimeOutNotificationV03) AddTransactionIdentification() *iso20022.SimpleIdentificationInformation

func (*TimeOutNotificationV03) AddTransactionStatus 

func (t *TimeOutNotificationV03) AddTransactionStatus() *iso20022.TransactionStatus4

func (*TimeOutNotificationV03) AddUserTransactionReference 

func (t *TimeOutNotificationV03) AddUserTransactionReference() *iso20022.DocumentIdentification5

type TransactionReportRequestV03 

type TransactionReportRequestV03 struct {

	// Identifies the request message.
	RequestIdentification *iso20022.MessageIdentification1 `xml:"ReqId"`

	// Parameters to be used as criteria for the content of the transaction report.
	ReportSpecification *iso20022.ReportSpecification4 `xml:"RptSpcfctn"`
}

Scope The TransactionReportRequest message is sent by a party involved in a transaction to the matching application. This message is used to request a report on details of transactions registered in the matching application. Usage The TransactionReportRequest message can be sent by either party involved in a transaction to request a report on a variety of details of all transactions that the requester is involved in. For example, the message can be used to request a report on all transactions that the requester is involved in with a certain customer.

func (*TransactionReportRequestV03) AddReportSpecification 

func (t *TransactionReportRequestV03) AddReportSpecification() *iso20022.ReportSpecification4

func (*TransactionReportRequestV03) AddRequestIdentification 

func (t *TransactionReportRequestV03) AddRequestIdentification() *iso20022.MessageIdentification1

type TransactionReportV03 

type TransactionReportV03 struct {

	// Identifies the report.
	ReportIdentification *iso20022.MessageIdentification1 `xml:"RptId"`

	// Reference to the previous message requesting the report.
	RelatedMessageReference *iso20022.MessageIdentification1 `xml:"RltdMsgRef"`

	// Detailed description of the items that correspond to the parameters set in the request.
	ReportedItems []*iso20022.TransactionReportItems3 `xml:"RptdItms,omitempty"`
}

Scope The TransactionReport message is sent by the matching application to the requester of a transaction report. This message is used to report on various details of transactions registered in the matching application. Usage The TransactionReport message can be sent by the matching application to report on various details of transactions that the requester of the report asked for. The message is sent in response to a TransactionReportRequest message.

func (*TransactionReportV03) AddRelatedMessageReference 

func (t *TransactionReportV03) AddRelatedMessageReference() *iso20022.MessageIdentification1

func (*TransactionReportV03) AddReportIdentification 

func (t *TransactionReportV03) AddReportIdentification() *iso20022.MessageIdentification1

func (*TransactionReportV03) AddReportedItems 

func (t *TransactionReportV03) AddReportedItems() *iso20022.TransactionReportItems3

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.