> 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 every active WhatsApp number. Billed pro-rata for a number's first, partial month, then at the full rate from the next full month onward. Full-month charges are issued on the first day of the month; pro-rata charges are issued at month-end. |
| Prepayment (Usage Top-Up)     | Funds added to the credit balance to cover messaging costs. Issued the moment 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 of the month.                                                                                                                                                          |

### When Does Billing Start

Billing begins as soon as signup is completed and the license purchase is finalised, not when the first message is sent. A newly onboarded number starts accruing its monthly license fee immediately, even before it is actively sending messages: the fee covers account access and support from day one, not just 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

An invoice is issued on the first day of each month for the license fees of the WhatsApp API.

License fees are billed per phone number (channel) and apply to every registered number, regardless of how many messages it sends. See [**Pricing**](https://docs.360dialog.com/docs/get-started/pricing) for current rates.

No payment processing fee applies to this invoice type, so payment by credit card carries no surcharge.

Payment is due on receipt. If it remains unpaid outbound messaging for the account is blocked until the invoice is settled.

#### **Example: License Fee**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FzJGUD9YXN66CapsavLJp%2Fimage.png?alt=media&amp;token=19c1fdc0-cdec-4077-9b19-e9122298f882" alt=""><figcaption></figcaption></figure>

Every line covers a full calendar month at the full rate when a channel renews on schedule.

### Pro-Rata License Subscription Invoice

A phone number onboarded during the month is invoiced separately from existing numbers. This pro-rated charge is issued the day the number is activated.

The pro-rata fee is calculated as: (days active in the month / total days in the month) x full monthly price.

For example, a number onboarded on the 21st of a 30-day month is active for 10 of the 30 days, about one-third of the month. The pro-rated invoice charges one-third of the full monthly price. From the first of the following month, the number is billed at the full monthly rate like any other active number.

#### **Example: Pro-Rata License Fee**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FP5wYMKKQX2QUjdikPQEq%2Fimage.png?alt=media&amp;token=053100c1-52ff-43cb-9fd4-fae9e1ffdf3f" alt=""><figcaption></figcaption></figure>

The fractional Quantity column (0.45, 0.13) is the pro-rated share of the month, applied to the same full monthly unit price used on a regular License invoice.

### WhatsApp Prepayment Invoice

The account has a credit balance that tracks messaging costs in real time.&#x20;

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 simply reflects the top-up pattern chosen for the account.

Auto-renewal can be set up to automate top-ups by setting an auto-renewal threshold and amount. For example, when the balance reaches 100 EUR, the system automatically charges 300 EUR.

#### **Example: Prepayment (Usage Top-Up)**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2F9oLMM4eXdhPKhOAkCCTW%2Fimage.png?alt=media&amp;token=27020df2-4c5a-495c-af06-0cd84c200ab2" alt=""><figcaption></figcaption></figure>

This invoice is generated the moment a top-up succeeds, so it is always issued as Paid; there is no Pending or Unpaid stage for this type.

### Monthly Closing Invoice (MCI)

An MCI is issued on the first day of each month for the messaging costs incurred in the previous month. For example, usage from January 2026 is invoiced on February 1, 2026.

This is a summary invoice for every transaction on the credit balance during that month: messaging costs, prepayments, and any refunds. In most cases, no separate payment is needed, since prepayments made during the month already cover the usage, and the MCI is automatically marked as paid. Either way, the MCI's purpose is to show the starting and ending balance for the month, so the credit balance can be reconciled at a glance.

#### **Example: Monthly Closing Invoice**

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FXNyoo2t7kGPf8ZOyvUWE%2Fimage.png?alt=media&amp;token=84a1bd38-d179-4e19-8b5e-fac015e10fe5" alt=""><figcaption></figcaption></figure>

**Monthly summary:** Hub ID: MRFd2oPA, Starting balance: 492.80 USD, Total added funds: 10500.00 USD, Total usage: 10440.60 USD, Total refunds: 0.00 USD, Ending balance: 552.20 USD, Usage reconciliation: 0.00 USD

The usage line and the "Settled with credit balance" line offset each other, so the Total is often 0.00. The Monthly summary block at the bottom is unique to the MCI: it shows starting balance, funds added, usage, refunds, and ending balance for the period.

### Payment Options

A valid credit card on file is mandatory for all accounts and is the default way 360dialog collects payment for License, Prepayment, and MCI invoices.

The card on file is charged automatically as soon as an invoice is issued.

### Payment Processing Fees

A processing fee applies to balance top-ups (Prepayment invoices) only.

| Payment Method | Processing Fee |
| -------------- | -------------- |
| Credit card    | 4%             |

License Fee and Pro-Rata invoices never carry a processing fee.

### Taxes and VAT

VAT treatment depends on where a 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 not completed, or manual payment is required.        | Manual 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=<question>&goal=<user_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.