> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/hub/invoices.md). # Invoices This page describes invoice types on the WhatsApp Business Platform through 360dialog, and how to read them Invoices can be viewed, downloaded, and paid from the **Invoices** page in the 360dialog Hub. Billing is split into three invoice types: * WhatsApp API License Fee * Prepayment for Messages * Monthly Closing Invoice (MCI) ## Invoice Types at a Glance | Type | Description | | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | License Fee (Full & Pro-Rata) | A recurring monthly charge for each active WhatsApp number. Upon registration, the initial invoice includes the pro-rata fee for the remaining days of the current month and the full license fee for the following month, charged upfront. Regular monthly billing resumes after the prepaid period. | | Prepayment (Usage Top-Up) | Funds added to the credit balance to cover messaging costs. An invoice is issued when a top-up succeeds. | | Monthly Closing Invoice (MCI) | A reconciliation of the previous month's messaging usage against the credit balance. Issued on the first day of each month. | {% hint style="info" %} **Note:** The license billing process described on this page applies to clients who registered on or after 27 October 2026 at 15:00 CET and pay 360dialog directly. Clients registered before this date continue under their existing billing arrangements, with the pro-rata fee for the initial partial month and the full license fee for the following month invoiced separately. {% endhint %} ## When Does Billing Start Billing begins when a WhatsApp number is registered and the initial license payment is completed. During registration, the number is connected first, followed by payment. Before payment, the checkout displays a breakdown of the pro-rata charge for the remaining days of the current month, the full license fee for the following month, and the total amount payable. The license is activated once payment is successful. License fees apply from activation, regardless of when the first WhatsApp message is sent. These fees cover access to the WhatsApp API and associated services, rather than messaging usage. ## How to Read an Invoice Every 360dialog invoice follows the same layout: 1. **Invoice number and dates** - a unique ID, plus when the invoice was issued and when payment is due. 2. **Bill to** - the entity being invoiced. 3. **Description** - what is being charged, and which channel, account, or date range it covers. 4. **Quantity x Unit price (Net) = Total net** - how the line's charge was calculated. 5. **Amount (Gross)** - what the line actually costs, including any VAT. 6. **Total / Amount payable** - the bottom-right summary: the final amount due. ### WhatsApp API License Subscription Invoice WhatsApp API license fees are charged per registered phone number (channel), regardless of the number of messages sent. When a new number is registered, the initial invoice includes the remaining portion of the registration month and the full following calendar month. Once this prepaid period has ended, regular license invoices are issued on the first day of each calendar month for that month's subscription. For example, a number registered in October is initially charged for the remaining days of October and the full month of November. Its next regular license invoice is issued on 1 December for December's subscription. See [**Pricing**](/docs/get-started/pricing.md) for current license rates. No payment processing fee applies to license subscription invoices, including the initial pro-rata invoice. Payment is due upon receipt. If a recurring license invoice remains unpaid, outbound messaging may be blocked until payment is completed. #### **Example: License Fee**
Every line covers a full calendar month at the full rate when a channel renews on schedule. ### Pro-Rata License Subscription Invoice When a WhatsApp number is registered partway through a calendar month, its initial license fee is calculated proportionally to the remaining days of that month. The initial invoice includes: * **Pro-rata license fee:** The charge for the remaining days of the registration month. * **Next month's license fee:** The full subscription charge for the following calendar month. Both charges are included in the same invoice and paid upfront during registration. The pro-rata fee is calculated as: **(Days remaining in the registration month, including the registration date ÷ Total days in that month) × Monthly license price** The following month's subscription is charged at the full monthly rate. Once payment is successful, the channel is activated. No additional license invoice is issued for the prepaid following month. Regular monthly billing resumes on the first day of the month after that. A client registers a WhatsApp number on 28 October 2026 with a monthly license fee of €49. | Billing period | Calculation | Amount | | ------------------------- | ------------------------ | ---------- | | 28–31 October 2026 | 4 ÷ 31 × €49 | €6.37 | | 1–30 November 2026 | Full monthly license fee | €49.00 | | **Total initial invoice** | | **€55.37** | The client pays €55.37 upon registration, covering both billing periods. The next regular license invoice is issued on 1 December 2026, covering December's subscription {% hint style="info" %} **New clients who pay 360dialog directly**\ The first charge, paid when a number is activated, covers the rest of the current month plus the full next month. {% endhint %} #### **Example: Pro-Rata License Fee**
The Quantity column represents the proportion of the month being charged. A full monthly subscription has a quantity of 1.00, while a pro-rata charge is represented by a fraction. ### WhatsApp Prepayment Invoice The account has a credit balance that tracks messaging costs in real time. Registered phone numbers can send WhatsApp messages as long as the credit balance is positive. A top-up can be made at any time, in any amount. The frequency and size of prepayment invoices reflect the top-up pattern chosen for the account. Top-ups can be made manually or configured through Auto-Renewal. For more information, see [Funds](https://docs.360dialog.com/docs/hub/funds). #### **Example: Prepayment (Usage Top-Up)**
This invoice is generated when a top-up succeeds and is issued with a Paid status. ### Monthly Closing Invoice (MCI) A Monthly Closing Invoice is issued on the first day of each month for messaging costs incurred during the previous month. For example, messaging usage from January 2026 is invoiced on 1 February 2026. The MCI summarises transactions recorded against the credit balance during the month, including messaging costs, prepayments, and refunds. In most cases, no additional payment is required because prepayments have already covered the messaging usage. The MCI provides a record of the starting and ending balances, allowing clients to reconcile their messaging costs. #### **Example: Monthly Closing Invoice**
The usage line and the "Settled with credit balance" line generally offset each other, resulting in a zero amount payable. The monthly summary includes the starting balance, funds added, messaging usage, refunds, and ending balance. ### Payment Options A valid credit card on file is required for accounts billed directly by 360dialog. During initial registration, the license payment is completed before the channel is activated. For subsequent invoices, the card on file is charged automatically when payment becomes due. Clients can review their invoices and payment status in the 360dialog Hub. ### Payment Processing Fees Payment processing fees apply to messaging balance top-ups (Prepayment invoices) only. | Payment method | Processing fee | | -------------- | -------------- | | Credit card | 4% | License subscription invoices, including pro-rata charges, do not carry a payment processing fee. ### Taxes and VAT VAT treatment depends on where the business is registered and is applied to invoices accordingly. See [**VAT and Withholding Tax**](https://docs.360dialog.com/docs/hub/billing#vat-and-withholding-tax) for the full breakdown by location. ### Invoice Status | Status | Description | Action | | ------- | -------------------------------------------------------------------------- | ---------------------------------------- | | Pending | The invoice has been issued and an automatic payment attempt is scheduled. | No action required unless payment fails. | | Unpaid | Automatic payment was unsuccessful or manual payment is required. | Payment required. | | Paid | The invoice has been successfully paid. | No action required. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.360dialog.com/docs/hub/invoices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.