One Account One Invoice (OAOI)
One Account One Invoice lets postpaid and manual customers receive a single consolidated invoice for all services on the account each billing cycle — instead of separate invoices for every service or billing event.
CMP groups billable items into one invoice per account per month.
OAOI does not support every account type or billing rule. Read Unsupported account types and billing rules before enabling.
Verify on this portal: Billing → Invoices → Billing Settings → Enabled Global Settings → enable_one_account_one_invoice
Overview
When OAOI is enabled:
- All billable services under an account are combined into one invoice
- The invoice is generated once per month on the 1st
- The invoice includes usage, renewals, and eligible contract charges from the previous billing period
Example
| Service | Type |
|---|---|
| Virtual Machine | Monthly |
| Block Storage | Monthly |
| Backup Service | Monthly |
Without OAOI, the customer might receive three invoices. With OAOI they receive one consolidated invoice, for example:
| Field | Example |
|---|---|
| Invoice date | 1 April |
| Billing period | 1 March – 31 March |
| Line items | Virtual Machine usage · Block Storage usage · Backup Service usage |
Requirements
All of the following must be true for OAOI to work correctly:
| Requirement | Description |
|---|---|
| Billing type | Account must be Postpaid or Manual |
| Billing cycle | Services must use 1st-to-1st monthly billing (calendar-aligned) |
| Advance billing | Advance billing must be disabled (POSTPAID_ADVANCE_* / MANUAL_ADVANCE_* as applicable — see Billing Settings — Environment Flags) |
| Global setting | enable_one_account_one_invoice must be true |
Configure: Admin Panel → Global Settings → enable_one_account_one_invoice (Billing). Confirm live value under Billing Settings (admin).
Ideal for enterprise customers, accounts with many services, finance teams that want one invoice per month, and providers who want simplified monthly billing for postpaid/manual customers.
Unsupported account types and billing rules
Prepaid accounts
Prepaid is not supported. Prepaid services invoice (or track) individually against the wallet / prepaid model and cannot be consolidated under OAOI.
See Prepaid.
DATE_TO_DATE billing
DATE_TO_DATE is not supported for OAOI consolidation.
Each service’s cycle is anchored to its creation date, so periods differ:
| Service | Billing cycle |
|---|---|
| Service A | 5th → 5th |
| Service B | 12th → 12th |
CMP must generate separate invoices. See DATE_TO_DATE.
For consolidated monthly postpaid/manual billing, use rules such as FIXED_PRORATA or calendar-month rules instead.
Custom billing dates
Services billed on different billing days cannot be grouped into a single monthly invoice.
Invoice generation mechanics: Consolidated vs. independent services
CMP supports different invoice generation methods depending on the selected payment mode and billing rule. Understanding the difference between Prepaid (Date-to-Date) and Postpaid + Pro-Rata clarifies why certain configurations allow a single consolidated invoice while others generate independent invoices per service.
1. Prepaid billing (Independent subscriptions)
In Prepaid mode, the invoice is generated immediately when a customer purchases a service, and the invoice amount is deducted directly from the customer's wallet balance.
Each service—such as a VPC, public IP address, or virtual machine—is treated as an independent subscription. Therefore, each purchase triggers its own invoice.
Example
Suppose a customer purchases the following services under a DATE_TO_DATE billing rule:
| Service | Creation date | Billing period | Renewal date |
|---|---|---|---|
| VPC | 5 October | Monthly | 5 November |
| Public IP | 10 October | Monthly | 10 November |
| Virtual Machine | 15 October | Monthly | 15 November |
In this case, CMP generates three separate invoices, one for each service.
Why are separate invoices generated?
- Independent purchase timing: Each service can be purchased independently at any time.
- Distinct billing schedules: Each service has its own billing start date and renewal date.
- No common monthly invoice cycle: Invoices are generated according to the individual subscription's billing schedule, rather than a common monthly calendar cycle.
- Isolated lifecycles: Even if all three services are purchased by the same customer, their billing schedules remain independent.
2. Postpaid + Pro-Rata billing (Consolidated invoicing)
In this configuration, CMP generates invoices based on fixed billing cycles, such as the end of each month (or on the 1st of the subsequent month). This makes it possible to combine multiple subscriptions belonging to the same billing cycle into one consolidated invoice.
Example
Suppose a customer purchases the exact same services:
| Service | Creation date | Billing cycle | Covered period on month-end invoice |
|---|---|---|---|
| VPC | 5 October | Monthly | 5 October – 31 October (prorated) |
| Public IP | 10 October | Monthly | 10 October – 31 October (prorated) |
| Virtual Machine | 15 October | Monthly | 15 October – 31 October (prorated) |
Under Postpaid + Pro-Rata billing, CMP can generate a single invoice at the end of October for all three services, covering the applicable charges from their respective creation dates through the end of the billing period:
- VPC: Charges from 5 October to 31 October
- Public IP: Charges from 10 October to 31 October
- Virtual Machine: Charges from 15 October to 31 October
The charges are calculated according to the applicable pro-rata rules, and the services are consolidated into one invoice because they belong to the same monthly billing cycle.
Going forward, these services can be billed together according to the monthly invoice cycle, subject to the applicable billing configuration.
What if the customer has different billing cycles?
If the customer has hourly, monthly, and yearly subscriptions, CMP can generate separate invoices for each applicable billing cycle at the end of the month:
- Subscriptions belonging to the monthly cycle are grouped into one invoice.
- Subscriptions belonging to the hourly cycle are grouped into their own usage invoice.
- Subscriptions belonging to the yearly cycle are grouped into their respective annual invoice.
The number of invoices depends on the applicable billing cycles, rather than simply the number of services.
3. Why can't we apply the same approach to Prepaid + Date-to-Date billing?
Providers often ask: “Can we generate one single invoice covering all services used by a customer—marked 'Paid' if consumption is deducted from available wallet balance, or 'Unpaid' for any usage exceeding the balance?”
The key difference lies in when the invoice is generated and how the subscription period is determined:
| Dimension | Postpaid + Pro-Rata | Prepaid + Date-to-Date (or any independent rule) |
|---|---|---|
| Invoice timing | Generated in arrears at the end of the billing period. | Generated immediately / upfront at service creation and renewal dates. |
| Subscription period | Prorated to a shared period-end boundary (e.g., end of month). | Each subscription follows its own independent billing and renewal schedule. |
| Consolidation mechanism | A common invoice generation cycle allows CMP to collect charges for multiple subscriptions and consolidate them into an invoice at the end of the billing period. | Services do not share a common invoice generation date or billing period. An invoice generated on 5 October cannot predict or consolidate a purchase made on 15 October. |
| Balance settlement | Invoice issued at month-end, then paid via payment gateway or manual wire. | Deducted from the prepaid wallet immediately; if wallet is insufficient at renewal, an unpaid invoice is created and the wallet reflects a negative balance. |
To achieve a single monthly invoice for multiple services, configure the account as Postpaid (or Manual) with FIXED_PRORATA billing and enable_one_account_one_invoice = true. For prepaid accounts, see Prepaid invoice payment workflow.
Long-term services (service contracts)
Services on longer cycles — quarterly, semi-annual, yearly, and similar — can still appear on the consolidated invoice when service contracts split the term into monthly installments.
- Total term cost is billed as monthly charges (Yearly ÷ 12 minus contract discount)
- Each monthly installment appears as a line on the consolidated invoice
Example: Yearly VM $1,200/year with no extra discount → $100/month on the OAOI invoice.
OAOI remains postpaid/manual only. Prepaid contracts use wallet / infra credits, not OAOI. See Service Contracts.
When the invoice is generated
Invoices are generated automatically on the 1st day of every month and include billable items from the previous month.
| Invoice date | Billing period |
|---|---|
| 1 April | 1 March – 31 March |
| 1 May | 1 April – 30 April |
New service mid-month
If a service is created during the billing period, it appears on the next monthly consolidated invoice.
| Service created | Appears on |
|---|---|
| 10 March | 1 April invoice |
Hourly usage
Hourly usage is aggregated during the month and included on the same monthly consolidated invoice.
Line items
Customers still see separate line items per service or usage type on the single invoice — one document, full charge transparency.
Extra invoices in the same month
Normally one invoice per account per month when OAOI is enabled. Additional invoices may still appear for:
- Manual billing adjustments
- Credits or refunds
- Administrative invoice generation
If OAOI is disabled
Invoices may be generated per service or per billing event, and customers may receive multiple invoices in a month.
Frequently asked questions
What is One Account One Invoice?
OAOI gives customers a single consolidated invoice for all eligible services under an account each monthly billing cycle, instead of one invoice per service or usage event.
When is the invoice generated?
On the 1st of every month, covering the previous month’s usage and renewals.
What charges are included?
Typical line items include VM usage, storage, network services, hourly usage, monthly renewals, contract monthly portions, and other billable services on the account — combined into one invoice.
Which account types support OAOI?
Postpaid and Manual only. Prepaid is not supported.
Why not prepaid?
Prepaid deducts wallet / infra credits per service or usage event upon purchase and renewal. Subscriptions follow their own schedules rather than a common month-end collection cycle. See Why can't we apply the same approach to Prepaid + Date-to-Date? and Prepaid.
Why not DATE_TO_DATE?
Creation-date cycles differ per service (e.g., 5th to 5th vs. 15th to 15th), so periods cannot share one calendar-month invoice. See Invoice generation mechanics and DATE_TO_DATE exception.
What if a postpaid customer has different billing cycles?
If a customer uses services across multiple cycles (such as Hourly, Monthly, and Yearly), CMP generates separate invoices for each applicable billing cycle at month end. Monthly services are consolidated into one invoice, while hourly and yearly are grouped into their own invoices. See What if the customer has different billing cycles?.
Can multiple services appear on the same invoice?
Yes — all eligible services on the account that follow monthly 1st–1st billing appear on the same consolidated invoice.
Can yearly or quarterly services appear?
Yes, when service contracts divide the cost into monthly charges on the consolidated invoice.
Can OAOI be enabled for existing customers?
Yes, for eligible postpaid/manual accounts when billing configuration meets the requirements.
Who should use this feature?
Enterprise and multi-service accounts, and finance teams that prefer one invoice per billing cycle.
Related
- Billing Settings (admin) — live
enable_one_account_one_invoicevalue - Postpaid
- Manual
- DATE_TO_DATE
- FIXED_PRORATA
- Service Contracts
- Billing Overview
- Billing FAQs