> Index of every Falcon docs page, for assistants: https://falcon.com/docs/llms.txt

# How a sub-company's usage is billed

While a company is a sub-company, its usage is billed to the parent. The parent's spending limits cover both, and the sub-company's own limits still apply.

Billing rolls up to the parent. There is no separate switch for it.

## Billed to the parent

- Usage while the link lasts is billed to the parent company. The parent's month includes it. The sub-company's own month leaves out the usage that was billed to the parent.
- Usage from while the companies were linked still bills to the parent, even when the record is written after they detach.
- After the sub-company is detached, new usage is billed to the sub-company itself. See [Detach a sub-company](https://falcon.com/docs/detach-a-sub-company).

## Spending limits still apply

- The parent's **Monthly limit** and **Daily limit** on **Spending** cover the parent and its sub-companies together.
- The sub-company's own **Spending** limits still apply to its own work. A run can be refused by either limit.
- A key the sub-company added is billed by that provider to the account on the key. The usage still counts here, as **Your keys** says, and it still rolls up to the parent until the company is detached.

## Related

- [Set the company's spending limits](https://falcon.com/docs/spending-limits)
- [Detach a sub-company](https://falcon.com/docs/detach-a-sub-company)
- [Add the sub-company's own key](https://falcon.com/docs/sub-company-own-key)