> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization billing

> One organization pays for the credits of several workspaces, as a pool with a monthly commit or metered per credit. What owners and workspaces see, how to add workspaces, limits and the cap

With organization billing, the [organization](https://docs.neoagent.io/customizing/organizations.md) pays for the credits of the workspaces you choose, on one bill. Each of those workspaces is **organization-billed**: it has no plan of its own. The other workspaces in the organization are **standalone**: each pays for its own plan, as before.

Your account manager turns organization billing on. The dashboard has no way to buy it. Until then, the **Billing** tab on the Organization page says: *Organization billing is not active. Contact your account manager to activate it.*

## Pool or metered

An organization is billed in one of two ways. Your account manager agrees the terms with you.

| | Pool | Metered |
| - | - | - |
| Each month in advance | The commit: a number of credits, at the commit price | Nothing |
| On the 1st, for the month before | Each credit above the commit, at the overage rate | Each credit, at the rate per credit |
| Unused credits | The commit's unused credits expire at the end of the month | Not applicable |
| Invoices | Two a month: the commit, and the usage invoice | One a month: the usage invoice |

The usage invoice has one line for each organization-billed workspace. Credits count the same way as on [Billing types](https://docs.neoagent.io/product/metered-billing.md#what-counts-as-a-billed-credit): agent, workflow and chat credits, plus Phone Agent minutes.

A pool can start on any day. Its first commit is charged for the days left until the next 1st. A later change to the commit takes effect on a 1st.

## The Billing tab

Open [**Organization** → **Billing**](https://dashboard.neoagent.io/organizations?tab=billing). Organization owners and administrators see this tab. Only owners add workspaces, remove them and set limits.

| State | What the tab shows |
| - | - |
| Not active | *Organization billing is not active. Contact your account manager to activate it.* |
| Starts later | *Organization billing starts on* the start date, and the list of workspaces |
| Active | This month's figures, the cap, the list of workspaces and the invoices |
| Payment failed | A banner with a link to update the card. Billing keeps running while Stripe retries the payment |

For a pool, the figures are the commit, the credits used, the overage so far and the estimated overage charge. For a metered organization, they are the credits used and the cost so far at your rate. All amounts are before tax.

The workspace table has these columns: **Workspace**, **Billing** (Organization or Standalone), **Credits this month**, **Share of total** and **Limit**. The credits are the ones the organization pays for this month. A workspace that left organization billing during the month keeps the credits it used before it left, and the organization pays for them. A workspace that was standalone all month shows *Not counted*.

## Add workspaces

An owner adds existing workspaces once organization billing is active or has a start date. There is no payment step, because the organization's card is already on file.

**1. Pick the workspaces**

On the [**Billing** tab](https://dashboard.neoagent.io/organizations?tab=billing), select **Add workspaces**. Every workspace in the organization is listed, and the ones that can join are selected. A workspace that cannot join says why.

**2. Review each join**

Select the **Review** button, which counts the workspaces. For each workspace, choose when it joins. The review shows the join date and what ends.

**3. Confirm**

Select **Confirm**. From its join date, the organization pays for the workspace's credits. Usage before that date stays on the workspace's own plan. The workspace's admins get an email that says when it joins.

A workspace on a plan has two choices:

| Choice | Joins | Its plan | Money |
| - | - | - | - |
| **At period end** (default) | When its paid plan period ends | Cancels at the end of the period | Nothing is lost |
| **Join now** | 00:00 UTC the next day | Ends then, with no proration | The unused part of the period is not returned. The review shows the amount before you confirm |

A workspace in a trial, or with no plan, joins at 00:00 UTC the next day.

When organization billing starts on a later date, no workspace joins before that date. **Join now** and a workspace with no plan join on the start date. **At period end** joins at the first end of a paid period on or after the start date, so the plan can renew once or more before then. The review shows each workspace's real join date.

| The workspace says | What to do |
| - | - |
| Auto top-up is on | Turn off auto top-up on that workspace's [**Billing**](https://dashboard.neoagent.io/billing) page, then add it |
| It has top-up credits left | Add it after it uses them, or ask your account manager to refund them |
| Pax8 bills this workspace | A workspace billed through [Pax8](https://docs.neoagent.io/product/buying-through-pax8.md) cannot join |
| Its own metered or Custom + overage deal, or an annual plan | Ask your account manager to move it |

## Create a workspace the organization pays for

When organization billing is active or has a start date, **Create workspace** on the Organization page asks how to bill the new workspace:

* **Own plan**: a 14-day free trial, then the workspace pays for its own plan.
* **Billed by the organization**: no trial. The organization pays for its credits from the start, or from the start date.

The rest of the steps are on [Create a subsidiary workspace](https://docs.neoagent.io/customizing/organizations.md#create-a-subsidiary-workspace).

## Limits and the cap

Both count the credits of the current month and start again on the 1st at 00:00 UTC.

* **Workspace limit**: only an organization owner sets, raises or clears it. The owner types a monthly credit limit in the **Limit** column of a workspace. It saves when you leave the box. Leave it empty for no limit. A workspace at its limit stops new agent and workflow runs until the 1st, so one workspace cannot use the whole commit.
* **Cap**: your agreement can set a cap for the whole organization. The **Billing** tab shows the credits used against it. Organization owners and administrators get an email alert at 80% and at 100% of the cap, once for each level in a month, and again if the cap changes. At the cap, new agent and workflow runs stop in every organization-billed workspace until the 1st. Only Neo raises the cap: ask your account manager.

## What an organization-billed workspace sees

Its [**Billing**](https://dashboard.neoagent.io/billing) page says *Billed through* the organization's name. It shows the workspace's own credits this month and its limit, if one is set. It shows no plan, top-up, add-on, price or invoice, and no other workspace. For an add-on such as the Phone Agent, contact your account manager.

When a run stops at the workspace limit or the organization cap, its message tells you to ask an owner of your organization.

## Neo API and the Neo Support agent

* [`GET /public-api/billing/organization`](https://docs.neoagent.io/developers/introduction) returns the open workspace's own share: the organization's name, its credits this month, its limit and the removal date. Any caller of the workspace can read it, and the Neo Support agent uses it to answer "how much has this workspace used".
* `GET /public-api/organizations/{organization_id}/billing` returns what the **Billing** tab shows, and `PUT /public-api/organizations/{organization_id}/billing/workspaces/{client_id}/limit` sets a workspace limit. Both need an organization owner or administrator; only an owner sets a limit. A workspace API key gets 403 on both.
* In the dashboard chat, the Neo Support agent answers organization-wide questions and sets limits for a person who holds that organization role. It asks for approval before it changes a limit. In Teams or Slack it answers only for the workspace, and sends you to the dashboard for the rest.

## Remove a workspace

An owner selects **Remove…** on the workspace's row and picks a removal date. The earliest date is 7 days from today, and the workspace's admins get an email 7 days before it. From that date the workspace has no plan, so new runs stop until one of its admins chooses a plan on its **Billing** page. Until that date its **Billing** page shows a **Choose a plan** banner with the date. The organization still pays until then, so the workspace cannot buy a plan of its own earlier.

A workspace leaves organization billing before it can leave the organization.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.