All Element Summary |
||||||||||
A notation to indicate whether the report being made relates to : (a) a Reportable Transaction that is an entry into of an arrangement that is a Derivative, in which case the notation must be "new"; (b) a Reportable Transaction that is a modification of an arrangement that is a Derivative, in which case the notation must be "modify"; (c) a Reportable Transaction that is a termination of an arrangement that is a Derivative, in which case the notation must be "cancel"; or (d) a compression of a Derivative, in which case the notation must be "compression".
|
||||||||||
Reports a regulator-specific code for the action associated with this submission.
|
||||||||||
Describes the type of event to the transaction (e.g., new transaction, modification or cancellation of existing transaction, etc.).
|
||||||||||
Reports a regulator-specific code for the action associated with this submission.
|
||||||||||
SFTR notation to indicate whether the report is New, Modification, Valuation, Collateral update, Error, Correction, Termination / Early Termination or Position component
|
||||||||||
|
||||||||||
|
||||||||||
When the details of the event were agreed.
|
||||||||||
Identifies the party responsible for executing the allocation for the counterparty
|
||||||||||
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
|
||||||||||
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
|
||||||||||
All the regulators to which this trade should be reported.
|
||||||||||
|
||||||||||
The date for which this document reports positions and valuations.
|
||||||||||
The date for which this document reports positions and valuations.
|
||||||||||
The time for which this report was generated (i.e., the cut-off time of the report).
|
||||||||||
The time for which this report was generated (i.e., the cut-off time of the report).
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
cleared (in cftc_part43_2012) |
|
|||||||||
cleared (in cftc_part43_2019) |
|
|||||||||
|
||||||||||
Indicator of whether the transaction has been cleared, or is intended to be cleared, by a central counterparty.
|
||||||||||
Specifies whether the reporting party takes a Principal or an Agent role in this trade.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Indicator of whether the collateral portfolio includes transactions exempt from reporting.
|
||||||||||
Identifies the types of collateral that may be posted according to the CSA.
|
||||||||||
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||||
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||||
For new reportable transactions (as defined by the CPMI-IOSCO Technical Guidance: Harmonisation of the Unique Transaction Identifier), whether the legally binding terms of an OTC derivatives contract were documented and agreed upon (confirmed) or not (unconfirmed).
|
||||||||||
Indicatdes the CFTC Contract type.
|
||||||||||
ESMA prodcut classification
|
||||||||||
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
|
||||||||||
Identifies the type of clearing exemption that the Counterparty 2 has elected (if not indicated previously).
|
||||||||||
Indicates whether the counterparty is in the European Economic Area
|
||||||||||
whether the counterparty is a US person
|
||||||||||
whether the counterparty is a US person
|
||||||||||
E.g.
|
||||||||||
E.g.
|
||||||||||
The revised state of the trade or its final state for a lifecycle ending event
|
||||||||||
|
||||||||||
|
||||||||||
Reports a regulator-specific code classifying the currency pair in the trade into risk categories such as Major Currencies or Emerging Markets.
|
||||||||||
ESMA delivery type
|
||||||||||
|
||||||||||
|
||||||||||
Effective date of the early termination (expiry) of the reported transaction.
|
||||||||||
When the event is actually effective from
|
||||||||||
|
||||||||||
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. wehter there is an exemption from clearing.
|
||||||||||
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. wehter there is an exemption from clearing.
|
||||||||||
Claims an end user exception and provides supporting evidence.
|
||||||||||
Claims an end user exception and provides supporting evidence.
|
||||||||||
Specifies a reason that the trade is exempted from a clearing requirement.
|
||||||||||
Specifies a reason that the trade is exempted from a clearing requirement.
|
||||||||||
When the agreed details where recorded.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
A unique event identifier.
|
||||||||||
Individual parties should only use a single event identifier to identify a retraction.
|
||||||||||
Various timestamps related to the event.
|
||||||||||
Explanation for the action being take on the transaction.
|
||||||||||
Indicate whether the transaction resulted from a post-transaction service (e.g. compression, reconciliation, etc.) or from a lifecycle event (e.g. novation, amendment, etc.).
|
||||||||||
A structured code indicating the event type.
|
||||||||||
Indicates whether the counterparty exceeds the volume threshold above which trades are required to be cleared.
|
||||||||||
Specifies 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.
|
||||||||||
Provides supporting evidence when a 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.
|
||||||||||
When the event was executed.
|
||||||||||
Used to describe how the trade was executed, e.g. via voice or electronically.
|
||||||||||
Used to describe how the trade was executed, e.g. via voice or electronically.
|
||||||||||
|
||||||||||
|
||||||||||
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
|
||||||||||
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
|
||||||||||
Unadjusted date as per the contract, by which all transfer of cash or assets should take place and the counterparties should no longer have any outstanding obligations to each other under that contract.
|
||||||||||
Indicates if the trade is now fully withdrawn from all regulatory reports.
|
||||||||||
Standard FpML message header
|
||||||||||
|
||||||||||
Indicates which regulation the trade is to withdrawn from.
|
||||||||||
index (in underlyer in esma_emirRts_2015) |
|
|||||||||
|
||||||||||
instrumentId (in underlyer in esma_emirRts_2015) |
|
|||||||||
Specifies whether the trade is anticipated to be allocated.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Identifies which party is electing the inter-affiliate exmption to the clearing requirement pursuant to section 50.52
|
||||||||||
If the Reporting Entity is not an Australian ADI, an AFS Licensee, a CS Facility Licensee, an Exempt Foreign Licensee or a Foreign ADI, an indication of whether the Derivative to which the Reportable Transaction relates is entered into by the Reporting Entity for the purpose of managing a financial risk that arises in the ordinary course of business.
|
||||||||||
Whether the transaction reduces risk in an objectively measurable way.
|
||||||||||
Whether the transaction reduces risk in an objectively measurable way.
|
||||||||||
Indicates if this message corrects an earlier submission.
|
||||||||||
Whether the transaction falls within the scope of activity but is exempted from reporting under [Securities Financing Transactions Regulation]
|
||||||||||
|
||||||||||
|
||||||||||
Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting.
|
||||||||||
Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting.
|
||||||||||
The date of the most recent sampling of the floating reference for the purposes of determining cashflow.
|
||||||||||
Whether the particular trade type in question is required by this regulator to be cleared.
|
||||||||||
Whether the particular trade type in question is required by this regulator to be cleared.
|
||||||||||
|
||||||||||
|
||||||||||
maturityDate (in underlyer in esma_emirRts_2015) |
|
|||||||||
maturityDate (in underlyer in esma_emirRts_2015) |
|
|||||||||
Indicates whether the swap is a mixed swap as defined by CFTC Part 45 (i.e. subject to reporting to both CFTC and SEC).
|
||||||||||
Indicates whether the swap is a multi-asset swap as defined by CFTC Part 45.
|
||||||||||
name (in index in underlyer in esma_emirRts_2015) |
|
|||||||||
The nearest date in the future that the floating reference resets on
|
||||||||||
Non public execution report message.
|
||||||||||
Acknowledgement message for nonpublicExecutionReport.
|
||||||||||
Exception message for nonpublicExecutionReport.
|
||||||||||
Retraction message for nonpublicExecutionReport.
|
||||||||||
Indicates that the price does not reflect the current market.
|
||||||||||
Indicates that the price does not reflect the current market.
|
||||||||||
Indicates which party (or parties) (and accounts) a trade or event is being processed for.
|
||||||||||
Indicates which party (or parties) (and accounts) a trade or event is being processed for.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Indicator of whether the package in which this trade was traded includes transactions exempt from reporting.
|
||||||||||
|
||||||||||
|
||||||||||
The supporting party definitions.
|
||||||||||
Reference information about parties, business units, and persons involed in the trade.
|
||||||||||
The supporting party definitions.
|
||||||||||
Payments in settlement of the event
|
||||||||||
|
||||||||||
|
||||||||||
The asset class of the underlying product.
|
||||||||||
Pricing information for the trade.
|
||||||||||
|
||||||||||
|
||||||||||
All the regulations that this trade should be reported under.
|
||||||||||
Regulatory disclosure message used for reporting to trade repositories.
|
||||||||||
Used to report that a regulatory reporting message (e.g. regulatory disclosure or withdrawal) was processed successfully, and the status of reporting to any regulators.
|
||||||||||
Used to report that a regulatory reporting message was not processed successfully, and the reasons for that.
|
||||||||||
Message used to request withdrawal from one or more jurisdictions.
|
||||||||||
relatedParty (defined in RelatedPartyAndPerson.model group) |
This may be used to identify one or more parties that perform a role within the transaction.
|
|||||||||
This may be used to identify one or more parties that perform a role within the transaction.
|
||||||||||
|
||||||||||
relatedPerson (defined in RelatedPartyAndPerson.model group) |
Provides information about a person that executed or supports this trade
|
|||||||||
An indication whether the report is done at trade or position level.
|
||||||||||
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
|
||||||||||
Identifies the type of clearing exemption that the Counterparty 1 has elected (if not indicated previously).
|
||||||||||
E.g.
|
||||||||||
E.g.
|
||||||||||
reportingPurpose (defined in ReportingRoleAndPurpose.model group) |
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
|
|||||||||
reportingRole (defined in ReportingRoleAndPurpose.model group) |
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
|
|||||||||
Information about how the position is being reported to regulators.
|
||||||||||
Upcoming important dates for the trade.
|
||||||||||
seniority (in creditDetails in esma_emirRts_2015) |
|
|||||||||
DEPRECATED.
|
||||||||||
Classification of the transaction as a short sale or not and, if short, of the type of transaction.
|
||||||||||
The type of Special entity/utility special entity that is reported by the reporting counterparty as per Section 23.401(c) and Section 1.3 (ggg)(4)(i)(B)(2), respectively.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The regulator or other supervisory body the organization is registered with (e.g.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
supervisoryBody (in other) |
The regulator or other supervisory body the organization is registered with (e.g.
|
|||||||||
|
||||||||||
|
||||||||||
The revised state of the trade or its final state for a lifecycle ending event
|
||||||||||
Whether the particular product must be executed on a SEF or DCM.
|
||||||||||
The data element will indicate if the swap is subject to the trade execution requirement under CEA section 2(h)(8).
|
||||||||||
|
||||||||||
identifies the affected trade
|
||||||||||
identifies the affected trade
|
||||||||||
Indicates how the parties to the trade (the counterparties) are related to each other with respect to this reporting regime, e.g.
|
||||||||||
This is provided to support snapshot reporting that requires trading history.
|
||||||||||
This is provided to support snapshot reporting that requires trading history.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
Classification of the pre-trade waiver, if any, that the transaction was executed under.
|
||||||||||
|
||||||||||
|
||||||||||
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||||
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation.
|
||||||||||
|
||||||||||
|
Complex Type Summary |
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The base type which all regulatory classification types extend.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
A type that defines a message to be used for reporting non-public information to a regulator, typically via a trade repository or other reporting service.
|
||||||||||
A type defining an acknowledgement to a regulatory reporting submission, e.g. regulatoryDisclosure or regulatoryWithdrawal.
|
||||||||||
A type defining the basic content for a message sent to inform another system that some exception has been detected in a regulatory reporting message.
|
||||||||||
|
||||||||||
A type defining the message used to request withdrawal from one or more jurisdictions.
|
Element Group Summary |
||||||||||
|
||||||||||
|
||||||||||
|
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2022-2023 All rights reserved. == Financial Products Markup Language is subject to the FpML public license. == A copy of this license is available at http://www.fpml.org/license/license.html --> <xsd:schema attributeFormDefault="unqualified" ecore:documentRoot="FpML" ecore:nsPrefix="" ecore:package="org.fpml.recordkeeping" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/recordkeeping" version="$Revision: 7629 $" xmlns="http://www.fpml.org/FpML-5/recordkeeping" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="fpml-reg-reporting-shared-5-13.xsd"/>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-contract-type" name="contractTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-credit-seniority" name="creditSeniorityScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="Scheme">
</xsd:simpleContent>
<xsd:attribute default="http://www.fpml.org/coding-scheme/esma-delivery-type" name="deliveryTypeScheme" type="NonEmptyURI"/>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:choice>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
</xsd:choice>
<xsd:choice>
</xsd:choice>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:element minOccurs="0" name="agreementDate" type="xsd:date">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation/>
</xsd:complexType>
<xsd:choice>
</xsd:choice>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="asOfDate" type="IdentifiedDate">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date for which this document reports positions and valuations.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The time for which this report was generated (i.e., the cut-off time of the report).
</xsd:documentation>
<xsd:annotation>
</xsd:group>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Allows a reference to porftfolio request to be included, such as a portfolio compression request. NOTE: this is an element that is under assessment and may not be available in a subsequent working draft.
</xsd:documentation>
<xsd:sequence>
</xsd:choice>
<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Upcoming important dates for the trade. Added to support CFTC Amendments to Part 43/45 (Published November 2020).
</xsd:documentation>
<xsd:element maxOccurs="2" minOccurs="0" name="collateralization" type="RegulatoryReportingCollateralization"/>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="NonCorrectableRequestMessage">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:choice minOccurs="0">
</xsd:choice>
<xsd:sequence>
</xsd:choice>
<xsd:element minOccurs="0" name="originatingEvent" type="OriginatingEvent"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This is provided to support snapshot reporting that requires trading history. Some implementations are using the "trade" event to report the current snapshot of a contract. In these cases it may also be necessary to report the most recent trading event to support regulatory reporting mandates. For this reason the tradingEvent is provided to allow that event to be attached to the trade report.
</xsd:documentation>
<xsd:element minOccurs="0" name="primaryAssetClass" type="AssetClass"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Individual parties should only use a single event identifier to identify a retraction. Platforms providing services on behalf of both parties in a transaction may provide event identifiers for both parties; in this case it is up to the recipient (the trade repository) to validate that the event IDs refer to the same event.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:group minOccurs="0" ref="RegulatoryBuyerAndSeller.model"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Unadjusted date as per the contract, by which all transfer of cash or assets should take place and the counterparties should no longer have any outstanding obligations to each other under that contract. For products that may not have a final contractual settlement date (eg American options), this data element reflects the date by which the transfer of cash or asset would take place if termination were to occur on the expiration date.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Effective date of the early termination (expiry) of the reported transaction. This data element is applicable if the termination of the transaction occurs prior to its maturity due to an ex-interim decision of a counterparty (or counterparties). Examples of early terminations (expiry) are: negotiated early termination; early termination under an optional early termination provision ("mutual put"); novation; offsetting (netting) transaction; option exercise; compression; early termination clause specified in the original contract which is a callable swap (bought embedded option); mutual credit break.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicator of whether the transaction has been cleared, or is intended to be cleared, by a central counterparty.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
For new reportable transactions (as defined by the CPMI-IOSCO Technical Guidance: Harmonisation of the Unique Transaction Identifier), whether the legally binding terms of an OTC derivatives contract were documented and agreed upon (confirmed) or not (unconfirmed). If documented and agreed, whether such confirmation was done: - via a shared confirmation facility or platform, or a private/bilateral electronic system (electronic); - via a human-readable written document, such as fax, paper or manually processed e-mails (non-electronic).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:sequence>
</xsd:complexType>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:element minOccurs="0" name="cftc_part43_2012" type="RegulatoryClassification.Part43_2012"/>
</xsd:sequence>
<xsd:element minOccurs="0" name="esma_mifirRts6a_2015" type="RegulatoryClassification.MifirRTS6a_2015"/>
<xsd:element minOccurs="0" name="esma_mifirRts6b_2015" type="RegulatoryClassification.MifirRTS6b_2015"/>
<xsd:element minOccurs="0" name="esma_mifirRts22_2015" type="RegulatoryClassification.MifirRTS22_2015"/>
<xsd:element minOccurs="0" name="esma_mifirRts23_2015" type="RegulatoryClassification.MifirRTS23_2015"/>
<xsd:element minOccurs="0" name="esma_mifirRts24_2015" type="RegulatoryClassification.MifirRTS24_2015"/>
<xsd:element minOccurs="0" name="csa_derivativesReporting_2016" type="RegulatoryClassification.CSA_2016"/>
<xsd:element minOccurs="0" name="asic_derivativesTransactionRules_2013" type="RegulatoryClassification.ASIC_2013"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="other" type="RegulatoryClassification.Other"/>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The base type which all regulatory classification types extend.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A notation to indicate whether the report being made relates to : (a) a Reportable Transaction that is an entry into of an arrangement that is a Derivative, in which case the notation must be "new"; (b) a Reportable Transaction that is a modification of an arrangement that is a Derivative, in which case the notation must be "modify"; (c) a Reportable Transaction that is a termination of an arrangement that is a Derivative, in which case the notation must be "cancel"; or (d) a compression of a Derivative, in which case the notation must be "compression". For the purposes of subrule 2.2.2(1), a notation to indicate whether the change relates to: (a) a cancellation of a report previously made in error, in which case, the notation must be "error"; (b) a change or update to the information referred to in items 30-32 (mark-to-market, mark-to-model, or other valuation) or items 40-44 (collateral), in which case the notation must be "valuation update"; or (c) any other amendments to a report previously made, in which case the notation must be "other".
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
If the Reporting Entity is not an Australian ADI, an AFS Licensee, a CS Facility Licensee, an Exempt Foreign Licensee or a Foreign ADI, an indication of whether the Derivative to which the Reportable Transaction relates is entered into by the Reporting Entity for the purpose of managing a financial risk that arises in the ordinary course of business.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Describes the type of event to the transaction (e.g., new transaction, modification or cancellation of existing transaction, etc.). TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Indicate whether the transaction resulted from a post-transaction service (e.g. compression, reconciliation, etc.) or from a lifecycle event (e.g. novation, amendment, etc.). TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="SupervisoryBody.EMIR">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The regulator or other supervisory body the organization is registered with (e.g. ESMA).
</xsd:documentation>
<xsd:element minOccurs="0" name="tradePartyRelationshipType" type="PartyRelationshipType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates how the parties to the trade (the counterparties) are related to each other with respect to this reporting regime, e.g. Affiliated, Intragroup, etc..
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code for the action associated with this submission. Used, for example, to report the ESMA action type.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates whether the counterparty exceeds the volume threshold above which trades are required to be cleared.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates the category or classification or business role of the organization referenced by the partyTradeInformation with respect to this reporting regime, for example Financial, NonFinancial etc.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates whether the counterparty is in the European Economic Area
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:sequence>
</xsd:extension>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element name="supervisoryBody" type="SupervisoryBody">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The regulator or other supervisory body the organization is registered with (e.g. SEC).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the transaction falls within the scope of activity but is exempted from reporting under [Securities Financing Transactions Regulation]
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Classification of the pre-trade waiver, if any, that the transaction was executed under. Note: Coding scheme to encapsulate: Articles 4 and 9 of Regulation (EU) 600/2014. e.g. default="http://www.fpml.org/coding-scheme/esma-mifir-trading-waiver"
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Classification of the transaction as a short sale or not and, if short, of the type of transaction. Note: Coding scheme to encapsulate: Article 11 of Regulation (EU) 600/2014. e.g. default="http://www.fpml.org/coding-scheme/esma-mifir-short-sale"
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the transaction reduces risk in an objectively measurable way. Only applicable for commodity derivative transactions.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Whether the transaction reduces risk in an objectively measurable way. Only applicable for commodity derivative transactions.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code classifying the currency pair in the trade into risk categories such as Major Currencies or Emerging Markets.
</xsd:documentation>
<xsd:element fpml-annotation:deprecated="true" fpml-annotation:deprecatedReason="Use instead the field within credit products: indexReferenceInformation/seniority" minOccurs="0" name="seniority" type="CreditSeniority">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
DEPRECATED. Use instead the field within credit products: indexReferenceInformation/seniority (RPTWG decision 2017-09)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:group>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates that the price does not reflect the current market. For example, in a credit trade where the two counterparties are not of equal credit standing, there is no initial margin and one party pays collateral to the other in the form of an add-on to the price (say a price that would otherwise be 100 at the market is struck at 105 to include the collateral, resulting in a very off-market looking price.)
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:element minOccurs="0" name="mandatorilyClearable" type="ReportingBoolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the particular trade type in question is required by this regulator to be cleared.
</xsd:documentation>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:sequence>
</xsd:choice>
<xsd:element minOccurs="0" name="endUserException" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. wehter there is an exemption from clearing. For historical reasons this is called "end-user exception", but this may be used to indication any exception from normal clearing mandates caused by the type of the partiees or their relationship, such as inter-affiliate trades. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="endUserExceptionReason" type="ClearingExceptionReason">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies a reason that the trade is exempted from a clearing requirement. This exemption may be an end-user exception, or another type such as in inter-affiliate trade.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Claims an end user exception and provides supporting evidence. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting. Normally this will only be applicable for off-facility trades.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation. This affect the timing of real-time reporting requirements. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation. This affects the process flow for confirmation messages. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the party responsible for executing the allocation for the counterparty
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates whether the swap is a multi-asset swap as defined by CFTC Part 45.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates whether the swap is a mixed swap as defined by CFTC Part 45 (i.e. subject to reporting to both CFTC and SEC).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="supervisoryBody" type="xsd:token"/>
</xsd:sequence>
<xsd:element minOccurs="0" name="mandatorilyClearable" type="ReportingBoolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the particular trade type in question is required by this regulator to be cleared.
</xsd:documentation>
<xsd:choice minOccurs="0">
</xsd:sequence>
<xsd:sequence>
</xsd:choice>
<xsd:element minOccurs="0" name="endUserException" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is not obligated to be cleared via a derivative clearing organization, i.e. wehter there is an exemption from clearing. For historical reasons this is called "end-user exception", but this may be used to indication any exception from normal clearing mandates caused by the type of the partiees or their relationship, such as inter-affiliate trades. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="endUserExceptionReason" type="ClearingExceptionReason">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies a reason that the trade is exempted from a clearing requirement. This exemption may be an end-user exception, or another type such as in inter-affiliate trade.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Claims an end user exception and provides supporting evidence. If a relatedParty block with a role of ClearingExceptionParty is present, that related party indicates which party is claiming the end user exception.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the sender of this trade considers it to be a large notional trade or block trade for reporting purposes, and thus eligible for delayed public reporting. Normally this will only be applicable for off-facility trades.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was executed, e.g. via voice or electronically.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe the type of venue where trade was executed, e.g via an execution facility or privately.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was or will be verified, e.g via a confirmation facility, via private electronic service, or via written documentation. This affect the timing of real-time reporting requirements. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to describe how the trade was confirmed, e.g via a confirmation facility, via private electronic service, or via written documentation. This affects the process flow for confirmation messages. This field is provisional pending detailed confirmation of the data requirements, and may not be included in subsequent working drafts.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the trade is anticipated to be allocated, has been allocated, or will not be allocated.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies whether the reporting party takes a Principal or an Agent role in this trade.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies which party is electing the inter-affiliate exmption to the clearing requirement pursuant to section 50.52
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reportingPartyClearingExemption" type="xsd:token">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the type of clearing exemption that the Counterparty 1 has elected (if not indicated previously). All applicable exceptions and exemption must be selected. The values may be repeacted as applicable. TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="counterPartyClearingExemption" type="xsd:token">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the type of clearing exemption that the Counterparty 2 has elected (if not indicated previously). All applicable exceptions and exemption must be selected. The values may be repeacted as applicable. TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the types of collateral that may be posted according to the CSA. TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:element minOccurs="0" name="collateralPortfolioContainsNonReportableComponents" type="xsd:boolean">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicator of whether the collateral portfolio includes transactions exempt from reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicator of whether the package in which this trade was traded includes transactions exempt from reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The type of Special entity/utility special entity that is reported by the reporting counterparty as per Section 23.401(c) and Section 1.3 (ggg)(4)(i)(B)(2), respectively. Note that "utility special entity" is a subset of "special entity." TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reports a regulator-specific code for the action associated with this submission. Used, for example, to report the ESMA action type. TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Explanation for the action being take on the transaction. TBD: FpML doesn’t currently define a coding scheme for this value. We anticipate that one will be developed in a future release.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The data element will indicate if the swap is subject to the trade execution requirement under CEA section 2(h)(8). If the swap is subject to an exemption from CEA section 2(h)(8)(a), this data element shall be populated with the value "False".
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date of the most recent sampling of the floating reference for the purposes of determining cashflow. Ties to "Last Floating Reference Value" field.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The nearest date in the future that the floating reference resets on
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="RegulatoryClassification">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:group minOccurs="0" ref="ReportingRoleAndPurpose.model"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
An indication whether the report is done at trade or position level.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
SFTR notation to indicate whether the report is New, Modification, Valuation, Collateral update, Error, Correction, Termination / Early Termination or Position component
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type that defines a message to be used for reporting non-public information to a regulator, typically via a trade repository or other reporting service. CAVEAT: This new regulatory reporting message set is supported by the FpML Standards Committee, and will be present in future versions of the standard. However, there is no absolute guarantee of backward compatibility with future versions of the standard, until such time as the Standards Committee deems that the message set has been extensively adopted in production. The Standards Committee will attempt to maintain full backward compatibility with this version while adjusting as required to take into account implementation experience with the message set. The Standards Committee advises that the areas where there is more likely to be change include the applicableRegulatiorns section, the regulatorionSpecificInformation section, and the regulatoryProductInformation product, which is developed as part of this reporting framework. Feedback or questions can be addressed to ISDA at rptwgchair@fpml.org.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="isCorrection" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates if this message corrects an earlier submission. If true, the recipient is directed to record information about the most recent lifecycle event affecting the trade as a correction of the previous submission, rather than as a new lifecycle event.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Also, in the context of a trade package there could be several parties for which limit check is requested, necessitating multiple onBehalfOf elements. Except for these cases, there should be no more than two onBehalfOf references in a message.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The date for which this document reports positions and valuations.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The time for which this report was generated (i.e., the cut-off time of the report).
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
All the regulators to which this trade should be reported. Optional, can be infeerred from the list of regulations to which the trade is submitted.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
All the regulations that this trade should be reported under.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The revised state of the trade or its final state for a lifecycle ending event
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The revised state of the trade or its final state for a lifecycle ending event
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="2" minOccurs="0" name="collateralization" type="RegulatoryReportingCollateralization">
<xsd:annotation/>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining an acknowledgement to a regulatory reporting submission, e.g. regulatoryDisclosure or regulatoryWithdrawal.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="Message">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="header" type="ResponseMessageHeader">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Information about how the position is being reported to regulators.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Reference information about parties, business units, and persons involed in the trade.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation xml:lang="en">
</xsd:annotation>
A type defining the basic content for a message sent to inform another system that some exception has been detected in a regulatory reporting message.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="Message">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element minOccurs="0" name="header" type="ExceptionMessageHeader">
</xsd:sequence>
<xsd:annotation/>
</xsd:element>
<xsd:annotation/>
</xsd:complexType>
<xsd:element name="tradedOnVenue" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Whether the particular product must be executed on a SEF or DCM. See to Dodd-Frank section 723(a)(8).
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Specifies 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.
</xsd:documentation>
<xsd:element minOccurs="0" name="exceptionDeclaration" type="FacilityExecutionExceptionDeclaration">
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides supporting evidence when a 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.
</xsd:documentation>
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
A type defining the message used to request withdrawal from one or more jurisdictions.
</xsd:documentation>
<xsd:complexContent>
<xsd:extension base="AddressedMessage">
</xsd:complexContent>
<xsd:sequence>
</xsd:extension>
<xsd:element maxOccurs="4" minOccurs="0" name="onBehalfOf" type="OnBehalfOf">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Indicates which party (or parties) (and accounts) a trade or event is being processed for. Normally there will only be a maximum of 2 parties, but in the case of a novation there could be a transferor, transferee, remaining party, and other remaining party. Also, in the context of a trade package there could be several parties for which limit check is requested, necessitating multiple onBehalfOf elements. Except for these cases, there should be no more than two onBehalfOf references in a message.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Indicates which regulation the trade is to withdrawn from. At least one child element must be selected.
</xsd:documentation>
<!-- requested action? ( retain records, purge records ) -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Indicates if the trade is now fully withdrawn from all regulatory reports. This can be used by a trade repository to perform a consistency check. For instance, if "fullyWithdrawn" is "true" but the TR believes that the trade is still reportable to at least one regulator, it could report an exception with the identity of that regulator. Or if "fullyWithdrawn" is false but the TR believes that the trade is no longer reportable to any regulator, the TR should report that fact.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation/>
</xsd:group>
<xsd:element minOccurs="0" name="contractType" type="ESMAContractType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:element>
<xsd:annotation/>
</xsd:group>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="relatedParty" type="RelatedParty">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
This may be used to identify one or more parties that perform a role within the transaction. If this is within a partyTradeInformation block, the related party performs the role with respect to the party identifie by the "partyReference" in the partyTradeInformation block.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Provides information about a person that executed or supports this trade
</xsd:documentation>
<xsd:annotation/>
</xsd:group>
<xsd:element minOccurs="0" name="reportingRole" type="ReportingRole">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Identifies the role of this party in reporting this trade for this regulator; roles could include ReportingParty and Voluntary reporting.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
The reason this message is being sent, for example Snapshot, PET, Confirmation, RealTimePublic.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Regulatory disclosure message used for reporting to trade repositories.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to report that a regulatory reporting message (e.g. regulatory disclosure or withdrawal) was processed successfully, and the status of reporting to any regulators.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation xml:lang="en">
</xsd:annotation>
Used to report that a regulatory reporting message was not processed successfully, and the reasons for that.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Message used to request withdrawal from one or more jurisdictions.
</xsd:documentation>
</xsd:schema>
|
XML schema documentation generated with FlexDoc/XML 1.12.2 using FlexDoc/XML XSDDoc 2.9.1 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit. |