Lede
The Deal "Amount" in Zoho CRM is showing many extra decimal places (for example 12.3456789 instead of 12.35). That usually means the stored numeric value or the transformation layer (Deluge, API client, or locale parser) is exposing raw floating-point precision instead of a formatted currency value.
What it means
Zoho CRM stores currency and decimal fields with numeric precision but the UI and APIs can surface either the formatted display or the raw numeric value. Community reports show two common contributors: a Deluge/decimal-handling bug that affected Currency/Decimal fields and differences in how comma vs period decimal formats are parsed when pasting or importing values [1][2]. If you see extra digits when fetching records through the API, the Get Records/metadata behavior can surface unrounded values to clients [1][5].
Common causes
- Field precision is left high or unset, so the stored value contains many fractional digits [5].
- A Deluge function, workflow or custom function is performing math and returning unrounded floating results [1][6].
- Locale or paste-format mismatch (commas vs periods) causes the system to parse values incorrectly and produce odd fractional parts [2].
- Your integration or API client shows the raw JSON numeric value instead of the module’s formatted display value [1][5].
How to fix it
- Confirm the field settings first: open Setup > Customization > Modules and Fields > Deals, edit the Amount (or custom currency) field and set Decimal Places to 2. Save and check a few records in the UI.
- Check organization currency/locale: open Setup > Company Details or Setup > Currencies and verify your default currency and locale decimal separator match how users paste values. Adjust if needed and test pasting a value [2].
- Inspect automation and functions: review any workflow rules, custom functions, or Deluge scripts that touch Deal.Amount. Add explicit rounding (for example, round(amount, 2) in Deluge) before writing back to the record. Community reports show Deluge math bugs can expose extra decimals so prefer explicit rounding [1].
- Fix integrations and API clients: when you call Get Records or other endpoints, format numeric values client-side to two decimals before display (for example, toFixed(2) or equivalent). If your client relies on the CRM formatted output, request the display/formatted field where available or apply rounding immediately after fetch [1][5].
- Clean existing data (if needed): if many records already contain unwanted decimals, run a bulk update via Data Import or a Mass Update function that sets Amount = round(Amount, 2). Test on a small set first.
- Reproduce and document: capture screenshots, record IDs, the API request/response, and any Deluge code that modifies the field.
When to escalate
Open a Zoho Support ticket when you can reproduce the issue after steps 1–4, and include a sample record ID, the exact API request/response, locale settings, and any Deluge code. If the problem matches the historical Deluge/decimal bug or looks like a server-side formatting regression, Zo