Abstract

A historical dividend audit found eight cached records under LSI for 2011 and 2012 that contradicted the semiconductor issuer’s annual filing. We rejected those records for the issuer-specific return calculation. Their true origin remains unresolved.

The case exposes a prerequisite for corporate-action accounting: a matching ticker does not establish that an event belongs to the instrument being modeled. This note separates the observed contradiction from possible causes and specifies the evidence a historical join should retain.

1. The issuer-level contradiction

The audit concerned LSI Corporation, the semiconductor company identified in SEC filings by CIK 703360. Its 2013 Form 10-K, Note 5, states: “No cash dividend was paid in 2012 or 2011.” Eight records in our local delisted-security cache nevertheless represented dividends in those years under LSI.

The September 7 audit compared the records with previously retained rejected evidence. The cache hash and all eight objects matched. The diagnostic refused to calculate an LSI return index from those actions. It did not delete the cache or change production stores.

Matching hashes establish continuity of the inspected bytes. They do not establish the truth of the financial events. In this case, byte agreement preserved a contradiction rather than resolving it.

2. What the evidence does not identify

We have not established whether the mismatch arose during retrieval, provider symbol resolution, local storage, or another stage. Ticker reuse is a general reason to avoid undated symbol joins, but this audit does not prove that reuse caused these records to appear under LSI. It also does not identify another issuer as their source.

The justified action was narrower: exclude the disputed actions from this issuer-specific diagnostic until the conflict is resolved. Reassigning them to a plausible alternative issuer would replace one unsupported mapping with another.

This is one rejected sample, not a measured provider-wide error rate. We did not estimate its effect on historical strategies or certify the remaining cache.

3. Requirements for a historical security join

A ticker identifies a listing within a market context and time interval. An issuer can have multiple instruments, and an instrument can have multiple listings or symbol changes. An issuer identifier is useful evidence, but it is not a complete instrument key: a CIK identifies an SEC filer, not a particular share class or exchange listing.

A historical data model should retain an internal instrument identifier, its issuer relationship, and dated listing mappings. Corporate actions should attach to the affected instrument through an explicit mapping, with the source’s original identifier preserved. The mapping must preserve the dividend’s declared currency and share basis, including whether an amount is quoted before or after a simultaneous split.

Two time dimensions matter. The effective interval states when the mapping applies economically. The observation or knowledge time states when the research system could have used it. A cache retrieved in 2026 may support retrospective checking of an earlier event; its retrieval timestamp cannot establish what a historical strategy knew at the time.

These are design requirements, not a claim that our current store implements a complete historical security master. The normalized store examined in the audit lacked an issuer/CIK key. The issuer evidence supported only the bounded cases under review.

4. Rejecting a join without inventing a repair

An unresolved issuer conflict should stop the calculation that depends on that mapping. The rejection record should identify the disputed input, the conflicting source, and the affected operation. Preserve the original data so a later correction can explain what changed.

That does not mean silently treating a disputed dividend as zero. Zero is an economic assertion too. A validated replacement requires evidence for the event or for its absence, followed by a versioned change and a fresh calculation. The LSI diagnostic produced no index rather than substituting a guessed event history.

Correct dividend arithmetic cannot compensate for an event attached to the wrong security. Identity validation precedes the reinvestment and cash-ledger distinctions covered in our dividend-accounting note.

Evidence and disclosure

The filing quotation and issuer identity are available in the linked SEC document. Our local observation is summarized in the publication evidence summary. The vendor records and private audit files are not released, so readers cannot independently reproduce the cache comparison from this article.

Publication review checked the saved rejection records and selected evidence hashes. It did not rerun the research engine or acquire a new vendor sample. We disclose the aggregate count and the public filing quotation, not vendor payloads or a reconstructed corporate-action dataset.