NUMBERVALUE in ONLYOFFICE: Convert Regional Number Text

=NUMBERVALUE(text, [decimal_separator], [group_separator])

The current official ONLYOFFICE NUMBERVALUE reference describes three arguments in this order.

Distinct concepts: Commas between formula arguments belong to the English syntax shown above; commas inside quotes can be decimal or grouping marks. Even if your regional setting changes the formula argument delimiter, a quoted text separator such as "," remains part of the input string. Review ONLYOFFICE’s regional settings for formula language, number formats and custom decimal/thousands separators.

Set A2:A8 as Text, then enter the characters shown below exactly. Do not type the quotes as cell contents; they indicate strings in this tutorial. If the editor autoformats a cell into a number, restore/import it as text before testing; otherwise the example no longer demonstrates conversion.

Formula and expected result table

Validation note: Decimal values were independently parsed with exact-decimal arithmetic. They are expected results only. The invalid word "INVALID" is the documented #VALUE! case; acceptance of a literal space as a grouping separator is a plausible interpretation of the group separator argument but specifically requires native ONLYOFFICE testing before relying on that example.

To confirm that a conversion is numeric rather than cosmetic, test an arithmetic step:

=NUMBERVALUE(A3,",",".")*2

Independently expected result: 2469 from 1.234,50 interpreted as 1234.50. If the result is displayed with currency, two decimal places or localized separators, that is cell formatting, not a different underlying arithmetic result.

Consider two vendor export files. One produces 1,000.25, where a comma groups thousands and a period separates the fraction. Another produces 1.000,25, where the roles are reversed. The formulas must specify different argument values:

=NUMBERVALUE("1,000.25",".",",")
=NUMBERVALUE("1.000,25",",",".")

Independently expected result for each: 1000.25. This is more reproducible than relying on =NUMBERVALUE(A2) without recording what region produced the spreadsheet. The official defaults when separators are omitted are locale-dependent.

Preserve identifiers as text. Converting text 0042 to the number 42 intentionally removes its leading zeros. If that value is a product SKU, laboratory specimen code or postal label, do not convert it. Similarly, a string like 00000123 should usually remain text unless numerical arithmetic is its genuine purpose.

Use three columns: A = original raw string, B = explicit NUMBERVALUE formula, C = manually verified reference value for a small sample. Confirm the first few rows and one extreme value for each input feed before copying B downward.

For a mixed feed, a formula such as:

=IFERROR(NUMBERVALUE(A7,".",","),"CHECK FORMAT")

has independently expected output CHECK FORMAT for A7 = INVALID because ONLYOFFICE documents a #VALUE! on nonnumeric text and supports IFERROR in its function catalogue. This combined behaviour still needs native execution. Keep the raw input even after adding a parsed numeric column, so incorrect separator conventions can be audited and corrected.

Avoid silently assuming the same feed always uses the same separators. A value like 1.234 is ambiguous without locale metadata: depending on convention, it may mean one thousand two hundred thirty-four or one and 234 thousandths.

• #VALUE! for a word or malformed number: The vendor explicitly documents #VALUE! for text that is not numeric. Check the actual stored text, not just its display.
• Strange magnitude: Check whether decimal/grouping separators were reversed (1,234 vs 1.234). Confirm the input feed’s documented locale.
• Spaces and nonbreaking spaces: The current reference calls the grouping symbol a character, but it does not specify all whitespace normalization or multi-character separator rules. Test with the exact imported characters, and mark space-group examples as provisional.
• Double conversion or lost zeros: If the imported cell is already numeric, you may not need this function. If the cell is a string identifier, you generally should not use it.
• Dates, currencies, percentages, scientific notation, and parentheses: The short vendor reference does not enumerate all accepted forms or the exact resulting errors. Don’t copy edge-case promises from Excel to ONLYOFFICE without native evidence.
• Different web/Desktop output: Record version, file format, Formula Language, region and imported cell type before diagnosing a purported engine difference.
• Separator arguments omitted: The vendor specifies locale-based defaults. Use explicit punctuation arguments for portable instructional examples, but still test on a destination build.

Microsoft’s NUMBERVALUE support page lists Excel for Microsoft 365, Excel 2024, Excel 2021, Excel 2019 and Excel 2016. Its description matches the broad purpose of ONLYOFFICE NUMBERVALUE, but does not prove identical acceptance of whitespace, percentages or malformed input.

ONLYOFFICE’s verified reference describes the function without a minimum product version; tests must establish whether a particular Desktop installation and hosted web editor calculate every sample identically. For Google Sheets, LibreOffice and other spreadsheet programs, this guide makes no feature-compatibility claim. Do not promise direct interoperability just because a formula has a familiar name.

Sources checked 13 October 2026:

• ONLYOFFICE NUMBERVALUE official reference
• ONLYOFFICE Spreadsheet Editor function catalogue
• ONLYOFFICE Advanced Settings: region and separators
• ONLYOFFICE VALUE reference — basic numeric-text conversion, not a substitute for explicitly documenting separators.
• Microsoft NUMBERVALUE official reference — comparative Excel applicability, not native ONLYOFFICE proof.

Native text import, whitespace separator acceptance, invalid-input boundaries, optional-argument defaults and localized execution remain untested. Preserve raw imported strings and confirm representative inputs in your own build.