Home
gpo.gov
govinfo.gov

e-CFR Navigation Aids

Browse

Simple Search

Advanced Search

 — Boolean

 — Proximity

 

Search History

Search Tips

Corrections

Latest Updates

User Info

FAQs

Agency List

Incorporation By Reference

eCFR logo

Related Resources

Electronic Code of Federal Regulations

We invite you to try out our new beta eCFR site at https://ecfr.federalregister.gov. We have made big changes to make the eCFR easier to use. Be sure to leave feedback using the Help button on the bottom right of each page!

e-CFR data is current as of September 25, 2020

Title 12Chapter IIISubchapter BPart 371 → Appendix


Title 12: Banks and Banking
PART 371—RECORDKEEPING REQUIREMENTS FOR QUALIFIED FINANCIAL CONTRACTS


Appendix B to Part 371—File Structure for Qualified Financial Contract Records for Full Scope Entities

Pursuant to §371.4(b), the records entity is required to provide the information required by this appendix B for itself and each of its reportable subsidiaries in a manner that can be disaggregated by legal entity. Accordingly, the reference to “records entity” in the tables of appendix B should be read as referring to each of the separate legal entities (i.e., the records entity and each reportable subsidiary).

Table A-1—Position-Level Data

   FieldExampleInstructions and
data application
DefinitionValidation
A1.1As of date2015-01-05Provide data extraction dateYYYY-MM-DD.
A1.2Records entity identifier999999999Provide LEI for records entity. Information needed to review position-level data by records entityVarchar(50)Validated against CO.2.
A1.3Position identifier20058953Provide a position identifier. Should be used consistently across all records entities. Use the unique transaction identifier if available. Information needed to readily track and distinguish positionsVarchar(100).
A1.4Counterparty identifier888888888Provide a counterparty identifier. Use LEI if counterparty has one. Should be used consistently by all records entities. Information needed to identify counterparty by reference to Counterparty Master TableVarchar(50)Validated against CP.2.
A1.5Internal booking location identifierNew York, New YorkProvide office where the position is booked. Information needed to determine system on which the trade is booked and settledVarchar(50)Combination A1.2 + A1.5 + A1.6 should have a corresponding unique combination BL.2 + BL.3 + BL.4 entry in Booking Location Master Table.
A1.6Unique booking unit or desk identifierxxxxxxProvide an identifier for unit or desk at which the position is booked. Information needed to help determine purpose of positionVarchar(50)Combination A1.2 + A1.5 + A1.6 should have a corresponding unique combination BL.2 + BL.3 + BL.4 entry in Booking Location Master Table.
A1.7Type of QFCCredit, equity, foreign exchange, interest rate (including cross-currency), other commodity, securities repurchase agreement, securities lending, loan repurchase agreement, guarantee or other third party credit enhancement of a QFCProvide type of QFC. Use unique product identifier if available. Information needed to determine the nature of the QFCVarchar(100).
A1.7.1Type of QFC covered by guarantee or other third party credit enhancementCredit, equity, foreign exchange, interest rate (including cross-currency), other commodity, securities repurchase agreement, securities lending, or loan repurchase agreementIf QFC type is guarantee or other third party credit enhancement, provide type of QFC that is covered by such guarantee or other third party credit enhancement. Use unique product identifier if available. If multiple asset classes are covered by the guarantee or credit enhancement, enter the asset classes separated by comma. If all the QFCs of the underlying QFC obligor identifier are covered by the guarantee or other third party credit enhancement, enter “All.”Varchar(500)Only required if QFC type (A1.7) is a guarantee or other third party credit enhancement.
A1.7.2Underlying QFC obligor identifier888888888If QFC type is guarantee or other third party credit enhancement, provide an identifier for the QFC obligor whose obligation is covered by the guarantee or other third party credit enhancement. Use LEI if underlying QFC obligor has one. Complete the counterparty master table with respect to a QFC obligor that is a non-affiliateVarchar(50)Only required if QFC asset type (A1.7) is a guarantee or other third party credit enhancement. Validated against CO.2 if affiliate or CP.2 if non-affiliate.
A1.8Agreement identifierxxxxxxxxxProvide an identifier for the primary governing documentation, e.g., the master agreement or guarantee agreement, as applicableVarchar(50)Validated against A3.3.
A1.9Netting agreement identifierxxxxxxxxxProvide an identifier for netting agreement. If this agreement is the same as provided in A1.8, use same identifier. Information needed to identify unique netting setsVarchar(50)Validated against A3.3.
A1.10Netting agreement counterparty identifierxxxxxxxxxProvide a netting agreement counterparty identifier. Use same identifier as provided in A1.4 if counterparty and netting agreement counterparty are the same. Use LEI if netting agreement counterparty has one. Information needed to identify unique netting setsVarchar(50)Validated against CP.2.
A1.11Trade date2014-12-20Provide trade or other commitment date for the QFC. Information needed to determine when the entity's rights and obligations regarding the position originatedYYYY-MM-DD.
A1.12Termination date2014-03-31Provide date the QFC terminates or is expected to terminate, expire, mature, or when final performance is required. Information needed to determine when the entity's rights and obligations regarding the position are expected to endYYYY-MM-DD.
A1.13Next call, put, or cancellation date2015-01-25Provide next call, put, or cancellation dateYYYY-MM-DD.
A1.14Next payment date2015-01-25Provide next payment dateYYYY-MM-DD.
A1.15Local Currency Of PositionUSDProvide currency in which QFC is denominated. Use ISO currency codeChar(3).
A1.16Current market value of the position in local currency995000Provide current market value of the position in local currency. In the case of a guarantee or other third party credit enhancements, provide the current mark-to-market expected value of the exposure. Information needed to determine the current size of the obligation or benefit associated with the QFCNum (25,5).
A1.17Current market value of the position in U.S. dollars995000In the case of a guarantee or other third party credit enhancements, provide the current mark-to-market expected value of the exposure. Information needed to determine the current size of the obligation/benefit associated with the QFCNum (25,5).
A1.18Asset Classification1Provide fair value asset classification under GAAP, IFRS, or other accounting principles or standards used by records entity. Provide “1” for Level 1, “2” for Level 2, or “3” for Level 3. Information needed to assess fair value of the positionChar(1).
A1.19Notional or principal amount of the position in local currency1000000Provide the notional or principal amount, as applicable, in local currency. In the case of a guarantee or other third party credit enhancement, provide the maximum possible exposure. Information needed to help evaluate the positionNum (25,5).
A1.20Notional or principal amount of the position In U.S. dollars1000000Provide the notional or principal amount, as applicable, in U.S. dollars. In the case of a guarantee or other third party credit enhancements, provide the maximum possible exposure. Information needed to help evaluate the positionNum (25,5).
A1.21Covered by third-party credit enhancement agreement (for the benefit of the records entity)?Y/NIndicate whether QFC is covered by a guarantee or other third-party credit enhancement. Information needed to determine credit enhancementChar(1).Should be “Y” or “N“.
A1.21.1Third-party credit enhancement provider identifier (for the benefit of the records entity)999999999If QFC is covered by a guarantee or other third-party credit enhancement, provide an identifier for provider. Use LEI if available. Complete the counterparty master table with respect to a provider that is a non-affiliateVarchar(50)Required if A1.21 is “Y”. Validated against CP.2.
A1.21.2Third-party credit enhancement agreement identifier (for the benefit of the records entity)4444444If QFC is covered by a guarantee or other third-party credit enhancement, provide an identifier for the agreementVarchar(50)Required if A1.21 is “Y.” Validated against A3.3.
A1.21.3Covered by third-party credit enhancement agreement (for the benefit of the counterparty)?Y/NIndicate whether QFC is covered by a guarantee or other third-party credit enhancement. Information needed to determine credit enhancementChar(1)Should be “Y” or “N“.
A1.21.4Third-party credit enhancement provider identifier (for the benefit of the counterparty)999999999If QFC is covered by a guarantee or other third-party credit enhancement, provide an identifier for provider. Use LEI if available. Complete the counterparty master table with respect to a provider that is a non-affiliateVarchar(50)Required if A1.21.3 is “Y”. Validated against CO.2 or CP.2.
A1.21.5Third-party credit enhancement agreement identifier (for the benefit of the counterparty)4444444If QFC is covered by a guarantee or other third-party credit enhancement, provide an identifier for agreementVarchar(50)Required if A1.21.3 is “Y”. Validated against A3.3.
A1.22Related position of records entity3333333Use this field to link any related positions of the records entity. All positions that are related to one another should have same designation in this fieldVarchar(100).
A1.23Reference number for any related loan9999999Provide a unique reference number for any loan held by the records entity or a member of its corporate group related to the position (with multiple entries delimited by commas)Varchar(500).
A1.24Identifier of the lender of the related loan999999999For any loan recorded in A1.23, provide identifier for records entity or member of its corporate group that holds any related loan. Use LEI if entity has oneVarchar(500).

Table A-2—Counterparty Netting Set Data

   FieldExampleInstructions and data
application
DefValidation
A2.1As of date2015-01-05Data extraction dateYYYY-MM-DD
A2.2Records entity identifier999999999Provide the LEI for the records entityVarchar(50)Validated against CO.2.
A2.3Netting agreement counterparty identifier888888888Provide an identifier for the netting agreement counterparty. Use LEI if counterparty has oneVarchar(50)Validated against CP.2.
A2.4Netting agreement identifierxxxxxxxxxProvide an identifier for the netting agreementVarchar(50)Validated against A3.3.
A2.4.1Underlying QFC obligor identifier888888888Provide identifier for underlying QFC obligor if netting agreement is associated with a guarantee or other third party credit enhancement. Use LEI if availableVarchar(50)Validated against CO.2 or CP.2.
A2.5Covered by third-party credit enhancement agreement (for the benefit of the records entity)?Y/NIndicate whether the positions subject to the netting set agreement are covered by a third-party credit enhancement agreementChar(1)Should be “Y” or “N”.
A2.5.1Third-party credit enhancement provider identifier (for the benefit of the records entity)999999999Use LEI if available. Information needed to identity third-party credit enhancement providerVarchar(50)Required if A2.5 is “Y”. Validated against CP.2.
A2.5.2Third-party credit enhancement agreement identifier (for the benefit of the records entity)4444444Varchar(50)Required if A2.5 is “Y”. Validated against A3.3.
A2.5.3Covered by third-party credit enhancement agreement (for the benefit of the counterparty)?Y/NInformation needed to determine credit enhancementChar(1)Should be “Y” or “N”.
A2.5.4Third-party credit enhancement provider identifier (for the benefit of the counterparty)999999999Use LEI if available. Information needed to identity third-party credit enhancement providerVarchar(50)Required if A2.5.3 is “Y”. Should be a valid entry in the Counterparty Master Table. Validated against CP.2.
A2.5.5Third-party credit enhancement agreement identifier (for the benefit of the counterparty)4444444Information used to determine guarantee or other third-party credit enhancementVarchar(50)Required if A2.5.3 is “Y”. Validated against A3.3.
A2.6Aggregate current market value in U.S. dollars of all positions under this netting agreement-1000000Information needed to help evaluate the positions subject to the netting agreementNum (25,5)Market value of all positions in A1 for the given netting agreement identifier should be equal to this value. A2.6 = A2.7 + A2.8.
A2.7Current market value in U.S. dollars of all positive positions, as aggregated under this netting agreement3000000Information needed to help evaluate the positions subject to the netting agreementNum (25,5)Market value of all positive positions in A1 for the given netting agreement identifier should be equal to this value. A2.6 = A2.7 + A2.8.
A2.8Current market value in U.S. dollars of all negative positions, as aggregated under this netting agreement-4000000Information needed to help evaluate the positions subject to the netting agreementNum (25,5)Market value of all negative positions in A1 for the given Netting Agreement Identifier should be equal to this value. A2.6 = A2.7 + A2.8.
A2.9Current market value in U.S. dollars of all collateral posted by records entity, as aggregated under this netting agreement950000Information needed to determine the extent to which collateral has been provided by records entityNum (25,5)Market value of all collateral posted by records entity for the given netting agreement Identifier should be equal to sum of all A4.9 for the same netting agreement identifier in A4.
A2.10Current market value in U.S. dollars of all collateral posted by counterparty, as aggregated under this netting agreement50000Information needed to determine the extent to which collateral has been provided by counterpartyNum (25,5)Market value of all collateral posted by counterparty for the given netting agreement identifier should be equal to sum of all A4.9 for the same netting agreement identifier in A4.
A2.11Current market value in U.S. dollars of all collateral posted by records entity that is subject to re-hypothecation, as aggregated under this netting agreement950,000Information needed to determine the extent to which collateral has been provided by records entityNum (25,5).
A2.12Current market value in U.S. dollars of all collateral posted by counterparty that is subject to re-hypothecation, as aggregated under this netting agreement950,000Information needed to determine the extent to which collateral has been provided by records entityNum (25,5).
A2.13Records entity collateral—net950,000Provide records entity's collateral excess or deficiency with respect to all of its positions, as determined under each applicable agreement, including thresholds and haircuts where applicableNum (25,5)Should be less than or equal to A2.9.
A2.14Counterparty collateral—net950,000Provide counterparty's collateral excess or deficiency with respect to all of its positions, as determined under each applicable agreement, including thresholds and haircuts where applicableNum (25,5)Should be less than or equal to A2.10.
A2.15Next margin payment date2015-11-05Provide next margin payment date for positionYYYY-MM-DD.
A2.16Next margin payment amount in U.S. dollars150,000Use positive value if records entity is due a payment and use negative value if records entity has to make the paymentNum (25,5).
A2.17Safekeeping agent identifier for records entity888888888Provide an identifier for the records entity's safekeeping agent, if any. Use LEI if safekeeping agent has oneVarchar(50)Validated against SA.2.
A2.18Safekeeping agent identifier for counterparty888888888Provide an identifier for the counterparty's safekeeping agent, if any. Use LEI if safekeeping agent has oneVarchar(50)Validated against SA.2.

Table A-3—Legal Agreements

   FieldExampleInstructions and data
application
DefValidation
A3.1As of Date2015-01-05Data extraction dateYYYY-MM-DD.
A3.2Records entity identifier999999999Provide LEI for records entityVarchar(50)Validated against CO.2.
A3.3Agreement identifierxxxxxxProvide identifier for each master agreement, governing document, netting agreement or third-party credit enhancement agreementVarchar(50).
A3.4Name of agreement or governing documentISDA Master 1992 or Guarantee Agreement or Master Netting AgreementProvide name of agreement or governing documentVarchar(50).
A3.5Agreement date2010-01-25Provide the date of the agreementYYYY-MM-DD.
A3.6Agreement counterparty identifier888888888Use LEI if counterparty has one. Information needed to identify counterpartyVarchar(50)Validated against field CP.2.
A3.6.1Underlying QFC obligor identifier888888888Provide underlying QFC obligor identifier if document identifier is associated with a guarantee or other third party credit enhancement. Use LEI if underlying QFC obligor has oneVarchar(50)Validated against CO.2 or CP.2.
A3.7Agreement governing lawNew YorkProvide law governing contract disputesVarchar(50).
A3.8Cross-default provision?Y/NSpecify whether agreement includes default or other termination event provisions that reference an entity not a party to the agreement (“cross-default Entity”). Information needed to determine exposure to affiliates or other entitiesChar(1)Should be “Y” or “N”.
A3.9Identity of cross-default entities777777777Provide identity of any cross-default entities referenced in A3.8. Use LEI if entity has one. Information needed to determine exposure to other entitiesVarchar(500)Required if A3.8 is “Y”. ID should be a valid entry in Corporate Org Master Table or Counterparty Master Table, if applicable. Multiple entries comma separated.
A3.10Covered by third-party credit enhancement agreement (for the benefit of the records entity)?Y/NInformation needed to determine credit enhancementChar(1)Should be “Y” or “N”.
A3.11Third-party credit enhancement provider identifier (for the benefit of the records entity)999999999Use LEI if available. Information needed to identity Third-Party Credit Enhancement ProviderVarchar(50)Required if A3.10 is “Y”. Should be a valid entry in the Counterparty Master Table. Validated against CP.2.
A3.12Associated third-party credit enhancement agreement document identifier (for the benefit of the records entity)33333333Information needed to determine credit enhancementVarchar(50)Required if A3.10 is “Y”. Validated against field A3.3.
A3.12.1Covered by third-party credit enhancement agreement (for the benefit of the counterparty)?Y/NInformation needed to determine credit enhancementChar(1)Should be “Y” or “N”.
A3.12.2Third-party credit enhancement provider identifier (for the benefit of the counterparty)999999999Use LEI if available. Information needed to identity Third-Party Credit Enhancement ProviderVarchar(50)Required if A3.12.1 is “Y”. Should be a valid entry in the Counterparty Master. Validated against CP.2.
A3.12.3Associated third-party credit enhancement agreement document identifier (for the benefit of the counterparty)33333333Information needed to determine credit enhancementVarchar(50)Required if A3.12.1 is “Y”. Validated against field A3.3.
A3.13Counterparty contact information: nameJohn Doe & Co.Provide contact name for counterparty as provided under notice section of agreementVarchar(200).
A3.14Counterparty contact information: address123 Main St, City, State Zip codeProvide contact address for counterparty as provided under notice section of agreementVarchar(100).
A3.15Counterparty contact information: phone1-999-999-9999Provide contact phone number for counterparty as provided under notice section of agreementVarchar(50).
A3.16Counterparty's contact information: email addressJdoe@JohnDoe.comProvide contact email address for counterparty as provided under notice section of agreementVarchar(100).

Table A-4—Collateral Detail Data

   FieldExampleInstructions and data
application
DefValidation
A4.1As of date2015-01-05Data extraction dateYYYY-MM-DD
A4.2Records entity identifier999999999Provide LEI for records entityVarchar(50)Validated against CO.2.
A4.3Collateral posted/collateral received flagP/NEnter “P” if collateral has been posted by the records entity. Enter “R” for collateral received by Records EntityChar(1).
A4.4Counterparty identifier888888888Provide identifier for counterparty. Use LEI if counterparty has oneVarchar(50)Validated against CP.2.
A4.5Netting agreement identifierxxxxxxxxxProvide identifier for applicable netting agreementVarchar(50)Validated against field A3.3.
A4.6Unique collateral item identifierCUSIP/ISINProvide identifier to reference individual collateral postedVarchar(50).
A4.7Original face amount of collateral item in local currency1500000Information needed to evaluate collateral sufficiency and marketabilityNum (25,5).
A4.8Local currency of collateral itemUSDUse ISO currency codeChar(3).
A4.9Market value amount of collateral item in U.S. dollars850000Information needed to evaluate collateral sufficiency and marketability and to permit aggregation across currenciesNum (25,5)Market value of all collateral posted by Records Entity or Counterparty A2.9 or A2.10 for the given netting agreement identifier should be equal to sum of all A4.9 for the same netting agreement identifier in A4.
A4.10Description of collateral itemU.S. Treasury Strip, maturity 2020/6/30Information needed to evaluate collateral sufficiency and marketabilityVarchar(200).
A4.11Asset classification1Provide fair value asset classification for the collateral item under GAAP, IFRS, or other accounting principles or standards used by records entity. Provide “1” for Level 1, “2” for Level 2, or “3” for Level 3Char(1)Should be “1” or “2” or “3”.
A4.12Collateral or portfolio segregation statusY/NSpecify whether the specific item of collateral or the related collateral portfolio is segregated from assets of the safekeeping agentChar(1)Should be “Y” or “N”.
A4.13Collateral locationABC broker-dealer (in safekeeping account of counterparty)Provide location of collateral postedVarchar(200).
A4.14Collateral jurisdictionNew York, New YorkProvide jurisdiction of location of collateral postedVarchar(50).
A4.15Is collateral re-hypothecation allowed?Y/NInformation needed to evaluate exposure of the records entity to the counterparty or vice-versa for re-hypothecated collateralChar(1)Should be “Y” or “N”.

Corporate Organization Master Table*

   FieldExampleInstructions and data
application
DefValidation
CO.1As of date2015-01-05Data extraction dateYYYY-MM-DD.
CO.2Entity identifier888888888Provide unique identifier. Use LEI if available. Information needed to identify entityVarchar(50)Should be unique across all records entities.
CO.3Has LEI been used for entity identifier?Y/NSpecify whether the entity identifier provided is an LEIChar(1)Should be “Y” or “N”.
CO.4Legal name of entityJohn Doe & CoProvide legal name of entityVarchar(200).
CO.5Immediate parent entity identifier77777777Use LEI if available. Information needed to complete org structureVarchar(50).
CO.6Has LEI been used for immediate parent entity identifier?Y/NSpecify whether the immediate parent entity identifier provided is an LEIChar(1)Should be “Y” or “N”.
CO.7Legal name of immediate parent entityJohn Doe & CoInformation needed to complete org structureVarchar(200).
CO.8Percentage ownership of immediate parent entity in the entity100.00Information needed to complete org structureNum (5,2).
CO.9Entity typeSubsidiary, foreign branch, foreign divisionInformation needed to complete org structureVarchar(50).
CO.10DomicileNew York, New YorkEnter as city, state or city, foreign countryVarchar(50).
CO.11Jurisdiction under which incorporated or organizedNew YorkEnter as state or foreign jurisdictionVarchar(50).

*Foreign branches and divisions shall be separately identified to the extent they are identified in an entity's reports to its appropriate Federal banking agency.

Counterparty Master Table

   FieldExampleInstructions and data
application
DefValidation
CP.1As of date2015-01-05Data extraction dateYYYY-MM-DD.
CP.2Counterparty identifier888888888Use LEI if counterparty has one. Should be used consistently across all records entities within a corporate group. The counterparty identifier shall be the global legal entity identifier if one has been issued to the entity. If a counterparty transacts with the records entity through one or more separate foreign branches or divisions and any such branch or division does not have its own unique global legal entity identifier, the records entity must include additional identifiers, as appropriate to enable the FDIC to aggregate or disaggregate the data for each counterparty and for each entity with the same ultimate parent entity as the counterpartyVarchar(50).
CP.3Has LEI been used for counterparty identifier?Y/NIndicate whether the counterparty identifier is an LEIChar(1)Should be “Y” or “N”.
CP.4Legal name of counterpartyJohn Doe & CoInformation needed to identify and, if necessary, communicate with counterpartyVarchar(200).
CP.5DomicileNew York, New YorkEnter as city, state or city, foreign countryVarchar(50).
CP.6Jurisdiction under which incorporated or organizedNew YorkEnter as state or foreign jurisdictionVarchar(50).
CP.7Immediate parent entity identifier77777777Provide an identifier for the parent entity that directly controls the counterparty. Use LEI if immediate parent entity has oneVarchar(50).
CP.8Has LEI been used for immediate parent entity identifier?Y/NIndicate whether the immediate parent entity identifier is an LEIChar(1)Should be “Y” or “N”.
CP.9Legal name of immediate parent entityJohn Doe & CoInformation needed to identify and, if necessary, communicate with counterpartyVarchar(200).
CP.10Ultimate parent entity identifier666666666Provide an identifier for the parent entity that is a member of the corporate group of the counterparty that is not controlled by another entity. Information needed to identify counterparty. Use LEI if ultimate parent entity has oneVarchar(50).
CP.11Has LEI been used for ultimate parent entity identifier?Y/NIndicate whether the ultimate parent entity identifier is an LEIChar(1)Should be “Y” or “N”.
CP.12Legal name of ultimate parent entityJohn Doe & Co.Information needed to identify and, if necessary, communicate with CounterpartyVarchar(100).

Booking Location Master Table

   FieldExampleInstructions and data
application
DefValidation
BL.1As of date2015-01-05Data extraction dateYYYY-MM-DD.
BL.2Records entity identifier999999999Provide LEIVarchar(50)Should be a valid entry in the Corporate Org Master Table.
BL.3Internal booking location identifierNew York, New YorkProvide office where the position is booked. Information needed to determine the headquarters or branch where the position is booked, including the system on which the trade is booked, as well as the system on which the trade is settledVarchar(50).
BL.4Unique booking unit or desk identifierxxxxxxProvide unit or desk at which the position is booked. Information needed to help determine purpose of positionVarchar(50).
BL.5Unique booking unit or desk descriptionNorth American trading deskAdditional information to help determine purpose of positionVarchar(50).
BL.6Booking unit or desk contact—phone1-999-999-9999Information needed to communicate with the booking unit or deskVarchar(50).
BL.7Booking unit or desk contact—emailDesk@Desk.comInformation needed to communicate with the booking unit or deskVarchar(100).

Safekeeping Agent Master Table

   FieldExampleInstructions and data
application
DefValidation
SA.1As of date2015-01-05Data extraction dateYYYY-MM-DD.
SA.2Safekeeping agent identifier888888888Provide an identifier for the safekeeping agent. Use LEI if safekeeping agent has oneVarchar(50).
SA.3Legal name of safekeeping agentJohn Doe & CoInformation needed to identify and, if necessary, communicate with the safekeeping agentVarchar(200).
SA.4Point of contact—nameJohn DoeInformation needed to identify and, if necessary, communicate with the safekeeping agentVarchar(200).
SA.5Point of contact—address123 Main St, City, State Zip CodeInformation needed to identify and, if necessary, communicate with the safekeeping agentVarchar(100).
SA.6Point of contact—phone1-999-999-9999Information needed to identify and, if necessary, communicate with the safekeeping agentVarchar(50).
SA.7Point of contact—emailJdoe@JohnDoe.comInformation needed to identify and, if necessary, communicate with the safekeeping agentVarchar(100).

Details of Formats

FormatContent in briefAdditional explanationExamples
YYYY-MM-DDDateYYYY = four digit date, MM = 2 digit month, DD = 2 digit date2015-11-12
Num (25,5)Up to 25 numerical characters including 5 decimalsUp to 20 numerical characters before the decimal point and up to 5 numerical characters after the decimal point. The dot character is used to separate decimals1352.67
12345678901234567890.12345
0
−20000.25
−0.257
Char(3)3 alphanumeric charactersThe length is fixed at 3 alphanumeric charactersUSD
X1X
999
Varchar(25)Up to 25 alphanumeric charactersThe length is not fixed but limited at up to 25 alphanumeric charactersasgaGEH3268EFdsagtTRCF543

Need assistance?