element <payment> (local)

Namespace: | http://www.fpml.org/FpML-5/reporting
Type: | PaymentMatching
Content: | complex, 7 elements
Defined: | locally witnin NettedTradeCashflows.model group in fpml-reconciliation-5-3.xsd; see XML source

Content Model Diagram

XML Representation Summary
<payment>
Content: | identifier?, payerPartyReference?, payerAccountReference?, receiverPartyReference?, receiverAccountReference?, paymentAmount?, calculationDetails*
</payment>

Content model elements (7):

  calculationDetails (defined in PaymentMatching complexType),
  identifier (defined in PaymentDetails.model group),
  payerAccountReference,
  payerPartyReference,
  paymentAmount (defined in PaymentDetails.model group),
  receiverAccountReference,
  receiverPartyReference (defined in PayerReceiver.model group)

Included in content model of elements (5):

  allegedCashflow (in nettedTradeCashflowsMatchResult), assertedCashflow (in nettedTradeCashflowsMatchResult), nettedTradeCashflowsAsserted, | nettedTradeCashflowsRetracted, proposedMatch (in nettedTradeCashflowsMatchResult)

Annotation
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.
XML Source (w/o annotations (1); see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="payment" type="PaymentMatching"/>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.