Billing, invoices and tax

Billing is per organization. Invoices, payment method, and usage against each limit are on the organization's billing page.

What you are charged

• Your plan, per seat where the plan is per-seat, monthly or annually.

• Overages, if you exceed included usage. See the overage article for the rates and how each is measured.

Annual billing is cheaper per seat: $3/month rather than $4 on Personal, $10 rather than $12 on Business. Enterprise is $20 per seat per month on a twelve-month commitment, with no separate annual rate and no month-to-month option. The dedicated add-on is a flat $2,500 per organization per month on top of Enterprise seats.

Timing

Your billing period is an anniversary month in UTC, and overages are aggregated across it and priced once at settlement — a job that runs for 40 seconds is not rounded up to a minute on its own. The billing-period article covers the boundaries, the short-month clamp, and what happens at settlement.

Mid-period changes

Seat increases and plan upgrades prorate immediately. Seat reductions and downgrades apply at renewal. Refunds are not automatic.

Who can see and change it

Billing is gated by organization role. Owner and Billing can manage it; Admin deliberately cannot — an administrator who manages members and repositories does not need the payment method. Auditor and Admin can see usage without touching billing.

Tax

Tax follows the billing details on the account, so keep them accurate — a wrong country produces a wrong invoice that has to be corrected rather than reissued silently. If your organization is tax-exempt, or needs a VAT or registration number to appear on the invoice, add it to the billing profile before the first charge rather than after.

Invoices

Every invoice is available on the billing page and emailed to the billing contact. Set a billing contact that is a shared address rather than one person's, so invoices do not follow an individual out of the company.

Disputes

Contact billing support with the invoice number. Do not include repository contents, keys, or tokens in a billing message — the rule about what never to send applies on every channel.