💡 LearnFrenzy Insight

Imagine you're calculating the total bill in a supermarket. The bill might be:

• ₹125.50
• ₹899.99
• ₹15000.75

Money almost always contains decimal values. Using an Integer would remove the decimal portion, while Decimal preserves the exact value required for accurate financial calculations.

💡 Pro Tip: Decimal in Apex is a high-precision 38-digit number. It's actually a Salesforce wrapper around the Java java.math.BigDecimal class, which provides arbitrary precision.

⚠️ Important Note: Apex Decimal supports up to 38 digits of precision. This is sufficient for virtually all business and financial calculations.

📝 Key Points:

• Uninitialized Decimal variables default to null, not 0.0.
• Always initialize Decimal variables before use to avoid null pointer exceptions.
• Use descriptive names like totalAmount instead of amt.

💡 Pro Tip: Always use setScale() with appropriate RoundingMode for financial calculations to maintain consistency.

🏢 Business Scenario 1: Opportunity Discount Calculation

A company offers a 15% discount on an Opportunity worth ₹25,000 with an additional 5% tax on the discounted amount.

Decimal opportunityAmount = 25000.00;
Decimal discountPercent = 15.00;
Decimal taxPercent = 5.00;

// Calculate discount
Decimal discount = (opportunityAmount * discountPercent) / 100;
System.debug('Discount Amount: ₹' + discount);  // ₹3750.00

// Calculate amount after discount
Decimal afterDiscount = opportunityAmount - discount;
System.debug('After Discount: ₹' + afterDiscount);  // ₹21250.00

// Calculate tax
Decimal tax = (afterDiscount * taxPercent) / 100;
System.debug('Tax Amount: ₹' + tax);  // ₹1062.50

// Calculate final amount
Decimal finalAmount = afterDiscount + tax;
System.debug('Final Amount: ₹' + finalAmount);  // ₹22312.50

Output

Discount Amount: ₹3750.00
After Discount: ₹21250.00
Tax Amount: ₹1062.50
Final Amount: ₹22312.50

🏢 Business Scenario 2: Employee Salary Calculation

Calculate monthly salary with basic pay, allowances, and deductions.

Decimal basicSalary = 50000.00;
Decimal hraPercent = 20.00;      // House Rent Allowance
Decimal daPercent = 15.00;       // Dearness Allowance
Decimal taxPercent = 10.00;      // Tax deduction
Decimal professionalTax = 200.00;

// Calculate allowances
Decimal hra = (basicSalary * hraPercent) / 100;
Decimal da = (basicSalary * daPercent) / 100;

// Calculate gross salary
Decimal grossSalary = basicSalary + hra + da;
System.debug('Gross Salary: ₹' + grossSalary);

// Calculate tax deduction
Decimal tax = (grossSalary * taxPercent) / 100;

// Calculate net salary
Decimal netSalary = grossSalary - tax - professionalTax;
System.debug('Net Salary: ₹' + netSalary);

Output

Gross Salary: ₹67500.00
Net Salary: ₹60550.00

🏢 Business Scenario 3: Inventory Valuation

Calculate the total value of inventory with product quantities and unit prices.

// Product inventory data
Decimal product1Price = 1500.50;
Integer product1Qty = 25;
Decimal product2Price = 750.25;
Integer product2Qty = 40;
Decimal product3Price = 299.99;
Integer product3Qty = 100;

// Calculate total value for each product
Decimal product1Value = product1Price * product1Qty;
Decimal product2Value = product2Price * product2Qty;
Decimal product3Value = product3Price * product3Qty;

// Calculate total inventory value
Decimal totalInventoryValue = product1Value + product2Value + product3Value;

System.debug('Product 1 Value: ₹' + product1Value);  // ₹37512.50
System.debug('Product 2 Value: ₹' + product2Value);  // ₹30010.00
System.debug('Product 3 Value: ₹' + product3Value);  // ₹29999.00
System.debug('Total Inventory Value: ₹' + totalInventoryValue);  // ₹97521.50

Developer Writes
Decimal amount = 9999.95;

        │
        ▼

Compiler Checks
✔ Decimal Type exists?
✔ Variable name valid?
✔ Numeric value compatible?

        │
        ▼

Memory Allocated
Variable length based on precision needed

        │
        ▼

High Precision Value Stored
9999.95 (exact decimal representation)

        │
        ▼

Available for Calculations
Used in formulas, logic, and updates

Decimal uses BigDecimal internally for exact decimal arithmetic without floating-point errors.

Opportunity Amount (Decimal)
        │
        ▼
Calculate Discount (Decimal)
Amount * Discount% / 100
        │
        ▼
Apply Tax Calculation (Decimal)
Discounted Amount * Tax% / 100
        │
        ▼
Rounding Applied (setScale)
Using HALF_UP rounding mode
        │
        ▼
Final Amount Generated (Decimal)
Displayed to User with formatting
        │
        ▼
Stored in Database
As Decimal field

✅ Best Practices

• Use Decimal for all financial calculations, currency, and precise measurements.
• Use meaningful variable names such as totalAmount, discountPercent, or taxValue.
• Avoid using Double for currency fields - always prefer Decimal for money.
• Always specify rounding mode when using setScale() for financial calculations.
• Validate and test calculations before updating Salesforce records.
• Initialize Decimal variables to avoid null pointer exceptions.
• Use Decimal.valueOf() for safe string to decimal conversions with error handling.
• Store decimal values with appropriate precision (e.g., currency usually needs 2 decimal places).

⚠️ Common Mistakes

• Using Integer for currency values (e.g., Integer price = 99.99;).
• Using Double for financial calculations (can introduce rounding errors).
• Ignoring decimal precision during calculations (unexpected results).
• Performing unnecessary type conversions that might lose precision.
• Forgetting to handle null values before arithmetic operations.
• Using default rounding when specific rounding mode is required for compliance.
• Assuming Decimal division always returns a Decimal (works but be careful with Integer division).

🎯 Interview Tip

Question: Why is Decimal preferred over Double for currency calculations in Apex?

Answer: Decimal provides exact decimal arithmetic and higher precision (up to 38 digits) while minimizing floating-point rounding errors. Double uses binary floating-point representation which can cause small rounding errors (like 0.1 + 0.2 = 0.30000000000000004). Salesforce specifically recommends using Decimal for financial values such as Opportunity Amount, Quotes, Discounts, Taxes, and Invoices because accuracy is critical in business applications.

Question: What is the difference between setScale() and round() in Apex?

Answer: setScale() is used to set the number of decimal places and can specify a rounding mode. round() is a simpler method that rounds to the nearest whole number. For financial calculations, setScale() with explicit rounding mode is preferred for precise control.

📌 Quick Revision

• ✔ Stores decimal numbers with high precision (up to 38 digits).
• ✔ Best choice for financial and currency calculations.
• ✔ Supports arithmetic operators (+, -, *, /, %).
• ✔ Uses BigDecimal internally for exact decimal arithmetic.
• ✔ Common methods: setScale(), format(), round(), valueOf().
• ✔ Commonly used for Opportunity Amount, Tax, Discount, and Invoice calculations.
• ✔ Preferred over Double when calculation accuracy matters.
• ✔ One of the most frequently used Apex data types in enterprise Salesforce applications.
• ✔ Always use Decimal.valueOf() for safe string parsing.
• ✔ Uninitialized Decimal variables default to null.

➡ Next Lesson

In the next lesson, you'll explore the Double data type in detail. You'll learn:

• How floating-point numbers work and their limitations.
• When to use Double vs Decimal in Apex.
• Common use cases for Double in scientific calculations.
• Understanding floating-point precision issues and how to handle them.