BAHTTEXT in Collabora Office: Express a Baht Amount in Thai Words

=BAHTTEXT(Number)

Number is the single required input. The Collabora help describes a number whose integral portion is expressed with the baht currency name and whose decimal portion is expressed with the satang currency name.

There is no currency-code, exchange-rate or output-language argument. Enter the amount already denominated in baht. Passing an amount in another currency does not convert its value into baht.

Enter the number 12.65 in A2. In B2 enter:

=BAHTTEXT(A2)

The expected result is a Thai-character text string meaning twelve baht and sixty-five satang. The vendor’s example specifies this meaning rather than publishing the literal Thai character sequence, so this guide does not claim an independently verified character-for-character native output.

The underlying amount can be checked independently: 12.65 baht = 12 baht + 65 satang. Keeping A2 numeric makes it available for arithmetic, while B2 is the human-readable wording.

A direct formula supplies the same documented control without a cell reference:

=BAHTTEXT(12.65)

When testing in the application, compare the meaning, currency names and numeric input. Do not compare an English explanatory gloss with the Thai output as though the gloss were the returned string.

Enter 8.40 in A2 and 4.25 in A3. In A4 calculate the numeric total; in B4 generate the wording:

A4: =SUM(A2:A3)
B4: =BAHTTEXT(A4)

The numeric expectation for A4 is 12.65, and B4 should express the same documented twelve-baht, sixty-five-satang amount. This workflow keeps the words tied to the current calculated total instead of maintaining a second manually typed amount.

Use A4, not B4, in later totals, discounts or balance calculations. BAHTTEXT’s text is suitable for a display or printable form; it is not a substitute for a numeric accounting field. SUM explains the numeric aggregation step.

The dedicated BAHTTEXT section does not specify how inputs with more than two fractional digits are rounded. To make a two-decimal reporting policy explicit, round the numeric amount first.

For a raw amount of 12.654 in D2:

E2: =ROUND(D2;2)
F2: =BAHTTEXT(E2)

The independent decimal check is E2=12.65, bringing F2 back to the documented control’s meaning. This does not establish what =BAHTTEXT(12.654) would do without the explicit rounding step. See ROUND for the separate numeric operation.

Changing only the display format of D2 to two decimal places is not the same as explicitly calculating a rounded value for E2. Keep the displayed amount and the input to BAHTTEXT aligned in a printable report.

If the formula appears literally, check that it was entered as a formula starting with = rather than as cell text. If the displayed words are unexpected, inspect the referenced numeric amount and any preceding rounding or currency-conversion step.

If Thai glyphs appear as boxes or render poorly, check the font and display environment. A rendering problem alone does not establish that the underlying formula result is wrong. Retain the numeric amount alongside the words so a reviewer can verify the intended value.

The function section does not define a complete native error matrix, accepted numeric-text coercions, precise handling of negative values, zero, very large amounts, or extra fractional digits. Those cases remain unverified here; do not infer their exact wording from another product’s implementation. Before issuing an important form, inspect the actual native result and have the Thai wording reviewed for the intended use.

Collabora identifies the namespace as COM.MICROSOFT.BAHTTEXT and says the function is outside the cited OpenFormula 1.3 standard. That namespace identifies the stored function; it does not prove identical behavior in another application or guarantee that an exported workbook will recalculate everywhere.

The exact function is documented in Collabora Office 26.04 desktop help, retrieved and reviewed on October 17, 2026. This establishes a documentation scope, not the first release that introduced the function or the last version in which it works; those versions and any retirement date remain unestablished. Collabora Online and mobile support are not inferred from desktop help, nor is behavior in another spreadsheet product.

The examples are documentation-based expectations with independent calculations. They have not been executed in Collabora Office. No application screenshot or native error/coercion certification is implied. Formulas use English function names and semicolon argument separators.

• Collabora Office 26.04: BAHTTEXT (checked October 17, 2026).
• Editorial testing standards.