FullPushThroughReportV03

tsmt.018.001.03

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

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% FullPushThroughReportV03 recursion level 0 with max 0
FullPushThroughReportV03 *-- "1..1" MessageIdentification1 : ReportIdentification
FullPushThroughReportV03 *-- "1..1" SimpleIdentificationInformation : TransactionIdentification
FullPushThroughReportV03 *-- "0..1" DocumentIdentification3 : EstablishedBaselineIdentification
FullPushThroughReportV03 *-- "1..1" TransactionStatus4 : TransactionStatus
FullPushThroughReportV03 *-- "0..2" DocumentIdentification5 : UserTransactionReference
FullPushThroughReportV03 *-- "1..1" ReportType1 : ReportPurpose
FullPushThroughReportV03 *-- "1..1" Baseline3 : PushedThroughBaseline
FullPushThroughReportV03 *-- "0..1" ContactIdentification1 : BuyerContactPerson
FullPushThroughReportV03 *-- "0..1" ContactIdentification1 : SellerContactPerson
FullPushThroughReportV03 *-- "0..1" ContactIdentification1 : BuyerBankContactPerson
FullPushThroughReportV03 *-- "0..1" ContactIdentification1 : SellerBankContactPerson
FullPushThroughReportV03 *-- "0..1" ContactIdentification3 : OtherBankContactPerson
FullPushThroughReportV03 *-- "0..1" PendingActivity2 : RequestForAction
  

Now, we will zero-in one-by-one on each of these building blocks.

ReportIdentification building block

Identifies the report. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

Member name Description Data Type / Multiplicity
Identification Identification of the message. IsoMax35Text - Required 1..1
CreationDateTime Date of creation of the message. IsoISODateTime - Required 1..1

TransactionIdentification building block

Unique identification assigned by the matching application to the transaction. This identification is to be used in any communication between the parties. Information related to an identification, eg, party identification or account identification. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SimpleIdentificationInformation recursion level 0 with max 1
class SimpleIdentificationInformation{
    Identification IsoMax35Text
}
  

SimpleIdentificationInformation members

Member name Description Data Type / Multiplicity
Identification Name or number assigned by an entity to enable recognition of that entity, eg, account identifier. IsoMax35Text - Required 1..1

EstablishedBaselineIdentification building block

Unique identification assigned by the matching application to the baseline when it is established. Identifies a document by a unique identification and a version. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification3 recursion level 0 with max 1
class DocumentIdentification3{
    Identification IsoMax35Text
    Version IsoNumber
}
  

DocumentIdentification3 members

Member name Description Data Type / Multiplicity
Identification Identification of a set of data. IsoMax35Text - Required 1..1
Version Unambiguous identification of the version of a set of data. Example: Version 1. IsoNumber - Required 1..1

TransactionStatus building block

Identifies the status of the transaction by means of a code. Identifies the status of the transaction by means of a code. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TransactionStatus4 recursion level 0 with max 1
class TransactionStatus4{
    Status BaselineStatus3Code
}
  

TransactionStatus4 members

Member name Description Data Type / Multiplicity
Status Identifies the status of the transaction by means of a code. BaselineStatus3Code - Required 1..1

UserTransactionReference building block

Reference to the transaction for the financial institution which submitted the baseline. Identifies a document by a unique identification and its issuer. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification5 recursion level 0 with max 1
class DocumentIdentification5{
    Identification IsoMax35Text
}
DocumentIdentification5 *-- "1..1" BICIdentification1 : IdentificationIssuer
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
  

DocumentIdentification5 members

Member name Description Data Type / Multiplicity
Identification Identification of a set of data. IsoMax35Text - Required 1..1
IdentificationIssuer Uniquely identifies the financial institution which has issued the identification of the set of data by using a BIC. BICIdentification1 - Required 1..1

ReportPurpose building block

Specifies the type of report. Specifies the type of report. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ReportType1 recursion level 0 with max 1
class ReportType1{
    Type ReportType1Code
}
  

ReportType1 members

Member name Description Data Type / Multiplicity
Type Specifies whether the pushed through baseline is a new one or an amendment or a resubmission. ReportType1Code - Required 1..1

PushedThroughBaseline building block

Specifies the commercial details of the underlying transaction. Specifies the commercial details of the underlying transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Baseline3 recursion level 0 with max 1
class Baseline3{
    ServiceCode TradeFinanceService2Code
    LatestMatchDate IsoISODate
    IntentToPayExpected IsoYesNoIndicator
}
Baseline3 *-- "1..1" DocumentIdentification1 : SubmitterBaselineIdentification
Baseline3 *-- "1..1" DocumentIdentification7 : PurchaseOrderReference
Baseline3 *-- "1..1" PartyIdentification26 : Buyer
Baseline3 *-- "1..1" PartyIdentification26 : Seller
Baseline3 *-- "1..1" BICIdentification1 : BuyerBank
Baseline3 *-- "1..1" BICIdentification1 : SellerBank
Baseline3 *-- "0..0" BICIdentification1 : BuyerSideSubmittingBank
Baseline3 *-- "0..0" BICIdentification1 : SellerSideSubmittingBank
Baseline3 *-- "0..1" PartyIdentification26 : BillTo
Baseline3 *-- "0..1" PartyIdentification26 : ShipTo
Baseline3 *-- "0..1" PartyIdentification26 : Consignee
Baseline3 *-- "1..1" LineItem7 : Goods
Baseline3 *-- "1..0" PaymentTerms1 : PaymentTerms
Baseline3 *-- "0..1" SettlementTerms2 : SettlementTerms
Baseline3 *-- "0..0" PaymentObligation1 : PaymentObligation
Baseline3 *-- "1..1" RequiredSubmission2 : CommercialDataSetRequired
Baseline3 *-- "0..1" RequiredSubmission2 : TransportDataSetRequired
Baseline3 *-- "0..1" RequiredSubmission3 : InsuranceDataSetRequired
Baseline3 *-- "0..0" RequiredSubmission4 : CertificateDataSetRequired
Baseline3 *-- "0..0" RequiredSubmission5 : OtherCertificateDataSetRequired
%% DocumentIdentification1 recursion level 1 with max 1
class DocumentIdentification1{
    Identification IsoMax35Text
    Version IsoNumber
}
DocumentIdentification1 *-- "1..1" BICIdentification1 : Submitter
%% DocumentIdentification7 recursion level 1 with max 1
class DocumentIdentification7{
    Identification IsoMax35Text
    DateOfIssue IsoISODate
}
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% BICIdentification1 recursion level 1 with max 1
class BICIdentification1{
    BIC IsoBICIdentifier
}
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% PartyIdentification26 recursion level 1 with max 1
class PartyIdentification26{
    Name IsoMax70Text
}
PartyIdentification26 *-- "0..1" GenericIdentification4 : ProprietaryIdentification
PartyIdentification26 *-- "1..1" PostalAddress5 : PostalAddress
%% LineItem7 recursion level 1 with max 1
class LineItem7{
    GoodsDescription IsoMax70Text
    PartialShipment IsoYesNoIndicator
    TransShipment IsoYesNoIndicator
    LineItemsTotalAmount IsoCurrencyAndAmount
    TotalNetAmount IsoCurrencyAndAmount
}
LineItem7 *-- "0..1" ShipmentDateRange1 : ShipmentDateRange
LineItem7 *-- "1..0" LineItemDetails7 : LineItemDetails
LineItem7 *-- "0..1" TransportMeans1 : RoutingSummary
LineItem7 *-- "0..0" Incoterms1 : Incoterms
LineItem7 *-- "0..0" Adjustment3 : Adjustment
LineItem7 *-- "0..1" Charge12 : FreightCharges
LineItem7 *-- "0..0" Tax13 : Tax
LineItem7 *-- "0..0" UserDefinedInformation1 : BuyerDefinedInformation
LineItem7 *-- "0..0" UserDefinedInformation1 : SellerDefinedInformation
%% PaymentTerms1 recursion level 1 with max 1
class PaymentTerms1{
    OtherPaymentTerms IsoMax140Text
    Percentage IsoPercentageRate
    Amount IsoCurrencyAndAmount
}
PaymentTerms1 *-- "1..1" PaymentPeriod1 : PaymentCode
%% SettlementTerms2 recursion level 1 with max 1
SettlementTerms2 *-- "0..1" IFinancialInstitutionIdentification4Choice : CreditorAgent
SettlementTerms2 *-- "1..1" CashAccount7 : CreditorAccount
%% PaymentObligation1 recursion level 1 with max 1
class PaymentObligation1{
    Amount IsoCurrencyAndAmount
    Percentage IsoPercentageRate
    ChargesAmount IsoCurrencyAndAmount
    ChargesPercentage IsoPercentageRate
    ExpiryDate IsoISODate
    ApplicableLaw CountryCode
}
PaymentObligation1 *-- "1..1" BICIdentification1 : ObligorBank
PaymentObligation1 *-- "1..1" BICIdentification1 : RecipientBank
PaymentObligation1 *-- "0..0" PaymentTerms2 : PaymentTerms
PaymentObligation1 *-- "0..1" SettlementTerms2 : SettlementTerms
%% RequiredSubmission2 recursion level 1 with max 1
RequiredSubmission2 *-- "1..0" BICIdentification1 : Submitter
%% RequiredSubmission2 recursion level 1 with max 1
RequiredSubmission2 *-- "1..0" BICIdentification1 : Submitter
%% RequiredSubmission3 recursion level 1 with max 1
class RequiredSubmission3{
    MatchIssueDate IsoYesNoIndicator
    MatchTransport IsoYesNoIndicator
    MatchAmount IsoYesNoIndicator
    ClausesRequired InsuranceClauses1Code
    MatchAssuredParty AssuredType1Code
}
RequiredSubmission3 *-- "1..0" BICIdentification1 : Submitter
RequiredSubmission3 *-- "0..1" PartyIdentification27 : MatchIssuer
%% RequiredSubmission4 recursion level 1 with max 1
class RequiredSubmission4{
    CertificateType TradeCertificateType1Code
    MatchIssueDate IsoYesNoIndicator
    MatchInspectionDate IsoYesNoIndicator
    AuthorisedInspectorIndicator IsoYesNoIndicator
    MatchConsignee IsoYesNoIndicator
    LineItemIdentification IsoMax70Text
}
RequiredSubmission4 *-- "1..0" BICIdentification1 : Submitter
RequiredSubmission4 *-- "0..1" PartyIdentification27 : MatchIssuer
RequiredSubmission4 *-- "0..1" PartyIdentification27 : MatchManufacturer
%% RequiredSubmission5 recursion level 1 with max 1
class RequiredSubmission5{
    CertificateType TradeCertificateType2Code
}
RequiredSubmission5 *-- "1..0" BICIdentification1 : Submitter
  

Baseline3 members

Member name Description Data Type / Multiplicity
SubmitterBaselineIdentification Identifies the baseline provided by the submitter. DocumentIdentification1 - Required 1..1
ServiceCode Identifies the service requested by the submitter by means of a code. TradeFinanceService2Code - Required 1..1
PurchaseOrderReference Reference to the purchase order of the underlying transaction. DocumentIdentification7 - Required 1..1
Buyer Party that buys goods or services, or a financial instrument. PartyIdentification26 - Required 1..1
Seller Party that sells goods or services, or a financial instrument. PartyIdentification26 - Required 1..1
BuyerBank Financial institution of the buyer, uniquely identified by its BIC. BICIdentification1 - Required 1..1
SellerBank Financial institution of the seller, uniquely identified by its BIC. BICIdentification1 - Required 1..1
BuyerSideSubmittingBank Financial institution on the buyer’s side, uniquely identified by its BIC. As part of the transaction, it may submit data sets. BICIdentification1 - Unknown 0..0
SellerSideSubmittingBank Financial institution on the seller’s side, uniquely identified by its BIC. As part of the transaction, it may submit data sets. BICIdentification1 - Unknown 0..0
BillTo Party to be invoiced for the purchase. PartyIdentification26 - Optional 0..1
ShipTo Party to whom the goods must be delivered in the end. PartyIdentification26 - Optional 0..1
Consignee Party to whom the goods must be delivered. PartyIdentification26 - Optional 0..1
Goods Goods or services that are part of a commercial trade agreement. LineItem7 - Required 1..1
PaymentTerms Specifies the payment terms by means of a code and a limit in time. PaymentTerms1 - Unknown 1..0
SettlementTerms Specifies how the underlying transaction should be settled. SettlementTerms2 - Optional 0..1
PaymentObligation Specifies the details of the payment obligation between financial institutions in this transaction. PaymentObligation1 - Unknown 0..0
LatestMatchDate Specifies the latest date on which a data set must be matched with a baseline. IsoISODate - Optional 0..1
CommercialDataSetRequired Specifies that a commercial data set is required for each shipment part of the transaction. RequiredSubmission2 - Required 1..1
TransportDataSetRequired Specifies that a transport data set is required for each shipment part of the transaction. RequiredSubmission2 - Optional 0..1
InsuranceDataSetRequired Specifies that an insurance data set is required for each shipment part of the transaction. RequiredSubmission3 - Optional 0..1
CertificateDataSetRequired Specifies that a certificate data set is required for each shipment part of the transaction. RequiredSubmission4 - Unknown 0..0
OtherCertificateDataSetRequired Specifies that another type of certificate data set is required for each shipment part of the transaction. RequiredSubmission5 - Unknown 0..0
IntentToPayExpected Specifies that IntentToPayNotice message(s) are expected as part of this transaction. IsoYesNoIndicator - Required 1..1

BuyerContactPerson building block

Person to be contacted in the organisation of the buyer. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

Member name Description Data Type / Multiplicity
Name Name by which a party is known and which is usually used to identify that party. IsoMax35Text - Required 1..1
NamePrefix Specifies the terms used to formally address a person. NamePrefix1Code - Optional 0..1
GivenName First name of a person. IsoMax35Text - Optional 0..1
Role Role of the party in the activity. IsoMax35Text - Optional 0..1
PhoneNumber Collection of information that identifies a phone number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
FaxNumber Collection of information that identifies a FAX number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
EmailAddress Address for electronic mail (e-mail). IsoMax256Text - Optional 0..1

SellerContactPerson building block

Person to be contacted in the organisation of the seller. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

Member name Description Data Type / Multiplicity
Name Name by which a party is known and which is usually used to identify that party. IsoMax35Text - Required 1..1
NamePrefix Specifies the terms used to formally address a person. NamePrefix1Code - Optional 0..1
GivenName First name of a person. IsoMax35Text - Optional 0..1
Role Role of the party in the activity. IsoMax35Text - Optional 0..1
PhoneNumber Collection of information that identifies a phone number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
FaxNumber Collection of information that identifies a FAX number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
EmailAddress Address for electronic mail (e-mail). IsoMax256Text - Optional 0..1

BuyerBankContactPerson building block

Person to be contacted in the buyer’s bank. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

Member name Description Data Type / Multiplicity
Name Name by which a party is known and which is usually used to identify that party. IsoMax35Text - Required 1..1
NamePrefix Specifies the terms used to formally address a person. NamePrefix1Code - Optional 0..1
GivenName First name of a person. IsoMax35Text - Optional 0..1
Role Role of the party in the activity. IsoMax35Text - Optional 0..1
PhoneNumber Collection of information that identifies a phone number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
FaxNumber Collection of information that identifies a FAX number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
EmailAddress Address for electronic mail (e-mail). IsoMax256Text - Optional 0..1

SellerBankContactPerson building block

Person to be contacted in the seller’s bank. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification1 recursion level 0 with max 1
class ContactIdentification1{
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification1 members

Member name Description Data Type / Multiplicity
Name Name by which a party is known and which is usually used to identify that party. IsoMax35Text - Required 1..1
NamePrefix Specifies the terms used to formally address a person. NamePrefix1Code - Optional 0..1
GivenName First name of a person. IsoMax35Text - Optional 0..1
Role Role of the party in the activity. IsoMax35Text - Optional 0..1
PhoneNumber Collection of information that identifies a phone number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
FaxNumber Collection of information that identifies a FAX number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
EmailAddress Address for electronic mail (e-mail). IsoMax256Text - Optional 0..1

OtherBankContactPerson building block

Person to be contacted in another bank than the seller or buyer’s bank. Information needed to contact a physical person. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ContactIdentification3 recursion level 0 with max 1
class ContactIdentification3{
    BIC IsoBICIdentifier
    Name IsoMax35Text
    NamePrefix NamePrefix1Code
    GivenName IsoMax35Text
    Role IsoMax35Text
    PhoneNumber IsoPhoneNumber
    FaxNumber IsoPhoneNumber
    EmailAddress IsoMax256Text
}
  

ContactIdentification3 members

Member name Description Data Type / Multiplicity
BIC Business Identifier Code to identify the financial institution that the contact person belongs to. IsoBICIdentifier - Required 1..1
Name Name by which a party is known and which is usually used to identify that party. IsoMax35Text - Required 1..1
NamePrefix Specifies the terms used to formally address a person. NamePrefix1Code - Optional 0..1
GivenName First name of a person. IsoMax35Text - Optional 0..1
Role Role of the party in the activity. IsoMax35Text - Optional 0..1
PhoneNumber Collection of information that identifies a phone number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
FaxNumber Collection of information that identifies a FAX number, as defined by telecom services. IsoPhoneNumber - Optional 0..1
EmailAddress Address for electronic mail (e-mail). IsoMax256Text - Optional 0..1

RequestForAction building block

Information on the next processing step required. Specifies the event that require an action from one of the parties to the trade transaction. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% PendingActivity2 recursion level 0 with max 1
class PendingActivity2{
    Type Action2Code
    Description IsoMax140Text
}
  

PendingActivity2 members

Member name Description Data Type / Multiplicity
Type Code which specifies the next course of action that the receiver of the message must take. Action2Code - Required 1..1
Description Further information on the course of action that the receiver of the message must take. IsoMax140Text - Optional 0..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the FullPushThroughReportV03 implementation follows a specific implementaiton pattern. First of all, FullPushThroughReportV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, FullPushThroughReportV03Document implements IOuterDocument. Because FullPushThroughReportV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type FullPushThroughReportV03.

classDiagram
    class IOuterRecord
    FullPushThroughReportV03 --|> IOuterRecord : Implements
    FullPushThroughReportV03Document --|> IOuterDocument~FullPushThroughReportV03~ : Implements
    class IOuterDocument~FullPushThroughReportV03~ {
        FullPushThroughReportV03 Message
     }
  

Document wrapper for serialization

The only real purpose FullPushThroughReportV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsmt.018.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using FullPushThroughReportV03.ToDocument() method. The returned FullPushThroughReportV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    FullPushThroughReportV03Document *-- FullPushThroughReportV03 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:tsmt.018.001.03">
    <FullPushThrghRpt>
        <RptId>
            <!-- ReportIdentification inner content -->
        </RptId>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <EstblishdBaselnId>
            <!-- EstablishedBaselineIdentification inner content -->
        </EstblishdBaselnId>
        <TxSts>
            <!-- TransactionStatus inner content -->
        </TxSts>
        <UsrTxRef>
            <!-- UserTransactionReference inner content -->
        </UsrTxRef>
        <RptPurp>
            <!-- ReportPurpose inner content -->
        </RptPurp>
        <PushdThrghBaseln>
            <!-- PushedThroughBaseline inner content -->
        </PushdThrghBaseln>
        <BuyrCtctPrsn>
            <!-- BuyerContactPerson inner content -->
        </BuyrCtctPrsn>
        <SellrCtctPrsn>
            <!-- SellerContactPerson inner content -->
        </SellrCtctPrsn>
        <BuyrBkCtctPrsn>
            <!-- BuyerBankContactPerson inner content -->
        </BuyrBkCtctPrsn>
        <SellrBkCtctPrsn>
            <!-- SellerBankContactPerson inner content -->
        </SellrBkCtctPrsn>
        <OthrBkCtctPrsn>
            <!-- OtherBankContactPerson inner content -->
        </OthrBkCtctPrsn>
        <ReqForActn>
            <!-- RequestForAction inner content -->
        </ReqForActn>
    </FullPushThrghRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_paNNeNE8Ed-BzquC8wXy7w_-1602880214"
  nextVersions="_9e8ZUdNTEeK-v49t1oWkNA"
  name="FullPushThroughReportV03"
  definition="Scope&#xD;&#xA;The FullPushThroughReport message is sent by the matching application to a party involved in a transaction.&#xD;&#xA;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.&#xD;&#xA;Usage&#xD;&#xA;The FullPushThroughReport message can be sent by the matching application to a party to convey&#xD;&#xA;- the details of an InitialBaselineSubmission message that it has obtained, or&#xD;&#xA;- the details of a BaselineResubmission message that it has obtained, or&#xD;&#xA;- the details of a BaselineAmendmentRequest message that it has obtained."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="FullPushThrghRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_paNNedE8Ed-BzquC8wXy7w_-1602880211"
    nextVersions="_9e8ZU9NTEeK-v49t1oWkNA"
    name="ReportIdentification"
    definition="Identifies the report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_paNNetE8Ed-BzquC8wXy7w_-1602880178"
    nextVersions="_9e8ZVdNTEeK-v49t1oWkNA"
    name="TransactionIdentification"
    definition="Unique identification assigned by the matching application to the transaction.&#xA;This identification is to be used in any communication between the parties."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_P-ile9p-Ed-ak6NoX_4Aeg_745508310" />
  <messageBuildingBlock
    xmi:id="_paNNe9E8Ed-BzquC8wXy7w_-1602879810"
    nextVersions="_9e8ZV9NTEeK-v49t1oWkNA"
    name="EstablishedBaselineIdentification"
    definition="Unique identification assigned by the matching application to the baseline when it is established."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="EstblishdBaselnId"
    complexType="_RJNBwdp-Ed-ak6NoX_4Aeg_-1127047102" />
  <messageBuildingBlock
    xmi:id="_paNNfNE8Ed-BzquC8wXy7w_-1602880093"
    nextVersions="_9e8ZWdNTEeK-v49t1oWkNA"
    name="TransactionStatus"
    definition="Identifies the status of the transaction by means of a code."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TxSts"
    complexType="_RbFb-Np-Ed-ak6NoX_4Aeg_1598523783" />
  <messageBuildingBlock
    xmi:id="_paW-cNE8Ed-BzquC8wXy7w_-1602879793"
    nextVersions="_9e8ZW9NTEeK-v49t1oWkNA"
    name="UserTransactionReference"
    definition="Reference to the transaction for the financial institution which submitted the baseline."
    registrationStatus="Provisionally Registered"
    maxOccurs="2"
    minOccurs="0"
    xmlTag="UsrTxRef"
    complexType="_RJWLsdp-Ed-ak6NoX_4Aeg_-86119846" />
  <messageBuildingBlock
    xmi:id="_paW-cdE8Ed-BzquC8wXy7w_-1602880136"
    nextVersions="_9e8ZXdNTEeK-v49t1oWkNA"
    name="ReportPurpose"
    definition="Specifies the type of report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RptPurp"
    complexType="_RJ8opdp-Ed-ak6NoX_4Aeg_1748144086" />
  <messageBuildingBlock
    xmi:id="_paW-ctE8Ed-BzquC8wXy7w_-1602879673"
    nextVersions="_9e9AYdNTEeK-v49t1oWkNA"
    name="PushedThroughBaseline"
    definition="Specifies the commercial details of the underlying transaction."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="PushdThrghBaseln"
    complexType="_Sq9IZdp-Ed-ak6NoX_4Aeg_-88106768" />
  <messageBuildingBlock
    xmi:id="_paW-c9E8Ed-BzquC8wXy7w_-1602879715"
    nextVersions="_9e9AY9NTEeK-v49t1oWkNA"
    name="BuyerContactPerson"
    definition="Person to be contacted in the organisation of the buyer."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="BuyrCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_paW-dNE8Ed-BzquC8wXy7w_-1602879163"
    nextVersions="_9e9AZdNTEeK-v49t1oWkNA"
    name="SellerContactPerson"
    definition="Person to be contacted in the organisation of the seller."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SellrCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_paW-ddE8Ed-BzquC8wXy7w_-1602879518"
    nextVersions="_9e9AZ9NTEeK-v49t1oWkNA"
    name="BuyerBankContactPerson"
    definition="Person to be contacted in the buyer's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="BuyrBkCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_paW-dtE8Ed-BzquC8wXy7w_-1602879638"
    nextVersions="_9e9AadNTEeK-v49t1oWkNA"
    name="SellerBankContactPerson"
    definition="Person to be contacted in the seller's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SellrBkCtctPrsn"
    complexType="_QBOtE9p-Ed-ak6NoX_4Aeg_-1391367345" />
  <messageBuildingBlock
    xmi:id="_paW-d9E8Ed-BzquC8wXy7w_-595440751"
    nextVersions="_9e9Aa9NTEeK-v49t1oWkNA"
    name="OtherBankContactPerson"
    definition="Person to be contacted in another bank than the seller or buyer's bank."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="OthrBkCtctPrsn"
    complexType="_QDTwsdp-Ed-ak6NoX_4Aeg_-1939165929" />
  <messageBuildingBlock
    xmi:id="_pagIYNE8Ed-BzquC8wXy7w_-1602879750"
    nextVersions="_9e9AbdNTEeK-v49t1oWkNA"
    name="RequestForAction"
    definition="Information on the next processing step required."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="ReqForActn"
    complexType="_RaowBtp-Ed-ak6NoX_4Aeg_-888447978" />
  <messageDefinitionIdentifier
    businessArea="tsmt"
    messageFunctionality="018"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.