The FpML specifications provided are without warranty of any kind, either expressed or implied, including, without limitation, warranties that FpML, or the FpML specifications are free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the specifications is with you. Should any of the FpML specifications prove defective in any respect, you assume the cost of any necessary servicing or repair. Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall ISDA, any of its members, or any distributor of documents or software containing any of the FpML specifications, or any supplier of any of such parties, be liable to you or any other person for any indirect, special, incidental, or consequential damages of any character including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages.
This is the FpML 5.5 Recommendation for review by the public and by FpML members and working groups.
The FpML Working Groups encourage reviewing organizations to provide feedback as early as possible. Comments on this document should be sent by filling in the form at the following link: http://www.fpml.org/issues. An archive of the comments is available at http://www.fpml.org/issues/
There are also asset class-specific mailing lists; you can join them at the following link:
Most diagrams in this specification come from TIBCO's XML Turbo application which is used to batch generate the pictures in the documentation. The notation follows the pattern:
No bubble indicates a mandatory element or attribute
A '?' indicates an optional element or attribute
A '*' indicates an occurrence of zero or many
A '+' indicates an occurrence of one or many
A '..' bubble with numbers above and below indicates specific range
A '1' in a bubble indicates the presence of a nested sequence or choice group
Diagonal lines indicate a choice group (< shape)
Non-diagonal lines indicate a sequence ([ shape)
A 'D' in a bubble indicates an attribute with a default value
The Financial Products Markup Language (FpML) is the industry standard enabling e-business activities in the field of financial derivatives and structured products. The development of the standard, controlled by ISDA (the International Swaps and Derivatives Association), will ultimately allow the electronic integration of a range of services, from electronic trading and confirmations to portfolio specification for risk analysis. All types of over-the-counter (OTC) derivatives will, over time, be incorporated into the standard.
FpML is an application of XML, an internet standard language for describing data shared between computer applications.
The FpML Reporting Working Group has defined two new views, "Transparency" and "Recordkeeping", to support parties and execution facilities reporting trading activity into Swaps Data Repositories (SDRs), as required by the Commodities Futures Trading Commission's 17 CFR 43 and 45, and similar requirements from the Securities and Exchange Commission in 17 CFR 240. The FpML Standards Committee invites comments on the proposed materials including schemas, examples, and documentation.
In WD#2, a number of new products have been added to Transparency view. The changes versus Confirmation view have been modeled on other products in WD#1, but the product representations have not yet been reviewed in detail in the working group. The FpML Reporting Working Group invites feedback on the detailed contents in Transparency view of any product.
1.5.2 Message Framework/Correlation ID
The FpML Business Process Working Group has adjusted the multiplicity of the correlation IDs and is seeking feedback on this change. In particular, is there a need for multiple correlation IDs if the correlation ID on original requests is made optional?
1.5.3 Providing Feedback
Comments on this document should be sent by filling in the form at the following link: http://www.fpml.org/issues.
1.6.2 Incompatible changes compared to FpML 5.4 - build#5
CorrelationId:
In Confirmation, Reporting, Recordkeeping and Transparency Views - > fpml-msg.xsd - > within "CorrelationId": replaced the base class "xsd:normalizedString" with “Scheme” which restricts the "xsd:normalizedString" to maxLength value="255".
Commodity Derivatives:
Recordkeeping View –> fpml-com-xsd -> within "SettlementPeriods" complex type: the "startDate" element's status changed from "optional" to "mandatory". Rational:Fix - to prevent the submission of the "endDate" without the "startDate". The change was agreed by the Commodity WG and approved by the Standards Committee (March-11-2013)
1.6.3 Changes compared to FpML 5.4 Recommendation
Addition of a New Pre-trade View:
Business Process:
Added a set of Credit Limit Check messages to support Clearing Certainty work flows.
Added support for IRS and CDS products in pretrade. Expanded coverage of IRS product scope for pre-trade Credit Limit Check work flows, including Non deliverable settlement, cross currency swaps, asset swaps, averaging, stubs and discounting structures.
The scope of FpML 5.5 includes broadened BusinessProcess/Messaging coverage and additional product support, specifically:
1.7.1 Architecture Framework
The various Working Groups have developed FpML 5.5 within the FpML Architecture 3.0 Specification defined by the Architecture Working Group. This document defines that standards and principles on which the FpML grammatical definitions are based.
The FpML Architecture 3.0 builds upon the earlier FpML Architecture specifications and the conventions of FpML 1.02b before that. The refinement of the FpML architecture is an evolutionary process bought about by changes in the XML technology upon which it is based and the requirements of the standard as its scope expands.
1.7.2 Business Process Scope
The FpML Messaging Task Force group was formed to define a new messaging framework in 5.x that insures consistent processes across trades and post-trade events, observable completion, consistent message correlation, consistent error reporting, consistent correction and retraction.
Most of the FpML 5 business processes are “generic” processes that can apply to new trades and/or any post-trade events. This means that the message name indicates the business process (e.g. confirmation, execution notification, etc.) but not the type of event (e.g. trade, amendment, etc.). The payload of the message indicates the type of the event.
The business processes currently supported in this view include:
All the processes described in this section are applied to the following events:
trade
novation
increase
termination
amendment
option exercise / option expiry
deClear
basketChange
corporateAction
indexChange
To support these business processes, a number of messages have been defined. Please see the "Business Process Architecture" section for more information.
1.7.3 Validation Scope
The Validation Working Group provides semantic, or business-level validation rules for FpML 5.5. These validation rules, which are aimed at normalizing the use of elements within FpML, are issued as part of the FpML Specification in the validation section of this document.
The validation working group publishes with its releases:
A set of rules described in English
Positive and negative test case documents for each rule
Non-normative reference implementations
The current specification includes a set of rules for Interest Rate Derivatives, Equity Derivatives, Credit Derivatives, Loans, FX, and for shared components. The rules for the different asset classes will be further enhanced in future versions.
1.7.4 IRD Scope
In FpML 5.5 Recommendation the following Interest Rate Derivative products are covered:
Single and Cross-Currency Interest Rate Swap
Forward Rate Agreement
Interest Rate Cap
Interest Rate Floor
Interest Rate Swaption (European, Bermuda and American Styles; Cash and Physical Settlement)
Extendible and Cancelable Interest Rate Swap Provisions
Mandatory and Optional Early Termination Provisions for Interest Rate Swaps
FX Resetable Cross-Currency Swap
1.7.5 Credit Derivatives Scope
In FpML 5.5 Recommendation the following Credit Derivative products are covered:
Producers of FpML documents intended for interchange with other parties must encode such documents using either UTF-8 or UTF-16. Consumers of FpML documents must be able to process documents encoded using UTF-8, as well as documents encoded using UTF-16. For more information, see
Certain elements and attributes (such as scheme URIs) are defined with more restrictive types, such as xsd:normalizedString, xsd:token, or xsd:anyURI. For these types, please see the relevant data type definition in the XML Schema datatypes specification:
The schema files and examples in this document have been validated with XercesJ (v.2.2.1 and v.2.6.2) and HandCoded's Toolkit for FpML Processing (version Java 1.1 Alpha 2).