Swap Data Repository Reporting Specifications Nov252016
Swap Data Repository Reporting Specifications Nov252016
This document provides descriptions of the CSV upload fields and sample uploadable CSV reports to the CME Sw
CME cleared transactions, and non-CME cleared transactions for interest rates, credit, foreign exchange, and co
used for custom queries, which can be saved as favorites for future use. Users can access the Interface to uploa
providers can also submit these CSVs via HTTPS web services or Secure FTP.
Uploading Reports
CSVs can be submitted over web services gateway (WSG) or SFTP.
For information on web services, please visit :
CME SDR has categorized the asset classes to assist clients with populating the appropriate asset class specific fiel
all asset classes. To view the different specifications, please follow the different selections within Asset Class (Colu
VALUATION_UPLOAD
CME Swap Data Repository CSV Specifications
CSV upload fields and sample uploadable CSV reports to the CME Swap Data Repository (SDR). These specifications support: bilateral o
ared transactions for interest rates, credit, foreign exchange, and commodities asset classes. The CME SDR User Interface is a powerful
d as favorites for future use. Users can access the Interface to upload transactions and view reports associated with their permissioned
TPS web services or Secure FTP.
repositorysupport@cmegroup.com
repository@cmegroup.com
assist clients with populating the appropriate asset class specific fields. In the TRADE_POSITION_UPLOAD spec worksheet, the user will be
cations, please follow the different selections within Asset Class (Column B).
All
pecifications
nt
he TRADE_POSITION_UPLOAD spec worksheet, the user will be able to see all the fields for
Definition
s
Provides the specific fields for Dodd-Frank Trade reporting
Provides the specific fields for Valuation Submissions at Trade and Position level
Fields Asset Class
Comment All
Action All
SubmissionDateTime All
Event All
EventDateTime All
EventID All
SubmissionType All
USI All
USINamespace All
RecordRefID All
PackageID All
Position All
Backload All
Bespoke All
ReportingEntityLEI All
ReportingPartyLEI All
ReportingPartyLEISource All
ReportingPartyAltID All
ReportingPartyAltIDType All
RptPtyType All
RptPtyUSPerson All
NonReportingPartyLEI All
NonReportingPartyLEISource All
NonReportingPartyAltID All
NonReportingPartyAltIDType All
NonRptPtyType All
NonRptPtyUSPerson All
UPI All
AssetClass All
SubAssetClass All
MultiAssetSwap All
SecondaryAsset All
BaseProduct Credit
SubProduct Credit
ProductName All
ProductType All
ProductSubType All
ProductCode All
ProductCodeType All
TradeType All
ExecutionVenueType All
ExecutionDateTime All
ExecutionVenueLEI All
ExecutionVenueLEISource All
ExecutionTradeID All
ConfirmType All
ConfirmDateTime All
Collateralization All
ClearingException All
RepClearingExceptionPartyLEI All
NonRepClearingExceptionPartyLEI All
Cleared All
DCOIndicator All
ClearingVenueLEI All
ClearingVenueLEISource All
ClearingTradeID All
ClearingMemberLEI All
ClearingMemberClientAccount All
ClearingMemberOrigin All
ClearingReceiptDateTime All
ClearingAcceptanceDateTime All
InitialSDRLEI All
PriorUSI All
PriorUSINamespace All
PriorUSIType All
OtherClearingSwapUSI All
OtherClearingSwapUSINamespace All
ClearingSwapSDRLEI All
ClearingSwapUSI1 All
ClearingSwapUSI1Namespace All
ClearingSwapUSI2 All
ClearingSwapUSI2Namespace All
IntlSDRLEI All
IntlSwapIdentifier All
IntlSwapInd All
MixedSwap All
MixedAlternateSDRLEI All
AllocationIntent All
PostAllocation All
PostAllocationBlockUSI All
PostAllocationBlockUSINamespace All
AllocationAgentLEI All
ReportingAssetManagerLEI All
NonReportingAssetManagerLEI All
ReportingBrokerLEI All
NonReportingBrokerLEI All
BuyerLEI All
SellerLEI All
StartDate All
MaturityDate All
SettlementDate All
SettlementCurrency All
ContractQuantity Commodity
ContractPrice Commodity
PriceUnit Commodity
Price Credit
PriceType Credit
ExchangeRate FX
CouponRate Credit
Leg1FixedPayment Commodity
Leg1FixedPaymentCurrency Commodity
Leg1Commodity Commodity
Leg1CommodityDesc Commodity
Leg1EffectiveDate Commodity
Leg1MaturityDate Commodity
Leg1StartDate Interest Rate
Leg1Notional Commodity
Leg1NotionalFreq Commodity
Leg1NotionalUnit Commodity
Leg1TotalNotional Commodity
Leg1TotalNotionalUnit Commodity
NotionalAmount1 FX
Currency1 FX
Notional Credit
NotionalCurrency Credit
Leg1AmortType Interest Rate
AppendixB Commodity
Leg1Location Commodity
Leg1IndexRegion Commodity
Leg1DeliveryLocation Commodity
Leg1DeliveryRegion Commodity
Leg1LoadType Commodity
Leg1AvgMethod Commodity
Leg1PaymentType Commodity
Leg1PriceType Commodity
Leg1Grade Commodity
Leg1DaysOfWeek Commodity
Leg1Hours Commodity
Leg1HoursTimezone Commodity
Leg2FixedPayment Commodity
Leg2FixedPaymentCurrency Commodity
Leg2Commodity Commodity
Leg2CommodityDesc Commodity
Leg2EffectiveDate Commodity
Leg2MaturityDate Commodity
PaymentFrequency Credit
DayCount Credit
Leg2Notional Commodity
Leg2NotionalFreq Commodity
Leg2NotionalUnit Commodity
Leg2TotalNotional Commodity
Leg2TotalNotionalUnit Commodity
NotionalAmount2 FX
Currency2 FX
Leg2Location Commodity
Leg2IndexRegion Commodity
Leg2DeliveryLocation Commodity
Leg2DeliveryRegion Commodity
Leg2LoadType Commodity
Leg2AvgMethod Commodity
Leg2PaymentType Commodity
Leg2PriceType Commodity
Leg2Grade Commodity
Leg2DaysOfWeek Commodity
Leg2Hours Commodity
Leg2HoursTimezone Commodity
FixingDateTime FX
AttachmentPoint Credit
ExhaustionPoint Credit
UpfrontFee All
UpfrontFeeCurrency All
UpfrontFeeDate All
UpfrontFeePartyLEI All
OptionType All
OptionStrikePrice All
OptionStrikePriceUpper Interest Rate & Commodity
OptionExerciseType All
OptionExerciseFrequency All
OptionExerciseStartDate All
OptionExerciseEndDate All
OptionExpirationDate All
OptionSettlementType All
OptionDeliveryDate All
OptionPremium All
OptionPremiumCurrency All
OptionPremiumDate All
Description of details to be reported
The date and time the trade is reported to SDR. DateTime value provided is converted and saved in UTC reference based on the offset pro
any).
The type of event being reported to the SDR
The date and time a new trade event or an event on an existing trade is reported to SDR. DateTime value provided is converted and saved
reference based on the offset provided (if any)
The unique swap identifier for the trade. If a USI is not provided, the SDR will generate one with the SDR namespace (1010000252)
- When a “New Trade” (Bilateral only) is uploaded and the USI field is blank, the USI is automatically generated. Clients can view the repor
the automatically generated USI for reconciliation purposes
- On FIXML (API) uploaded trades the USI is provided on the “TrdCaptRpt” response upon successful submission
- “Amends” on a previously submitted USI require the USI and USINamespace
The unique swap identifier for the trade. If a USI is not provided, the SDR will generate one with the SDR namespace (1010000252)
- When a “New Trade” (Bilateral only) is uploaded and the USI field is blank, the USI is automatically generated. Clients can view the repor
the automatically generated USI for reconciliation purposes
- On FIXML (API) uploaded trades the USI is provided on the “TrdCaptRpt” response upon successful submission
- “Amends” on a previously submitted USI require the USI and USINamespace
Optional internal identifier that helps track trades against other systems
Indication of whether the record being submitted is part of a backloading activity (e.g. for part 46 reporting)
Indication if the trade is bespoke. Bespoke refers to Trades with specific conditions that could not be put in through the upload template.
marked as Bespoke (i.e. Bespoke = Y) user should upload associated term sheet or confirmation document via the SDR UI - Submit Docum
In case the reporting counterparty has delegated the submission of the report to a third party or to the other counterparty
The LEI of the reporting counterparty as determined by the reporting counterparty hierarchy under §45.8. This is not linked to the pay/rec
of the counterparty, see Leg 1/2 LEI
An LEI is obtained through one of the LEI issuing organizations – also referred to as Local Operating Units (LOUs) - accredited by the Globa
Entity Identifier Foundation (GLEIF) e.g., GMEI
This field is to be used to explain the origin of the reporting counterparty entity identifier specified in the ReportingPartyLEI field. If the Re
counterparty populates the ReportingPartyLEI field with either a Legal Entity Identifier (LEI) or a CFTC Interim Compliant Identifier (CICI) pe
https://www.gmeiutility.org , the value in this field is to be specified as “LEI”. If the Reporting counterparty populates the ReportingPartyL
a value that is neither an LEI nor a CICI, then this field is to be populated with a value of “Other”
An optional alternative non-LEI id for the reporting party such as an account number
If providing an alternative non-LEI id for the reporting party, an indicator of the type of id (e.g. account)
This field represents the entity classification of the reporting counterparty. Valid values for this field are “SD”, “MSP”, “FE”, "NFE"which re
denote “Swap Dealer”, “Major Swap Participant” , “Financial Entity”, and "Non-Financial Entity" entity classifications. If this field is not ap
should remain blank
This field identifies whether the Reporting Counterparty is a US Person or not. The valid values for this field are “Y” and “N”, where a value
indicates the Reporting Counterparty is a US Person and “N” indicates that the Reporting Counterparty is not a US Person
The LEI of the counterparty who has not been determined to be the reporting counterparty under §45.8. This is not linked to the pay/rec
of the counterparty, see Leg 1/2 LEI
If an LEI for the non-reporting counterparty is provided specify the NonReportingPartyLEISource field as 'LEI'.
If an natural person, a substitute should be provided and the NonReportingPartyLEISource field should specify ‘Other’.
This field is to be used to explain the origin of the non-reporting counterparty entity identifier specified in the NonReportingPartyLEI field.
Reporting counterparty populates the NonReportingPartyLEI with either a Legal Entity Identifier (LEI) or a CFTC Interim Compliant Identifie
https://www.gmeiutility.org , the value in this field is to be specified as “LEI”. If the Non Reporting counterparty populates the NonReporti
with a value that is neither an LEI nor a CICI, then this field is to be populated with a value of “Other”.
If providing an alternative non-LEI id for the non-reporting party, an indicator of the type of id (e.g. account)
This field represents the entity classification of the non-reporting counterparty. Valid values for this field are “SD”, “MSP”, “FE”, "NFE"whic
respectively denote “Swap Dealer”, “Major Swap Participant” , “Financial Entity”, and "Non-Financial Entity" entity classifications. If this fi
applicable it should remain blank.
This field identifies whether the non-reporting counterparty is a US Person or not. The valid values for this field are “Y” and “N”, where a v
indicates the non-reporting counterparty is a US Person and “N” indicates that the non-reporting counterparty is not a US Person.
Unique product identifier for product (Not applicable, pending UPI product definition)
The primary asset class
This is a field implemented per the CFTC’s data harmonization initiative. The CFTC has begun this harmonization effort in the credit asset c
This is a field implemented per the CFTC’s data harmonization initiative. The CFTC has begun this harmonization effort in the credit asset c
The product sub-type/classification for e.g. OIS, Basis, ZeroCoupon, ABX, iTraxx, Fixed-Float etc
The type of execution venue where trade being reported was executed
Execution time stamp is used to provide the date and time when the trade was executed at the SEF, DCM, or off-facility. DateTime value p
converted and saved in UTC reference based on the offset provided (if any)
If the ExecutionVenueType is other than 'O' or 'Off Facility Swap', the LEI of the SEF or DCM
This field is to be used to explain the origin of the execution venue entity identifier specified in the ExecutionVenueLEI field. If the
ExecutionVenueLEI field is populated with either a Legal Entity Identifier (LEI) or a CFTC Interim Compliant Identifier (CICI) per
https://www.gmeiutility.org , the value in this field is to be specified as ”LEI”. If the ExecutionVenueLEI field is populated with a value that
an LEI nor a CICI, then this field is to be populated with a value of “Other”
Optional internal trade identifier used by the execution venue, which can be used to find trades in report in the event of a USI being gener
CME
An indication of whether an exception or exemption from clearing was elected, and if elected the clearing exception or exemption type
claimed. Select ‘NA’ if the swap is ‘Uncleared’ and no exception or exemption was claimed.
If clearing exception or exemption is elected by the reporting party, the LEI, or substitute identifier for a natural person, of the reporting p
If clearing exception or exemption is elected by the non-reporting party, the LEI , or substitute identifier for a natural person, of the non-re
party
If cleared/intend to clear, the LEI of the Clearing House. A LEI is obtained through one of the LEI issuing organizations – also referred to as
Operating Units (LOUs) - accredited by the Global Legal Entity Identifier Foundation (GLEIF) e.g., GMEI
This field is to be used to explain the origin of the clearing venue entity identifier specified in the ClearingVenueLEI field. If the ClearingVe
is populated with either a Legal Entity Identifier (LEI) or a CFTC Interim Compliant Identifier (CICI), per https://www.gmeiutility.org , the va
field is to be specified as ”LEI”. If the ClearingVenueLEI field is populated with a value that is neither an LEI nor a CICI, then this field is to b
populated with a value of “Other”
The Trade ID of the clearing venue
The LEI of the Clearing Member. A LEI is obtained through one of the LEI issuing organizations – also referred to as Local Operating Units (L
accredited by the Global Legal Entity Identifier Foundation (GLEIF) e.g., GMEI
An indication whether the clearing member acted as principal for a house trade or agent for a customer trade
The date and time in UTC at which the Clearing House received the swap for clearing
The date and time in UTC at which the Clearing House accepted the swap for clearing
The LEI of the SDR to which the primary economic terms for the bilateral swap was reported. Please note that if the field is not being popu
because the swap is a non-CFTC reportable swap (NCRS) the field should be populated with text as 'NCRS'
The USI of the trade novated from and resulting in the trade being reported
The USI Namespace of the trade novated from and resulting in the trade being reported
Indication of the type of the PriorUSI for e.g. Clearing Novation
The USI of the other swap resulting from a clearing novation not populated in the USI field
The USI namespace of the other swap resulting from a clearing novation not populated in the USINamespace field
Clearing Swap USI associated with the Reporting Party on the bilateral. Please note there is no specific guidance to say this has to be the c
associated with the Reporting Party on the Bilateral but is being suggested so as to maintain consistent information
Clearing Swap USINamespace associated with the Reporting Party on the bilateral. Please note there is no specific guidance to say this has
cleared USI associated with the Reporting Party on the Bilateral but is being suggested so as to maintain consistent information
Clearing Swap USI associated with the Non Reporting Party on the bilateral. Please note there is no specific guidance to say this has to be t
USI associated with the Non Reporting Party on the Bilateral but is being suggested so as to maintain consistent information
Clearing Swap USINamespace associated with the Non Reporting Party on the bilateral. Please note there is no specific guidance to say thi
the cleared USI associated with the Non Reporting Party on the Bilateral but is being suggested so as to maintain consistent information
This is a repeatable field. This field and IntlSwapIdentifier field must be repeated together in the following scenarios -
1. If reported to more than one foreign SDR, repeat this field as many times as the number of SDR's it was reported to by specifying the LE
SDR
2. If multiple IntlSwapIdentifier are reported, repeat this field with the LEI of the SDR that corresponds to that IntlSwapIdentifier. If same L
reported, specify the same LEI in each
See example in 'Interest Rates-sample UL' worksheet.
This is a repeatable field. This field and IntlSDRLEI field must be repeated together in the following scenarios -
1. If multiple IntlSDRLEI are reported, repeat this field with the UTI that corresponds to that IntlSDRLEI. If same UTI is reported, specify the
in each
If mixed swap, as defined in Commodity Exchange Act section 1a(47)(D), then set value to Y. If not applicable, set to NA
If mixed swap under§45.1 the LEI of security-based SDR to which the swap is or will be reported
The USI of the block trade allocated from and resulting in the trade being reported
The USI Namespace of the block trade allocated from and resulting in the trade being reported
If trade is to be allocated or was allocated, the LEI of the allocation agent or substitute identifier for a natural person
The LEI, or substitute identifier for a natural person, of the purchasing (buy side) counterparty
When referring to legs of Swap for payment streams such as fixed, float or physical legs.
• The buyer is the payer on the fixed leg and receiver on the float leg.
• The seller is the person who is paying float and receiving fixed.
The LEI, or substitute identifier for a natural person, of the selling (sell side) counterparty
When referring to legs of Swap for payment streams such as fixed, float or physical legs.
• The buyer is the payer on the fixed leg and receiver on the float leg.
• The seller is the person who is paying float and receiving fixed.
Effective date of the swap. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided
converted and saved in UTC reference based on the offset provided (if any)
Maturity date of the swap. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided
converted and saved in UTC reference based on the offset provided (if any)
Settlement date of the swap. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provide
converted and saved in UTC reference based on the offset provided (if any).
If the settlement date is unknown, enter the maturity date as the settlement date and amend the trade when the settlement date is know
The Unit of measure applicable for the price of the swap (For e.g. MMBtu for a natural gas contract)
If fixed payment leg, the fixed payment amount, which is price*number of contracts bought*contract unit
Additional details for the underlying commodity (For e.g. 6x16, Monday-Saturday Hours Ending 07:00-22:00 (PPT), Excluding NERC Holiday
Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are converted and saved in
reference based on the offset provided (if any)
The contract maturity date for leg 1. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime)
are converted and saved in UTC reference based on the offset provided (if any)
If a trade matures on a specified maturity date when initially reported, it is not required to be reported to the SDR again
The start date for leg 1. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are
and saved in UTC reference based on the offset provided (if any)
The end date for leg 1. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are
and saved in UTC reference based on the offset provided (if any)
The payment frequency for leg 1 (For e.g. 1M, 1Y, 15D)
The reset frequency for leg 1 (For e.g. 1M, 3Wk, 15D)
The day count convention for leg 1 (For e.g. 30/360, ACT/360)
The frequency of the base notional value (For e.g. 1M, 1D, 15D)
The base unit of the notional value (For e.g. MMBtu, MWh)
The unit for total summed notional value (For e.g. MMBtu, MWh)
Start date of amortizations schedule, if different from trade date. Date being submitted should be in reference to UTC, as all DateTime val
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
End date of amortizations schedule, if different from trade date. Date being submitted should be in reference to UTC, as all DateTime valu
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
AppendixB value is to indicate whether or not the trade being submitted (1) references one of the contracts described in appendix B to pa
is economically related to one of the contracts described in appendix B to part 43
Mapping of the Leg1 Index Pricing Point to Geographic Region as set forth in Appendix E
If physical delivery leg, the physical delivery location (For e.g. Palo Verde)
Mapping of the Leg1 Delivery Point to Geographic Region as set forth in Appendix E
The load type for the commodity
If floating index leg, the averaging method (For e.g. Arithmetic average of midpoint price)
The grade of the commodity, if applicable (For e.g. Minimum Gravity 36.4 API, Maximum Sulfur 0.46%)
The days of the week for the commodity (e.g. PJM electricity Sunday-Friday)
The LEI and name of the counterparty who pays leg 2. Each spread leg to be submitted as a separate trade with a unique USI. They are ass
common execution venue type or execution trade type.
Indication if leg 2 is fixed or floating or Physical (Delivery leg only applicable for commodities)
If fixed payment leg, the fixed payment amount, which is price*number of contracts bought*contract unit
The effective date of the second leg of the trade. Date being submitted should be in reference to UTC, as all DateTime values (like
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
The contract maturity date for leg 2. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime)
are converted and saved in UTC reference based on the offset provided (if any).
If a trade matures on a specified maturity date when initially reported, it is not required to be reported to the SDR again
The start date for leg 2. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are
and saved in UTC reference based on the offset provided (if any)
The end date for leg 2. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are
and saved in UTC reference based on the offset provided (if any)
The payment frequency for leg 2 (For e.g. 1M, 1Y, 15D, 1Wk)
The day count convention for leg 2 (For e.g. 30/360, 30/365)
The day count convention of the associated cash flow stream (For e.g. 30/360, ACT/360)
The frequency of the base notional value (For e.g. 1M, 1D, 15D)
The base unit of the notional value (For e.g. MMBtu, MWh)
The unit for total summed notional value (For e.g. MMBtu, MWh)
Start date of amortizations schedule, if different from trade date. Date being submitted should be in reference to UTC, as all DateTime val
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
End date of amortizations schedule, if different from trade date. Date being submitted should be in reference to UTC, as all DateTime valu
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
Indicates the amortization frequency (For e.g. 1M, 3Wk, 15D, 1Y)
Mapping of the Leg2 Index Pricing Point to Geographic Region as set forth in Appendix E
If physical delivery leg, the physical delivery location (For e.g. Palo Verde)
Mapping of the Leg2 Delivery Point to Geographic Region as set forth in Appendix E
If floating index leg, the averaging method (For e.g. Arithmetic average of midpoint price)
The grade of the commodity, if applicable (For e.g. Minimum Gravity 36.4 API, Maximum Sulfur 0.46%)
The days of the week for the commodity (e.g. PJM electricity - Sunday - Friday)
For NDFs, the fixing date & time for the settled exchange rate. DateTime value provided is converted and saved in UTC reference based on
provided (if any)
It is the rate source for the conversion of the settlement currency (For e.g. BRL.PTAX/BRL09)
The number of business days used in the future value notional calculation
Fee date, if applicable. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) provided are
and saved in UTC reference based on the offset provided (if any)
Indication of the type of option applied to the trade, if any. Option types include cancellable swaps, extendable swaps, swaptions, etc
If option type exists, the exercise type. Types include American, Bermudan and European
If American or Bermudan exercise type, the first date for executions. Date being submitted should be in reference to UTC, as all DateTime
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any)
If American or Bermudan exercise type, the last date for executions. Date being submitted should be in reference to UTC, as all DateTime
ExecutionDateTime) provided are converted and saved in UTC reference based on the offset provided (if any).
Expiration date of exercise option. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) p
converted and saved in UTC reference based on the offset provided (if any)
Delivery date of exercise option. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime) pro
converted and saved in UTC reference based on the offset provided (if any).
If fixed premium, premium amount
The date that the premium was paid. Date being submitted should be in reference to UTC, as all DateTime values (like ExecutionDateTime
are converted and saved in UTC reference based on the offset provided (if any)
Valid Format & Values
Valid Format:
Valid Values:
New
Amend
Terminate
Snapshot
SnapVal
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset. For example, “2012-
10-12T16:34:56Z” is in reference to a timestamp of 2012-10-12T16:34:56Z UTC
“X” is a positive or negative UTC offset, allowing for the specification of a timezone via an offset relative
to UTC. For example:
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset. For example, “2012-
10-12T16:34:56Z” is in reference to a timestamp of 2012-10-12T16:34:56Z UTC
“X” is a positive or negative UTC offset, allowing for the specification of a timezone via an offset relative
to UTC. For example:
Valid Format:
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Y
N
Valid Values:
Y
N
Valid Values:
Y
N
Valid Format:
Valid Format:
LEI
InternalSDR
Other
Valid Format:
Text (1-50 Characters)
Valid Format:
Valid Values:
SD
MSP
FE
NFE
Valid Values:
Y
N
Valid Format:
Valid Values:
LEI
InternalSDR
Other
Valid Format:
Valid Values:
SD
MSP
FE
NFE
Valid Values:
Y
N
Valid Format:
Interest Rate
Credit
FX
Commodity
Valid Format:
Valid Values:
Where AssetClass = Commodity
Precious Metals
Metals-Other
Bullion
Energy
Index
Agricultural
Environmental
Freight
Chemicals
Plastics
Weather
Volatility
Exotic
Other
Valid values:
Y
NA
Valid Values:
Interest Rate
Credit
FX
Commodity
Equity
Valid Values:
Single Name
Index
Index Tranche
Credit Basket
Valid Values:
Corporate
Sovereign
CDX
CDX Structured
iTraxx
iTraxx Structured
Muni
ABS
High Grade
Investment Grade
LCDX
Valid Format:
InterestRateSwap
Swaption
FRA
CapFloor
CDSIndex
CDSIndexTranche
CDSIndexOption
FX Valid Values:
FXForward (FXFWD)
FXNDF
FXSwap
FXOption (OPT)
Valid Values:
CommoditySwap (CMDTYSWAP)
CommoditySwaption (SWAPTION)
Forward (FWD)
Option (OPT)
Valid Format:
Valid Values:
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset.
For example:
Valid Format:
Valid Values:
LEI
InternalSDR
Other
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset. For example, “2012-
10-12T16:34:56Z” is in reference to a timestamp of 2012-10-12T16:34:56Z UTC
“X” is a positive or negative UTC offset, allowing for the specification of a timezone via an offset relative
to UTC. For example:
2012-10-12T16:34:56+0500 is in reference to a local timestamp of 2012-10-12T16:34:56, in a timezone
that is 5 hours ahead of UTC.
2012-10-12T16:34:56-0500 is in reference to a local timestamp of 2012-10-12T16:34:56, in a timezone
that is 5 hours behind UTC
Valid Values:
Uncollateralized
Partially Collateralized
One-Way Collateralized
Fully Collateralized
Valid Values:
End-user
Inter-affiliate
Treasury-affiliate
Cooperative
NA
Valid Format:
Valid Format:
Valid Values:
Cleared
Intend to Clear
Uncleared
Valid Values:
Y
N
Valid Format:
Valid Values:
LEI
InternalSDR
Other
Valid Format:
House
Customer
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset. For example, “2012-
10-12T16:34:56Z” is in reference to a timestamp of 2012-10-12T16:34:56Z UTC
“X” is a positive or negative UTC offset, allowing for the specification of a timezone via an offset relative
to UTC. For example:
Valid Format:
yyyy-MM-ddThh:mm:ss.SSSZ
yyyy-MM-ddThh:mm:ss.SSS±X, where X is a UTC offset
“Z” is the UTC zone designator, allowing for the specification of a zero UTC offset. For example, “2012-
10-12T16:34:56Z” is in reference to a timestamp of 2012-10-12T16:34:56Z UTC
“X” is a positive or negative UTC offset, allowing for the specification of a timezone via an offset relative
to UTC. For example:
Valid Format:
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Valid Format:
Valid values:
Y
N/A
NA
Not Applicable
Valid Format:
Y
N
Valid Values:
Y
N
Valid Format:
Text (1-32 Characters). Certain special characters are permitted - colon, hyphen (minus), period (full
stop) and underscore but the identifier cannot not start or end with a special character and multiple
consecutive special characters are also not permitted
Valid Format:
Valid Format:
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy OR yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Values:
Cash
Physical
Valid Values:
Number
Valid Format:
Number
Valid Format:
Spread
Price
Valid Format:
Number
Valid Format:
Number
Valid Format:
Text (1-50 Characters)
Valid Values:
Fixed
Float
Physical (Only for Commodities)
Valid Format:
Valid Format:
Number
Valid Values:
Currency (Must use ISO Code)
Valid Format:
Valid Format:
Valid Format:
yyyy-MM-dd
yyyyMMdd
MM/dd/yyyy
Valid Format:
yyyy-MM-dd
yyyyMMdd
MM/dd/yyyy
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Values:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Valid Format:
Text (1-10 Characters)
Valid Format:
Number
Valid Format:
Number
Valid Format:
Number
Valid Values:
Currency (MUST use ISO code)
Valid Format:
Number
Valid Values:
Number
Valid Values:
Bullet
Equal
Step Down
Annuity
Schedule
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Number
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Valid Values:
Add
Subtract
Multiply
Divide
Valid Format:
Number
Valid Values:
Y
N
Valid Format:
Valid Values:
Periodic
Initial
Single
Valid Values:
Percentage
Per Unit
Fixed Amount
Valid Format:
Valid Format:
Valid Values:
Fixed
Float
Physical (Only for Commodities)
Valid Format:
Decimal (e.g. 0.04 = 4%)
Valid Format
Number
Valid Values:
Valid Format:
Valid Values:
yyyy-MM-dd
MM/DD/YYYY
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Valid Format:
Number
Valid Format:
Number
Valid Format:
Number
Valid Values:
Valid Format:
Number
Valid Values:
Valid Values:
Bullet
Equal
Step Down
Annuity
Schedule
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Number
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Valid Values:
Add
Subtract
Multiply
Divide
Valid Format:
Number
Valid Format:
Valid Values:
Periodic
Initial
Single
Valid Values:
Percentage
Per Unit
Fixed Amount
Valid Values:
Number
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Text(1-30 Characters)
Valid Format:
Number
Valid Format:
Number
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Valid Values:
Swaption
Cancellable
Extendible
Cap
Floor
Collar
Straddle
Strangle
Valid Format:
Valid Values:
American
Bermudan
European
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Values:
Cash
Physical
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Valid Format:
Number
Valid Values:
Valid Format:
MM/dd/yyyy
yyyy-MM-dd
Upload Requirements
Optional
Required
Optional
Required
Required
Optional
Required
Optional
Optional
Optional
Optional
Optional
Required
Optional
Optional
Optional
Optional
Optional
Required
Optional
Optional
Optional
Optional
Optional
Optional
Required
Optional
Optional
Optional
Optional
Required
Required
Optional
Optional
Optional
Required
Optional
Optional
Optional
Optional
Optional
Required
Optional
Optional
Optional
Required if IntlSwapInd = Y
Required if IntlSwapInd = Y
Optional
Optional
Required if MixedSwap = Y
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required
Required
Required
Optional
Required
Optional
Optional
Optional
Required
Required
Required
Optional
Optional
Optional
Optional
Required
Optional
Required
Required
Required
Required
Required
Optional
Optional
Optional
Required
Required
Required
Required
Required
Required
Required
Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required
Required
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Required for AssetClass = Interest Rate if ProductType =
Swaption or Cap/Floor
Action ALL
USI ALL
USINamespace ALL
ReportingPartyLEI ALL
NonReportingPartyLEI ALL
SubmissionType ALL
ValuationDate ALL
MTM ALL
MTMCurrency ALL
An LEI is obtained through one of the LEI issuing organizations – also referred to as
Local Operating Units (LOUs) - accredited by the Global Legal Entity Identifier
Foundation (GLEIF) e.g., GMEI
The LEI of the counterparty who has not been determined to be the reporting
counterparty under §45.8. This is not linked to the pay/receive status of the
counterparty, see Leg 1/2 LEI
The date/time of the valuation. DateTime value provided is converted and saved in
UTC reference based on the offset provided (if any)
Prior day's spot FX rate used to convert BRL valuations to USD settlement amounts
Valuation Required
Valid Format:
Valid Format:
Valid Format:
Required
Text (1-50 Characters)
Valid Format:
Required
Text (1-50 Characters)
Valid Values:
Required
Valuation
Valid Values:
MM/dd/yyyy Required
yyyy-MM-dd
Valid Values:
Required
Number
Valid Values:
Required
Currency
Valid Values:
Optional
Number
Valid Values:
Optional
Number
Valid Values:
Optional
Number
Valid Values:
MM/dd/yyyy Optional
yyyy-MM-dd