BAHTTEXT
Supported, behaves as documentedCategory: Text · Last tested 2026-09-01
Real compatibility results for the BAHTTEXT function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.
Support matrix
| Engine | Documented | Live-tested | Verdict |
|---|---|---|---|
| Excel (desktop) | Yes | No — documented only | n/a |
| Excel for the web | — | Yes (recalc, 2026-09-01) | Supported, behaves as documented |
| Google Sheets | No | Yes (Drive import, 2026-08-31) | Supported, behaves as documented |
| LibreOffice Calc | Yes | Yes (25.8.7.3, 2026-08-31) | Supported, behaves as documented |
LibreOffice version history
We executed the same test cases under each LibreOffice release to show exactly when BAHTTEXT’s support changed — not documentation claims, real results.
| LibreOffice version | Verdict | Tested |
|---|---|---|
| 24.2.0.3 | Supported, behaves as documented | 2026-08-31 |
| 24.8.7.2 | Supported, behaves as documented | 2026-08-31 |
| 25.2.0.3 | Supported, behaves as documented | 2026-08-31 |
| 25.8.7.3 | Supported, behaves as documented | 2026-08-31 |
Executed test cases
Excel for the web (executed 2026-09-01 via OneDrive recalculation)
These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =BAHTTEXT(A2) | Microsoft's documented worked example: 1234 rendered as Thai text with a Baht suffix | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วน | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วนProvenanceMicrosoft's page publishes this example's result as the Thai string for "one thousand two hundred thirty four Baht", transcribed here character for character from the page: หนึ่ง (one) พัน (thousand) สอง (two) ร้อย (hundred) สาม (three) สิบ (ten) สี่ (four) บาท (Baht) ถ้วน (exactly). The documented output is a 31-character Thai string |
Matched |
| =ISTEXT(BAHTTEXT(A2)) | The result is a text value, not a number | True | TrueProvenanceExcel documents BAHTTEXT as converting "a number to Thai text", so the result is a text value and ISTEXT is TRUE. This case survives any locale-dependent difference in the Baht wording, unlike the exact-string case above |
Matched |
| =BAHTTEXT("abc") | A non-numeric text argument | #VALUE! | #VALUE!ProvenanceExcel documents the single argument as "A number you want to convert to text, or a reference to a cell containing a number, or a formula that evaluates to a number"; non-numeric text is the wrong argument type, which is Excel's documented #VALUE! case |
Matched |
Google Sheets (executed 2026-08-31 via Drive import)
Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =BAHTTEXT(A2) | Microsoft's documented worked example: 1234 rendered as Thai text with a Baht suffix | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วน | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วนProvenanceMicrosoft's page publishes this example's result as the Thai string for "one thousand two hundred thirty four Baht", transcribed here character for character from the page: หนึ่ง (one) พัน (thousand) สอง (two) ร้อย (hundred) สาม (three) สิบ (ten) สี่ (four) บาท (Baht) ถ้วน (exactly). The documented output is a 31-character Thai string |
Matched |
| =ISTEXT(BAHTTEXT(A2)) | The result is a text value, not a number | True | TrueProvenanceExcel documents BAHTTEXT as converting "a number to Thai text", so the result is a text value and ISTEXT is TRUE. This case survives any locale-dependent difference in the Baht wording, unlike the exact-string case above |
Matched |
| =BAHTTEXT("abc") | A non-numeric text argument | #VALUE! | #VALUE!ProvenanceExcel documents the single argument as "A number you want to convert to text, or a reference to a cell containing a number, or a formula that evaluates to a number"; non-numeric text is the wrong argument type, which is Excel's documented #VALUE! case |
Matched |
LibreOffice Calc 25.8.7.3 (tested 2026-08-31)
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =BAHTTEXT(A2) | Microsoft's documented worked example: 1234 rendered as Thai text with a Baht suffix | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วน | หนึ่งพันสองร้อยสามสิบสี่บาทถ้วนProvenanceMicrosoft's page publishes this example's result as the Thai string for "one thousand two hundred thirty four Baht", transcribed here character for character from the page: หนึ่ง (one) พัน (thousand) สอง (two) ร้อย (hundred) สาม (three) สิบ (ten) สี่ (four) บาท (Baht) ถ้วน (exactly). The documented output is a 31-character Thai string |
Matched |
| =ISTEXT(BAHTTEXT(A2)) | The result is a text value, not a number | True | TrueProvenanceExcel documents BAHTTEXT as converting "a number to Thai text", so the result is a text value and ISTEXT is TRUE. This case survives any locale-dependent difference in the Baht wording, unlike the exact-string case above |
Matched |
| =BAHTTEXT("abc") | A non-numeric text argument | #VALUE! | #VALUE!ProvenanceExcel documents the single argument as "A number you want to convert to text, or a reference to a cell containing a number, or a formula that evaluates to a number"; non-numeric text is the wrong argument type, which is Excel's documented #VALUE! case |
Matched |
Docs & syntax
- Excel (desktop): official documentation
- LibreOffice Calc: official documentation
Where BAHTTEXT behaves differently
- Your function exists but your file cannot say so: _xlfn storage tokens
Executed: eight IM* functions LibreOffice implements return #NAME? on all four builds because it cannot read Excel's _xlfn. token for them, while COT and CSC only work under that same prefix. Eleven LibreOffice aliases are erased by its own exporter, and a token change between 24.2 and 24.8 makes a 24.8-written file open as #NAME? in 24.2.