If you are searching for how to translate CFI codes, how to translate ISO 10962 Classification of Financial Instruments codes, how to translate FISNs, or how to preserve standardized financial-instrument short names across languages, the first rule is to separate classification data from human-language explanation. A CFI code is controlled structured data; a FISN is a standardized short-name representation built under defined rules. Neither should be casually rewritten into target-language initials.
This matters in security-master databases, banks, brokerages, exchanges, market-data feeds, regulatory reporting, portfolio systems, corporate actions, investment research, trading platforms, reference-data services and financial APIs. A target can be linguistically fluent yet financially wrong if a six-letter CFI is altered, if a FISN is treated like free marketing copy, if an ISIN is confused with a classification code, or if the instrument’s issuer, type, currency or nominal terms drift during localization.
This guide explains how to translate around ISO 10962 CFI codes and ISO 18774 FISNs safely. It separates identity, classification and naming; explains how CFI and FISN relate to ISIN, MIC, currency and issuer data; shows how to handle abbreviations and standardized short names; and provides a QA workflow so multilingual financial records continue to describe the same instrument with the same classification meaning.
1. CFI classifies; it does not uniquely identify
ISO 10962 defines an internationally valid classification system for financial instruments. The CFI tells systems about instrument characteristics and category. It is therefore different from an ISIN, which is designed to identify a particular financial instrument.
Translation control: Translate the explanation of the classification while preserving the six-letter CFI code. Quality assurance: Verify that CFI and ISIN remain in separate fields throughout the workflow.
2. CFI is a six-letter code
SIX describes the CFI as a six-letter code whose positions describe instrument structure and characteristics. Those letters are controlled classification values, not initials that should be recreated from a target-language phrase.
Translation control: Keep all six characters unchanged unless authoritative reference data supplies a corrected CFI. Quality assurance: Run exact-length and allowed-character checks on target data.
3. The first CFI character expresses a category
The CFI code is positional: characters carry defined classification meaning rather than forming a pronounceable acronym. The first position identifies a broad category, while later positions refine attributes according to that category.
Translation control: Do not translate one letter into a target-language category initial. Quality assurance: Decode the CFI using the current standard or maintained reference data when explanation is required.
4. Later CFI positions depend on instrument category
The meaning of later CFI characters can differ depending on the category represented earlier in the code. A translator cannot safely interpret an isolated letter without the full six-character context.
Translation control: Treat the CFI as one structured unit rather than six independent abbreviations. Quality assurance: Validate interpretation through a standards-aware decoder or reference table.
5. CFI is not a ticker symbol
A ticker is a market-specific symbol used for trading or display. A CFI is a standardized instrument classification. The same instrument can have different tickers on different venues while retaining the classification appropriate to its characteristics.
Translation control: Keep ticker and CFI fields separate. Quality assurance: Check records containing both so a market symbol never overwrites the classification code.
6. CFI is not an ISIN
An ISIN answers which instrument; a CFI answers what kind of financial instrument and which coded characteristics it has. Both can be assigned to the same record because identity and classification solve different problems.
Translation control: Preserve both identifiers without using one as a replacement for the other. Quality assurance: Trace one instrument by ISIN and compare its CFI before and after localization.
7. CFI is not a MIC
A MIC identifies an exchange or trading venue under ISO 10383. A CFI classifies the financial instrument itself. Venue and instrument classification belong to different reference-data dimensions.
Translation control: Translate venue names and classification descriptions independently. Quality assurance: Audit tables where MIC and CFI appear adjacent to each other.
8. CFI is not a currency code
A financial instrument can have a nominal, trading, settlement or strike currency expressed with ISO 4217 codes. Those three-letter currency values are different from the six-letter CFI classification.
Translation control: Keep currency fields and CFI fields distinct in schemas and labels. Quality assurance: Check every instrument record for code-length and namespace consistency.
9. CFI can apply across traditional and newer financial products
ISO 10962 is designed to classify financial instruments broadly, including classical securities, derivatives and newer financial products. Translation should therefore avoid narrowing financial instrument to share or bond when the category is broader.
Translation control: Use instrument-neutral terminology until the CFI or source record provides a narrower type. Quality assurance: Review target wording against the decoded category.
10. CFI should reflect authoritative instrument characteristics
The classification is based on instrument characteristics defined under the standard. A translator should not generate a new CFI because a translated product description sounds like another category.
Translation control: Treat classification assignment as reference-data governance rather than language work. Quality assurance: Escalate description-CFI mismatches to the responsible financial-data owner.
11. Certain lifecycle changes can affect CFI
ISO notes that CFI characteristics are generally defined at issuance and remain stable, while some events can lead to a new CFI for the same instrument, such as changes in particular rights or restrictions. This is a data-governance event, not a translation edit.
Translation control: Preserve the source CFI until an authorized reference-data update is supplied. Quality assurance: Record effective dates for classification changes.
12. Historical CFI values can be correct historical evidence
A translated archive may contain a CFI that was valid before an instrument event or a standards revision. Replacing it automatically with a current code can rewrite the historical record.
Translation control: Keep event-time classification when translating evidentiary material. Quality assurance: Distinguish archival fidelity from current security-master normalization.
13. A FISN is a standardized financial instrument short name
ISO 18774 defines an international method for building financial instrument short names within a defined structure. The FISN is designed to be human-readable while remaining interoperable with financial systems.
Translation control: Treat a FISN as controlled reference data rather than ordinary free-form translation. Quality assurance: Verify the source FISN against authoritative instrument reference data.
14. FISN is not the same as a ticker
A ticker is venue-specific, while a FISN is a standardized abbreviated name intended to work across financial services. A ticker may change by market even when the FISN remains a reference name for the instrument.
Translation control: Do not translate a ticker into a FISN or vice versa. Quality assurance: Compare one instrument across venues to confirm the two fields remain distinct.
15. FISN is not the same as ISIN
ISIN is a structured identifier; FISN is a standardized human-readable short name. They complement one another in reference data rather than replacing each other.
Translation control: Keep ISIN machine identity and FISN short-name data in separate fields. Quality assurance: Check exports to make sure the FISN never enters the ISIN column.
16. FISN can combine issuer and instrument information
SIX illustrates FISNs using issuer information together with abbreviated instrument characteristics, such as instrument type, currency and nominal value where applicable. That makes the short name information-dense even though it is human-readable.
Translation control: Preserve the standardized FISN string and translate explanations outside it. Quality assurance: Compare the FISN components with issuer and instrument master data.
17. Issuer short name is reference data
A FISN can include a standardized issuer short name. Translating the legal or marketing name of the issuer in narrative prose does not authorize rebuilding the FISN with target-language company initials.
Translation control: Keep the FISN issuer component as assigned by the reference-data authority. Quality assurance: Verify the issuer-FISN relationship against the same instrument record.
18. Instrument abbreviations inside FISN are controlled
Short forms for shares, bonds or other instrument attributes can be standardized within FISN construction. They should not be expanded and re-abbreviated according to a translator’s preferred target-language shorthand.
Translation control: Translate a separate explanatory label if users need a localized description. Quality assurance: Check that the standardized FISN remains exact where required.
19. Currency inside or associated with FISN is separate reference data
A FISN example can include a currency code as part of the instrument short-name information. The currency code follows its own ISO identity and should not be translated into a currency symbol or local-language abbreviation.
Translation control: Preserve ISO 4217 codes inside standardized FISN strings. Quality assurance: Compare currency fields and the FISN for consistency.
20. Nominal value is not prose
Debt and equity instruments can contain nominal or par-value information. If such a value is represented in a standardized short name, changing decimal punctuation or grouping casually can alter the standardized FISN.
Translation control: Preserve the assigned FISN and localize explanatory displays separately. Quality assurance: Validate nominal value against the instrument master record.
21. FISN is readable but still not free text
Because a FISN looks more like a name than an identifier, translators can be tempted to improve style, spell out abbreviations or reorder components. That defeats the standardization purpose.
Translation control: Treat FISN as protected reference text. Quality assurance: Flag any target FISN that differs from the source without an explicit reference-data update.
22. The language of an instrument is a separate field
Financial-data systems can store a main language applicable to an instrument. That language metadata is not itself the FISN, CFI or ISIN. A change in interface language does not automatically change the instrument’s reference language.
Translation control: Keep language metadata separate from financial identifiers and names. Quality assurance: Test multilingual display without changing the instrument master record.
23. Product name and FISN can coexist
Issuers often assign a marketing or product name that is longer, more expressive and potentially localized. The FISN serves a standardized short-name function. A user interface can display both when appropriate.
Translation control: Translate product marketing copy according to project rules while preserving the standardized FISN. Quality assurance: Check that search and export use the correct field for each purpose.
24. Legal name and short name should not be merged
The issuer’s full legal name, short issuer name and the instrument FISN solve different problems. Merging them into one translated field can make corporate identity and instrument naming ambiguous.
Translation control: Keep entity and instrument names structurally separate. Quality assurance: Review issuer-level and instrument-level joins after localization.
25. CFI explanation can be localized without changing the code
A user may need a target-language explanation that a CFI represents an equity, debt instrument, option, future or other category. That explanation is valuable, but it should be generated from the code using authoritative definitions rather than by replacing code letters.
Translation control: Translate decoded descriptions, not the code itself. Quality assurance: Compare the localized explanation with the authoritative CFI decode.
26. FISN explanation can be localized alongside the standardized string
A professional platform can show the FISN and a longer localized instrument description. This gives users readable information without sacrificing reference-data interoperability.
Translation control: Keep standardized and localized-name fields visibly distinct. Quality assurance: Search both fields and confirm they resolve to the same ISIN.
27. Reference-data providers can enrich CFI and FISN
Security-master services may attach issuer, instrument type, currency, maturity, market and other attributes to the same record. Translation should not assume all those attributes are encoded in CFI or FISN themselves.
Translation control: Translate each descriptive field according to its own semantics. Quality assurance: Use the instrument key to preserve relationships across the enriched record.
28. CFI assignment is not a linguistic inference problem
Two financial products with similar English names can have different classifications because their contractual characteristics differ. Conversely, different marketing names can map to the same broad category.
Translation control: Do not classify from surface wording alone. Quality assurance: Require authoritative instrument data for any CFI correction.
29. FISN generation is not ordinary summarization
A model can shorten an instrument name into a plausible phrase, but that does not make the result an ISO 18774 FISN. Standardized short-name construction follows defined rules and allocation processes.
Translation control: Do not use free-form summarization to create production FISNs. Quality assurance: Compare assigned FISNs with the registration or reference-data source.
30. National Numbering Agencies play a reference-data role
ANNA and National Numbering Agencies participate in the global infrastructure around ISINs and FISNs, with agencies feeding instrument information into central services. Translators should respect those assigned reference values rather than creating local substitutes.
Translation control: Treat NNA-supplied CFI/FISN data as protected master data. Quality assurance: Record the source agency or data provider where provenance matters.
31. ANNA data can include ISIN, CFI and FISN together
The same financial instrument can have an ISIN for identity, a CFI for classification and a FISN for a standardized short name. This trio is useful precisely because each field contributes something different.
Translation control: Translate only the descriptive layers around the trio. Quality assurance: Check that all three still belong to the same instrument after localization.
32. One instrument can trade on multiple MICs without changing the basic trio
Venue identity is handled separately through MICs. A financial instrument can appear on multiple markets while its ISIN, CFI and FISN continue to describe the instrument itself.
Translation control: Keep market and instrument reference data separate. Quality assurance: Test cross-listed instruments to ensure venue changes do not overwrite CFI/FISN.
33. A change in ticker does not automatically change FISN
Tickers are market-specific symbols and can change for corporate or venue reasons. FISN follows standardized instrument naming rules and should not be regenerated merely because the ticker changes.
Translation control: Treat ticker maintenance and FISN maintenance as separate processes. Quality assurance: Check change logs when one field changes and another does not.
34. A change in issuer name may require governed reference-data review
Corporate actions, mergers or renamings can affect issuer data and potentially standardized names according to applicable rules. Translators should not rewrite FISNs from news knowledge or a newly translated corporate name.
Translation control: Wait for authoritative reference-data updates. Quality assurance: Record effective dates and old/new values when master data changes.
35. Corporate actions can create new instrument records
Splits, conversions, reorganizations or other events can change instrument characteristics or identity. Translation should preserve the source record rather than guess whether a new ISIN, CFI or FISN should exist.
Translation control: Route corporate-action interpretation to the responsible reference-data process. Quality assurance: Keep pre-event and post-event records distinguishable.
36. Security-master tables need explicit columns
A spreadsheet with ISIN, CFI, FISN, ticker, MIC, currency and issuer can be extremely compact. Ambiguous translated headers such as code, name or market can make the table unusable even if every value survives.
Translation control: Translate field names precisely and keep original schema mappings. Quality assurance: Reimport the localized file and confirm each column lands correctly.
37. CFI columns should be stored as text
CFI is alphabetic reference data. It should never be case-folded, spell-checked or converted into a localized word. Spreadsheet autocomplete and find-and-replace operations can still damage short codes.
Translation control: Lock the CFI column as text/reference data. Quality assurance: Compare exact source-target strings after processing.
38. FISN columns should not be spell-checked as prose
Standardized abbreviations inside FISNs can look unusual to office software. Automatic spelling correction, smart punctuation or typography normalization can alter the string.
Translation control: Disable language-side autocorrection on FISN fields. Quality assurance: Run exact comparison against source reference data.
39. CSV delimiters can collide with human-readable financial names
Instrument names can contain punctuation, spaces and abbreviations. Poor CSV quoting can split FISNs or long names into extra columns during localization export.
Translation control: Use schema-safe quoting and structured interchange. Quality assurance: Round-trip representative rows through the production import process.
40. JSON and XML should separate code and display fields
APIs can expose cfi, fisn, isin, ticker, mic and localized description fields separately. Translating schema keys or flattening them into one string destroys machine readability.
Translation control: Localize the presentation layer while preserving reference-data fields. Quality assurance: Run schema and contract validation after translation.
41. Databases should not key instruments by translated names
Localized product names are useful for search and display but can change by language. Instrument identity should be anchored in stable identifiers such as ISIN or internal master keys, with CFI and FISN attached as reference attributes.
Translation control: Keep translated names out of primary identity joins. Quality assurance: Switch locale and verify instrument relationships remain unchanged.
42. Translation memories can pollute standardized names
A translation memory may suggest a prior instrument name or FISN from a similar security. Financial strings can differ by one issuer, currency, coupon or nominal value, making near-matches dangerous.
Translation control: Protect CFI, FISN, ISIN and numeric terms as variables or non-translatable fields. Quality assurance: Search target output for reference strings absent from the current source.
43. Machine translation should not touch CFI
A six-letter CFI can look like an abbreviation or unknown word to a language model. Expansion, case change or punctuation insertion would corrupt classification.
Translation control: Mask or lock CFI fields before machine translation. Quality assurance: Verify exact code sets after restoration.
44. Machine translation should not rewrite FISN
A FISN is intentionally human-readable enough to tempt machine translation, but standardization depends on preserving its assigned form.
Translation control: Exclude FISN values from general MT input and translate a separate explanatory name instead. Quality assurance: Compare the target FISN with the security master.
45. Generative AI should not assign CFI from a product title alone
A model can infer that a product sounds like a bond, option or share, but CFI positions depend on precise characteristics. Missing contractual details can change the code.
Translation control: Use AI for explanation and anomaly detection, not final classification. Quality assurance: Require reference-data evidence before changing a CFI.
46. Generative AI should not invent FISNs
A plausible abbreviated instrument name may not comply with ISO 18774 or the allocation conventions used by the responsible numbering agency. The output can look professional while being non-standard.
Translation control: Use assigned FISNs from authoritative sources. Quality assurance: Reject generated short names in protected FISN fields.
47. OCR can damage six-letter CFIs
Scanned statements can confuse I with 1, O with 0 or other characters. A six-position string can still look code-like after one error.
Translation control: Check OCR-derived CFIs against allowed values and the instrument record. Quality assurance: Do not guess a replacement from appearance alone.
48. OCR can also alter FISN punctuation and abbreviations
FISNs contain compact issuer and instrument information, so a missing slash, decimal point or abbreviation can change the standardized string. OCR output should be treated as a draft.
Translation control: Retrieve reference data electronically where possible. Quality assurance: Compare the OCR result with authoritative FISN records before translation.
49. Right-to-left layouts need identifier isolation
Arabic and Hebrew financial interfaces can contain Latin-script CFIs, FISNs, ISINs and MICs within right-to-left prose. Poor bidi handling can reorder punctuation or make codes hard to copy.
Translation control: Use directional isolation rather than reversing or transliterating the reference string. Quality assurance: Test visual order, selection and clipboard output in the final interface.
50. Localized digits must not alter embedded financial values
If a FISN contains currency or nominal-value information, changing digits into another glyph set may break exact matching even when the visible amount is understandable.
Translation control: Preserve the standardized FISN while presenting a localized long description separately. Quality assurance: Compare machine data across locales.
51. Search interfaces should index both FISN and localized description
Users may search by issuer name, instrument type, ticker, ISIN or a translated description. Keeping FISN as a stable searchable field improves cross-language retrieval without forcing the standardized short name to change.
Translation control: Index standardized and localized text in separate fields. Quality assurance: Search one instrument from multiple locales and verify a single master record is returned.
52. Accessibility can expose both the short name and a readable description
A dense FISN may be efficient for professional users but harder for screen-reader users or less experienced investors. An accessible interface can provide a localized expanded description while retaining the official FISN.
Translation control: Use accessible labels for comprehension without modifying reference data. Quality assurance: Test the same instrument with assistive technology in the target language.
53. Worked example: equity instrument
A security-master row contains ISIN, a six-letter CFI, FISN, issuer name, ticker and MIC. The French interface translates the long issuer and instrument descriptions where appropriate, but leaves CFI, FISN, ISIN, ticker and MIC in their governed forms.
Translation control: Separate reference data from localized presentation. Quality assurance: Compare the target row with the source master field by field.
54. Worked example: debt instrument with currency and nominal data
A bond record includes a FISN carrying standardized issuer and instrument information plus separate coupon, maturity, nominal currency and amount fields. The target translates explanatory bond terminology while preserving assigned reference strings.
Translation control: Keep structured financial attributes outside free prose where possible. Quality assurance: Reconcile currency, nominal terms and FISN against the master record.
55. Worked example: derivative on an underlying instrument
A derivative record can include its own ISIN, CFI and FISN plus an underlying instrument’s identity and market data. Translation that copies the underlying CFI into the derivative field would fundamentally change classification.
Translation control: Label direct and underlying instruments explicitly. Quality assurance: Trace both records independently after localization.
56. Worked example: ticker changes but reference data does not
A venue changes an instrument’s ticker. The localized platform updates the ticker according to market data but does not regenerate the FISN or CFI without an authoritative reference-data event.
Translation control: Apply each update to the field whose governance owns it. Quality assurance: Review field-level change logs after corporate actions.
57. Worked example: historical CFI
A regulatory archive contains an older CFI recorded before a later instrument event. The translation preserves that code because the report documents a past state. A current classification can be shown separately only if the project asks for it.
Translation control: Keep event-time and current reference data distinguishable. Quality assurance: Record the report date and classification source.
58. Worked example: near-match FISN in translation memory
Two bonds from the same issuer differ in currency and maturity. A translation memory suggests the earlier instrument’s compact short name. The reviewer rejects it because FISN is reference data, not prose to be borrowed from a similar segment.
Translation control: Populate FISN from the current instrument record only. Quality assurance: Scan the target for stale issuer/instrument strings.
59. Search intent: translate CFI code
A user may want to know what a six-letter code means, identify the instrument category, or translate the decoded characteristics into another language. The useful answer preserves the CFI and translates the explanation.
Translation control: Decode first from authoritative CFI definitions, then localize the human description. Quality assurance: Do not substitute a target-language six-letter code.
60. Search intent: translate FISN
A user may want to understand an abbreviated FISN, translate the issuer or instrument description, or know whether the short name itself should change. The standardized FISN generally remains the reference string while an explanation can be localized.
Translation control: Show the FISN and a separate translated explanation. Quality assurance: Verify every component against the source instrument master.
61. Reference route: ISO 10962
ISO 10962:2021 defines the CFI structure for an internationally valid classification system covering financial instruments. SIX acts as the maintenance agency for the CFI code data.
Translation control: Use ISO 10962 and current maintained CFI data for operational interpretation. Quality assurance: Record the standard and reference-data version used.
62. Reference route: ISO 18774
ISO 18774:2024 specifies rules for an international method of building Financial Instrument Short Names and emphasizes human readability and interoperability. It is the current ISO edition replacing the 2015 edition.
Translation control: Use ISO 18774:2024 for current FISN rules. Quality assurance: Do not rely on old short-name conventions without checking the applicable edition.
63. Reference route: SIX and ANNA data standards
SIX financial standards material places CFI, FISN, ISIN, MIC and related identifiers within a connected reference-data ecosystem, while ANNA and National Numbering Agencies support global instrument numbering and FISN allocation processes.
Translation control: Use authoritative reference data rather than rebuilding values during translation. Quality assurance: Keep provenance for instrument master values used in the target.
64. Connection to existing ISIN owner
eduKateSG already has a specialist owner covering ISIN, CUSIP, LEI and stock-ticker identity. This page does not duplicate that intent. Its job is classification and standardized short-name meaning through CFI and FISN.
Translation control: Link to the existing identifier owner when the user’s primary problem is instrument or entity identity. Quality assurance: Keep this page’s headings and examples focused on CFI classification and FISN naming.
65. Connection to the master translation architecture
This specialist article belongs beneath eduKateSG’s Master Art of Translation — Technical Translation System. The master owns broad specifications, terminology, QA and change control; this article owns financial classification and standardized short-name preservation.
Translation control: Link upward for general technical-translation practice rather than creating a competing finance-translation hub. Quality assurance: Keep search intent narrowly on ISO 10962 CFI and ISO 18774 FISN.
66. Provenance and versioning belong beside the translated record
A production security master should preserve the origin of its CFI and FISN values: the responsible numbering or reference-data source, the retrieval or effective date, and the instrument record to which those values belonged. This becomes especially important when standards are revised, instruments undergo lifecycle events, or several vendors distribute slightly different descriptive fields around the same governed identifiers.
Translation teams should record their own transformation separately from reference-data changes. If a localized long name changes, that is a language revision. If a CFI or FISN changes, the audit trail should point to an authorized financial-data event. Keeping those histories separate makes later reconciliation, compliance review and error diagnosis far more reliable.
67. A practical source-to-target verification loop
First extract the ISIN, CFI, FISN, ticker, MIC, currency and issuer key from the current source record. Second, translate only the human-language fields. Third, restore or retain protected reference values from the security master. Fourth, compare the target record field by field rather than as one sentence. Fifth, decode the CFI and read the FISN against the instrument attributes to detect mismatches that exact-string comparison alone cannot catch.
This loop separates identity, classification, naming and presentation. An exact CFI can still be attached to the wrong ISIN after a row shift; a correct FISN can still belong to a different bond from the same issuer. Relational integrity is therefore as important as character integrity.
68. Release checklist
Before release, preserve every six-letter CFI, keep CFI distinct from ISIN, MIC, ticker and currency, protect assigned FISNs from translation and spell-checking, verify issuer and instrument relationships, review lifecycle changes through reference-data governance, lock reference fields in CAT tools, validate spreadsheets and APIs, compare source-target code sets, check RTL rendering, and ensure localized long descriptions still describe the same financial instrument.
Then perform ordinary linguistic QA on instrument categories, issuer descriptions, security terminology and explanatory text. Reference-data integrity and language quality are separate controls and both must pass.
69. Final rule: translate the explanation, preserve the classification and standardized name
Financial reference data works because different standards answer different questions consistently. ISIN says which instrument, CFI describes what kind of instrument it is, FISN supplies a standardized short name, MIC says where it trades, and currency codes describe monetary units. Translation should make those relationships understandable without blurring them. Move the human explanation across languages; keep the governed reference values stable and auditable.