Answered from these docs only, by a model that cannot see your account. Check the pages it cites.

AI spend by department

Which department your AI spend goes to, by initiative category or by a department, class or tracking tag in your books.

View as Markdown

Answered from these docs only, by a model that cannot see your account. Check the pages it cites.

Checked against the product on November 11, 2026

Finance → AI Spend has two tabs. Vendors lists what you pay each AI vendor. Departments splits the same spend by department, over the same reporting period. Its rows always add up to the total on Vendors: what can't be put in a department gets a row of its own that says why, so nothing drops out.

The Department from filter decides what a department is. Roiva reads it from your own records, not from usage telemetry.

Initiative category

This is the default. Each initiative's category, such as Sales, Finance or Engineering, is a department.

  • What an initiative books of a bill is its category's spend. A bill an allocation rule shares between a Support initiative and a Sales initiative splits by the rule's shares.
  • A provider's own bill, such as Anthropic's or OpenAI's API bill, splits by what each linked initiative booked from it over the period, or evenly between them where nothing records what each booked.
  • Not on an initiative is the AI spend no initiative books. It's the same figure as AI Spend's unbooked spend.
  • Credits on no initiative is a refund or credit note no initiative booked. AI Spend counts a credit as booked in full, so it isn't unbooked spend, and it isn't any department's either.

A department in your books

Once your books are connected, the filter also offers their own dimensions:

  • QuickBooks: class and location;
  • Xero: each tracking category;
  • NetSuite: department, class and location.

Roiva reads the tag on each line of each AI vendor's bill and splits the bill by its lines' amounts. A bill with a $600 line tagged Engineering and a $400 line with no tag puts $600 under Engineering and $400 under Not tagged.

Not from these books is AI spend those books don't carry: a provider's own bill, which comes from its usage report, card charges from a card feed, and bills from any other books connection you have. Pick that connection's dimension to split those.

If your team codes every AI invoice to IT or G&A, that's what this shows. The page reports how your books coded the spend. It doesn't guess who used it.

What it doesn't cover

  • A cloud bill's AI part. Its booked part splits by everything each initiative booked from that cloud account, AI services or not. An initiative that books both EC2 and Bedrock weighs its EC2 too.
  • One figure for the period. Departments are shown over the reporting period as a whole, as AI Spend is. They're not broken out month by month.
  • Not per person. No tab here says which person or API key spent what.
  • The departments your books list. Only dimensions your books' chart lists can be picked. A dimension shows up once the connection has synced its chart of accounts.
  • NetSuite's line tags. These are read when vendor bills sync. A bill synced before this page existed, or by a role NetSuite won't let read transaction lines, counts as Not tagged. A sync that can't read the lines keeps the tags it last read. NetSuite card charges are always Not tagged.