Research draft

ISO 4217

vr.tr.iso-4217 · INF.MED

Enable an AI agent to recognise ISO 4217 as a maintained currency identification standard, assess which assignments apply in context, and decide whether to accept, translate, preserve or escalate a currency designation.

Thing Registry Information and virtual systems

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Researched by: Codex + Grok

Purpose and description

ISO 4217 is the International Organization for Standardization's three-letter alphabetic and three-digit numeric code system that uniquely identifies currencies, funds, and precious metals used in international financial transactions.

It can be Resolve a supplied designation against an authoritative ISO 4217 assignment at a stated date.; Translate between alphabetic and numeric representations while preserving the original input and leading zeros.; Classify a recognised assignment before deciding whether its use fits the requested operation.; Interpret a documented minor-unit exponent when the receiving interface uses that convention.; Compare list snapshots and assess which validations or stored interpretations an amendment affects.; Preserve historical designations and escalate unresolved aliases, conflicting evidence or unsupported application use..

Distinguishing features

Identify a standard governing currency representations, rather than a particular currency, monetary amount or exchange-rate feed.

Check for three-letter alphabetic and corresponding three-digit numeric representations, together with minor-unit relationships where applicable. [ISO standard description](https://www.iso.org/standard/64758.html?browse=tc)

Require an authoritative assignment lookup; a plausible three-letter ticker or currency symbol alone does not establish ISO 4217 membership.

Distinguish current currency and funds lists from registered funds and historical lists. [SIX currency-code maintenance](https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html?printout=1)

Treat a code's identification role separately from claims that the represented unit is legal tender, exchangeable or supported by a payment service.

Scope

+ Standard edition and authoritative code-list provenance

+ Alphabetic and numeric currency-code assignments and their correspondence

+ Distinctions among currency, fund and special-purpose assignments

+ Entity associations and limits on inferring geography from codes

+ Minor-unit interpretation and explicit treatment of unavailable information

+ Assignment changes, historical interpretation and application eligibility

- Currencies as monetary institutions, including issuance and monetary policy

- Exchange rates, valuations and redenomination calculations

- Legal-tender status and jurisdiction-specific payment obligations

- Payment-network support, settlement rules and transaction authorization

- Locale-specific currency symbols, formatting and cash-rounding rules

- Country-code governance and financial instrument or digital-token identification

Characteristics

Standard edition: Verified ISO edition designation; unknown if unverified Separates the governing specification from subsequent changes to maintained assignments.
Assignment evidence: Links to authoritative list snapshots and applicable amendment notices Makes acceptance or rejection of a designation traceable.
Alphabetic and numeric correspondence: Assigned three-letter representation paired with its three-digit representation Supports translation between representations without deriving assignments from spelling.
Assignment role: Currency, fund, precious metal, other documented special purpose, or unresolved Prevents all recognised codes from being treated as ordinary spendable currencies.
Temporal assignment state: Effective at reference date, announced for future effect, historical at reference date, or unresolved Supports different decisions for new transactions and historical records.
Listed entity associations: Documented associations between a designation and listed entities, qualified by date Prevents unsupported assumptions that each currency has exactly one country.
Minor-unit exponent: Documented decimal exponent n, where one minor unit equals 10^-n major units; retain explicit not-applicable and unknown states Supports amount interpretation without conflating zero decimal places with missing information.
List currency: Checked through a specified amendment or date, superseded, or freshness unresolved Shows whether a locally available list can support the intended decision.
Consumer acceptance: Link to the receiving application's accepted codes and amount conventions Separates ISO recognition from permission to use a designation in a particular workflow.

Where this came from

wikidata · CC0 1.0

Source repository Registry entry point

Drafted structure

Bundle to layer to finding to question, as the second pass will find it: 7 bundles · 13 layers · 20 findings · 39 questions.

Standard and Maintenance Authority Identify the governing ISO 4217 specification and the authority behind the assignments being applied.

An edition reference alone cannot establish which maintained code assignments an agent has checked.

Governing Specification

Establish which specification supplies the interpretation rules.

Edition and Rule Basis

Record the verified edition and distinguish consulted normative provisions from public summaries.

Which ISO 4217 edition governs this interpretation, and what evidence establishes its status? provenance
Which interpretation rules were read in the specification, and which remain supported only by summaries? boundary

Maintained Assignment Evidence

Establish the authority and coverage of the list snapshot.

Authoritative List Basis

Record the source list, retrieval context and amendment coverage; SIX identifies itself as the official maintenance agency. [SIX maintenance authority](https://www.six-group.com/en/products-services/financial-information/market-reference-data/data-standards.html?printout=1)

Which authoritative list or amendment establishes the assignment being used? provenance
What evidence shows that this snapshot includes changes effective on the decision date? measurement

Code Recognition and Correspondence Resolve code representations without mistaking syntactic plausibility for assignment.

Currency symbols, vendor tickers and malformed numeric representations can resemble ISO designations while requiring different handling.

Representation Recognition

Distinguish a supplied token's form from its authoritative meaning.

Syntax Versus Assignment

Record the original token, any normalization and the evidence that it matches an assignment.

Is the input an alphabetic code, numeric code, currency name, symbol or external alias? definition
After any explicitly recorded normalization, does the token match an authoritative assignment? provenance
Should an unassigned but syntactically plausible token be rejected or referred for alias resolution? action

Paired Designations

Preserve the meaning shared by the two code representations.

Verified Code Pair

Record the list-backed alphabetic-to-numeric correspondence, retaining all three numeric positions.

Which alphabetic and numeric codes identify the same assignment in the selected snapshot? definition
Can conversion preserve leading zeros and detect a supplied pair whose components disagree? action

Assignment Role and Entity Context Establish what a designation represents and what its entity associations actually support.

Recognition must not collapse funds, special-purpose designations and shared currencies into a one-country-one-currency assumption.

Represented Unit Role

Identify the assignment's documented economic or special-purpose role.

Assignment Purpose

Record the assigned name, list membership and documented purpose before allowing currency-like operations.

Does this assignment designate a currency, fund, precious metal or another documented purpose? definition
What authoritative wording limits its interpretation as an ordinary currency? boundary
Does the requested operation accommodate that role, or require a different model or explicit policy? action

Entity Association Boundaries

Represent listed associations without inventing territorial exclusivity or legal status.

Listed Entity Meaning

Record all relevant listed entities and separate those associations from independently governed monetary facts.

Which entities are explicitly associated with this assignment at the reference date? provenance
Would inferring a single country, legal-tender status or universal local acceptance exceed the list's evidence? boundary

Minor Unit and Amount Interpretation Establish what the listed minor-unit information permits an agent to infer about amount representation.

Incorrect scaling can change an amount's value even when its currency code is recognised.

Listed Minor Unit

Interpret the listed decimal relationship while preserving absent or inapplicable information.

Minor Unit Evidence

Record the documented exponent and distinguish a numeric value from an explicit non-applicable marker or missing evidence.

What minor-unit value is documented for this assignment in the relevant snapshot? measurement
Does the source specify an exponent, declare the field inapplicable or leave its meaning unresolved? definition

Amount Use Boundaries

Check the amount convention before applying a minor-unit relationship.

Scaling Preconditions

Require evidence about major-unit versus minor-unit encoding and delegate rounding or interface exceptions to the relevant model.

Does the receiving interface express this amount in major units, ISO minor units or another documented scale? boundary
Can the proposed scaling preserve the amount exactly, or does it require a separately authorized rounding rule? action
Which external rule governs cash rounding or permitted accounting precision for this use? provenance

Assignment Lifecycle and History Apply amendments according to their effective timing and preserve historical meaning.

A current-list lookup alone cannot resolve past records or announced changes.

Amendment Effect

Distinguish publication timing from the time a change takes effect.

Dated Assignment Change

Record what an amendment changes, when it takes effect and any unresolved precision in its timing.

Does the amendment change a code, name, entity association, minor-unit value or list membership? definition
What effective date is stated, and how does it differ from the announcement or retrieval date? measurement
Which dependent validations should change when the amendment becomes effective? action

Historical Resolution

Interpret older designations without silently rewriting the represented unit.

Historical Record Continuity

Preserve the original designation and distinguish assignment withdrawal from conversion or legal circulation; an amendment can place a currency in the historical list while describing parallel circulation. [SIX amendment 174](https://www.six-group.com/dam/download/financial-information/data-center/iso-currrency/amendments/dl-currency-iso-amendment-174.pdf)

Which assignment evidence supports this designation for the record's own date? provenance
Would replacing the historical code change the unit of account or require an independently sourced conversion? boundary
Should the designation remain valid for historical interpretation while being restricted for new operational use? action

Application Decisions and Exceptions Translate ISO assignment evidence into a justified decision for a specific consuming workflow.

Standard membership, historical interpretability and operational acceptance answer different questions.

Contextual Acceptance

Combine assignment status with the consumer's declared requirements.

Use Eligibility

Record whether the proposed operation requires recognition, current assignment, a particular assignment role or explicit consumer support.

Is the task archival interpretation, display, data interchange or initiation of a new monetary operation? definition
Which consumer rule determines whether this recognised designation is accepted for that task? provenance
Given the date, assignment role and consumer rule, should the agent accept, preserve, reject or escalate it? action

Unresolved Code Handling

Handle aliases and conflicting snapshots without inventing assignments.

Exception Resolution

Retain unresolved input and identify the evidence needed to resolve an external alias, stale list or conflicting interpretation.

Is the unresolved token an external convention, an assignment absent from the local snapshot or an input error? boundary
What authoritative update or documented external mapping would justify resolving it? provenance
Which operation must remain pending until that evidence is available? action

Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.

A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.