The National Securities Clearing Corporation (NSCC) provides a standardized set of record formats that enable participants to report, exchange, and reconcile assetpricing information efficiently. These formats support a wide range of securitiesfrom equities and corporate bonds to structured productsallowing market participants to maintain accurate pricing data for clearing, settlement, and riskmanagement purposes.
Why Standardized Record Formats Matter
- Operational consistency: Uniform files reduce the need for custom parsers and manual data cleaning.
- Regulatory compliance: The formats satisfy reporting obligations under SEC, FINRA, and other jurisdictional rules.
- Risk transparency: Accurate pricing feeds enable realtime margin calculations and distress monitoring.
- Cost efficiency: Automation lowers processing costs and shortens settlement cycles.
Core Record Types
The NSCC assetpricing suite consists of four primary record types. Each type has a clearly defined layout, mandatory fields, and optional extensions.
| Record Type | Description | Typical Use Cases |
|---|---|---|
PRI Price Record | Captures the quoted or derived price for a security at a specific timestamp. | Daily settlement pricing, intraday margin calls. |
VAL Valuation Record | Provides a full valuation snapshot, including accrued interest, market value, and net asset value (NAV) for funds. | Portfolio valuation, NAV calculation for mutual funds. |
CRP Composite Record | Aggregates multiple price sources (e.g., exchange, brokerdealer, thirdparty vendor) into a single composite price. | Bestprice determination, reference pricing for derivatives. |
ADJ Adjustment Record | Records posttrade price adjustments such as corporate actions, errors, or reconciling differences. | Corporate action processing, error correction. |
Common Fields Across All Formats
While each record type has unique aspects, the following fields appear in every NSCC pricing file:
- Record Identifier A threecharacter code (e.g., PRI, VAL).
- Message Sequence Number Ensures proper ordering.
- Security Identifier CUSIP, ISIN, or an internal NSCC ID.
- Effective Date/Time Timestamp in UTC (ISO 8601 format).
- Currency Code ISO4217 threeletter code.
- Price Indicator Bid, Ask, Mid, Close, etc.
File Structure and Transmission
NSCC records are exchanged via fixedwidth, delimited, or XML files depending on the participants capability.
FixedWidth Files
Each column occupies a predetermined number of characters. This layout is the legacy format, favored for highvolume batch processing. Example line (PRI record):
PRI00123456789USD2024-05-30T14:45:00ZMKT12345678 101.2500
Delimited (CSV) Files
Commaseparated values are increasingly used because they are humanreadable and easily imported into analytics tools.
PRI,00123456789,USD,2024-05-30T14:45:00Z,MKT,12345678,101.2500
XML Format
XML provides hierarchical structuring and schema validation (XSD). It is preferred when participants need to embed supplementary metadata, such as source attribution or regulatory tags.
00123456789 USD 2024-05-30T14:45:00Z MKT 12345678 101.2500
Transmission channels include secure FTP (SFTP), MQ messaging, and APIbased HTTP POST/GET endpoints. All files must be encrypted (TLS 1.2+) and signed with an approved digital certificate.
Validation Rules
Before a file is accepted, NSCC runs a series of validation checks:
- Schema conformity Fixedwidth lengths, CSV column counts, or XML schema must match.
- Data type checks Numeric fields contain only digits, timestamps follow ISO8601, currency codes are valid.
- Businesslogic validation Prices must be positive, accrued interest cannot exceed the coupon, composite prices must be weighted correctly.
- Duplicate detection Sequence numbers must be unique within a transmission session.
Errors are returned in a ERR record that references the offending line and provides an error code and description. Participants are required to correct and resubmit within the same business day.
Extending the Standard
The NSCC framework allows participants to add optional fields, provided they are placed in a designated Extension area and flagged in the file header. The extension segment must be documented in a separate schema agreement to avoid processing conflicts.
Best Practices for Implementation
- Automate generation of sequence numbers to guarantee monotonic ordering.
- Maintain a mapping table of internal identifiers to NSCC security IDs; keep it synchronized daily.
- Use a test environment (NSCCs Sandbox) for initial integration and regression testing.
- Implement a monitoring dashboard that flags validation failures in real time.
- Schedule file deliveries at the same time each day to simplify downstream processing.
Resources
Further guidance can be found in the official NSCC documentation:
