Component Types Quantity-Based On/Off Prepaid Usage Metered Usage Events Based Usage
|
Component Type |
Best for |
|
Metered usage |
for any usage-based items that are basic, and billed in arrears |
|
Events based |
for any usage-based items that are advanced, and/or have a multi-attribute rating system, and/or you have big data, and billed in arrears |
|
Prepaid usage |
for any usage-based items that are advanced, and billed upfront |
|
Quantity-based |
for any recurring items with a quantity of 0, 1, 2+ |
|
Quantity-based One-time |
for any non-recurring items with a quantity of 0, 1, 2+ |
|
On-off |
for any recurring items with a quantity of 0 or 1 |
Summary - Create a Quantity-Based Component (One-time or Recurring)
- Feature
- Component
- You Need
- Access to your company's price book
- Code
- None
- Difficulty
- ◉◎◎◎◎
1. Create New Component
2. Select Quantity-Based Component (One-time or Recurring)
3. Set Component Details
| Field | Description |
| Component Name Required | The name of your Product. This shows as a line item on your customer's invoices. |
| API Handle Optional | Developers can make API requests to create subscriptions that have components, they can use the API handle of the component in the API request. |
| Accounting Code Optional | A read only field. |
| Item Category Optional | A read only field. |
| Unit Name Required | A singular unit name. If you sell messages, put "message" without the s. |
| Description Optional | A description of your Component. Shows on public signup pages, shows in the Billing Portal, does not show on customer invoices. |
4. Create a Component Pricing Scheme
| Option | Description |
| Per Unit | Sets pricing to Per Unit. The component will be on a single price per-unit basis. |
| Volume Based | Sets pricing to Volume Based. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit. |
| Tiered | Sets pricing to Tiered. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit plus the previous bracket's price per unit. |
| Stairstep | Sets pricing to Stairstep. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged a flat fee based on their bracket. |
5. Setup Advanced Options (Optional)
| Field | Description |
| Enable Taxes |
Sets up taxes on the component based on whether it is classified by it being a Digital Good, Physical Good, a custom tax code, or none. (Please note Taxes will need to be set up on the site for this to function properly.) |
| Billing Portal | When enabled, customers can edit this component on their billing portal if applicable. |
| Fractional Quantities | Allows for fractional quantities in the component. |
| Date Ranges on Invoices | Will display the date range on the invoice for this particular line item. |
| Proration Settings | This will setup alternate proration settings other that the default setup. |
Summary - Create an On/Off Component
- Feature
- Component
- You Need
- Access to your company's price book
- Code
- None
- Difficulty
- ◉◎◎◎◎
1. Create New Component
2. Select On/Off Component
3. Set Component Details
| Field | Description |
| Component Name Required | The name of your Product. This shows as a line item on your customer's invoices. |
| API Handle Optional | Developers can make API requests to create subscriptions that have components, they can use the API handle of the component in the API request. |
| Accounting Code Optional | A read only field. |
| Item Category Optional | A read only field. |
| Description Optional | A description of your Component. Shows on public signup pages, shows in the Billing Portal, does not show on customer invoices. |
4. Setup Price
5. Setup Advanced Options (Optional)
| Field | Description |
| Enable Taxes |
Sets up taxes on the component based on whether it is classified by it being a Digital Good, Physical Good, a custom tax code, or none. (Please note Taxes will need to be set up on the site for this to function properly.) |
| Billing Portal | When enabled, customers can edit this component on their billing portal if applicable. |
| Fractional Quantities | Allows for fractional quantities in the component. |
| Date Ranges on Invoices | Will display the date range on the invoice for this particular line item. |
| Proration Settings | This will setup alternate proration settings other that the default setup. |
Summary - Create a Prepaid Usage Component
- Feature
- Component
- You Need
- Access to your company's price book
- Code
- None
- Difficulty
- ◉◎◎◎◎
1. Create New Component
2. Select Prepaid Usage Component
3. Set Component Details
| Field | Description |
| Component Name Required | The name of your Product. This shows as a line item on your customer's invoices. |
| API Handle Optional | Developers can make API requests to create subscriptions that have components, they can use the API handle of the component in the API request. |
| Accounting Code Optional | A read only field. |
| Item Category Optional | A read only field. |
| Unit Name Required | A singular unit name. If you sell messages, put "message" without the s. |
| Description Optional | A description of your Component. Shows on public signup pages, shows in the Billing Portal, does not show on customer invoices. |
4. Create a Component Pricing Scheme
| Option | Description |
| Per Unit | Sets pricing to Per Unit. The component will be on a single price per-unit basis. |
| Volume Based | Sets pricing to Volume Based. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit. |
| Tiered | Sets pricing to Tiered. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit plus the previous bracket's price per unit. |
| Stairstep | Sets pricing to Stairstep. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged a flat fee based on their bracket. |
5. Setup Unit Options
| Option | Description |
| Enable Recurring Allocations | Will allow the allocated amount to renew every billing period. |
| Enable Rollover of Units | Will allow for any leftover units to carry over into the next billing period. |
| Enable Expiration of Allocated Units | Only applicable if Rollover Units are enabled. Will set an expiration timer for the rollover units. |
6. Setup Overage Pricing
| Option | Description |
| Per Unit | Sets pricing to Per Unit. The component will be on a single price per-unit basis. |
| Volume Based | Sets pricing to Volume Based. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit. |
| Tiered | Sets pricing to Tiered. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit plus the previous bracket's price per unit. |
| Stairstep | Sets pricing to Stairstep. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged a flat fee based on their bracket. |
7. Setup Advanced Options (Optional)
| Field | Description |
| Enable Taxes |
Sets up taxes on the component based on whether it is classified by it being a Digital Good, Physical Good, a custom tax code, or none. (Please note Taxes will need to be set up on the site for this to function properly.) |
| Fractional Quantities | Allows for fractional quantities in the component. |
| Date Ranges on Invoices | Will display the date range on the invoice for this particular line item. |
Summary - Create a Metered Usage Component
- Feature
- Component
- You Need
- Access to your company's price book
- Code
- None
- Difficulty
- ◉◎◎◎◎
1. Create New Component
2. Select Metered Usage Component
3. Set Component Details
| Field | Description |
| Component Name Required | The name of your Product. This shows as a line item on your customer's invoices. |
| API Handle Optional | Developers can make API requests to create subscriptions that have components, they can use the API handle of the component in the API request. |
| Accounting Code Optional | A read only field. |
| Item Category Optional | A read only field. |
| Unit Name Required | A singular unit name. If you sell messages, put "message" without the s. |
| Description Optional | A description of your Component. Shows on public signup pages, shows in the Billing Portal, does not show on customer invoices. |
4. Create a Component Pricing Scheme
| Option | Description |
| Per Unit | Sets pricing to Per Unit. The component will be on a single price per-unit basis. |
| Volume Based | Sets pricing to Volume Based. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit. |
| Tiered | Sets pricing to Tiered. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit plus the previous bracket's price per unit. |
| Stairstep | Sets pricing to Stairstep. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged a flat fee based on their bracket. |
5. Setup Advanced Options (Optional)
| Field | Description |
| Enable Taxes |
Sets up taxes on the component based on whether it is classified by it being a Digital Good, Physical Good, a custom tax code, or none. (Please note Taxes will need to be set up on the site for this to function properly.) |
| Fractional Quantities | Allows for fractional quantities in the component. |
| Date Ranges on Invoices | Will display the date range on the invoice for this particular line item. |
Summary - Create an Events Based Component
- Feature
- Component
- You Need
- Access to your company's price book
- Access to Advanced Billing's Event Based Billing Feature
- Code
- None
- Difficulty
- ◉◎◎◎◎
1. Create New Component
2. Select Event Based Component
3. Set Component Details
| Field | Description |
| Component Name Required | The name of your Product. This shows as a line item on your customer's invoices. |
| API Handle Optional | Developers can make API requests to create subscriptions that have components, they can use the API handle of the component in the API request. |
| Accounting Code Optional | A read only field. |
| Item Category Optional | A read only field. |
| Unit Name Required | A singular unit name. If you sell messages, put "message" without the s. |
| Description Optional | A description of your Component. Shows on public signup pages, shows in the Billing Portal, does not show on customer invoices. |
| Billing Metric | Set the metric you would like to use for this component. |
4. Create a Component Pricing Scheme
| Option | Description |
| Per Unit | Sets pricing to Per Unit. The component will be on a single price per-unit basis. |
| Volume Based | Sets pricing to Volume Based. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit. |
| Tiered | Sets pricing to Tiered. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged for that price per unit plus the previous bracket's price per unit. |
| Stairstep | Sets pricing to Stairstep. This allows for multiple price brackets. If a customer buys into a certain bracket, they will be charged a flat fee based on their bracket. |
5. Setup Advanced Options (Optional)
| Field | Description |
| Enable Taxes |
Sets up taxes on the component based on whether it is classified by it being a Digital Good, Physical Good, a custom tax code, or none. (Please note Taxes will need to be set up on the site for this to function properly.) |
| Billing Portal | When enabled, customers can edit this component on their billing portal if applicable. |
| Fractional Quantities | Allows for fractional quantities in the component. |
| Date Ranges on Invoices | Will display the date range on the invoice for this particular line item. |
| Proration Settings | This will setup alternate proration settings other that the default setup. |