tsin

type Document00100101 ¶

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

func (d *Document00100101) AddMessage() *InvoiceFinancingRequestV01

type Document00200101 ¶

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

func (d *Document00200101) AddMessage() *InvoiceFinancingRequestStatusV01

type Document00300101 ¶

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

func (d *Document00300101) AddMessage() *InvoiceFinancingCancellationRequestV01

type Document00400101 ¶

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

func (d *Document00400101) AddMessage() *FinancialInvoiceV01

type Document00500101 ¶

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

func (d *Document00500101) AddMessage() *UndertakingApplicationV01

type Document00600101 ¶

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

func (d *Document00600101) AddMessage() *InvoiceAssignmentRequestV01

type Document00700101 ¶

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

func (d *Document00700101) AddMessage() *InvoiceAssignmentStatusV01

type Document00800101 ¶

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

func (d *Document00800101) AddMessage() *InvoiceAssignmentNotificationV01

type Document00900101 ¶

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

func (d *Document00900101) AddMessage() *PartyRegistrationAndGuaranteeRequestV01

type Document01000101 ¶

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

func (d *Document01000101) AddMessage() *PartyRegistrationAndGuaranteeStatusV01

type Document01100101 ¶

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

func (d *Document01100101) AddMessage() *PartyRegistrationAndGuaranteeNotificationV01

type Document01200101 ¶

type Document01200101 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:tsin.012.001.01 Document"`
	Message *PartyRegistrationAndGuaranteeAcknowledgementV01 `xml:"PtyRegnAndGrntAck"`
}

func (d *Document01200101) AddMessage() *PartyRegistrationAndGuaranteeAcknowledgementV01

type Document01300101 ¶

type Document01300101 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:tsin.013.001.01 Document"`
	Message *InvoiceAssignmentAcknowledgementV01 `xml:"InvcAssgnmtAck"`
}

func (d *Document01300101) AddMessage() *InvoiceAssignmentAcknowledgementV01

type FinancialInvoiceV01 ¶

type FinancialInvoiceV01 struct {

	// Collection of data that is exchanged between two or more parties in written, printed or electronic form. It contains general data relevant to the main body of the invoice such as date of issue, currency code and identification number.
	InvoiceHeader *iso20022.InvoiceHeader1 `xml:"InvcHdr"`

	// Commercial information such as terms of commerce, parties, and documentation, related to the trading agreement under which this invoice is issued.
	TradeAgreement *iso20022.TradeAgreement6 `xml:"TradAgrmt"`

	// Supply chain shipping arrangements for delivery of invoiced products and/or services.
	TradeDelivery *iso20022.TradeDelivery1 `xml:"TradDlvry"`

	// Settlement information that enables the financial reconciliation and payment of this invoice.
	//
	TradeSettlement *iso20022.TradeSettlement1 `xml:"TradSttlm"`

	// Unit of information in this invoice showning the related  provision of products and/or services and monetary summations reported as a discrete line item.
	//
	//
	//
	LineItem []*iso20022.LineItem10 `xml:"LineItm,omitempty"`
}

Scope The FinancialInvoice message is used to support the provision of financial and related services where there is a requirement to exchange invoice information. Usage While the prime function of the FinancialInvoice message is as a request from the seller to the buyer for payment, the FinancialInvoice message can also serve to evidence an invoice in support of a financial service such as invoice factoring, letters of credit, and bank payment obligations, to enable Web based services such as electronic bill payment and presentment, and as the basis to transfer invoice information via third parties such as e-invoicing service providers. A consequence of the receipt of an invoice by the buyer is that it acts as a trigger for the use of related messages that are already defined in ISO 20022, notably where the information contained in the Financial Invoice enables payment for the goods or services received, and/or is provided in support of a request for invoice financing. While certain of these related messages, such as the CreditTransfer and PaymentInitiation messages, are shown in the sequence diagram they are out of scope. They are shown only to illustrate a given scenario and to place the invoice in the context of the financial banking processes that might be conducted between different financial institutions. The use of self-billing by the buyer to the seller, where the buyer acts as the invoice issuer or the process of handling an incorrect invoice, is not in scope.

func (f *FinancialInvoiceV01) AddInvoiceHeader() *iso20022.InvoiceHeader1

func (f *FinancialInvoiceV01) AddLineItem() *iso20022.LineItem10

func (f *FinancialInvoiceV01) AddTradeAgreement() *iso20022.TradeAgreement6

func (f *FinancialInvoiceV01) AddTradeDelivery() *iso20022.TradeDelivery1

func (f *FinancialInvoiceV01) AddTradeSettlement() *iso20022.TradeSettlement1

type InvoiceAssignmentAcknowledgementV01 ¶

type InvoiceAssignmentAcknowledgementV01 struct {

	// Set of characteristics that unambiguously identify the status, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of payment status information.
	PaymentStatusList []*iso20022.FinancingItemList1 `xml:"PmtStsList"`

	// Number of payment information lists as control value.
	PaymentStatusCount *iso20022.Max15NumericText `xml:"PmtStsCnt,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 InvoiceAssignmentAcknowledgement message is sent from a trade partner to communicate the status of payment obligations related to financial items. The message can be sent independently or as a response to an InvoiceAssignmentNotification message. Depending on legal contexts the message may be required as a response to an InvoiceAssignmentNotification message in order for the assignment to become effective. The trade party may include references to the corresponding items of an InvoiceAssignmentRequest, InvoiceAssignmentStatus or InvoiceAssignmentNotification or other messages and may include referenced data. The message can carry digital signatures if required by context.

func (i *InvoiceAssignmentAcknowledgementV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (i *InvoiceAssignmentAcknowledgementV01) AddHeader() *iso20022.BusinessLetter1

func (i *InvoiceAssignmentAcknowledgementV01) AddPaymentStatusList() *iso20022.FinancingItemList1

func (i *InvoiceAssignmentAcknowledgementV01) SetControlSum(value string)

func (i *InvoiceAssignmentAcknowledgementV01) SetItemCount(value string)

func (i *InvoiceAssignmentAcknowledgementV01) SetPaymentStatusCount(value string)

type InvoiceAssignmentNotificationV01 ¶

type InvoiceAssignmentNotificationV01 struct {

	// Set of characteristics that unambiguously identify the assignment notification, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of assignment notifications.
	NotificationList []*iso20022.FinancingItemList1 `xml:"NtfctnList"`

	// Number of assignment notification lists.
	NotificationCount *iso20022.Max15NumericText `xml:"NtfctnCnt,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"`
}

This message is sent from a factoring service provider or a factoring client to a trade partner to inform about assignments of financing items and, optionally, to an interested party. The information given to the trade party indicates that property of the payment obligation has been or is being transferred to the financial institution and that payments have to be done between the trade partner and the factoring service provider. The message indicates whether the notified party is required to acknowledge the notified assignment and to which party an acknowledgement has to be sent. This message can also be used outside a factoring context directly between a payer and a payee for example as a reminder about a payment obligation or to make an adjustment. If applicable, the message may reference corresponding items of an InvoiceFinancingRequest or InvoiceFinancingStatus or other related messages and may contain referenced data. The message can carry digital signatures if required by context.

func (i *InvoiceAssignmentNotificationV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (i *InvoiceAssignmentNotificationV01) AddHeader() *iso20022.BusinessLetter1

func (i *InvoiceAssignmentNotificationV01) AddNotificationList() *iso20022.FinancingItemList1

func (i *InvoiceAssignmentNotificationV01) SetControlSum(value string)

func (i *InvoiceAssignmentNotificationV01) SetItemCount(value string)

func (i *InvoiceAssignmentNotificationV01) SetNotificationCount(value string)

type InvoiceAssignmentRequestV01 ¶

type InvoiceAssignmentRequestV01 struct {

	// Set of characteristics that unambiguously identify the invoice assigment request, such as group identification, creation date time, number of single invoice financing requests, totals and subtotals.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of assignments of financial items.
	AssignmentList []*iso20022.FinancingItemList1 `xml:"AssgnmtList"`

	// Number of assignments.
	AssignmentCount *iso20022.Max15NumericText `xml:"AssgnmtCnt,omitempty"`

	// Total number of individual items in all assignments.
	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 InvoiceAssignmentRequest message is sent from a factoring client to a factoring service provider and, optionally, to an interested party. It indicates the transfer of payment obligations concerning financial documents. The message contains a list of financing requests together with data that are necessary to transfer the related rights for example regarding legal references for example jurisdiction, language or country. Furthermore, the message can reference related messages and can include data from other messages. A factoring client combines a set of financial documents with same characteristics and assigns them to a factoring service. The client can send several assignments in one message and combine them according to different criteria for example for different clients or different currencies.

func (i *InvoiceAssignmentRequestV01) AddAssignmentList() *iso20022.FinancingItemList1

func (i *InvoiceAssignmentRequestV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (i *InvoiceAssignmentRequestV01) AddHeader() *iso20022.BusinessLetter1

func (i *InvoiceAssignmentRequestV01) SetAssignmentCount(value string)

func (i *InvoiceAssignmentRequestV01) SetControlSum(value string)

func (i *InvoiceAssignmentRequestV01) SetItemCount(value string)

type InvoiceAssignmentStatusV01 ¶

type InvoiceAssignmentStatusV01 struct {

	// Set of characteristics that unambiguously identify the assignment status, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of assignments of financial items.
	AssignmentList []*iso20022.FinancingItemList1 `xml:"AssgnmtList"`

	// Number of assignments.
	AssignmentCount *iso20022.Max15NumericText `xml:"AssgnmtCnt,omitempty"`

	// Total number of individual items in all assignments.
	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 InvoiceAssignmentStatus is sent by a factoring service provider to a factoring client and, optionally, to an interested party as a response to assignments requests. The factoring service provider returns a copy of items of corresponding requests together with an information about the status of treatment, for example acceptance, rejection or treatment not yet finished. A rejection can be the result of bad message syntax, but also for other motives such as risk, compliance or covenants. For each reported financial item, the factoring service provider includes a reference to the corresponding item of the InvoiceFinancingRequest message and may include the referenced item as well as data from other related and referenced messages. The message contains information about other parties to be notified and whether these parties are required to acknowledge the assignment. The message can carry digital signatures if required by context.

func (i *InvoiceAssignmentStatusV01) AddAssignmentList() *iso20022.FinancingItemList1

func (i *InvoiceAssignmentStatusV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (i *InvoiceAssignmentStatusV01) AddHeader() *iso20022.BusinessLetter1

func (i *InvoiceAssignmentStatusV01) SetAssignmentCount(value string)

func (i *InvoiceAssignmentStatusV01) SetControlSum(value string)

func (i *InvoiceAssignmentStatusV01) SetItemCount(value string)

type InvoiceFinancingCancellationRequestV01 ¶

type InvoiceFinancingCancellationRequestV01 struct {

	// Unique and unambiguous identification of the message.
	CancellationRequestIdentification *iso20022.MessageIdentification1 `xml:"CxlReqId"`

	// Set of information related to the cancellation request, such as actors involved and identification of the original invoice financing request to which the cancellation request refers.
	CancellationRequestInformation *iso20022.CancellationRequestInformation1 `xml:"CxlReqInf"`
}

Scope The InvoiceFinancingCancellationRequest message is sent by the Financing Requestor to the Intermediary Agent (relay scenario) or First Agent (direct scenario). It is used to request the cancellation of a previously sent financing request. Usage The InvoiceFinancingCancellationRequest message is used by the Financing Requestor to request the cancellation of a previously sent financing request. It is not possible to send a cancellation request for a single invoice contained in a bulk invoice financing request. The InvoiceFinancingCancellationRequest message contains references (original group identification and original creation date and time) of the original financing request message to which is referred. As for InvoiceFinancingRequest, the message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the First Agent. The First Agent is the account servicer of the Financing Requestor. - In a relay scenario, the message is sent to an Intermediary Agent. The Intermediary Agent forwards the InvoiceFinancingCancellingRequest message to the First Agent.

func (i *InvoiceFinancingCancellationRequestV01) AddCancellationRequestIdentification() *iso20022.MessageIdentification1

func (i *InvoiceFinancingCancellationRequestV01) AddCancellationRequestInformation() *iso20022.CancellationRequestInformation1

type InvoiceFinancingRequestStatusV01 ¶

type InvoiceFinancingRequestStatusV01 struct {

	// General information that unambiguously identify the invoice financing status report, such as status identification, creation date time.
	StatusIdentification *iso20022.MessageIdentification1 `xml:"StsId"`

	// Set of summary information that unambiguously identifies the original invoice financing (or cancellation) request to which the status is referred. The status of the original request is also given in this block.
	//
	OriginalRequestInformationAndStatus *iso20022.OriginalRequestInformation1 `xml:"OrgnlReqInfAndSts"`

	// Information concerning the business status of a financing request.
	FinancingInformationAndStatus *iso20022.FinancingInformationAndStatus1 `xml:"FincgInfAndSts,omitempty"`
}

Scope The InvoiceFinancingRequestStatus message is sent by the First Agent to the Financing Requestor, alternatively through an Intermediary Agent (relay scenario). It is used to inform the Financing Requestor about the positive or negative status of a financing request or a financing cancellation request. Usage The InvoiceFinancingRequestStatus message flows from the First Agent to the Financing Requestor (alternatively through an Intermediary Agent) to provide status information about a request previously sent. Its usage will always be governed by a bilateral agreement between the First Agent and the Financing Requestor. The InvoiceFinancingRequestStatus message can be used two fold: - to provide information about the reception status (eg rejection, acceptance) of a request message. In this case the status message is the result of a technical validation performed by the First Agent on the request message received; - to inform the Financing Requestor about the business status of the financing process initiated. In this case the First Agent can: * communicate that a single financing request has been granted, is pending or has not been granted at all; * inform that a financing cancellation request has been allowed or denied. Note. If the Financing Requestor requests financing for more than one instalment related to the same invoice, the First Agent can decide to finance only some of the instalments. In such case the status message contains details and status of every single instalment (financed, not financed). The message can be used in a direct or in a relay scenario: - In a direct scenario, the message is sent directly by the First Agent to the Financing Requestor; - In a relay scenario, the message is sent first by the First Agent to the Intermediary Agent, who forwards it to the Financing Requestor. The InvoiceFinancingRequestStatus message refers to the original request(s) by means of references and a set of data elements included into the original request.

func (i *InvoiceFinancingRequestStatusV01) AddFinancingInformationAndStatus() *iso20022.FinancingInformationAndStatus1

func (i *InvoiceFinancingRequestStatusV01) AddOriginalRequestInformationAndStatus() *iso20022.OriginalRequestInformation1

func (i *InvoiceFinancingRequestStatusV01) AddStatusIdentification() *iso20022.MessageIdentification1

type InvoiceFinancingRequestV01 ¶

type InvoiceFinancingRequestV01 struct {

	// Specifies a set of characteristics that unambiguously identify the invoice financing request, such as group identification, creation date time, number of single invoice financing requests.
	RequestGroupInformation *iso20022.RequestGroupInformation1 `xml:"ReqGrpInf"`

	// Set of characteristics that unambiguously identify the single invoice financing request related to the entire invoice or a specific instalment of the invoice settlement, such as actors involved, invoice totals or payment method.
	InvoiceRequestInformation []*iso20022.InvoiceRequestInformation1 `xml:"InvcReqInf"`
}

Scope The InvoiceFinancingRequest message is sent by Financing Requestor to the Intermediary Agent or First agent. It is used to request financing of a set of invoices, referenced in the request message itself. If the whole financing request (or a selection of single invoice requests included) is accepted, the amount financed by the First Agent will be credited either to the account specified in the financing request or to another account held by Financing Requestor to First Agent. Usage The InvoiceFinancingRequest message is issued by the Financing Requestor and represents a bulk financing request since it can contain one or more single financing requests, each request related to an invoice. For every invoice it is always possible to identify a supplier and a buyer. The subject playing the role of supplier can be different from the Financing Requestor; in this case the Financing Requestor is allowed to send the request message on behalf of the supplier itself. This caters for example in the scenario of a collection agency initiating all requests on behalf of a large corporate. In instances where an invoice is going to be paid by means of instalments, the Financing Requestor can request financing for one or more instalments related to the invoice payment. In this case, together with the general information related to the invoice, references about instalments to be financed are specified into the request message. The request message must contain information only about the instalments that the Financing Requestor wants to be financed. The InvoiceFinancingRequest message is used to exchange: - One instance of general information related to the invoice financing request; - One instance of information for each single invoice financing request; - Optionally, one instance of information for each single instalment to be financed. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the First Agent. The First Agent is the account servicer of the Financing Requestor; - In a relay scenario, the message is sent to an Intermediary Agent. The Intermediary Agent acts as an access point that will forward the InvoiceFinancingRequest message to the First Agent.

func (i *InvoiceFinancingRequestV01) AddInvoiceRequestInformation() *iso20022.InvoiceRequestInformation1

func (i *InvoiceFinancingRequestV01) AddRequestGroupInformation() *iso20022.RequestGroupInformation1

type PartyRegistrationAndGuaranteeAcknowledgementV01 ¶

type PartyRegistrationAndGuaranteeAcknowledgementV01 struct {

	// Set of characteristics that unambiguously identify the acknowlegement, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of party management acknowledgements.
	AcknowledgementList []*iso20022.FinancingAgreementList1 `xml:"AckList"`

	// Number of acknowledgement lists as control value.
	AcknowledgementCount *iso20022.Max15NumericText `xml:"AckCnt"`

	// 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 PartyManagementPaymentAcknowledgement is sent from a trade partner to any partner requested through a PartyManagementPaymentAcknowledgemenNotification message to acknowledge the notified factoring service agreement. Depending on legal contexts, the acknowledgement may be required in order for the financial service agreement to become effective. The message references related messages and may include referenced data. The message can carry digital signatures if required by context.

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) AddAcknowledgementList() *iso20022.FinancingAgreementList1

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) AddHeader() *iso20022.BusinessLetter1

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) SetAcknowledgementCount(value string)

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) SetControlSum(value string)

func (p *PartyRegistrationAndGuaranteeAcknowledgementV01) SetItemCount(value string)

type PartyRegistrationAndGuaranteeNotificationV01 ¶

type PartyRegistrationAndGuaranteeNotificationV01 struct {

	// Set of characteristics that unambiguously identify the notification, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of otifications.
	NotificationList []*iso20022.FinancingAgreementList1 `xml:"NtfctnList"`

	// Number of notification lists as control value.
	NotificationCount *iso20022.Max15NumericText `xml:"NtfctnCnt,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 PartyRegistrationAndGuaranteeNotification message is sent by a factoring client or a financial service to a trade partner and, optionally, to an interested party in order to notify the status of a requested financial service agreement. The trade partner is given information to explain the consequences of a financial service agreement, for instance, the trade partner must pay the financial institution and must use the electronic address to inform it and pay it using the bank account given. The message may reference related messages and may include referenced data. The message can carry digital signatures if required by context.

func (p *PartyRegistrationAndGuaranteeNotificationV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (p *PartyRegistrationAndGuaranteeNotificationV01) AddHeader() *iso20022.BusinessLetter1

func (p *PartyRegistrationAndGuaranteeNotificationV01) AddNotificationList() *iso20022.FinancingAgreementList1

func (p *PartyRegistrationAndGuaranteeNotificationV01) SetControlSum(value string)

func (p *PartyRegistrationAndGuaranteeNotificationV01) SetItemCount(value string)

func (p *PartyRegistrationAndGuaranteeNotificationV01) SetNotificationCount(value string)

type PartyRegistrationAndGuaranteeRequestV01 ¶

type PartyRegistrationAndGuaranteeRequestV01 struct {

	// Set of characteristics that unambiguously identify the request, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of agreements.
	AgreementList []*iso20022.FinancingAgreementList1 `xml:"AgrmtList"`

	// Number of agreement lists as control value.
	AgreementCount *iso20022.Max15NumericText `xml:"AgrmtCnt,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 PartyRegistrationAndGuaranteeRequest is sent by a factoring client either to a financial service or a guarantee issuer. The message can also be sent from a financial service to a guarantee issuer. Furthermore, the message can be sent to an interested party for example a fiscal authority. When the message is sent to a guarantee issuer, the factoring client or financial service provider requests a guarantee for the factoring agreement concerning the indicated trade party. When the message is sent to a financial service, the financial client requests an agreement to execute assignments of financial items. The financial client may request the guarantee amount to be obtained in case of insolvency of the trade partner for a corresponding account receivable directly from the financial service. Alternatively and depending on the contractual and product definition, the financial client may be required to include a copy of a guarantee status received from a guarantee issuer. The message can carry digital signatures if required by context.

func (p *PartyRegistrationAndGuaranteeRequestV01) AddAgreementList() *iso20022.FinancingAgreementList1

func (p *PartyRegistrationAndGuaranteeRequestV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (p *PartyRegistrationAndGuaranteeRequestV01) AddHeader() *iso20022.BusinessLetter1

func (p *PartyRegistrationAndGuaranteeRequestV01) SetAgreementCount(value string)

func (p *PartyRegistrationAndGuaranteeRequestV01) SetControlSum(value string)

func (p *PartyRegistrationAndGuaranteeRequestV01) SetItemCount(value string)

type PartyRegistrationAndGuaranteeStatusV01 ¶

type PartyRegistrationAndGuaranteeStatusV01 struct {

	// Set of characteristics that unambiguously identify the status, common parameters, documents and identifications.
	Header *iso20022.BusinessLetter1 `xml:"Hdr"`

	// List of agreements.
	AgreementList []*iso20022.FinancingAgreementList1 `xml:"AgrmtList"`

	// Number of agreement lists as control value.
	AgreementCount *iso20022.Max15NumericText `xml:"AgrmtCnt,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 PartyRegistrationAndGuaranteeStatus is either sent by a factoring service to a financing client to indicate the status of a factoring service agreement or from a guarantee issuer to a factoring client or a factoring service to indicate the guarantee covering a requested factoring service agreement. The message can also be sent to an interested party. The factoring service or guarantee issuer may include references to a corresponding PartyRegistrationAndGuaranteeRequest message or other related messages and may include referenced data. The message contains information about other parties to be notified about the financial service agreement or the guarantee and whether these parties are required to acknowledge the agreement. The message contains information returned by the financial institution indicating acceptance or rejection of the trade partner; a positive response is necessary before being able to assign financial items concerning the trade party. This message contains identifications of cash accounts to enable payer and payee to treat the transferred payment obligations. The message can carry digital signatures if required by context.

func (p *PartyRegistrationAndGuaranteeStatusV01) AddAgreementList() *iso20022.FinancingAgreementList1

func (p *PartyRegistrationAndGuaranteeStatusV01) AddAttachedMessage() *iso20022.EncapsulatedBusinessMessage1

func (p *PartyRegistrationAndGuaranteeStatusV01) AddHeader() *iso20022.BusinessLetter1

func (p *PartyRegistrationAndGuaranteeStatusV01) SetAgreementCount(value string)

func (p *PartyRegistrationAndGuaranteeStatusV01) SetControlSum(value string)

func (p *PartyRegistrationAndGuaranteeStatusV01) SetItemCount(value string)

type UndertakingApplicationV01 ¶

type UndertakingApplicationV01 struct {

	// Details of the application for an independent undertaking, such as a demand guarantee or standby letter of credit, that provides financial assurance, to be collected on the presentation of documents that comply with its terms and conditions.
	UndertakingApplicationDetails *iso20022.Undertaking1 `xml:"UdrtkgApplDtls"`

	// Instructions specific to the bank receiving the message.
	InstructionsToBank []*iso20022.Max2000Text `xml:"InstrsToBk,omitempty"`

	// Digital signature of the undertaking application.
	DigitalSignature *iso20022.PartyAndSignature2 `xml:"DgtlSgntr,omitempty"`
}

The UndertakingApplication message is sent by the party requesting issuance of the undertaking (applicant or obligor) to the party issuing the undertaking. It is used to request the issuance of an undertaking (demand guarantee or standby letter of credit or suretyship) or counter-undertaking (counter-guarantee or counter-standby or suretyship), and provides details on the applicable rules, terms, conditions and content of the undertaking to be issued.

func (u *UndertakingApplicationV01) AddDigitalSignature() *iso20022.PartyAndSignature2

func (u *UndertakingApplicationV01) AddInstructionsToBank(value string)

func (u *UndertakingApplicationV01) AddUndertakingApplicationDetails() *iso20022.Undertaking1