# XML Schema Documentation

### Complex Type: TradeCashflowsProposedMatch

#### [Table of contents]

Super-types: | None
Sub-types: | None

Name | TradeCashflowsProposedMatch
Used by (from the same schema document) | Complex Type TradeCashflowsMatchResult
Abstract | no
Documentation | "Other side's" cashflow that meets the minimimum matching criteria and is proposed as match to the cash flow that is being asserted.

XML Instance Representation
<...>
<tradeCashflowsId> TradeCashflowsId </tradeCashflowsId> [1]

'Unique identifier assigned by either party to a set of cashflows.'

Start Group: TradeCashflows.model [0..1]
<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.'

End Group: TradeCashflows.model
<matchId> MatchId </matchId> [1]

'A unique identifier assigned by the matching service to each set of matched cashflows.'

<difference> TradeDifference </difference> [0..*]

'A type used to record the details of a difference between two sides of a payment.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="TradeCashflowsProposedMatch">
<xsd:sequence>
<xsd:group ref=" IdAndTradeCashflows.model "/>
<xsd:element name="matchId" type=" MatchId "/>
<xsd:element name="difference" type=" TradeDifference " minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>