XML Schema Documentation

Super-types:	NotificationMessage < FacilityNotice (by extension) < OneOffFeeNotice (by extension)
Sub-types:	None

Name	OneOffFeeNotice
Abstract	no
Documentation	There are cases where the borrower may be required to make a one-off fee payment. This will usually be based on a certain business event occurring. The rules as to how much is charged will be stated in the credit agreement. The only fee type covered in this section is amendment Fee: A fee charged to the borrower for an amendment being made to the originally agreed credit agreement. The fee is based on a rate (as stated in the agreement) applied to the current commitment level.

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="4 [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]

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

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

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

<dealIdentifier> DealIdentifier </dealIdentifier> [1]

<facilityIdentifier> FacilityIdentifier </facilityIdentifier> [1]

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

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

'Manually-entered field which will be used by human users only.'

<loanContractIdentifier> LoanContractIdentifier </loanContractIdentifier> [0..1]

<feePayment> OneOffFeePayment </feePayment> [1]

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

</...>

Schema Component Representation

<xsd:complexType name="OneOffFeeNotice">

<xsd:complexContent>

<xsd:extension base=" FacilityNotice ">

<xsd:sequence>

<xsd:element name="loanContractIdentifier" type=" LoanContractIdentifier " minOccurs="0"/>

<xsd:element name="feePayment" type=" OneOffFeePayment "/>

<xsd:element name="party" type=" Party " minOccurs="2" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Generated by <oXygen/> XML Editor using a modified version of xs3p that adds schema diagrams and chunking support.

Complex Type: OneOffFeeNotice

[Table of contents]