GridExtractOCR to Excel
Guides/Localization & Formatting

Handling International Currency Symbols & Decimal Separators in Table OCR

Published October 28, 2026 · 5 min read · GridExtract Technical Staff

The Problem with International Number Formatting in OCR

Global commerce operates under starkly contrasting typographic conventions for numeric punctuation. In the United States and the United Kingdom, numbers use a comma as the thousands delimiter and a period for decimals (e.g., $1,250,500.75). However, across Continental Europe and Latin America, the convention is inverted: periods represent thousands, and commas indicate decimals (e.g., 1.250.500,75 €). In Scandinavian and Swiss accounting, thin spaces are frequently used for thousands (1 250 500,75).

When an analyst processes a German or French vendor invoice using basic OCR software, the tool usually strips the comma or confuses it with a thousands separator, turning € 14,50 into 1450. A $14.50 charge suddenly registers as $1,450.00 in the accounting system.

How GridExtract Resolves Localization Ambiguity

  1. Contextual Suffix Inspection: The engine examines the trailing 2 or 3 characters of numbers. If digits follow a comma at the end of every value in a column (e.g., ,50, ,75, ,00), the comma is flagged as a decimal separator.
  2. Currency Symbol Disambiguation: Prefix and postfix currency symbols ($, €, £, CHF, ¥, kr) are parsed into separate semantic tokens, allowing calculations in Excel without string truncation.
  3. Universal Standard Output: In TSV and CSV exports, values can be normalized to standard decimal numbers ready for instant formula aggregation.

Format Normalization Matrix

Source StringRegional FormatGridExtract Normalized Output
1.450,80 €German / French (Euro)1450.80
$2,400.50US / UK (USD)2400.50
(850.00)US Accounting Negative-850.00
450.00-Legacy Mainframe Negative-450.00

Try It Online

Convert your international invoices or financial statements on the GridExtract Workbench, or read our guide on Why TSV is the Best Clipboard Format for Spreadsheets.

Currency & Numeric Formatting FAQs

Why do European decimal commas cause errors in English Excel?
In Germany, France, and Spain, numbers use a comma as the decimal separator and a period for thousands (e.g., '1.250,50 €'). When opened in an English-configured Excel spreadsheet, Excel interprets this as text or misplaces the decimal point by a factor of 100.
How does GridExtract detect international numeric conventions?
The engine analyzes the distribution of punctuation marks across entire columns. If numbers consistently feature periods followed by 3 digits and trailing commas with 2 digits, European formatting is recognized and normalized accordingly.
Are non-Latin currency symbols like ¥, £, and ₹ preserved?
Yes. All UTF-8 currency symbols are accurately recognized and parsed, allowing you to retain the currency context or strip symbols for pure numeric computation.
How are negative amounts denoted with trailing minus signs handled (e.g., '125.00-')?
In some legacy SAP ERP and mainframe reports, negative balances are printed with trailing minus signs. GridExtract identifies this convention and repositions the negative sign to the front (-125.00) so Excel treats it as a standard formula operand.
Can I choose between US (1,000.00) and European (1.000,00) output formats?
Yes. By default, exports use standard IEEE decimal points for universal spreadsheet compatibility, but you can retain raw character text using TSV copy.
What happens if a column contains mixed currencies (e.g., both USD and EUR)?
The parser retains the currency code alongside the numeric value in the cell to prevent accidental cross-currency summation.