# XML Schema Documentation

### Complex Type: TradeCashflowsAsserted

#### [Table of contents]

Super-types: | NotificationMessage < TradeCashflowsAsserted (by extension)
Sub-types: | None

Name | TradeCashflowsAsserted
Abstract | no
Documentation | Message for assertion of payments to be reconciled. Notification message that submits cashflows that need to be reconciled per payment date at the trade level.

XML Instance Representation
<...
version=" xsd:token (value comes from list: {'4-0'|'4-1'|'4-2'|'4-3'|'4-4'|'4-5'}) [1]

'Indicate which version of the FpML Schema an FpML message adheres to.'

"
expectedBuild=" xsd:positiveInteger [0..1]

'This optional attribute can be supplied by a message creator in an FpML instance to specify which build number of the schema was used to define the message when it was generated.'

"
actualBuild="1 [0..1]

'The specific build number of this schema version. This attribute is not included in an instance document. Instead, it is supplied by the XML parser when the document is validated against the FpML schema and indicates the build number of the schema file. Every time FpML publishes a change to the schema, validation rules, or examples within a version (e.g., version 4.2) the actual build number is incremented. If no changes have been made between releases within a version (i.e. from Trial Recommendation to Recommendation) the actual build number stays the same.'

">
<header> NotificationMessageHeader </header> [1]
<validation> Validation </validation> [0..*]
<asOfDate> xsd:dateTime </asOfDate> [0..1]

'The date and time at which the set of cashflows was defined.'

<tradeCashflowsId> TradeCashflowsId </tradeCashflowsId> [1]

'Unique identifier assigned by the party asserting the set of cashflows to be reconciled.'

<tradeIdentifyingItems> TradeIdentifyingItems </tradeIdentifyingItems> [1]

'Structure that holds reference to the trade through the tradeId and optionally some trade-specific elements for identifying the trade in the case of trades that have not been negotiated through electronic platforms and for which the counterparty\'s trade ID has not been captured.'

<adjustedPaymentDate> xsd:date </adjustedPaymentDate> [1]

'The adjusted date in which the payments are being paid/received.'

<payment> PaymentMatching </payment> [1..*]

'Specifies the payment that is exposed to the matching process. Usually there will be a single payment but for cross-currency swaps a different payment per currency shall be provided.'

<matchId> MatchId </matchId> [0..1]

'A unique identifier assigned by either party, or matching service, as agreed, to each set of matched cashflows.'

<party> Party </party> [2..*]

'One party element for each of the principal parties and any other party that is referenced.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="TradeCashflowsAsserted">
<xsd:complexContent>
<xsd:extension base=" NotificationMessage ">
<xsd:sequence>
<xsd:group ref=" TradeCashflowsDefinition.model "/>
<xsd:group ref=" TradeCashflows.model "/>
<xsd:element name="matchId" type=" MatchId " minOccurs="0"/>
<xsd:element name="party" type=" Party " minOccurs="2" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>