Ticker changes: inspect issue identity before linking old and new records

A changed label is not a complete history of the instrument

A news headline may say that a ticker has changed. A data file may then show a new short code beside a familiar company name. Before joining the histories, preserve what each field identifies and what the source actually says about the transition. A neat old-to-new arrow is not enough to establish that quantities, contractual rights or price-series treatment stay unchanged.

This worksheet reviews one proposed mapping and two supplied observations. It keeps the old and new labels in place, checks the identifier grain and compares the observations with the stated effective boundary. It does not rewrite a portfolio, migrate a database, infer a conversion ratio or turn a notice into an instruction to trade.

Read the ASX code and issue identifier as separate fields

ASX publishes a table with dated old and new company details, including code changes and name-only changes. Its code guidance separately explains that an ISIN identifies a specific securities issue. The distinction matters: an issuer-level label and an issue-level identifier do not answer the same identity question. A row in a name-and-code table does not by itself supply every fact needed for your holdings or data history.

The worksheet therefore asks what the supplied identifier represents. If you choose issuer or unknown, it withholds a simple issue-continuity result even when the two strings match. The default DEMO ID is not a real ISIN and no checksum or directory lookup is performed. For another venue or a crypto asset, use that source’s actual identifier system and do not borrow ASX rules by analogy.

Sources: ASX — Codes and descriptors, ASX — Code and company name changes.

Same text, same namespace and same grain are separate requirements

An identifier has meaning within a system. Equal strings from different registries are not necessarily the same instrument. This small tool assumes you have selected a single exact namespace and declared issue-level grain for both records. It preserves that declaration with the source reference; typing it is not independent verification.

If old and new issue IDs differ, the tool explicitly says not to merge by ticker. That does not prove the instruments are unrelated: a corporate action could link them under rules this worksheet has not inspected. It means a simple same-ID label change is unsupported here. No merger ratio, token migration rate, split factor or new quantity is guessed.

A publication date is not automatically an effective instant

A notice can be published on one day and take effect on another. The ASX change table’s dated old/new structure is a useful reminder to preserve those dates, but an exact intraday boundary needs its own source evidence. The worksheet has separate fields for a Sydney effective date and a precise instant, and it checks their local-date consistency when both are supplied.

A date-only entry never gains midnight automatically. If an observation falls on the effective date and no instant is known, its side of the boundary is unknown. An old observation on an earlier Sydney day and a new observation on a later day can be ordered around the stated day without inventing a time. That still checks only the supplied convention, not the legal effect of a real notice.

Sydney dates can differ from the UTC file date

The NSW Government records the 2026 start of daylight saving on 4 October. The fictional example uses a later October date and an explicit+11:00 offset. Its stated midnight on 21 October is 13:00 UTC on 20 October. Reading the UTC date as the Sydney effective day would place the transition in the wrong diary day.

The old observation at 12:59 UTC is 23:59 Sydney on 20 October. The new observation at 13:01 UTC is 00:01 on 21 October. Their labels and IDs match the proposed old/new mapping. These are calculated relationships in an invented record set, not evidence that a real instrument changed at midnight. The worksheet does not assume all Australian locations use Sydney time.

Sources: NSW Government — Daylight saving.

A notice and an observed record support different claims

The notice reference describes the proposed change. Each observed record separately needs a symbol, issue ID, timestamp and saved reference. If the new record still shows the old symbol, the tool flags that discrepancy rather than relabelling it. If its ID differs from the proposed new ID, that mismatch remains visible as another issue.

A plausible explanation might involve delayed distribution, a stale display, another share class or an incorrectly transcribed record. The worksheet does not choose among those explanations. It also rejects an old observation that is not earlier than the new observation, or a record timestamp later than the report’s as-of time. These are narrow chronology checks, not a current-market status probe.

A consistent card does not authorise a merge

The successful result means the typed mapping fields and the two typed records agree under this model. The output still sets merge authorisation to no and leaves corporate-action ratio, holdings and current trading status unknown. This is deliberate: the tool has not read your account or independently validated the notice, IDs or asset rights.

Do not use it to splice charts without investigating the series definition. A continuity rule for price data may require adjustments that a ticker record cannot supply. Likewise, a token moving to a new network requires network and asset identifiers beyond a short code. Keep those separate questions separate instead of treating every rebranding as the same corporate action.

Preserve the original history and the unresolved question

Keep the source’s exact old and new wording, the namespace, issue IDs and the date evidence with your own records. If you discover a corrected notice, create a new review and retain the earlier one. An amended source should not silently rewrite what you originally had available. The CSV keeps both observations and their discrepancy lists.

The tool reads only what you enter and never opens the supplied URL. It does not fetch an ASX directory, validate a security issue, change a symbol in an account or alter any files. Formula-like text is protected in the audit export, and edits invalidate stale results. The method and fictional table remain readable with JavaScript disabled; the optional site offer remains a separate choice.

Use the open issues to choose the next piece of evidence

An unknown boundary calls for the source’s timing convention. A missing issue ID calls for an issue-level reference, not a more familiar company name. Different IDs call for the actual transition terms rather than a one-to-one assumption. These are different gaps and should not be collapsed into a generic failed or complete label.

Once the evidence is available, add it to a new dated card and compare the outcome with the earlier audit. If the missing information cannot be obtained, keep the relationship unresolved. A clear unresolved record is more useful than a confident join that later makes an old price, quantity or ownership statement impossible to trace.

Worked examples

{
  "venue": "DEMO Australian venue",
  "id_namespace": "DEMO issue-level registry",
  "id_grain": "security_issue",
  "old_symbol": "DEMO-OLD",
  "new_symbol": "DEMO-NEW",
  "old_id": "DEMO-ISSUE-0001",
  "new_id": "DEMO-ISSUE-0001",
  "notice_reference": "DEMO saved notice versionA",
  "notice_url": "https://example.org/demo-code-notice",
  "effective_date": "2026-10-21",
  "effective_at": "2026-10-21T00:00:00+11:00",
  "as_of": "2026-10-20T13:02:00Z",
  "old_seen_at": "2026-10-20T12:59:00Z",
  "old_record_symbol": "DEMO-OLD",
  "old_record_id": "DEMO-ISSUE-0001",
  "old_record_reference": "DEMO saved old-label record",
  "new_seen_at": "2026-10-20T13:01:00Z",
  "new_record_symbol": "DEMO-NEW",
  "new_record_id": "DEMO-ISSUE-0001",
  "new_record_reference": "DEMO saved new-label record"
}

Questions about the method

Primary sources and scope

1. ASX — Codes and descriptorsChecked 2026-10-20. Distinguishes code descriptions and a security-issue ISIN. No specific live ID is retrieved or validated.
2. ASX — Code and company name changesChecked 2026-10-20. Dated old/new details include code changes and name changes; the article does not infer an issue mapping or ratio from those rows.
3. NSW Government — Daylight savingChecked 2026-10-20. Observed 2026 start date 4 October and one-hour advance. Used for the fictional Sydney date conversion, not a universal Australian time rule.

Examples explain a method. They do not predict prices or establish where a trading service is available. Check the named source before relying on future schedules.