Allcora Join the waitlistJoin

Help / Track spend

Unattributed spend

Usage that Allcora can't place on an engagement waits in the firm's pool. Assign it once, add a rule, and the same key or person lands automatically next time.

What lands in the pool

Usage goes to the pool when no engagement tag, key rule, person rule or workspace rule matches it. Common causes are a new API key nobody has mapped yet, and usage tagged with the code of an engagement that is closed or still a draft.

Org admins and Finance owners see the running total as Unattributed spend on the Engagements page, with a Review link. The pool has a nominal budget of 1,000 in your reporting currency, so the person who created the firm gets a one-off alert when total unattributed spend since the firm started passes it.

Assign usage to an engagement

  1. Open Unattributed in the menu. Each item shows when it happened, the person or key, the vendor and model, the source and the cost.
  2. Select the items that belong together. A page shows 100 items, and you can select up to a page at a time.
  3. Select Assign n to an engagement and choose an open engagement.
  4. If the items share one key or one person, Also send future usage from … to this engagement is ticked for you and creates an attribution rule. Untick it if you don't want one.

Items from today move with their figures straight away. Items from the previous two days update at the next morning's reconciliation. For older items, contact us before relying on the engagement's reconciled figures for billing. Every move is recorded in the audit log. Org admins and Finance owners can assign any item. Engagement owners can assign items to engagements they own.

A clear pool is the best sign that your rules are complete. If the same key keeps appearing, assign it with the rule box ticked, or ask an Org admin or Finance owner to add a rule under Usage sources → Attribution rules. See Connect usage sources.

Daily reconciliation

Every morning at 07:15 UTC, Allcora compares the last three days of estimates with your Anthropic and OpenAI usage reports, which are the financial record. A day becomes final once every Anthropic and OpenAI source has reported past the end of that day. Until then, figures carry an "Estimated, not yet reconciled" label. If one of those sources is paused or failing, its days stay estimated, and days more than three days old aren't reconciled later, so keep vendor sources healthy.

If Allcora's priced figure for a day differs from the vendor's cost report by more than 2% (and at least US$1), Finance owners and Org admins get an email. A difference usually means a key is missing from Allcora or a model's price has changed.

Claude Code

When the Claude Code source has an Anthropic Admin API key, each person's daily Claude Code cost from Claude Code's analytics is shared across the engagements they ran through the Allcora CLI that day, in proportion to that use. If they ran nothing through the CLI that day, their Claude Code cost for the day is added to the unattributed total. It shows in the total but not as items on the Unattributed page, so it can't be assigned; the fix is to start sessions with allcora run.

Seat subscriptions

Seat-priced tools, such as Claude Team or Cursor seats, are entered under Settings → Seats by an Org admin or Finance owner. Tick everyone who holds a seat: only seats assigned to people are charged. On the 1st of each month, last month's seat cost is split across engagements by each person's share of tagged usage. A person with no tagged usage that month goes to the pool.

Last reviewed 29 October 2026, Allcora platform version 15.