Decimal Places
Decimal Places in Salesforce is the per-field configuration on Number, Currency, and Percent field types that controls how many digits appear after the decimal point.
Definition
Decimal Places in Salesforce is the per-field configuration on Number, Currency, and Percent field types that controls how many digits appear after the decimal point. A Currency field configured with 2 decimal places stores 1234.5678 as 1234.57 (rounded); a Number field with 4 decimal places stores the full 1234.5678. The decimal places setting is part of the field definition; admins set it at field creation and it governs both storage precision (how many digits the platform persists) and display formatting (how many digits users see in the UI).
Decimal Places matters because precision requirements differ by use case. Currency for commercial transactions needs 2 decimal places (dollars and cents). Currency for forex trading might need 4 or 6 (basis points). Number for quantity counts needs 0 (whole units). Number for scientific measurements might need 6 or 8. Picking the wrong decimal places at field creation produces either over-precision (storage and display waste) or under-precision (data loss through rounding). The setting is hard to change later for fields with data, so getting it right at creation matters.
Why Decimal Places is the field-creation decision that is hardest to change later
Where Decimal Places is configured
On Number, Currency, and Percent custom field definitions, the wizard asks for two related values: Length (total digits) and Decimal Places (digits after the decimal point). A Currency field with Length 16 and Decimal Places 2 stores up to 9999999999999.99 (14 digits before decimal, 2 after). The two values together define the precision and range of the field. Adjusting either after creation is restricted; widening Length is allowed, narrowing or changing Decimal Places is restricted on fields with data.
Storage precision and the rounding behavior
Salesforce stores values per the configured Decimal Places. A value with more precision than configured gets rounded to the configured precision at save time. The rounding is half-up (1.235 with 2 decimal places stores as 1.24). The rounded value is what every consumer sees: reports, formulas, integrations, API responses. The full precision is gone after save; the original value is unrecoverable. This is the trap: a field with 0 decimal places that was the wrong choice silently loses the fractional data on every save.
Display formatting and the locale interaction
Display formatting respects the configured Decimal Places plus the user's locale. A value of 1234.5 in a Currency field with 2 decimal places displays as $1,234.50 for en_US locale, 1.234,50 EUR for de_DE locale, etc. The Decimal Places setting is universal; the thousands separator and decimal symbol vary by locale. Reports and formulas use the platform-internal representation (always period-decimal); display surfaces apply locale formatting at render time.
Currency-specific behavior and the multi-currency interaction
Currency fields have a fixed 2 decimal places for most major currencies in multi-currency orgs (USD, EUR, GBP). Some currencies use different defaults (JPY uses 0 decimal places traditionally, BHD uses 3). Salesforce respects per-currency precision when the multi-currency setting is enabled. Custom Currency fields the admin creates can override the default; setting a Currency field to 4 decimal places stores 4 regardless of the underlying currency's traditional precision.
Formula fields and the calculated precision
Formula fields have their own Decimal Places setting independent of the source fields they reference. A formula that multiplies a Number with 4 decimal places by a Currency with 2 decimal places produces a result whose precision is the formula's configured Decimal Places, not the sources'. Set the formula's precision based on the calculation's actual precision need; over-precision in formulas is visually noisy, under-precision rounds before downstream calculations.
Changing Decimal Places after the fact
Salesforce restricts Decimal Places changes on fields with data. Widening is sometimes allowed (2 to 4) but narrowing usually requires a workaround: create a new field with the desired precision, migrate data, retire the old field. The migration is operationally heavy; getting the precision right at creation is significantly cheaper than fixing it later. The most common case for change is widening for fields that turned out to need more precision than the original designer planned; the workaround pattern is well-documented but never welcome.
Integration considerations and the API-precision question
External systems integrating with Salesforce receive values per the field's Decimal Places. An integration expecting 4 decimal places that receives a 2-decimal value loses precision on the inbound side. An integration sending 4 decimal places to a 2-decimal Salesforce field loses precision on the Salesforce side. Both directions matter; document the field precision as part of the integration contract. Most integration debugging traces to mismatched precision expectations between Salesforce and the external system.
How to set Decimal Places correctly at field creation
The pattern: think through the precision requirement before creating the field, set Decimal Places to match, document the choice for integrations. Changing later is restricted; the upfront thought is much cheaper than the migration workaround.
- Identify the precision requirement
Currency for commercial: 2. Currency for forex: 4 or 6. Quantity: 0. Percentages: 2 or 4. Scientific measurements: 6 to 8. Pick based on the field's actual use case.
- Set Length and Decimal Places together
Length is total digits; Decimal Places is digits after the decimal. Length must accommodate the largest expected value plus the decimal places.
- Verify the storage behavior with test data
Save a value with more precision than configured. Confirm the rounding matches expectation. The rounding is half-up; values exactly halfway round up.
- Configure related formula fields to match
Formula fields reference the source but have their own precision. Set formula precision based on the calculation's actual need, not just the source's precision.
- Document the precision in the integration contract
Integrations that read or write the field need to know the precision. Document in the integration spec; mismatches produce silent data loss.
- Test with locale variations if multi-currency or international
Different locales display differently. Confirm the display matches expectation for the user populations that will see the field.
- Plan the migration path if precision needs change
Changing Decimal Places on a field with data requires create-migrate-retire. Document the workaround if you anticipate the field's precision needs evolving.
0 to ~16 depending on field type. Match to precision requirement.
Total digits including decimals. Must accommodate largest value plus decimal precision.
Number, Currency, or Percent. Each has slightly different behavior around defaults and currency-specific precision.
Currency fields respect per-currency precision defaults; custom precision overrides.
Independent of source precision; set per calculation need.
- Decimal Places changes after creation are restricted on fields with data. The migration workaround is operationally heavy.
- Rounding is silent; the original precision is gone after save. A 0-decimal-place field saving 1234.5678 stores 1235 and the .5678 is unrecoverable.
- Per-currency precision defaults vary in multi-currency orgs. JPY uses 0 by default; configuring 2 overrides the traditional precision.
- Integration precision mismatches produce silent data loss. Document field precision as part of the integration contract.
- Formula precision is independent of source. A formula on a 4-decimal source with 2-decimal formula precision loses the fractional precision before downstream consumers see it.
Trust & references
Cross-checked against the following references.
- Field types referenceSalesforce
- Add Custom Fields referenceSalesforce
Straight from the source - Salesforce's reference material on Decimal Places.
- Custom Field TypesSalesforce Help
- About Custom Field TypesSalesforce Help
- Multiple CurrenciesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Decimal Places control?
Q2. What is the maximum number of Decimal Places?
Q3. What happens if you reduce Decimal Places on a field with existing data?
Discussion
Loading discussion…