Cursor Enterprise Billing Groups: Spend by Team, SCIM & Chargebacks

Each member belongs to exactly one billing group at a time. Anyone not assigned lands in the reserved Unassigned group, so until you assign people, a rollout's first month reports as one large number. Usage is attributed to the member's group at the time it occurs. Moving someone later doesn't rewrite history, unless you delete a group, in which case its historic usage moves to Unassigned.

Because nobody can sit in two groups, billing groups give you one axis of attribution: department, cost center or product line, but only one of them. Pick the axis your finance system already reconciles against. The report is only useful if someone downstream can match it to a budget they own, and rebuilding the groups later splits the history across two schemes.

Attribution at the time of usage surprises people after a reorg. Say an engineer moves from the platform group to the payments group in the middle of a billing cycle. Usage before the move stays with platform and usage after it goes to payments, so each group's report carries part of that person's month, matching neither the old org chart nor the new one. If someone later deletes the platform group, its share moves to Unassigned, and the payments share stays where it is.

The numbers are right, but you can't reconcile that quarter against the current structure. Reconcile on each billing cycle, while the moves are still recent.

Create groups in the dashboard and fill them in one of four ways: SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. sync, the Admin API, a CSV upload or manual selection.

1. 1Open the web dashboard Members & Groups tab (Enterprise admins only).
2. 2Click Create Group and name the group.
3. 3Assign members through SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. (sync with an existing SCIM group), the Admin API, a CSV of group names and member emails, or manual selection from Unassigned.
4. 4SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition.-synced groups can't be edited by CSV, API or manual changes in the dashboard. Membership must come from your identity provider.

Choose by where the truth about your org already lives. Use SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. if your identity provider carries departments, so Cursor mirrors it instead of keeping a second copy. Use the Admin API when an internal platform owns cost centers and can push changes, and CSV for a one-off backfill of people who joined before the scheme. Manual selection works for a small org and gets expensive in a large one, because it depends on someone remembering.

Step four reads like a limitation, but it is the reason to use SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition.: a SCIM-synced group can't be edited by CSV, by API or by hand, so membership has exactly one source. A reorg in the directory then moves people's future usage to their new groups on its own, while past usage stays where it was. The trade-off lands on finance. Regrouping one person for a chargeback becomes a change request against the directory, which can mean a different team and a different week.

Decide the source of truth before you create the first group. A group managed in two places drifts, and the drift shows up as a number nobody can explain. The CSV also pairs group names with emails, so after a rename, the spreadsheet finance saved last quarter matches nothing.

Moving and renaming are routine, and deleting is the one to watch. How you move members depends on whether the group is manual, SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition.-synced or driven by the API. Deleting a group reassigns all of its historic usage to Unassigned, with no way back.

Handling delete carefully usually means not deleting. Deleting a group changes the numbers behind every report it appeared in, so a rerun no longer matches the copies already circulated. When a department stops existing, rename its group instead, for example to Platform (through 2026), and leave it in place. The history stays attached to a name that still explains itself.

When a chargeback report looks wrong, start from the Members & Groups table, which shows each group's configuration, member count and spend for the period. Then check three things in this order before you conclude the numbers are broken:

1. 1Is the member in Unassigned? That is where anyone the process missed ends up.
2. 2Did they move groups mid-cycle? Then the split is real and the report is right.
3. 3Is the group SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition.-synced? Then the fix is in your identity provider, and no change in Cursor will reach it.

Billing groups manage spend attribution within one Enterprise team. For cohorts across linked teams, Cursor documents Organization Groups, which do a different job. They apply settings such as spend limits, model access and agent controls to a cohort across teams, and they can drive team membership.

One person can sit in a billing group, a team directory group and an Organization Group at the same time, and all three can sync from your identity provider. Billing groups handle only attribution. Spend limits and policy within a team are a directory-group question, and settings for a cohort across teams are an Organization Groups question.

Billing groups don't enforce a budget either. They attribute usage for reporting, and Cursor's billing-group docs describe no spend limit on them. Per-group ceilings come from spend limits on directory groups or Organization Groups, and when someone belongs to several groups, the highest applicable limit wins. Pooled usage covers how the shared budget behaves underneath all of this.

If you automate any of this, keep the API routes apart. Billing groups use the Admin API's /teams/groups routes and group_ ids. Team directory groups use /teams/directory-groups and team_group_ ids, and Organization Groups use the Organization API.