XML Schema Documentation

Element: tradeCashflowsAsserted

[Table of contents]

Name tradeCashflowsAsserted
Type TradeCashflowsAsserted
Nillable no
Abstract no
Logical Diagram
XML Instance Representation
<tradeCashflowsAsserted
fpmlVersion=" xsd:token (value comes from list: {'5-0'}) [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="9 [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> [0..1]
<validation> Validation </validation> [0..*]
Start Group: Correlation.model [0..1]
<correlationId> CorrelationId </correlationId> [0..1]

'A qualified identifier used to correlate between messages'

End Group: Correlation.model
Start Group: Sequence.model [0..1]
<sequenceNumber> xsd:positiveInteger </sequenceNumber> [0..1]

'A numeric value that can be used to order messages with the same correlation identifier from the same sender.'

End Group: Sequence.model
Start Group: OnBehalfOf.model [0..1]
<onBehalfOf> OnBehalfOf </onBehalfOf> [0..1]

'Indicates which party (and accounts) a trade is being processed for.'

End Group: OnBehalfOf.model
<asOfDate> xsd:dateTime </asOfDate> [0..1]

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

<reportContents> ReportContents </reportContents> [0..1]

'The specific characteristics included in the report.'

<tradeCashflowsId> TradeCashflowsId </tradeCashflowsId> [0..1]

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

<tradeIdentifyingItems> TradeIdentifyingItems </tradeIdentifyingItems> [0..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> [0..1]

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

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

'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> [0..*]

'A legal entity or a subdivision of a legal entity.','Parties can perform multiple roles in a trade lifecycle. For example, the principal parties obligated to make payments from time to time during the term of the trade, but may include other parties involved in, or incidental to, the trade, such as parties acting in the role of novation transferor/transferee, broker, calculation agent, etc. In FpML roles are defined in multiple places within a document.'

<account> Account </account> [0..*]

'Optional account information used to precisely define the origination and destination of financial instruments.'

</tradeCashflowsAsserted>
Diagram
Schema Component Representation
<xsd:element name="tradeCashflowsAsserted" type=" TradeCashflowsAsserted "/>