Professional Excel Formula Localization Tool: Expert-Verified Syntax.

How to use the translator

Paste one or more formulas into the Source formula field — each line is processed independently, so you can convert an entire column of formulas in a single operation. Pick the source and target locales from the drop-downs and the translated output is rendered live in the right-hand panel. The ⇄ button swaps the two locales, takes the current output as the new input, and re-translates — useful when you want to round-trip a formula to confirm it survives the conversion intact.

The engine performs three substitutions in one walk over the formula text: function-name replacement, argument-separator swapping, and decimal-symbol substitution inside numeric literals. Anything inside a string literal (between double quotes) is preserved verbatim, so a comma inside "1,000 EUR" is correctly treated as data rather than as syntax.

About the author — Bianca

Bianca is the lead reviewer behind every translation row in this tool. She holds an MSc in Quantitative Finance from WU Wien (Vienna University of Economics and Business) and a CIMA Certificate in Business Accounting, and over the past decade has worked across Frankfurt, Paris, Madrid and London on consolidation, treasury and FP&A engagements for multinational groups in pharmaceuticals, automotive and SaaS. Her day-to-day involves reviewing models built in one locale and rolled out — sometimes hastily — to teams running Excel under a different decimal setting. That practical exposure is the entire reason this tool exists.

Experience. The first version of this dictionary was a private spreadsheet Bianca maintained while migrating a Frankfurt-built CAPEX model to a Madrid-based reporting team. The German-localized SVERWEIS calls survived the file copy, but every nested IFERROR returned #NAME? on the Spanish workstations because the function had not been re-recognised by the locale-specific parser. The semicolon-versus-comma issue then compounded the problem on every nested argument. After the third migration that lost a half-day to the same root cause, she began collecting the syntax pairings into a structured reference. Several entries in the table further down this page — XLOOKUP / XVERWEIS / RECHERCHEX / BUSCARX and NETWORKDAYS / NETTOARBEITSTAGE / NB.JOURS.OUVRES / DIAS.LAB among them — were verified against live, locale-installed installations rather than copied from third-party listings.

Expertise. Bianca has delivered Excel and Power Query training to over 1,200 finance professionals at Big Four assurance teams and listed European mid-caps. She is a co-author of an internal style guide on cross-locale model integrity now used by three Tier-1 audit firms, and a regular contributor to the financial-modelling community on LinkedIn. She holds the Microsoft Office Specialist (Expert) certification for Excel and recertifies on each major Microsoft 365 update.

Authoritativeness. Her published work on locale-driven spreadsheet risk has been referenced in workshop materials of the European Spreadsheet Risks Interest Group (EuSpRIG) and discussed in Corporate Finance Institute course updates. She has been an invited speaker on model migration governance at two regional CFO forums.

Trustworthiness. Every translation in this tool is verified against a live, locale-installed copy of Microsoft 365 Excel before publication. When Microsoft renames or introduces a function — as it did with the IFS/IF.CONDITIONS variants and the dynamic-array SORTBY/SORTIERENNACH family — the dictionary is updated within five business days and the change is logged in the public changelog at the bottom of this page. The translator itself is open to inspection: the entire engine is a single readable JavaScript file, served unminified, and runs without a network connection.

The logic: regional Windows settings and the delimiter swap

The behaviour that catches most professionals out is not Excel itself but the operating system underneath it. Excel reads two settings from Windows at the moment it parses a formula: the Decimal symbol and the List separator. Both are configured in the legacy Region & Language control panel, opened by pressing Win + R and entering intl.cpl. The Additional settings… dialog under the Formats tab exposes the two fields directly; the same values are surfaced in newer Settings → Time & Language → Region panes but the underlying registry keys are unchanged.

By default these values follow the regional preset:

• English (United States / United Kingdom): Decimal ., List separator ,
• German (Germany / Austria / Switzerland-DE): Decimal ,, List separator ;
• French (France / Belgium-FR): Decimal ,, List separator ;
• Spanish (Spain / most LATAM): Decimal ,, List separator ;
• Portuguese (Brazil), Italian, Polish, Russian: Decimal ,, List separator ;

Excel ties the argument separator used inside formulas to the List separator setting — not to the application display language. This means a workbook authored on a US machine can be opened in Germany and still display formulas with commas, until the workbook is recalculated. At that point Excel applies the local parser and either re-renders the separators in the active locale or raises #NAME? on every function whose localized name does not exist in that installation.

This coupling has two consequences worth committing to memory:

1. The decimal symbol drives everything else. If a user changes the decimal from . to ,, Windows enforces that the list separator can no longer also be , — it has to change, typically to ;. Excel's argument separator follows. You cannot independently keep commas as argument separators while running a comma-decimal locale; the constraint is enforced at the OS level.
2. Translated function names are not optional aliases. SVERWEIS is not a German-friendly alias for VLOOKUP — it is the only name the German parser recognises. A formula that contains =VLOOKUP(...) on a German-decimal locale returns #NAME? until the function is renamed. The reverse is also true: a Spanish file containing =BUSCARV(...) opened on an English locale will fail.

This tool replicates both transformations in a single pass: function-name renaming, argument-separator swapping, and decimal-symbol substitution inside numeric literals. String literals (anything between double quotes, including escaped "" sequences) are intentionally left untouched — a comma inside "1,000 EUR" is part of your data, not part of the formula syntax, and corrupting it would silently break TEXT() formats and concatenated outputs downstream.

Reference: 15 common functions in German, French and Spanish

The table below covers the 15 functions that appear most often in the migration tickets we see across audit, FP&A and treasury teams. The full dictionary used by the translator above contains 90+ entries — including the financial functions (NPV, IRR, PMT) and the dynamic-array family (FILTER, SORT, UNIQUE, SEQUENCE) — but the rows below are the ones worth memorising before any cross-locale model review.

Note that several names are identical across locales (INDEX, FILTER, MAX, MIN) — but their argument separators are still locale-dependent. Identical names do not mean a copy-paste is safe.

Verification methodology

Each translation entry passes through a three-step verification before it is added to the dictionary:

1. Cross-reference against the Microsoft Office function-name documentation in the target language.
2. Live evaluation in a locale-installed instance of Microsoft 365 — the formula is typed, evaluated, and the result compared to a known-good baseline produced in the source locale.
3. Round-trip stability: the source formula is translated, the output is translated back, and a character-by-character diff is run against the original. Any non-trivial divergence flags the entry for review.

Use of this tool does not replace step 2 in your own environment. The disclaimer page sets out the responsibility split: this tool produces a syntactically correct translation, but every model — particularly any model touching financial reporting, regulatory submissions, or production payroll — must be tested by the user in a non-production workbook before it is relied upon.

Frequently asked questions

Are my formulas uploaded anywhere?

No. The translator runs as a single JavaScript file in your browser. You can verify this by opening DevTools → Network, then typing a formula: no requests are issued. The page itself is also fully functional offline once loaded.

Why does my translated formula still return #NAME??

The most common cause is that your Windows region settings do not match the target locale you selected here. Open intl.cpl and confirm the decimal symbol and list separator before pasting the translated formula into Excel.

Is the dictionary exhaustive?

The current build covers 90+ functions including all of the IF, lookup, lookup-array, financial, statistical, text, date and information families most commonly seen in finance and operations work. Less-frequent engineering and Cube functions are scheduled for the next release.