Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

A ticker is not an identity

Description and use

A trading system was improved by validating company names, expanding exchange suffix handling, and storing ticker currency to prevent mis‑trades caused by ticker reassignment.

Problem

Two trading APIs used the same four‑letter ticker to refer to different companies, causing an unintended trade and potential loss.

Outcome

The system now avoids trading misidentified securities, correctly handles multi‑exchange suffixes, and accurately applies currency for position sizing, eliminating the risk of unintended trades.

Workflow

  • 1. Retrieve Yahoo ticker and company name from screener.
  • 2. Generate candidate broker tickers by appending known suffixes.
  • 3. For each candidate, fetch broker company name via instrument lookup.
  • 4. Compare fuzzy token sets of Yahoo and broker names; if they match, accept ticker; otherwise refuse.
  • 5. Store the ticker’s currency from broker data for downstream calculations.
  • 6. Use the validated ticker for order placement.
  • 7. Log any refusals for audit.
  • 8. Periodically refresh broker instrument list and currency mapping.

Evidence

A symbol is a display label, not a primary key.

Source

The broker’s London listings all end in the same suffix, l_EQ. Here is what that single suffix actually contains, counted from my own instrument book this morning:

Source

  • Record date: 2026-09-15T07:01:35.851Z