XML Schema Documentation

Complex Type: InterestPaymentNotice

[Table of contents]

Super-types: NotificationMessage < LoanContractNotice (by extension) < InterestPaymentNotice (by extension)
Sub-types: None
Name InterestPaymentNotice
Abstract no
Documentation A notice defining the payment requested by the agent bank from each lender for given interest accrual period for a given loan contract.
XML Instance Representation
<...
version=" xsd:token (value comes from list: {'4-0'|'4-1'|'4-2'|'4-3'|'4-4'}) [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="12 [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..*]
<noticeDate> xsd:date </noticeDate> [1]

'The date on which the notice was generated.'

<agentBankPartyReference> PartyReference </agentBankPartyReference> [0..1]

'A reference to the agent bank for the given deal.'

<borrowerPartyReference> PartyReference </borrowerPartyReference> [0..1]

'A reference to the borrower against the associated loan contract(s).'

<lenderPartyReference> PartyReference </lenderPartyReference> [0..1]

'A reference to the lender(s) associated with the associated loan contract(s).'

<dealSummary> DealSummary </dealSummary> [1]

'A data structure which contains the identifying characteristics of the given deal.'

<facilitySummary> FacilitySummary </facilitySummary> [1]

'A data structure which contains the identifying characteristics of the given facility.'

<facilityCommitmentPosition> FacilityCommitmentPosition </facilityCommitmentPosition> [0..1]

'A structure which contains the position being held by the lender on both the facility and loan contract levels. This position information is from the message sender\'s viewpoint as of the date of the associated notice.'

<exceptionFlag> xsd:boolean </exceptionFlag> [0..1]

'A flag which can be set by the message sender in order to signify an exceptional business event.'

<comments> xsd:string </comments> [0..1]

'A free-form, manually entered field which will be used by users directly for additional information.'

Start Choice [1]

'The sender may choose to either transmit the full or partial loan contract details.'


<loanContract> LoanContract </loanContract> [1]

'A core structure describing a loan contract between borrower and lenders forming part or all of the credit line offered by a facility structure within a deal.'

<loanContractSummary> LoanContractSummary </loanContractSummary> [1]

'A basic set of fields used to uniquely identify the loan contract.'

End Choice
<interestPayment> InterestPayment </interestPayment> [1]

'Represents the total amount of interest paid by the borrower to the agent bank and the share of it paid to the lender.'

<interestAccrualSchedule> InterestAccrualSchedule </interestAccrualSchedule> [1]

'A schedule that incorporates all sub-periods of an interest accrual calculation.'

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

'The parties involved with the associated transaction.'

</...>
Diagram
Schema Component Representation
<xsd:complexType name="InterestPaymentNotice">
<xsd:complexContent>
<xsd:extension base=" LoanContractNotice ">
<xsd:sequence>
<xsd:element name="interestPayment" type=" InterestPayment "/>
<xsd:element name="interestAccrualSchedule" type=" InterestAccrualSchedule "/>
<xsd:element name="party" type=" Party " minOccurs="2" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>