FpML® Financial product Markup Language Last Call Working Draft 2 May 2014 (Confirmation View)

Version: 5.7

This version: http://www.fpml.org/spec/fpml-5-7-3-lcwd-1

Latest version: http://www.fpml.org/spec/fpml-5-7-3-lcwd-1

Previous version: http://www.fpml.org/spec/fpml-5-7-2-wd-2/

Errata for this version: http://www.fpml.org/spec/fpml-5-7-3-lcwd-1/html/confirmation/fpml-5-7-errata.html

Build Number: 3; Document built: Wed 04/23/2014 1:16:08.73

Copyright (c) 1999 - 2014 by International Swaps and Derivatives Association, Inc.

Financial Products Markup Language is subject to the FpML® Public License.

FpML® is a registered trademark of the International Swaps and Derivatives Association, Inc.

A copy of this license is available at http://www.fpml.org/license/license.html



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.



1 INTRODUCTION AND OVERVIEW

1.1 STATUS OF THIS DOCUMENT

This is the FpML 5.7 Last Call Working Draft 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:

Join a Working Group at FpML

A list of current FpML Recommendations and other technical documents can be found at

http://www.fpml.org/spec

This document has been produced as part of the FpML 5.7 activity and is part of the Standards Approval Process.

1.2 ORGANIZATION OF THE DOCUMENTATION

The FpML documentation is organized into a number of subsections.

This section provides an overview of the specification.

1.2.1 Schema Reference

These are automatically generated reference documents detailing the contents of the various sections in the FpML schema.

1.2.2 Other Documents in the Specification

1.2.3 Diagram Notation

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

images/main/BaseType.jpg

images/main/DerivedType.jpg

This document was produced by the following working groups:

1.3.1 Architecture Working Group
  • Andrew Jacobs (HandCoded Software), chair
  • Anthony B. Coates (Miley Watts)
  • Igor Dayen (Object Centric Solutions)
  • Daniel Dui (University College London)
  • Marc Gratacos (ISDA)
  • Simon Heinrich (IONA Technologies)
  • Lyteck Lynhiavu (ISDA)
  • Andrew Parry (JP Morgan Chase Bank)
  • Raj Patel (HSBC)
  • Henri Pegeron (MarkitSERV)
  • Matthew Rawlings (JP Morgan Chase Bank)
  • John Weir (Goldman Sachs)
  • Irina Yermakova (ISDA)

1.3.2 Business Process Working Group
  • Brian Lynn (Global Electronic Markets), chair
  • Andrew Jacobs (HSBC)
  • Claire Lobo (MarkitSERV)
  • Darcy Baber (LCH)
  • David Kempster (Morgan Stanley)
  • Devansh Rastogi (DTCC)
  • Dibyendu Majumdar (LCH)
  • Harry McAllister (BNPP)
  • Henri Pegeron (Sapient)
  • Jaskiran Dhillon (MarkitSERV)
  • John Booth (MarkitSERV)
  • Katrina Bell (TrueEX)
  • Leon Shor (DTCC)
  • Liz Scott (DTCC)
  • Mia Colasuonno (DTCC)
  • Mike Anthony (Bank New York Mellon)
  • Niranjana Sharma (CME)
  • Shawn Kelly (ARK EDI Solutions)
  • Simone Milani-Foglia (LCH)
  • Sivagami Gomathinayagam (DTCC)
  • Sreedhar Segu (Deutsche Bank)
  • Sudipto Haldar (Morgan Stanley)
  • Ted Brooks (MarkitSERV)
  • Vijay Addanki (State Street)
  • Yuval Kost (Traiana)
  • Irina Yermakova (ISDA)
  • Lyteck Lynhiavu (ISDA)
  • Marc Gratacos (ISDA)

1.3.3 Regulatory Reporting Working Group
  • Brian Lynn (Global Electronic Markets), chair
  • Ahfan Chan (JPMorgan)
  • Andrew Jacobs (HSBC)
  • Avneesh Dutta (Citi)
  • David Kempster (Morgan Stanley)
  • Devansh Rastogi (DTCC)
  • Harry McAllister (BNP Paribas)
  • Henri Peregon (Sapient)
  • John Booth (MarkitSERV)
  • Jonathan Elliot (MarkitSERV)
  • Justin Roy (Deutsche Bank)
  • Leon Shor (DTCC)
  • Liz Scott (DTCC)
  • Lynn Callahan (Treasury)
  • Martin Sexton (London Market Systems)
  • Mia Colasuonno (DTCC)
  • Naima Zerrouki (Societe Generale)
  • Niranjana Sharma (CME)
  • Peter Schulze (Citi)
  • Peter Stockman (Deep River Group)
  • Shawn Kelly (ARK EDI Solutions)
  • Stephen White (Fidelity)
  • Steve Goswell (Incept5)
  • Sreedhar Segu (Deutsche Bank)
  • Tony Coates (Deutsche Bank)
  • Venkat Krishnasamy (JPMorgan)
  • Karel Engelen (ISDA)
  • Lyteck Lynhiavu (ISDA)
  • Marc Gratacos (ISDA)
  • Irina Yermakova (ISDA)

1.3.4 Validation Working Group
  • Andrew Jacobs (HSBC, HandCoded Software), co-chair
  • Daniel Dui (Barclays Capital and UCL), co-chair
  • Tony Coates (UBS)
  • Andrew Dingwall-Smith (Message Automation)
  • Marc Gratacos (ISDA)
  • Lyteck Lynhiavu (ISDA)
  • Irina Yermakova (ISDA)

1.3.5 IRD Products Working Group
  • Harry McAllister (BNP Paribas), chair
  • John Aldridge (JP Morgan Chase Bank)
  • Marc Gratacos (ISDA)
  • Robert Green (DTCC)
  • Guy Gurden (MarkItSERV)
  • Pierre Lamy (Goldman Sachs)
  • Philippe Negri (Sungard)
  • Jamie Orme (Goldman Sachs)
  • Andrew Parry (JP Morgan Chase Bank)
  • Marty Ross-Trevor (Bank of Tokyo-Mitsubishi)
  • Marc Teichman (ICE)
  • Jeff Valentino (Bank of America)
  • Irina Yermakova (ISDA)

1.3.6 Credit Derivatives Working Group
  • John Booth (MarkitSERV), chair
  • Kathy Andrews (Bank of America)
  • Milla Bouklieva (Goldman Sachs)
  • Karel Engelen (ISDA)
  • Piers Evans (MarkitSERV)
  • Marc Gratacos (ISDA)
  • Robert Green (DTCC)
  • Guy Gurden (MarkitSERV)
  • Tony Kao (Goldman Sachs)
  • Lyteck Lynhiavu (ISDA)
  • Pierre Lamy (Goldman Sachs)
  • Anna Lukasiak (Goldman Sachs)
  • Andrew Parry (JPMorgan Chase Bank)
  • Henri Pegeron (Sapient)
  • Mark Perry (Goldman Sachs)
  • Ben Lis (ICE)
  • Marc Teichman (ICE)
  • Irina Yermakova (ISDA)
  • Shel Xu (Goldman Sachs)

1.3.7 FX Working Group
  • Richard Haslock (Marit Serv), chair
  • Andrew Gregory (HSBC)
  • Andrew Jacobs (HSBC)
  • Brian Lynn (GEM)
  • Christina Yeung (Goldman Sachs)
  • Harry McAllister (BNP Paribas)
  • Irina Yermakova (ISDA)
  • Lyteck Lynhiavu (ISDA)
  • Marc Gratacos (ISDA)
  • Stephen Turner (JP Morgan Chase)
  • Vijay Addanky (State Street)

1.3.8 Equity Derivatives Working Group

Voting Members

  • Andrew Parry (JP Morgan Chase Bank), Chair
  • Jasone Brasil (State Street)
  • James Clark (MarkItSERV)
  • Piers Evans (MarkItSERV)
  • Robert Green (DTCC)
  • Guy Gurden (MarkItSERV)
  • Shabbir Irfani (Goldman Sachs)
  • Rajan Khorana (Citadel Group)
  • Robert Masri (DTCC)
  • Coner Mongey
  • Bin Shen (Goldman Sachs)
  • Marc Teichman (ICE)

Non-Voting Members

  • Takeo Asakura (MarkItSERV)
  • Oluwasegun Bewaji (University of Essex)
  • Jim Bonner (ML)
  • Tom Brown (Omgeo)
  • Jim Brous (Metro Solutions)
  • Prashant Choudhary (Cognizant)
  • Karel Engelen (ISDA)
  • Philip Franz (Bank of America)
  • Steve Goswell (Barclays Global)
  • Marc Gratacos (ISDA)
  • Vinod Jain (Headstrong)
  • Lucio Iida (Barclays Global)
  • Selma Laidoudi (MarkItSERV)
  • Philip Leach (DTCC)
  • Jianan Li (Citadel Group)
  • Gaurav Makhija (Citadel Group)
  • Mark Parris (UBS)
  • Dharmender Rai
  • Matthew Rawlings
  • Sreedhar Segu (DTCC)
  • Alicia Szybillo (DTCC)
  • Sam Twum (Blue Tawny)
  • Chise Yamamoto (DTCC)
  • Irina Yermakova (ISDA)

1.3.9 Commodity Derivatives Working Group
  • Andrew Jacobs (HSBC), co-chair
  • Peter Stockman (DTCC), co-chair
  • Andrew Solomon (Morgan Stanley)
  • Brian Lynn (GEM)
  • Fred Litjens (Murex)
  • Irina Yermakova (ISDA)
  • Jyoti Sahrawat (CME Group)
  • Kent Tung(Goldman Sachs)
  • Lyteck Lynhiavu (ISDA)
  • Marc Gratacos (ISDA)
  • Ronan Hughes (HSBC)
  • Susan Helfter (Credit Suisse)
  • Timothy Capuano (Goldman Sachs)

1.3.10 Pricing and Risk Working Group
  • Brian Lynn (Global Electronic Markets), chair
  • Michael Di Stefano (Integrasoft)
  • Amod Dixit (Standard Chartered Bank)
  • Marc Gratacos (ISDA)
  • Mahmood Hanif (Bank of America)
  • Pierre Lamy (Goldman Sachs)
  • Philippe Negri (Sungard)
  • Henrik Nilsson (TriOptima)
  • Robert Stowsky (Progress)
  • Vlad Efroimson (Bank of America)
  • Irina Yermakova (ISDA)

1.3.11 Collateral Working Group
  • Richard Barton (Algorithmics), Chair
  • Caroline Foran (HSBC)
  • Anil Panchal (GlobeOp)
  • Kaizad Bhathena (GlobeOp)
  • Sammy Lee (GlobeOp)
  • Harry McAllister (BNP Paribas)
  • Jesse Nolan (UBS)
  • Vivian Wu (Goldman Sachs)
  • Simone Milani-Foglia (LCH Clearnet)
  • Nicole Jolliffe (SWIFT)
  • Evelyne Piron (SWIFT)
  • Chip Miller (JPMorgan)
  • John Straley (DTCC)
  • Joe Novellino (DB)
  • Lucio Iida (Blackrock)
  • Tom Brown (Omgeo)
  • Benjamin Riley (Deloitte and Touche)
  • Marc Gratacos (ISDA)
  • Irina Yermakova (ISDA)
  • Lyteck Lynhiavu (ISDA)

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.

1.5.1 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.1 Changes compared to FpML 5.7 Second Working Draft (build#2)
  • Credit Derivatives:
    • Added additional support for 2014 ISDA Credit Derivatives Definitions: an optional Boolean indicator standardReferenceObligation within the existing ReferenceObligation component. It indicates if the reference obligation is a Standard Reference Obligation. ISDA 2014 Term: Standard Reference Obligation.
  • Business Process:
    • Enhanced Package Transactions representation:
      • Updated examples and schemes.
      • Within the packageHeader, added package type, size and originatingEvent
      • Within the tradeHeader, added originatingPackage including package id, size and sequence number: these will provide more information about the originating package and how this trade relates to it once the trade is separated from the package.
      • Pretrade view: Within tradePackage/allocations, added the “allocatingPartyReference” and changed the multiplicity of the allocations element to allow up to 2 instances of it
    • Partial termination of a TRS – Added an id attribute to the equity derivative “ActualPrice” type to allow price references to be made to it (See example #100 in confirmation/business-processes/execution-advice of a partial termination of a TRS)
    • Reporting:
      • Entity Classification: Within the reportingRegime, added partyEntityClassification as an improved way to relate an entity classification to a party (e.g., Financial/NonFinancial, Dealer/NonDealer, LocalParty/NonLocalParty)
      • Within the reportingRegime, added tradePartyRelationshipType to specify intragroup (ESMA), inter-affiliate (CSA). (See recordkeeping examples ex140, ex141, ex142)
      • Removed the now redundant intragroup flag introduced in WD1. Renamed isCompressedTrade to compressedTrade.
    • Confirmation view: Correction: Made ReportingRegime/supervisorRegistration optional when reportingRegime/Name is supplied. It had been made mandatory in Confirmation view in error since version 5.3. The original intention under recordkeeping was to mandate the existence of at-least-one-of (name, supervisorRegistration).
    • Predetermined Clearing: renamed specifiedClearingOrganizationPartyReference to predeterminedClearingOrganizationPartyReference to match last agreed working group documents/emails.
  • The following issues have been resolved:
  • View PDF for details on schema changes

    View PDF for details on validation rules changes

    View SCHEME DEFINITIONS for details on coding schemes changes

1.6.2 Changes compared to FpML 5.6 Recommendation (build#5)
  • Commodity Derivatives:
    • Added support for Commodity Performance Swap, a swap in which the payout(s) are based on the price performance of an index rather than the price level of the index. Current support price performance metrics include price return and price variance.
    • Enhanced the CommoditySwaption and commodityOption/commodityForward models to include a field indicating the pre-determined clearing organization for the resulting swap created due from swaption exercise. This change has been approved by the CommWG – see the minutes from Sep-18-2013's meeting.
  • Credit Derivatives:
    • Added support for 2014 ISDA Credit Derivatives Definitions:
      • Within 'CreditEvents', added 'governmentalIntervention' credit event.
      • Added an optional Boolean indicator standardReferenceObligation within the existing ReferenceObligation component. It indicates if the reference obligation is a Standard Reference Obligation. ISDA 2014 Term: Standard Reference Obligation.
    • Added support for Credit index swaps quoted using price: Added 'marketPrice' to 'feeLeg' in fpml-cd.xsd and 'price' to 'quotationStyleEnum' enumeration
    • Enhanced the CreditDefaultSwapOption model to include a field indicating the pre-determined clearing organization for the resulting swap created due from swaption exercise. This change has been approved by the CDWG – see the minutes from Mar-26-2014's meeting.
  • Interest Rate Derivatives:
    • Fixed incorrect 'PaymentCalculationPeriod' type's derivation introduced in FpML-4-6 as part of the rationalization of the 'Payment' type hierarchy. The 'PaymentCalculationPeriod' is not a type of Payment so derivation from 'PaymentBase' is inappropriate. Within 'PaymentCalculationPeriod' complex type, removed derivation from 'PaymentBase'.
    • Updated ird-ex33-BRL-CDI-swap.xml example to reflect the current market practice as defined in the 2009 ISDA/EMTA recommendation for BRL CDI Non-Deliverable swaps.
      • Added the futureValueNotional component
      • Revised term start and end-dates
      • Replaced business center collection (BRBR, BRRJ, BRSP) with single value BRDB
      • Corrected fixing days offset
    • Enhanced the Swaption model to include a field indicating the pre-determined clearing organization for the resulting swap created due from swaption exercise.
  • Equity Derivatives:
    • Enhanced the DividendSwapOptionTransactionSupplement and VarianceOptionTransactionSupplement models to include a field indicating the pre-determined clearing organization for the resulting swap created due from swaption exercise.
  • Business Process:
    • Package Transactions - Refined the "tradePackage" representation (a bundle or package of trades executed and cleared as part of a single transaction). Note: Package Transactions are available in Confirmation, Pretrade, and Reporting views. Regulatory reporting would be at the granular level, not at the package level. For pre-trade view, the list of supported products include CDS, IRS and FX NDF.
      • Within the packageHeader, added package type, size and originatingEvent
      • Within the tradeHeader, added originatingPackage including package id, size and sequence number: these will provide more information about the originating package and how this trade relates to it once the trade is separated from the package.
    • For post trade events (increases, terminations, novations) added support for a size change of a notional schedule, not just a single value
    • For post trade events (increases, terminations, novations) added support for a price change to support resetting during the event.
    • Added support for partial exercises on trades with multiple notionals (of various types)
    • Created examples of approvals of allocations (clearing/msg-ex20)
    • Enhanced the consent business process to allow more information about approvals to be captured. (see confirmation examples consent/msg-ex400 and msg-ex401)
    • Added support for "clearing instructions" to the physicaly settled options (CreditDefaultSwapOption, CommoditySwaption, DividendSwapOptionTransactionSupplement, VarianceOptionTransactionSupplement) that specifies any instructions on how the physical settlement is to be effected when the option is exercised.
    • Partial termination of a TRS – Added an id attribute to the equity derivative “ActualPrice” type to allow price references to be made to it (See example #100 in confirmation/business-processes/execution-advice of a partial termination of a TRS)
  • Reporting:
    • Joint and Several Liable Parties: Refined support for multiple legal entities with joint and several liability
      • Within party, added a groupType flag (JointAndSeveralLiability) followed by several party references.
      • Within party, removed jointAndSeveralLiability added in the first working draft.
    • Added a Facility Execution flag to indicate whether the particular product must be executed on a SEF or DCM.
      • Within reporting regime, added a mandatoryFacilityExectution flag and additional elements to specify whether the party invoked exception to not execute the trade on facility such as SEF and DCM even though the particular product is mandated to execute on a SEF.
    • Added to reduce the overuse of the category element:
      • Within partyTradeInformation, compressedTrade - Specifies whether this trade is a result of compression activity.
    • Entity Classification: Within the reportingRegime, added partyEntityClassification as an improved way to relate an entity classification to a party (e.g., Financial/NonFinancial, Dealer/NonDealer, LocalParty/NonLocalParty)
    • Within the reportingRegime, added tradePartyRelationshipType to specify intragroup (ESMA), inter-affiliate (CSA). (See recordkeeping examples ex140, ex141, ex142)
    • Confirmation view: Correction: Made ReportingRegime/supervisorRegistration optional when reportingRegime/Name is supplied. It had been made mandatory in Confirmation view in error since version 5.3. The original intention under recordkeeping was to mandate the existence of at-least-one-of (name, supervisorRegistration).
    • Predetermined Clearing: renamed specifiedClearingOrganizationPartyReference to predeterminedClearingOrganizationPartyReference to match last agreed working group documents/emails.
  • Shared:
    • Schema clean-up as per standards' recomendation
      • Removed orphan types

1.6.3 Incompatible changes compared to FpML 5.6 (build#5)

None.

The scope of FpML 5.7 includes broadened BusinessProcess/Messaging coverage and additional product support, specifically:

1.7.1 Architecture Framework

The various Working Groups have developed FpML 5.7 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:

1.7.2.1 Generic processes:
1.7.2.1.1 Post-trade
  • Execution notification (for platforms to report order fills)
  • Execution advice (to report executions and settlement info to service providers)
  • Allocation
  • Confirmation
  • Consent negotiation
  • Clearing
  • Clearing Eligibility
  • Status reporting
1.7.2.2 Generic (Multi-Event) Flows

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
  • tradePackage (a bundle or package of trades executed and cleared as part of a single transaction). The tradePackage representation and examples have been refined in WD2. Note: Package Transactions are available in Confirmation, Pretrade, and Reporting views. Regulatory reporting would be at the granular level, not at the package level. For pre-trade view, the list of supported products include CDS, IRS and FX NDF.

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.7. 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.7 Last Call Working Draft 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.7 Last Call Working Draft the following Credit Derivative products are covered:

  • Credit Default Swap
  • Standard Coupon Credit Default Swap
  • Credit Default Swap Index
  • Tranche on Credit Default Swap Index
  • Credit Default Swap Basket
  • Credit Default Swap on a Mortgage
  • Credit Default Swap on a Loan
  • Option on Credit Default Swap
  • Credit Event Notice

1.7.6 FX Scope

The Scope of FpML 5.7 Last Call Working Draft includes redesigned FX product model developed by the Modeling Task Force (MTF) and FX Working Group to make it more consistent with other FpML product representations and to facilitate its further development. As a result of this work many of an original 4.x model’s issues were addressed:

  • A number of sets of reusable components that facilitates product development were defined, so that the existing and future FX products will leverage these building blocks to ensure the FX model is coherent and easy to maintain, as per FpML best practices
  • Extended the existing coverage to include Dual Currency Deposits and FX Flexible Forward.
  • Rationalized the models' constraints:
    • Made use of grammar to bring related data together.
    • Made better use of XML schema to simplify the validation rules.

In FpML 5.7 Last Call Working Draft the following FX products are covered:

  • Basic FX Products
    • FX Spot, FX Forward (including non-deliverable settlements, or NDFs) and FX Flexible Forward.
    • FX Swap
  • Simple FX Option Products (including, features, cash and physical settlement)
    • FX options
      • European and American
      • Averaging
      • Barriers
    • Digital Options
  • Option Strategies (multiple simple options)

In addition, support for the following money market instrument is also provided:

  • Term Deposits (including features)
    • Money Market Deposits
    • Dual Currency

1.7.7 Equity Derivative Options and Forwards Scope

The EQD Products Working Group has extended the FpML standard to cover the following Equity Derivative products

  • Broker Equity Options;
  • Long Form Equity Forwards;
  • Long Form Equity Options;
  • Short Form Equity Options represented as Transaction Supplements under ISDA Master Confirmation Agreements.

1.7.8 Return Swaps Scope

FpML provides generic Return Swaps support including "long form" Equity Swap representations, as well as Total Return Swaps. A separate product element called equitySwapTransactionSupplement supports "short form" Equity Swap Transaction Supplement.

Return-type Swaps have 1-to-many Legs, all of which must be derived from the ReturnSwapLeg type. Instances of Legs are returnLeg, interestLeg. Other Leg types may be derived from ReturnSwapLeg at will, to allow for private extensions to support whatever type of Generic Return Swap is desired.

The scope of this FpML representation for return swaps is to capture the following types of swaps that have equity-related underlyers:

  • Single stock swaps as well as basket swaps (i.e. swaps with multiple underlyers);
  • Swaps that have a different types of underlying assets (equity, index, mutual funds, exchange-traded funds, convertible bond, futures), or a combination of these;
  • 2-legged swaps with a combination of an equity leg and a funding leg, as well as swaps that either have only one leg (e.g. fully funded or zero-strike swap) or multiple equity legs (e.g. outperformance swaps);
  • Total Return Swaps, a type of swap in which one party (total return payer) transfers the total economic performance of a reference obligation to the other party (total return receiver).
  • Swaps that have specific adjustment conditions, such as execution swaps or portfolio rebalancing swaps;
  • Swaps that involve the exchange of principal cashflows;
  • Swaps that have inital and final stubs;
  • Swaps which can be represented as Transaction Supplements under ISDA Master Agreements;

Extraordinary Events terms have been incorporated, to take into consideration the release of the 2002 ISDA Definitions for Equity Derivatives.

Trigger swaps, in which equity risk morphs into a fixed income risk once a certain market level is reached, may be supported in a subsequent release.

1.7.9 Correlation Derivatives Scope

The Equity Derivative Working Group extended FpML to cover:

  • Correlation Swaps

1.7.10 Variance Derivatives Scope

The Equity Derivative Working Group extended FpML to cover:

  • Variance Swaps, a type of volatility swap where the payout is linear to variance rather than volatility, therefore the payout will rise at a higher rate than volatility;
  • Short Form Variance Options represented also as Transaction Supplements under ISDA Master Confirmation Agreements.

1.7.11 Dividend Derivatives Scope

The Equity Derivative Working Group extended FpML to cover:

  • Dividend Swap Transaction Supplement

1.7.12 Commodity Derivative Product Scope

The Commodities Working Group will extend the FpML standard to include trade types and products for the OTC commodities markets, following the structure and coverage of the 2005 ISDA Commodity Definitions. The following are included in version 5-7:

  • Support for financially settled swaps, options and spreads
  • Support for physically-settled swaps/forwards, options
  • Natural Gas, Oil, Electricity, Coal, Metal, Environmental as the underlying Commodity product
  • Gold Interest Rate Swap (Official Name: Gold Forward Offered Rate)

Business Process is including Confirmations, Valuations, Reporting

1.8.1 Character Encoding

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

http://www.w3.org/TR/REC-xml#charencoding

1.8.2 Character Repertoire

Unrestricted FpML elements may use any valid XML characters. For more information, see

http://www.w3.org/TR/REC-xml#charsets

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:

http://www.w3.org/TR/xmlschema-2/

1.9.1 Schema and Example Validation

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).

Top of Section Next