HubSpot applies two rounding steps to stored line-item values in its "Use line items" feature, as documented by HubSpot.
Key takeaways
- Check the rounding method before comparing totals across tools.
- HubSpot uses different rounding methods depending on where the value is applied. Their two-step process first applies Banker's Rounding to three decimal places, then uses a 0–5 down and 6–9 up rule for the final two decimal places.
- If the discarded digit is exactly 5, the value rounds to the nearest even digit.
- Microsoft defines a specific set precision using values between 0 and 4. This setting allows you to enable and set decimal precision for all supported price-related fields in the system.
- Under the section for setting currency precision, you select a value for Pricing Decimal Precision.
HubSpot uses two rounding steps on stored line-item values
The first step rounds the value to three decimal places using Banker's Rounding, according to HubSpot. The second step takes that three-decimal number and rounds it to two decimal places using a 0–5 down and 6–9 up rule, according to HubSpot. HubSpot uses different rounding methods depending on where the value is applied, according to HubSpot. This specific two-step sequence defines how the final line-item total is stored in the system.
The initial Banker's Rounding step handles the first rounding to three decimal places. The subsequent 0–5 down and 6–9 up rule then determines the final two-decimal precision. These steps apply to the line items editor context described in the source.
If you are comparing totals across different tools, note that this rule is specific to HubSpot's line items editor. Other systems may use different precision or rounding logic. The distinction between the two steps matters because the first step's output becomes the input for the second. Banker's Rounding to 3 decimals is the first action, then that 3 decimal number is rounded using 0–5 down / 6–9 up, according to HubSpot. See Weighted deal amount: 5 fields to check HubSpot, Pipedrive.
A filled reference table of rounding rules by publisher
The table below compares the documented rounding and decimal rules for each publisher. Each row lists the specific rule found in that publisher's documentation. Use this to check if two totals follow the same logic before treating them as identical numbers.
| Publisher | Rounding or Decimal Rule | Source Quote |
|---|---|---|
| HubSpot | Two-step rounding: rounds to three decimal places using Banker's Rounding, then rounds to two decimal places using a 0–5 down and 6–9 up rule. | "Two-step rounding: rounds to three decimal places using Banker's Rounding, then rounds to two decimal places using a 0–5 down and 6–9 up rule." |
| Microsoft | This is used to define a specific set precision using values between 0 and 4. | "This is used to define a specific set precision using values between 0 and 4." |
HubSpot's rule is a two-step process. According to HubSpot, the first step uses Banker's Rounding to three decimal places. The second step rounds that result to two decimal places using a 0–5 down and 6–9 up rule. This order means small differences with external systems can occur, depending on when those systems round. For example, an accounting tool might round after each line or only at the end.
Microsoft's approach differs. According to Microsoft, the setting allows you to enable and set decimal precision for all supported price-related fields in the system. This is used to define a specific set precision using values between 0 and 4. It also affects rounding in calculations. This is a single precision setting, not a two-step rounding method.
Pipedrive's documentation focuses on tax application. According to Pipedrive, you can set the default tax setting, which defines whether your products include tax, exclude tax or have no tax at all. Each user sets their own default tax method, and it only applies going forward, not to deals that already have products linked.
HubSpot's two rounding steps
The line-item editor applies a specific sequence to stored values. According to HubSpot, the process is called "Two-step rounding." It first rounds to three decimal places using Banker's Rounding. Then it rounds that result to two decimal places using a 0–5 down and 6–9 up rule.
The first step relies on Banker's Rounding, which rounds to the nearest value. The second step takes the three-decimal number and applies a directional rule. If the third decimal digit is between 0 and 5, the second decimal digit remains unchanged and all subsequent digits are removed. This sequence defines how the final two-decimal total is stored.
The initial banker's rounding handles the first reduction, and the second step applies the directional rule to the remaining digit. The result is a value with exactly two decimal places.
To verify a specific line item, locate the unit price and quantity. The first step uses Banker's Rounding to reach three decimals. The second step uses the 0–5 down and 6–9 up rule to reach two decimals.
If the third decimal digit falls in the 0–5 range, the second digit stays the same. If the third decimal digit falls in the 6–9 range, the second digit increases. The final stored total is the result of this specific order. Changing the order or the method would produce a different stored value.
The documentation describes this as the standard behavior for the line items editor.
The first step ensures the intermediate value is rounded to the nearest value at three decimals. The second step ensures the final value is rounded to two decimals using the directional rule.
The two steps are distinct. The first uses Banker's Rounding. The second uses the directional rule. They are applied in sequence. The result is the stored line-item total.
What happens when the discarded digit is 5
When a line item total in the "Use line items" feature drops a digit that is exactly 5, the system does not simply round up. Instead, the value rounds to the nearest even digit, according to HubSpot. This specific rule applies during the rounding process for stored values. If the digit before the 5 is even, the number stays as is. If the digit before the 5 is odd, the number rounds up to make it even.
You might see a total that differs slightly from a spreadsheet calculation if your spreadsheet uses standard "round half up" logic. If the digit before the 5 is odd, the number rounds up to the next even number. The key is the parity of the preceding digit, not the 5 itself.
Illustrative example of a discarded 5
Picture a value carried to three decimal places where the third digit is 5. In the first step, a discarded 5 rounds to the nearest even digit. When the digit before that 5 is 4, an even digit, the 5 is dropped and that digit stays 4. When the digit before that 5 is 3, an odd digit, the value rounds up to the next even digit.
This order of operations means small differences with external systems can occur, depending on when those systems round, according to HubSpot. The source notes an example where an accounting tool rounds after each line or only at the end. This is not an error; it is a difference in timing and method.
Microsoft's decimal precision range
The "Decimal precision in currency and pricing" page describes a setting that allows you to enable and set decimal precision for all supported price-related fields in the system, according to Microsoft. This is used to define a specific set precision using values between 0 and 4, according to Microsoft. The page notes that the setting also affects rounding in calculations, according to Microsoft.
To configure this, the page instructs you to go under the "Set the currency precision that is used for pricing throughout the system" section and select a value for Pricing Decimal Precision, according to Microsoft. This specific range of 0 to 4 is distinct from the two-step rounding process described in other sections of this guide.
When comparing totals across different systems, note that this precision setting applies to Dynamics 365 Sales as described on this page. The value you select for Pricing Decimal Precision determines the number of decimal places used for pricing throughout the system, according to Microsoft.
Pipedrive tax choices and Close number fields
The Products page in the Pipedrive knowledge base explains that you can set the default tax setting, which defines whether your products include tax, exclude tax, or have no tax at all, according to Pipedrive. This setting establishes the baseline for how tax is handled on product records within the system. Each user sets their own default tax method, and it only applies going forward, not to deals that already have products linked, according to Pipedrive. This distinction matters when comparing totals across different time periods or users, as the tax application method may differ based on when the product was linked to the deal.
The tax setting defines the inclusion or exclusion of tax in the product price.
In the Custom Fields guide, the Number field is described as a text field that only accepts numeric values, including numbers with decimal places, according to Close. This field type allows for the storage of numeric values, including numbers with decimal places, without restricting the input to whole numbers. The guide also states that you can pick the main Currency on the Settings > Organization > General page, and it will be used in various places across the whole application, making the use of Close more intuitive, according to Close. See Choose a deal field type: 4 systems and storage rules.
See Quote checks before the forecast call: 4 tools.
Check the current Pricing Decimal Precision value in your system configuration. Write down the selected value and compare it against the unit price and stored total on a specific line item to verify how the precision setting aligns with the displayed figures. This check helps ensure that the precision setting matches the expected decimal places for your pricing fields.
FAQ about rounding a line-item total
What are HubSpot's two rounding steps?
HubSpot applies a two-step rounding process to line items, first rounding to three decimal places using Banker's Rounding, then rounding to two decimal places using a 0–5 down and 6–9 up rule, according to HubSpot. The initial step uses Banker's Rounding, which rounds to the nearest value, according to HubSpot. The second step takes that three-decimal number and applies the 0–5 down / 6–9 up rule, according to HubSpot.
What happens when the discarded digit is 5?
If the discarded digit is exactly 5, the value rounds to the nearest even digit, according to HubSpot. This specific rule applies during the Banker's Rounding phase of the process, according to HubSpot. The final stored value depends on this even-digit resolution before the second rounding step occurs, according to HubSpot.
Which decimal values does Microsoft's specific set precision allow?
Microsoft's specific set precision uses values between 0 and 4, according to Microsoft. This setting allows you to enable and set decimal precision for all supported price-related fields in the system, according to Microsoft. You select a value for Pricing Decimal Precision under the section that sets the currency precision used for pricing throughout the system, according to Microsoft.
Does Pipedrive's tax setting choose the rounding method?
Pipedrive's default tax setting defines whether products include tax, exclude tax, or have no tax at all, according to Pipedrive.
Does Close state banker's rounding?
Close's Number field is a text field that only accepts numeric values, including numbers with decimal places, according to Close. You can pick the main Currency on the Settings > Organization > General page, and it will be used in various places across the whole application, according to Close.
Evidence register
Found an error in this note? The correction record explains how to report it.