← Back to catalogue
Published

ISO 4217

vr.tr.iso-4217 · thing-q37431

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 INF.MED

Bundle → Layer → Finding → Questions Filled

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.

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.

  1. Which ISO 4217 edition governs this interpretation, and what evidence establishes its status? provenance
  2. 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)

  1. Which authoritative list or amendment establishes the assignment being used? provenance
  2. 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.

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.

  1. Is the input an alphabetic code, numeric code, currency name, symbol or external alias? definition
  2. After any explicitly recorded normalization, does the token match an authoritative assignment? provenance
  3. 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.

  1. Which alphabetic and numeric codes identify the same assignment in the selected snapshot? definition
  2. 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.

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.

  1. Does this assignment designate a currency, fund, precious metal or another documented purpose? definition
  2. What authoritative wording limits its interpretation as an ordinary currency? boundary
  3. 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.

  1. Which entities are explicitly associated with this assignment at the reference date? provenance
  2. 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.

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.

  1. What minor-unit value is documented for this assignment in the relevant snapshot? measurement
  2. 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.

  1. Does the receiving interface express this amount in major units, ISO minor units or another documented scale? boundary
  2. Can the proposed scaling preserve the amount exactly, or does it require a separately authorized rounding rule? action
  3. 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.

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.

  1. Does the amendment change a code, name, entity association, minor-unit value or list membership? definition
  2. What effective date is stated, and how does it differ from the announcement or retrieval date? measurement
  3. 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)

  1. Which assignment evidence supports this designation for the record's own date? provenance
  2. Would replacing the historical code change the unit of account or require an independently sourced conversion? boundary
  3. 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.

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.

  1. Is the task archival interpretation, display, data interchange or initiation of a new monetary operation? definition
  2. Which consumer rule determines whether this recognised designation is accepted for that task? provenance
  3. 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.

  1. Is the unresolved token an external convention, an assignment absent from the local snapshot or an input error? boundary
  2. What authoritative update or documented external mapping would justify resolving it? provenance
  3. 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.

Reported evidence

Findings from the breadth pass, kept separate from the structural claims.

Kinds and varieties

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these kinds and varieties hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Identifiers and schemes

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these identifiers and schemes hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Standards and regulation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these standards and regulation hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Real-world use

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these real-world use hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Typical measurements

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these typical measurements hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Failure modes and hazards

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these failure modes and hazards hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Regional variation

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these regional variation hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Neighbouring kinds and how to tell them apart

Reported by the breadth pass; each item needs checking against its source before it becomes normative.

  1. Which of these neighbouring kinds and how to tell them apart hold for the sense of ISO 4217 this model covers, and on what evidence? provenance

Classifiers Filled

Family
Thing Registry
Category
Information and virtual systems
Entry kind
thing
Plane
INF
Domain
INF.MED

What it is Filled

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.

In 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

Out of scope

  • 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

Why it exists Filled

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.

Distinguishing features Filled

  • 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.

What robots and AI may and may not do Filled

Must not

  • Use withdrawn codes as current.
  • Invent codes for unofficial currencies.
  • Present codes as recognition of a state.

Only with a human decision

  • Changing codes in financial systems.

May

  • Look up currency codes from the official list.
  • Validate currency codes in data the agent is authorized to edit.

Moral aspects Filled

  • Errors in codes can misroute payments.
  • Currency changes affect people's money.

Who is affected

  • Banks
  • Businesses
  • Data users

Owners Filled

Steward

The standardization body and its maintenance agency.

Master systems

  • The standard's published code lists

Links to other meta-models Filled

parent

  • Q6545185 - registry parent class

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.iso-4217
  • Wikidata: Q37431 (https://www.wikidata.org/wiki/Q37431)

Direct properties not applicable Not applicable

  • Standard edition: Verified ISO edition designation; unknown if unverified
  • Assignment evidence: Links to authoritative list snapshots and applicable amendment notices
  • Alphabetic and numeric correspondence: Assigned three-letter representation paired with its three-digit representation
  • Assignment role: Currency, fund, precious metal, other documented special purpose, or unresolved
  • Temporal assignment state: Effective at reference date, announced for future effect, historical at reference date, or unresolved
  • Listed entity associations: Documented associations between a designation and listed entities, qualified by date
  • Minor-unit exponent: Documented decimal exponent n, where one minor unit equals 10^-n major units; retain explicit not-applicable and unknown states
  • List currency: Checked through a specified amendment or date, superseded, or freshness unresolved
  • Consumer acceptance: Link to the receiving application's accepted codes and amount conventions

Plane INF: no invented physical properties.

Recognition optional Filled

  • Three letters such as USD or EUR in financial data.
  • Three-digit numeric codes.

Capabilities and actions required Filled

  • 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.

Hazards and failure modes required Filled

  • Payment errors from wrong codes.

Standards and interfaces required Filled

  • ISO 4217, Codes for the representation of currencies, International Organization for Standardization.

Context of use required Filled

  • ISO 4217 is used in payment messages, accounting records, exchange rate data and commercial systems to identify currencies consistently.
  • Its codes help distinguish currencies that share names or symbols and support automated processing across countries.
  • Historical records require attention to the validity dates of assignments because currencies and their codes can change.

Sources Filled

  1. ISO 4217 Currency codes - Official definition and maintenance of the ISO 4217 currency code standard
  2. ISO 4217 - Overview of alphabetic and numeric codes, special codes, and historical currencies
  3. Wikidata item Q37431: ISO 4217 - identity and sense of the item

Open questions

  • Which normative edition and complete amendment baseline should this publication adopt, and has the full specification been read?
  • What exact rules govern assignment roles, exceptional code construction and possible code reuse across editions?
  • How complete and temporally precise are the available historical lists for reconstructing assignments at arbitrary past dates?
  • What precise semantics do authoritative minor-unit markers have for each special-purpose assignment?
  • Which target applications require documented departures from ISO minor-unit conventions, restrict recognised codes or use external aliases?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q37431/spec.json