TWSE Versus TPEx: Verify the Venue Before Applying a Ticker Suffix

The suffix is a vendor route, not the legal identifier

Taiwan securities can trade on the Taiwan Stock Exchange (TWSE) or Taipei Exchange (TPEx). Many global quote services commonly request TWSE names with .TW and TPEx names with .TWO, but the exchanges identify the securities by native code, company name, market status, and ISIN or listing record. Different vendors may use different notation.

The safe workflow is venue first, vendor symbol second. A returned quote does not prove the venue, share class, currency, adjustment method, or that the instrument is still listed.

1. Exact TWSE example: Taiwan Semiconductor Manufacturing, code 2330

TWSE's exact company profile for code 2330 identifies Taiwan Semiconductor Manufacturing Co., Ltd., ISIN TW0002330008, semiconductor industry, and listing date September 5, 1994. The official TWSE ISIN directory also labels 2330 as TWSE listed. A vendor may request 2330.TW, but that string should be stored as a provider mapping beside the official identity.

2. Exact TPEx example: GlobalWafers, code 6488

TPEx's exact September 24, 2015 announcement states that GlobalWafers Co., Ltd. ordinary shares began TPEx trading on September 25, 2015 under code 6488, short name GWC, in the semiconductor category. The record distinguishes the ordinary TPEx listing from its earlier emerging-stock status. A global vendor may route it as 6488.TWO.

3. Why venue verification changes downloaded data

A wrong suffix can return no result, a stale object, or a different instrument. That error then flows into market capitalization, dividend yield, currency conversion, adjusted price history, and peer screens. The dangerous case is not always an obvious error; it is a plausible series attached to the wrong security.

Validate at least one dated close and share count against an official source before trusting a bulk import. Record whether the vendor adjusts for cash dividends, stock dividends, rights issues, splits, capital reductions, or trading halts. Raw and adjusted closes answer different questions.

4. Do not turn venue into a peer classification

TSMC and GlobalWafers are both connected to semiconductors, but their roles differ: one is a foundry and the other supplies semiconductor wafers. Venue does not establish business comparability. Build the peer thesis from products, customers, capital intensity, cycle exposure, and accounting periods after verifying the symbol.

If financial statements are compared, preserve native TWD values, exact year-ends, consolidation scope, and units. For cross-currency peers, use average rates for period flows and closing rates for point-in-time balances, with all rates dated. Do not convert price while leaving earnings in another currency and then calculate a multiple.

5. A machine-readable symbol audit

A robust scraper should store fields separately: native_code, exchange, market, isin, instrument_type, trading_currency, vendor, vendor_symbol, verified_at, and source_url. A vendor-symbol change should update a mapping, not overwrite the official identity.

Reject a price or fundamental row when the issuer name, venue, or currency conflicts with the security master. Quarantine ambiguous rows for review. This is slower than accepting every successful API response, but it prevents silent corruption of histories and ratios.

6. Taiwan verification checklist

• Start with the native numeric code and exact company name.
• Verify TWSE or TPEx using an exact current exchange or ISIN record.
• Confirm ordinary share, ETF, preferred share, warrant, or other instrument type.
• Store the vendor suffix as provider metadata, not as the exchange identity.
• Check TWD units, fiscal period, consolidation scope, and report language.
• Validate price adjustment rules after every material corporate action.
• Use venue and industry as separate peer-selection fields.
• Retain source URL and verification date so the mapping can be audited.