**NSCC ASSET PRICING RECORD FORMATS** and Reference File Download Link
https://eu2.contabostorage.com/00f3241116844f24b628f46d81abb929:st1/folder7/7236/1656285361_nsccaapw_-_Standar_Format.xls
2026-05-30 21:32:04 - Admin
<style> body { font-family: Arial, Helvetica, sans-serif; line-height: 1.6; margin: 0; padding: 0; color:#333; background:#fafafa; } header { background:#00457c; color:#fff; padding:20px 10%; } header h1 { margin:0; font-size:1.8em; } main { max-width:960px; margin:30px auto; padding:0 10%; } h2 { color:#00457c; margin-top:2em; } table { width:100%; border-collapse:collapse; margin:20px 0; } th, td { border:1px solid #ccc; padding:8px; text-align:left; } th { background:#e6f2ff; } a { color:#0066cc; } </style><header> <h1>NSCC Asset Pricing Record Formats</h1></header><main> <section> <p> 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. </p> </section> <section> <h2>Why Standardized Record Formats Matter</h2> <ul> <li><strong>Operational consistency:</strong> Uniform files reduce the need for custom parsers and manual data cleaning.</li> <li><strong>Regulatory compliance:</strong> The formats satisfy reporting obligations under SEC, FINRA, and other jurisdictional rules.</li> <li><strong>Risk transparency:</strong> Accurate pricing feeds enable realtime margin calculations and distress monitoring.</li> <li><strong>Cost efficiency:</strong> Automation lowers processing costs and shortens settlement cycles.</li> </ul> </section> <section> <h2>Core Record Types</h2> <p>The NSCC assetpricing suite consists of four primary record types. Each type has a clearly defined layout, mandatory fields, and optional extensions.</p> <table> <thead> <tr> <th>Record Type</th> <th>Description</th> <th>Typical Use Cases</th> </tr> </thead> <tbody> <tr> <td><code>PRI</code> Price Record</td> <td>Captures the quoted or derived price for a security at a specific timestamp.</td> <td>Daily settlement pricing, intraday margin calls.</td> </tr> <tr> <td><code>VAL</code> Valuation Record</td> <td>Provides a full valuation snapshot, including accrued interest, market value, and net asset value (NAV) for funds.</td> <td>Portfolio valuation, NAV calculation for mutual funds.</td> </tr> <tr> <td><code>CRP</code> Composite Record</td> <td>Aggregates multiple price sources (e.g., exchange, brokerdealer, thirdparty vendor) into a single composite price.</td> <td>Bestprice determination, reference pricing for derivatives.</td> </tr> <tr> <td><code>ADJ</code> Adjustment Record</td> <td>Records posttrade price adjustments such as corporate actions, errors, or reconciling differences.</td> <td>Corporate action processing, error correction.</td> </tr> </tbody> </table> </section> <section> <h2>Common Fields Across All Formats</h2> <p>While each record type has unique aspects, the following fields appear in every NSCC pricing file:</p> <ul> <li><strong>Record Identifier</strong> A threecharacter code (e.g., PRI, VAL).</li> <li><strong>Message Sequence Number</strong> Ensures proper ordering.</li> <li><strong>Security Identifier</strong> CUSIP, ISIN, or an internal NSCC ID.</li> <li><strong>Effective Date/Time</strong> Timestamp in UTC (ISO 8601 format).</li> <li><strong>Currency Code</strong> ISO4217 threeletter code.</li> <li><strong>Price Indicator</strong> Bid, Ask, Mid, Close, etc.</li> </ul> </section> <section> <h2>File Structure and Transmission</h2> <p>NSCC records are exchanged via fixedwidth, delimited, or XML files depending on the participants capability.</p> <h3>FixedWidth Files</h3> <p>Each column occupies a predetermined number of characters. This layout is the legacy format, favored for highvolume batch processing. Example line (PRI record):</p> <pre>PRI00123456789USD2024-05-30T14:45:00ZMKT12345678 101.2500 </pre> <h3>Delimited (CSV) Files</h3> <p>Commaseparated values are increasingly used because they are humanreadable and easily imported into analytics tools.</p> <pre>PRI,00123456789,USD,2024-05-30T14:45:00Z,MKT,12345678,101.2500 </pre> <h3>XML Format</h3> <p>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.</p> <pre><PriceRecord> <SecurityId>00123456789</SecurityId> <Currency>USD</Currency> <EffectiveTimestamp>2024-05-30T14:45:00Z</EffectiveTimestamp> <PriceType>MKT</PriceType> <SourceId>12345678</SourceId> <Price>101.2500</Price></PriceRecord> </pre> <p>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.</p> </section> <section> <h2>Validation Rules</h2> <p>Before a file is accepted, NSCC runs a series of validation checks:</p> <ol> <li><strong>Schema conformity</strong> Fixedwidth lengths, CSV column counts, or XML schema must match.</li> <li><strong>Data type checks</strong> Numeric fields contain only digits, timestamps follow ISO8601, currency codes are valid.</li> <li><strong>Businesslogic validation</strong> Prices must be positive, accrued interest cannot exceed the coupon, composite prices must be weighted correctly.</li> <li><strong>Duplicate detection</strong> Sequence numbers must be unique within a transmission session.</li> </ol> <p>Errors are returned in a <code>ERR</code> 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.</p> </section> <section> <h2>Extending the Standard</h2> <p>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.</p> </section> <section> <h2>Best Practices for Implementation</h2> <ul> <li>Automate generation of sequence numbers to guarantee monotonic ordering.</li> <li>Maintain a mapping table of internal identifiers to NSCC security IDs; keep it synchronized daily.</li> <li>Use a test environment (NSCCs Sandbox) for initial integration and regression testing.</li> <li>Implement a monitoring dashboard that flags validation failures in real time.</li> <li>Schedule file deliveries at the same time each day to simplify downstream processing.</li> </ul> </section> <section> <h2>Resources</h2> <p>Further guidance can be found in the official NSCC documentation:</p> <ul> <li><a href="https://www.nscc.com/clearing-price-records">NSCC Pricing Record Manual (PDF)</a></li> <li><a href="https://www.nscc.com/api-specs">API Specifications for RealTime Pricing</a></li> <li><a href="https://www.nscc.com/sandbox">Sandbox Environment Access</a></li> </ul> </section></main>