Skip to main content

Organization billing

"The plan and the invoices belong to the organization, not to any one person." That is the biggest difference from a personal account: when an organization has a plan, the plan serves the whole organization, and someone leaving does not take it with them.

The collection mechanics - payment methods, invoices, re-authentication, the grace period after a failed renewal - are identical to a personal account and written out in full under Billing. The pricing rules are in Pricing, the collection rules in Payment policy. This page covers only what is different when several people share one account.

Who can change what​

The owner - usually whoever created the organization - owns the invoice and is the one who changes the plan, changes the seat count, or cancels the subscription. Admins manage people, not money.

More precisely, the billing owner is the only person who can:

  • add, change or remove the organization's payment method,
  • edit the invoicing details,
  • upgrade, downgrade, change the seat count or cancel the plan.

Admins still invite people and cap usage, but will see the line "Only owners can change roles and organization settings."

Hand over the invoice before that person leaves

The payment method belongs to the organization, but the only person who can change it is the billing owner. A billing owner leaving the company without naming a successor is how you end up with an expired card nobody can replace - and the next renewal fails. An organization must always keep at least one owner; name the successor first, under Members.

Invoicing details​

Invoices use the legal entity name entered under Billing, not the organization's display name. A friendly name for the workspace has no effect on the accounting paperwork.

An organization account needs all four of these:

FieldWhy it is needed
Company (legal name)The name printed on the invoice - it has to match the paperwork.
Tax codeWithout a tax code, no VAT invoice can be issued.
Billing emailBetter the accounts department's mailbox than the billing owner's personal address - people change jobs, and the invoices should still arrive.
Registered addressThe address printed on the invoice.

Fill these in before the renewal date: invoices are issued against the details held at the time of charge, so adding a tax code after the money has gone is too late for that period.

Seats​

The seat count decides how many people you can invite:

  • Adding seats is prorated for the time remaining and takes effect immediately - you can invite someone the same day.
  • Removing seats takes effect at the end of the period.
  • The Team plan holds a minimum seat count.

Removing a person from a seat does not reduce the invoice. The seat is the unit of charge and the person is what you put in it - to pay less you have to remove seats, and that only takes effect at the end of the period. What that person created stays with the organization; it does not leave with them.

Putting people into seats is an administrative step, not a billing one - do it under Members.

Enterprise does not go through a card​

Enterprise is a contract, not a checkout button:

  • Billed by invoice or PO under contract - there is no self-service card checkout, so the payment-method section decides nothing here.
  • An annual contract; changing seats, renewing or terminating follows the contract terms and goes through your account manager, not the app.
  • If a contract ends without renewal, the Enterprise entitlements are withdrawn and whatever exceeds the next plan's limits becomes read-only - nothing is deleted.

The organization's invoices and history​

The transaction history and each invoice sit just below the plan card and read like the personal version: Billing period · Paid with · Subtotal · VAT · Total. The difference is the seat count shown on every row - that is what explains why this period's amount differs from the last.

Where the money went inside the organization is a different question, answered under Organization usage.

When a renewal fails​

Kara gives notice with a deadline for updating the card, and the whole organization keeps working normally in the meantime. Nobody gets locked out mid-meeting because a card expired.

Two things are specific to organization accounts:

  • The notice goes to the billing owner, not to every member - so the only person who can fix it is also the only person who sees it. This is exactly why there must always be an active owner.
  • When the grace period runs out, every seat drops to Starter at once. Nobody's data is deleted; whatever exceeds the Starter limits becomes read-only.

Provide a valid method within the grace period and everything carries on immediately, with no interruption.

Cancelling an organization's plan​

The mechanics match a personal account: the plan is kept to the end of the period, then returns to Starter, and nothing is deleted - whatever exceeds the Starter limits becomes read-only. The detail is under Billing.

Content created by members but owned by the organization stays with the organization after cancellation; each person's access ends on the period boundary.

To delete the organization outright, the plan has to be cancelled first - Kara blocks it and says so: "To delete the organization, cancel the subscription first."