Apple Numbers CURRENCYCODE Function: Currency Identity and Locale

The official CURRENCYCODE reference was retrieved October 15, 2026. It currently documents this function for Apple Numbers. The original introduction release and last functioning version are unknown from the checked sources. Current documentation is not a final supported-version endpoint or proof of identical behavior on every older client.

No native Apple Numbers session was executed. Numeric examples are independently calculated controls; locale-dependent examples retain their stated context. Apple’s shared function help is not a test of every Mac, iPhone, iPad or iCloud build.

CURRENCYCODE(value)

value is optional. =CURRENCYCODE() requests the default currency code for the computer or current document context. A supplied currency value asks about that value. Ordinary numbers and currency-looking text must be interpreted in their actual context; a symbol alone is not an unambiguous global currency identifier.

The official examples deliberately include regional conditions. Retain those conditions when reproducing the formulas instead of expecting a single output from every document on every device.

These are separate scenarios, not four simultaneous language settings in one document.

The second case follows Apple’s currency-value example. It should not be silently replaced with an arbitrary plain-text import that merely resembles ¥12. Similarly, the last case establishes the specifically shown pound-text example in its stated UK context, not universal parsing of every currency string.

In a fictional French (France) document, put =CURRENCYCODE() in B2. The official target is EUR. Record that code alongside the document’s intended currency policy before importing an unlabelled numeric column.

For a separate English (United States) control, =CURRENCYCODE(5) targets USD. Neither result proves that all imported rows are denominated in that currency. A default describes a context; the original data source still determines what an imported amount means.

Suppose four source records are explicitly labelled as follows: A: 120 USD, B: 80 USD, C: 90 EUR, and D: 10 EUR. Keep columns for record identifier, numeric amount and confirmed source currency code.

The independently calculated totals are 200 USD and 100 EUR. Adding all four numeric amounts produces 300, but presenting that number as USD or EUR would lose the mixed-currency meaning. No exchange rate has been provided, so this example intentionally has no single converted total.

Use the function as one contextual check while retaining the source’s explicit denomination. A mismatch between a default code and a source code is a reason to investigate the import, not permission to relabel every row automatically.

The yen/yuan-style symbol in Apple’s mainland-China example leads to CNY under that stated setting. Do not generalize the example into “every ¥ value means CNY.” Preserve the currency code as a separate field when exporting a table or exchanging data between regions.

For a text report, distinguish amount, code and display string. A row can carry amount 90 and code EUR even if the viewer’s ordinary default is USD. This data-design recommendation does not claim that Numbers automatically converts or retypes such a row.

Apple documents a document-level language/region choice on Mac at File > Advanced > Language & Region, and a language choice when creating a document. System defaults also depend on the device’s language/region settings. No setting was changed for this guide.

If the result changes after moving a document, compare the applicable document setting, system setting and stored input type before changing the formula. If an imported currency-looking string is ambiguous, preserve it and resolve its source denomination rather than guessing from a symbol.

The dedicated reference does not establish exact errors for malformed currency strings, arbitrary unsupported codes, blank cells or every mixed-currency expression. Those coercion cases remain untested. The four controls above are the supported reproducible examples, and their regional qualifiers are part of the expected result.