OCC Equities Special Settlements

How to use it

Effective-dated contract reference data. Adjusted (non-standard) contracts carry a modified deliverable; use the OCC settlement details rather than the standard 100-share multiplier for them.

Typical use

Contract identity, lifecycle, and adjusted-deliverable handling for US-listed options.

Limitations

Vendor-curated reference data: rows can be restated when AlgoSeek learns of a late or corrected event, so land each delivery as a snapshot rather than overwriting history. Identifies the adjusted root only (OptionTicker such as AAL1); there is no strike, expiration or call/put. Join to contract masters by root and date to get strikes and expirations. Deliverable semantics: each adjusted root has TotalDelivComponents rows, one per DeliveryComponents index. In all 69 roots of the sample, the row count equals TotalDelivComponents and StrikePercent sums to 100 across components. Cash components appear as UnderTicker = USD with SettlementMethod MON and StrikePercent 0 (19 sample rows, DeliverableUnits 100); stock components use CNS. Twelve other MON rows in the sample carry a non-USD UnderTicker with StrikePercent 100. Effective dating: ProcessDate = file/record date; SettlementDate = date delivery and payment is due (blank for 52 of 100 sample rows). There are no explicit start/end-date columns for the adjustment itself.

Coverage

Non-standard (adjusted) equity option contracts listed on US public exchanges after corporate events (mergers, splits, spin-offs, special dividends); data from 2017-11-01.

Usage constraints

• Licensed vendor data: never export raw rows to a tenant-local destination or include them verbatim in a public artifact; serve only through entitlement-checked platform reads.
• Do not treat the vendor's `Ticker` as a stable identity across time; join on an AlgoSeek security key (SecId or ASID, which are distinct) or the platform symbol mapping.

Known issues (8)

• Primary key is inferred; AlgoSeek's guide does not name one.
• Documentation discrepancyUnderTicker is described as 'underlying symbol name' but in the sample and guide Table 1 it holds the deliverable component symbol (including USD for cash, and different tickers per component of one option symbol, e.g. AGEN, USD, INKT for AGEN1).
• Documentation discrepancyTotalDelivComponents and DeliveryComponents are typed integer but delivered zero-padded to 2 digits (01, 02).
• Documentation discrepancyProcessDate is defined as the date OCC created the record, yet the sample file dated 20240315 contains rows with SettlementDate 20150330, so the daily file seems to carry earlier-settled records rather than only newly created ones.
• Documentation discrepancyCashAmount is described as per-contract, but sample values (e.g. 6.850000 with DeliverableUnits 100 for ACI1; 0.010200 for AGEN1) look like per-unit/per-share amounts; unit basis should be verified.
• Documentation discrepancyGuide revision table says initial release effective Feb 6, 2024 while the cover says Mar 2024.
• Documentation discrepancyGuide Table 1 shows a different set of tickers (AEMD1, AFMD1, AGEN1 ...) than the sample CSV (AAGR1, AAL1, ACB1 ...), both dated 20240315.
• Documentation discrepancyGuide columns match the 12-column sample header exactly, in the same order.