How Sage Intacct determines variable billing quantities for usage
This topic is specific to quantity-based billing with Quantity type = Variable.
When you execute Preview in the Generate Invoices page for a contract that includes usage, Intacct combines all usage records that have not been invoiced as of the selected As of date and presents the total usage charges by contract line. This topic describes how different combinations of price parameters determine usage quantities.
About usage price parameters
Different combinations of the following price parameters can produce different billing quantities for the same recorded usage quantities:
- Included units—whether or not the price has defined any included units (if yes, there is no charge for the included units).
- Reset usage quantity—determines when the included units are counted and determines when the system counter resets.
- Quantity is recurring—when true, the system considers every usage record you enter for a line item as a recurring usage record. Each period, it creates new usage records in order to re-invoice the quantities.
The examples in this topic show how these parameters work together. The examples have different combinations of the Included units and Quantity is recurring parameters, and present two tables that illustrate the count difference between when Reset usage quantity = "After each invoice" and when Reset usage quantity = "After each renewal".
Example tier price table
All examples use the following tiered price list entry with Price type = Volume for a quantity-based item:
| Tier quantity | Rate |
|---|---|
| 1 - 14 | 5 |
| 15 - 30 | 3 |
| 31 | 2 |
Partial usage quantities
You can add usage quantities with up to 2 decimal places. If you input more than 2 decimal places, Intacct rounds the quantity to two decimal places. For example, if you enter a usage quantity of 1.3456, Intacct rounds it to 1.35.
Intacct includes partial quantities in included unit calculations. For example, if the included units is 10.5 and the quantity used for the period is 11, Intacct bills the 0.5 quantity at the applicable usage rate.
Example 1 - Usage without included units
Common parameters
| Included units | Quantity is recurring | Tier rates |
|---|---|---|
| 0 | No | Tier rates from example tier price table |
Table 1-1: Reset usage quantity = After every invoice
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 10 | 10 | 50.00 (10 * 5) |
| Feb | 5 | 5 | 5 | 25.00 (5 * 5) |
| March | 2 | 2 | 2 | 10.00 (2 * 5) |
| April | 7 | 7 | 7 | 35.00 (7 * 5) |
| May | 9 | 9 | 9 | 45.00 (9 *5) |
| June | -4 | 0 | 0 | 0.00. Will not appear on invoice. |
Table 1-1 is the simplest usage example as the system counter starts at 0 after every invoice. Usage quantities are always priced each period at the tier in which they fall. If the usage recorded for May is 17, then the usage price would be 51 (17 * 3), and so on.
Table 1-2: Reset usage quantity = After each renewal
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 10 | 10 | 50.00 (10 * 5) |
| Feb | 5 | 5 | 15 | 25.00 (5 * 5) |
| March | 2 | 2 | 17 | 6.00 (2 * 3) |
| April | 7 | 7 | 24 | 21.00 (7 * 3) |
| May | 9 | 9 | 33 | 18.00 (9 * 2) |
| June | -4 | 0 | 29 | 0.00. Will not appear on invoice. |
In Table 1-2, the system keeps track of the usage and bills each usage quantity based on the system counter tier rate for the contract term. When the contract is renewed, the system counter resets to zero.
Example 2 - Usage with included units
Common parameters
| Included units | Quantity is recurring | Tier rates |
|---|---|---|
| 10 | No | Tier rates from example tier price table |
Table 2-1: Reset usage quantity = After each invoice
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 0 | 0 | 0.00 (10 included units) |
| Feb | 5 | 0 | 0 | 0.00 (10 included units) |
| March | 2 | 0 | 0 | 0.00 (10 included units) |
| April | 7 | 0 | 0 | 0.00 (10 included units) |
| May | 9 | 0 | 0 | 0.00 (10 included units) |
| June | -4 | 0 | 0 | 0.00 . Will not appear on invoice. |
| July | 17 | 7 | 7 | 35.00 (10 included units, 7 * 5) |
In Table 2-1, the customer gets 10 included units each billing period. The system counter does not start for an invoice period until all included quantities are used for the period.
Table 2-2: Reset usage quantity = After each renewal
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 0 | 0 | 0.00 (10 included units) |
| Feb | 5 | 5 | 5 | 25.00 (10 included units, 5 * 5) |
| March | 2 | 2 | 7 | 10.00 (10 included units, 2 * 5) |
| April | 7 | 7 | 14 | 35.00 (10 included units, 7 * 5) |
| May | 9 | 9 | 23 | 27.00 (10 included units, 9 * 3) |
| June | -4 | 0 | 19 | 0.00. Will not appear on invoice. |
| July | 17 | 17 | 36 | 34.00 (10 included units, 17 *2) |
In Table 2-2, the customer only gets to use the included units once per contract term. The system counter starts after the included units are used and then does not reset during the contract term. Each time usage is invoiced, the Computation memo for a usage billing amount will show the units included in the system count.
Example 3 - Recurring usage without included units
Common parameters
| Included units | Quantity is recurring | Tier rates |
|---|---|---|
| 0 | Yes | Tier rates from example tier price table |
Table 3-1: Reset usage quantity = After each invoice
| Month | Recorded usage | Billing usage quantity | System counter for tier | Billing price |
|---|---|---|---|---|
| Jan | 10 | 10 | 10 | 50.00 (10 * 5) |
| Feb | 5 | 15 = (10 + 5) | 15 | 45.00 (15 * 3) |
| March | 2 | 17 = (10 + 5 + 2) | 17 | 51.00 (17 * 3) |
| April | 7 | 24 = (10 + 5 + 2 + 7) | 24 | 72.00 (24 * 3) |
| May | 9 | 33 = (10 + 5 + 2 + 7 + 9) | 33 | 66.00 (33 * 2) |
| June | -4 | 29 = (10 + 5 + 2 + 7 + 9 - 4) | 29 | 87.00 (29 * 3) |
In table 3-1, the recorded usage repeats each subsequent month (so Feb = Jan + Feb, Mar = Jan + Feb + Mar, and so on). As the system counter resets after every invoice, the billing usage quantity and the system counter are the same.
Table 3-2: Reset usage quantity = After each renewal
| Month | Recorded usage | Billing usage quantity | System counter for tier | Billing price |
|---|---|---|---|---|
| Jan | 10 | 10 | 10 | 50.00 (10 * 5) |
| Feb | 5 | 15 = (10 + 5) | 15 | 45.00 (15 * 3) |
| March | 2 | 17 = (10 + 5 + 2) | 32 | 34.00 (17 * 2) |
| April | 7 | 24 = (10 + 5 + 2 + 7) | 56 | 48.00 (24 * 2) |
| May | 9 | 33 = (10 + 5 + 2 + 7 + 9) | 89 | 66.00 (33 *2) |
| June | -4 | 29 = (10 + 5 + 2 + 7 + 9 - 4) | 118 | 58.00 (29 * 2) |
In table 3-2, the recorded usage repeats each subsequent month (so Feb = Jan + Feb, Mar = Jan + Feb + Mar, and so on). However, the system counter resets upon renewal, so the billing usage quantity differs from the system counter. In March, the billing usage quantity is 17, which would seem to be a rate of 3, but the system counter is 32, so the rate of 2 applies.
Example 4 - Recurring usage with included units
Common parameters
| Included units | Quantity is recurring | Tier rates |
|---|---|---|
| 10 | Yes | Tier rates from example tier price table |
Table 4-1: Reset usage quantity = After each invoice.
| Month | Recorded usage | Billing usage quantity | System counter for tier | Billing price |
|---|---|---|---|---|
| Jan | 10 | 0 | 0 | 0 (10 included units) |
| Feb | 5 | 5 = (10 + 5)- 10 included units | 5 | 25.00 (10 included units, 5 * 5) |
| March | 2 | 7 = (10 + 5 + 2) - 10 included units | 7 | 35.00 (10 included units, 7 * 5) |
| April | 7 | 14 = (10 + 5+ 2 +7) - 10 included units | 14 | 70.00 (10 included units, 14 * 5) |
| May | 9 | 23 = (10 + 5 + 2 + 7 + 9) - 10 included units | 23 | 69.00 (10 included units, 23 * 3) |
| June | -4 | 19 = (10 +5 +2 +7 +9 -4) - 10 included units | 19 | 57.00 (10 included units, 19 * 3) |
In table 4-1, the recorded usage repeats each subsequent month (so Feb = Jan + Feb, Mar = Jan + Feb + Mar, and so on). As 10 units are always included, the user is never billed for the recurring 10 units. As the system counter resets after every invoice, the billing usage quantity and the system counter are the same.
Table 4-2: Reset usage quantity= After each renewal
| Month | Recorded usage | Billing usage quantity | System counter for tier | Billing price |
|---|---|---|---|---|
| Jan | 10 | 10 | 0 | 0 (10 included units) |
| Feb | 5 | 15 = (10 + 5) | 15 | 45.00 (15 * 3) |
| March | 2 | 17 = (10 + 5 + 2) | 32 | 34.00 (17 * 2) |
| April | 7 | 24 = (10 + 5 + 2 + 7) | 56 | 48.00 (24 * 2) |
| May | 9 | 33 = (10 + 5 + 2 + 7 + 9) | 89 | 66.00 (33 * 2) |
| June | -4 | 29 = (10 + 5 + 2 + 7 + 9 - 4) | 118 | 58.00 (29 * 2) |
In table 4-2, the customer only gets to use the 10 included units once per contract term, so the recurring 10 quantity is included in the billing usage quantity after January.
Example 5 - Evergreen contract lines - without included units
In quantity-based evergreen contract lines, Quantity is recurring is always false and Reset usage quantity is always After each invoice.
Common parameters
| Included units | Recurring billing period start day | Billing frequency | Tier rates |
|---|---|---|---|
| 0 | <month> 01 | Monthly | Tier rates from example tier price table |
Table 5-1
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 10 | 10 | 50.00 (10 * 5) |
| Feb | 15 | 15 | 15 | 45 (15 * 3) |
| March | 2 | 2 | 2 | 10 (2 * 5) |
| April | 27 | 27 | 27 | 81 (27 * 3) |
| May | 9 | 9 | 9 |
45 (9 * 5) |
| June | -4 | 0 | 0 | 0.00. Will not appear on invoice. |
| July | 17 | 17 | 17 | 51 (17 * 3) |
The system counter starts at 0 after every invoice. If the total usage for a contract line for a recurring billing period is negative, it has no effect on billing.
There is a Contracts configuration option that can affect in which recurring billing period usage quantities are counted. Learn more about usage in quantity-based evergreen lines.
Example 6 - Evergreen contract lines - with included units
In quantity-based evergreen contract lines, Quantity is recurring is always false and Reset usage quantity is always After each invoice.
Common parameters
| Included units | Recurring billing period start day | Billing frequency | Tier rates |
|---|---|---|---|
| 10 | <month> 01 | Monthly | Tier rates from example tier price table |
Table 6-1
| Month | Recorded usage | Billing usage quantity | System counter for tier | Usage price |
|---|---|---|---|---|
| Jan | 10 | 0 | 0 | 0.00 (10 included units) |
| Feb | 15 | 5 = (10 +5) - 10 included units | 5 | 25.00 (10 included units. 5 * 5) |
| March | 2 | 0 | 0 | 0.00 (10 included units) |
| April | 27 | 17 = (10 + 17) - 10 included units | 17 | 51.00 (10 included units. 17 * 3) |
| May | 9 | 0 | 0 | 0.00 (10 included units) |
| June | -4 | 0 | 0 | 0.00 . Will not appear on invoice. |
| July | 17 | 7 = (10 + 7) - 10 included units | 7 | 35.00 (10 included units, 7 * 5) |
The customer gets 10 included units each billing period. The system counter does not start for an invoice period until all included quantities are used for the period. If the total usage for a contract line for a recurring billing period is negative, it has no effect on billing.
There is a Contracts configuration option that can affect in which recurring billing period usage quantities are counted. Learn more about usage in quantity-based evergreen lines.