NUMBERVALUE in Collabora Office: Parse Imported Numbers with Explicit Separators

• Introduced: the original Collabora release and launch date are not established by the reviewed sources.
• Availability: documented in Collabora Office 26.04 desktop help.
• Platform scope: online and mobile deployment support is not inferred from the desktop documentation.
• Checked: October 14, 2026. Function-specific documentation and independent controls; no native Collabora execution.

=NUMBERVALUE(Text [; DecimalSeparator [; GroupSeparator]])

DecimalSeparator is a single character. GroupSeparator is a string specifying the grouping characters. The decimal character should not appear in the grouping specification.

The official page allows the decimal separator to be omitted when the input has neither decimal nor grouping separators, and allows the group separator to be omitted when no grouping is present. It does not establish a universal default for an ambiguous separated input. Supply the relevant separators instead of guessing from the current locale.

The result is numeric and displayed using the cell’s number format. “Locale-independent” describes parsing with the supplied separators, not a guarantee that every reader sees the same decimal punctuation afterward.

Format A2:A5 as Text before entering the first column. Calculate B with =NUMBERVALUE(A2;",";"."), filled down. The expected numbers below are displayed with English (USA) decimal punctuation.

The same parsing contract applies to every record: a full stop is grouping and a comma is decimal. The third record therefore means one thousand, not one.

=SUM(B2:B5) has expected numeric result 3364.375. A display format can show fewer decimal places, but the unrounded sum is still that value. Retain both source text and parsed number for an import audit.

Compare two explicit interpretations of the same string:

=NUMBERVALUE("1.234";".";",")
=NUMBERVALUE("1.234";",";".")

Expected results are 1.234 and 1234. Both are internally coherent under different contracts. Successful conversion therefore does not prove that you selected the correct convention for the original file.

The ratio is 1000. A data validation step should check the source specification or realistic quantity range; it should not assume that every plausible numeric result is correct.

The dedicated page explicitly demonstrates a two-character grouping string. Reproduce it with:

=NUMBERVALUE("1#!234#!567";".";"#!")

Expected result: 1234567. The grouping markers are removed, leaving the intended integer. This specific control does not certify every malformed or partially matching grouping pattern.

For a custom decimal character without grouping, =NUMBERVALUE("123·4";"·") has documented result 123.4. For scientific notation without either separator, =NUMBERVALUE("123e12") has documented result 1.23E+14, or 123000000000000.

The examples show why a parser must follow the field specification rather than merely remove all punctuation indiscriminately.

Return to the first fixture. Put =ROUND(B2;2) in C2 and fill down. Expected numeric values are 2345.75, 18.5, 1000 and 0.13. Their sum is 3364.38.

In this particular dataset, rounding the total also gives 3364.38. That agreement is not a universal rule: two separate values of 0.125 round to 0.13 each, totaling 0.26, while their unrounded sum is 0.25. Keep parsing and rounding as explicit stages with separate purposes.

=ISNUMBER(B2) should be TRUE for a successfully parsed numeric result. ISNUMBER confirms type; it cannot detect a wrong-but-valid separator choice.

Currency symbols, percent signs, whitespace cleanup, blank or Boolean coercion, malformed group placement and exact native errors are not fully specified by this dedicated source. This guide does not silently import another application’s rules. FIXED performs the reverse kind of task, creating formatted text; it does not recover an original import’s arbitrary separator history.

• Collabora Office 26.04: NUMBERVALUE.
• Editorial testing standards.

Complete dedicated product documentation reviewed. Outputs are independent decimal, positional, character or type models, or explicit vendor controls; no native Collabora execution. Formulas use English names and semicolon separators. Optional-argument brackets describe syntax and are not typed into working formulas.