Professional Documents
Culture Documents
FP XML
FP XML
5
Syndicated Loan Product Architecture
Contents
Page | 1
Version 1.5
Version
Page | 2
Version 1.5
1 Syndicated Loan Product Scope
The syndicated loan business working group collectively decided to focus on designing one-way
borrower-centric notifications for the phase 1 release of the standard. These notifications comprise
most of the manual traffic that both agent banks and lenders must process on a daily basis.
In order to fully describe the notifications, it was necessary to design the following supporting
object types, all of which are embedded within various notification types:
• ‘Short-form’ Product Definitions. These are summary objects which, in the future, will
form the foundation for defining the ‘long-form’ loan product:
o Deal Summary
o Facility Summary
• Loan Contract Definitions. These objects describe the value of outstanding loan contracts at
a given point in time. The outstanding loan balance fluctuates over the life of a facility. There
are two variations designed: the short-form summary and the long-form version of the loan
contract:
• Lender Position Definitions. These objects describe the amount of a facility and loan
contract that a single lender owns at a given point in time:
Page | 3
Version 1.5
2 Syndicated Loan Product Overview
A “Credit Agreement” is a legal document which outlines the various financing options available to
the “Borrower(s)” (referred to with the credit agreement). The financing terms are structured within
the document using a set of well-defined products. Within the loan industry a single credit agreement
is referred to as a “Deal”.
Within a deal there are one or more “Facilities”; in effect, each facility is a distinct credit line with
its own notional limit. Within the secondary loan markets these facilities are often referred to as
“Tranches”. In the FpML language, the business group preferred usage of the term, facility.
Each facility can be “Utilized” up its notional limit. Utilization occurs with one or more “Loan
Contracts”. A loan contract is a single instance of an actual borrowing made and is the source for
generating the interest-based cash flows. The sum of the current outstanding loan contracts is what
was previously referred to as the “Utilization Level of the Facility”. The balance of the loan
contracts could be either static, amortizing/increasing over time or fluctuating on an intra-day basis
(depends on the type of facility and the type of loan contract).
Every credit agreement is managed by an “Agent Bank”. The agent bank is responsible for ensuring
correctness of all cash flow to and from the borrower. Syndicated loans of this type are usually
shared between groups of “Lenders”. The agent bank is also responsible for all lender cash flow.
Page | 4
Version 1.5
The diagram below represents the high-level flow within the syndicated loan product. The notices
are used for communication of various business events by the agent bank to the lender community.
Agent Bank
originates Deal
Agent Bank
Syndicates Deal
Notice
Rate Set Notice
Repayment Notice
L/C Balance
Borrower repays
Change Notice
loan
Breakage Fee
(One-Off Fee)
L/C Balance
Borrower Drawdown Notice
Change Notice
redraws loan
3 Overall Architecture
The diagram below provides an overview of the main objects introduced for this version of the
syndicated loan product space.
IdentifiedAsset
Notification
Message
Loan Contract
Facility Notice
Notice
Pricing
Repayment Figure Rollover
2: Syndicated loan On-going
object hierarchy One-off Fee Rate Set Drawd
Change
Notice Notice Fee Notice Notice Notice Noti
Notice
The Loan Contract and Facility Commitment Position objects do not inherit from any existing FpML
structure, since they do not fit into existing definitions of any of the base objects.
LC
LC Issuance LC Balance
Termination
Notice Notice
Notice
Page | 6
Version 1.5
Page | 7
Version 1.5
The Facility Summary is a high-level representation of a single facility within a Deal (credit
agreement).
Page | 8
Version 1.5
The Loan Contract has been defined in both short and long form. Not all aspects have been captured
in each phase but this definition will expand as the standard progresses.
Explanations:
• Although there can be multiple borrower against the loan contract, only the main borrower is
shown for the purposes of loan contract identification.
• It is important to note that only the original amount of the loan contract is represented. This is
the only value that remains constant and can be used for identification purposes.
Page | 9
Version 1.5
This object reflects the full details of the loan contract, as currently defined. Embedded within the
loan contract is the current interest rate period (see next page).
Page | 10
Version 1.5
Explanations:
The loan contract contains a “currentInterestRatePeriod”. This describes the underlying base and
margin rates currently applied to the loan contract. This is core to the definition of the loan contract.
Page | 11
Version 1.5
These objects are used to define the lender position at a given point in time.
Page | 12
Version 1.5
This is an abstract object type that defines all fields which are common to facility-level notifications.
Page | 13
Version 1.5
This template can be used for scheduled, unscheduled (mandatory & voluntary) notices.
Page | 14
Version 1.5
Page | 15
Version 1.5
The on-going fee notification is dependent on the underlying value of the fee margin as well as the
position held by the lender throughout the fee period. The business required us to provide this
information within the Fee Accrual Schedule object, as shown below.
Page | 16
Version 1.5
This notice represents the scenario where one-off payments are made by the borrower. These
payments may be associated with a facility or a specific loan contract or L/C level – the fee type will
determine the level.
The optional loan contract summary provides a possible link for this cash flow to a specific loan
contract.
Page | 17
Version 1.5
Page | 18
Version 1.5
Page | 19
Version 1.5
Page | 20
Version 1.5
The L/C issuance notice is a simple structure containing the entire letter of credit object to together
with the facility notice header.
Page | 21
Version 1.5
Page | 22
Version 1.5
Page | 23
Version 1.5
Page | 24
Version 1.5
Page | 25
Version 1.5
These notices are actions which take place against a specific loan contract. The loan contract notice
generic type contains either the loan contract summary or full definition of the loan contract.
Page | 26
Version 1.5
This is a notification which alerts the lender community of an upcoming loan contract. The notice
covers only a (vanilla) funded loan.
Page | 28
Version 1.5
Figure 22: Interest Payment Notice
Page | 29
Version 1.5
It is important to highlight the Interest Accrual Schedule associated with each interest payment.
Page | 30
Version 1.5
Page | 31
Version 1.5
Page | 32