New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now

Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices, Credit Notes and Quotes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Site Configuration
  3. Multi-decimal Support
  1. Billing
  2. Site Configuration
  3. Multi-decimal Support

Multi-decimal Support

Overview

Accurate calculation of your product pricing based on the quantities purchased is important while billing your customers. When you want to charge your customers in fractional amounts, or when you want to charge for fractional quantities, Chargebee allows configuring your product pricing and units with a maximum of two decimal places, by default. When you want to use more than two decimals places, you end up overcharging or undercharging your customers by rounding-off to the default settings.

For example, businesses in the telecommunication domain may want to track data consumption in multiple decimals like 1245.3587 MB, and the pricing could be $0.015 per MB. Inaccurate billing in the absence of multiple decimal support can lead to a considerable deficit in your company's overall revenue.

The multi-decimal support feature helps you avoid compromising your price and unit values, and ensures more accurate billing. With multi-decimal pricing enabled, you can use up to 20 decimal places while specifying the price and units for your plans and addons.

The product price and units with multiple decimal places as configured are considered in their entirety for invoice amount computation, tax application, reporting, and other third-party integrations.

Configuring Multi-decimal Support

To configure multiple decimal pricing in your Chargebee site, follow these steps:

  1. Click Settings > Configure Chargebee > Billing LogIQ > Multi-decimal support.

  2. In the Multi-decimal support page, click Enable to set up multiple decimal pricing.

  3. Under Pricing Length, select the number of decimal places for price from the drop down. You can select up to 20 decimal places.

    image
  4. Under Quantity Length, select the number of decimal places for the quantity from the drop down. You can select up to 20 decimal places.

  5. Click Publish.

Note:

  • Once you select the number of decimal places for price and units and publish the settings, you can not go back to select a lesser number of decimal places.
  • For example, if you have initially set the decimal place as 5 and if you try to update it to 2, this operation will fail and displays an error message since the selected value is lesser than the initially set decimal place.

After the setting is enabled, you can start specifying the quantity and price values for your plans and addons in multiple decimal places, with the number specified in the above settings being the upper limit. For example, when you specify 10 decimal places to be the Pricing and Quantity lengths, you can define the price or quantity value with any number of decimal places upto 10.

While creating a new plan/addon or updating an existing plan/addon, you can specify the unit value and the price in multiple decimals based on the number of decimal places that you have configured.

image

When a subscription is created, the price and quantity reflects multiple decimal values as defined for the plan/addon. You can also override this value, at the time of creating or changing the subscription.

image

Similarly, your customer facing essentials such as emails, invoices, quotes, and so on display the product price and quantity in multiple decimal places. The line item amounts are however rounded off to their currency precision. Learn more about the rounding logic for line item amounts.

image

Rounding Logic for Line Item Amounts

When multi-decimal support is enabled, the decimal places of your plan/addon price and quantities are considered in their entirety for line item amount and tax computation. However, these line item amount and tax amount that are derived after price computation are displayed, rounded off to zero or two decimal places based on the currency format.

Here is an example of how rounding logic works:

Consider a plan that is priced at 4.4556 per unit.

When the total quantity subscribed for is 10.625, the invoice amount is calculated as follows:

Plan Price 4.4556 X Quantity subscribed 10.625 = Line item amount computed 47.34075

  • When the plan currency is USD, the line item amount 47.34075 is rounded off to two decimal places, and gets displayed as $47.34. This is as per the currency format of USD that supports 2 decimal places.
  • When the plan currency is Japanese Yen (JPY), the line item amount 47.34075 is rounded off to zero decimal places, and gets displayed as JPY 47.

The same rounding logic is applied to credit notes and quotes. The line item amount and tax amount are rounded off to their currency precision.

Note

  • Once Multi-decimal support is enabled for your Chargebee site, you cannot disable it.
  • The setup cost for a plan cannot be defined in multiple decimals.

Refined Zero Truncation Logic for Enhanced Clarity

Customers can experience improved functionality when utilizing multi-decimal support for displaying unit prices and quantities, regardless of whether they use a UBB solution. The enhancement involves truncating trailing zeroes after two decimal places. This practice is commonly employed to achieve a more concise and aesthetically pleasing number format. Notably, this adjustment exclusively impacts the visual representation of invoices, invoice details, credit notes, and quotes.

For example,

The zeros in this number, $143.000000000000, do not add value and lack clarity. This modification is essential to improve the presentation for end customers without introducing inconsistencies.

It is important to note that this truncation does not apply if non-zero digits follow the decimal point, as illustrated by the number 1.2300000033.

Articles & FAQs

What is the rounding logic for line item amounts?

Was this article helpful?