> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/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/partner/partner-hub/invoices.md).

# Invoices

This page describes invoice types in the Partner Hub, and how to read them

Invoices can be viewed, downloaded, and paid from the Invoices tab in the Partner Hub. Billing is split into three invoice types:

* License Fee
* Monthly Closing Invoice (MCI)
* Usage Top-Up

#### Invoice Types at a Glance

| Type                          | Description                                                                                                                                                                                                                                                                                                                                                                                   |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| License Fee (Full & Pro-Rata) | A recurring monthly invoice combining the Partner Plan platform fee, billed to every partner, with the License Fee for each active Partner-Paid channel. Channel fees are billed pro-rata for a channel'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. |
| Monthly Closing Invoice (MCI) | A reconciliation of the previous month's messaging usage and other platform charges. Issued on the first day of the month.                                                                                                                                                                                                                                                                    |
| Usage Top-Up                  | Funds added to the prepaid balance to cover messaging costs. Issued the moment a top-up succeeds. A processing fee applies to credit card top-ups.                                                                                                                                                                                                                                            |

### 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.

### License Fee (Full & Pro-Rata)

Every partner on the Partner-Paid billing model receives a recurring monthly License Fee invoice. It always carries the Partner Plan platform fee, and adds a License Fee line for each active channel.&#x20;

A Partner-Paid partner with no channels still receives this invoice for the Partner Plan fee alone. License fees are billed per phone number (channel) and apply to every registered channel, regardless of how many messages it sends.&#x20;

See [**Pricing**](https://docs.360dialog.com/partner/get-started/pricing) for current rates.

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

A channel added partway through the month is billed separately for that first, partial month. This pro-rata charge is issued at the end of the month, covering only the days the channel was active, and is calculated as: (days active in the month / total days in the month) x full monthly price.&#x20;

From the first of the following month, the channel is billed at the full monthly rate like any other active channel, on the standard License Fee invoice.

#### **Example: License Fee (Full Month, with Partner Plan)**

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2F0qwiwOwJh13L0q6N532p%2Fimage.png?alt=media&amp;token=848367df-a87e-4f36-9bc5-ab5ad8a6cdc0" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FtGfBAuiy8paC3dl7mPX2%2Fimage.png?alt=media&amp;token=b2812b4a-6c70-4da1-944a-bc5eee084f8f" alt=""><figcaption></figcaption></figure>

### Monthly Closing Invoice (MCI)

An MCI is issued on the first day of each month for the messaging costs incurred in the previous month across all channels. 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.&#x20;

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://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FxKIFIfwIXVyZL5s96YMq%2Fimage.png?alt=media&amp;token=7d7a7598-dbf8-42fa-8e67-35f893f168be" alt=""><figcaption></figcaption></figure>

### Usage Top-Up

The credit balance for Partner-Paid channels tracks messaging costs in real time. Messaging rates follow [**Meta's rate cards**](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing#rate-cards-and-volume-tiers).

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 Usage Top-Up invoices simply reflect the top-up pattern chosen for the account.[ Auto-renewal](https://docs.360dialog.com/partner/partner-hub/funds#auto-recharge) can be set up to automate top-ups by setting an auto-renewal threshold and amount.

A processing fee of 4% applies to credit card top-ups, passed through from the card network. Bank transfer and Pix or Boleto top-ups carry no processing fee, but please always check with your banking partner.

#### **Example: Usage Top-Up**

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2F5hzKbDt9WBTN5iNrdJmS%2Fimage.png?alt=media&amp;token=50a7aa6b-5756-4828-ab1d-47ba3592b803" alt=""><figcaption></figcaption></figure>

### Additional Reports

For partners on the Partner-Paid billing model, two additional reports are generated and sent each month:

* **WhatsApp Usage Summary by WABA** - a monthly breakdown of billable messages by category (Marketing, Utility, Authentication) and the associated cost per channel.
* **Daily Message Counts** - a daily report of delivered message volumes, grouped by channel and category.

### Payment Options

1. **Credit card** - a valid credit card is advised for all accounts. The card on file is charged automatically as soon as an invoice is issued.
2. **Bank transfer** - available for accounts with significant volumes once enabled after a volume evaluation.&#x20;
3. **Pix and Boleto** - local payment methods for Brazilian customers.

### 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/partner/partner-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/partner/partner-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.
