8

Description

In Dynamics 365 Sales, when discounts are applied to a unit price, the system calculates the discounted price using full precision (e.g., 20.3994) and applies rounding based on currency precision only after multiplying by quantity.

This causes a discrepancy between:


The expected rounded unit price (e.g., 20.40)

The final line total calculated by the system


Example:


Unit price: 25.20

Discount: 19.05% → discounted price = 20.3994


Current system behavior:

20.3994 × 10 = 203.994 → rounded = 203.99


Expected business behavior:

ROUND(20.3994) = 20.40  

20.40 × 10 = 204.00


This results in small but noticeable financial variances.


Business Impact

  • Causes discrepancies between unit price and line totals
  • Leads to billing inconsistencies and customer disputes
  • Requires manual adjustments or custom development
  • Misalignment with accounting or external ERP expectations

This becomes more significant for:

  • Large quantities
  • High-volume transactions
  • Pricing scenarios driven by percentage discounts


Current Limitation

While the system allows configuration of:

  • Currency precision
  • Pricing decimal precision

There is no option to control when rounding is applied in the pricing calculation process (e.g., before or after quantity multiplication).


Proposed Solution

Introduce a configurable rounding behavior setting, such as:

Rounding calculation option:

  • Round unit price before multiplying by quantity
  • (Default) Round final calculated amount (current behavior)

Optional:

  • Allow this configuration at:
  • Organization level
  • Price list level


Expected Benefit

  • Ensures consistency between displayed unit price and calculated totals
  • Improves billing accuracy and customer trust
  • Reduces need for custom plugins or manual corrections
  • Aligns pricing calculations with common business and financial expectations


Additional Context

Currently, this requirement can only be achieved through customization (e.g., plugin or custom pricing logic), which increases maintenance effort and complexity.

Providing this capability as a standard feature would address a common business need across multiple industries.

Category: Journey Design
STATUS DETAILS
New

Comments

R

Great idea! Please help see this and improve our platform @msft

Category: Journey Design

R

Very good Idea, this is much needed as changing behavior would assist customer in understand clearer about the rounding behavior, therefore, the full number will be displayed, not with too precision.

Category: Journey Design

R

I find this proposal really helpful. Please implement it.

Category: Journey Design