Standards
ISO 4217 currency codes
Alphabetic and numeric codes for currencies and certain funds.
- Kind
- Vocabularies
- Steward
- International Organization for Standardization (ISO); SIX as maintenance agency
- Official source
- https://www.iso.org/iso-4217-currency-codes.html
What it describes
ISO 4217 assigns codes to currencies and certain funds for unambiguous representation in financial data. Three-letter alphabetic codes are familiar in prices and payments, while numeric codes support other exchange contexts. A currency code states the denomination of an amount. It does not state the exchange rate, valuation date, settlement currency, or the jurisdiction governing the transaction.
Currency codes and minor-unit conventions can change, particularly after monetary reform or a change in legal tender. Historical data must retain the code used at the time and the source of any conversion. A value without a currency code is ambiguous; a value with one can still be misleading if its amount, date, or rate basis is absent. Treat those as separate fields.
Structure
Three-letter alphabetic or three-digit numeric code, with associated minor-unit information.
Useful for
- Disambiguate monetary amounts.
- Reconcile payment and reporting currencies.
- Track historical code changes.
Limits
- Does not provide an exchange rate.
- Minor-unit rules may change.
- Currency alone does not establish transaction jurisdiction.
How it is used in practice
Every price, balance and payment needs a currency. ISO 4217 provides the three-letter alphabetic codes that appear in invoices and payment messages, the three-digit numeric codes used in some systems, and the minor-unit exponent that says how many decimal places a currency has. The standard also includes codes for some funds and for special purposes, such as a code for transactions where no currency is involved and one reserved for testing. A maintenance agency publishes the current list and the history of changes.
The minor unit matters when amounts are stored as integers. Most currencies use two decimal places, some use none, and some use three, so an integer amount without the exponent is ambiguous by a factor of ten or a thousand.
A worked example
A fictional treasury file lists a payment of 1,500 in a column labelled amount, with a currency column reading JPY, and another payment of 1,500 reading EUR. A reporting tool converts both to a base currency by multiplying by a rate. The yen payment is worth far less than the euro payment even though the numerals are equal.
An auditor reviewing the file asks for the rate source, the rate date and the minor-unit convention. The record holds the currency code as stated by the bank message, the amount as an integer in minor units together with the exponent from the code list, the rate with its provider and timestamp, and the converted amount as a separate derived field. A later restatement of rates changes the converted figure, not the original, and the audit trail shows both.
Evaluating a claim that rests on a currency code
A currency code states the denomination of an amount. It does not state the rate, the date of valuation or the legal tender status. A claim that a contract was worth a figure in euros needs the contract's own statement of currency, and a conversion needs a rate source and date. If the document states a sum without a currency, the correct entry is an unknown currency, not a guess from the country of the parties.
Check changes over time. When a country adopts a different currency, the old code is withdrawn and the new one begins, and historical data uses the code in force at the time. Croatia's adoption of the euro at the start of 2023 replaced its previous national currency code in current data. A time series that spans such a change needs a documented conversion at the fixed rate. A silent recode makes the earlier amounts appear to be in euros.
Confusions to avoid
Currency codes resemble country codes, because many alphabetic codes begin with a country's two-letter code, but they are separate standards. A currency may be used in several countries, and a country may use several currencies. Do not infer one from the other.
A symbol is not a code. The dollar sign is used for many different currencies, and the same symbol may precede different amounts in different documents. Store the code and the symbol-as-printed separately. Likewise, informal or cryptographic asset tickers are not ISO 4217 codes, and a field that mixes them needs a second column naming the scheme.
Questions a reviewer can ask
Is the currency stated in the source document, or inferred? Is the minor unit stored with the amount? Which rate, from which provider and at what time, was used for any conversion? Does the series cross a currency change, and what fixed rate was applied? Are codes for funds, special codes and nonstandard tickers separated from ordinary currency codes? Is the converted value stored apart from the original amount?
Related terms
Found an error on this page? See corrections for what counts as one, how to report it and the dated log.
Enquiry
Which of your sources carry ISO 4217 currency codes?
Tell us which sources carry it, which key the same entity some other way and who may read which. We reply with whether and how a first record would use this vocabulary.
Or write to [email protected] in your own words.