How costs reach an initiative
Every way spend becomes an initiative's cost, where the same dollar can arrive twice, and what Roiva leaves out, counts anyway, or only suspects.
Answered from these docs only, by a model that cannot see your account. Check the pages it cites.
Checked against the product on November 9, 2026
An initiative's cost is the sum of its cost entries. Every one of those is one row, and every row goes through the same door — whether a sync wrote it, a recurring schedule wrote it, or a person typed it — so a currency, a cost category and a period mean the same thing whatever recorded them.
This page is about where those rows come from, and about the question a finance team asks second: if spend can reach an initiative from several directions, how do you know it hasn't been counted twice?
The ways spend becomes a cost
- A connection linked as a cost source. The provider's own bill, narrowed to the part the initiative runs on. What narrows it depends on the platform — the vendors you pick on a finance or card system, the services or usage types on a cloud, the projects, workspaces, API keys, Claude Enterprise user groups or chat Projects a model provider claims for the initiative, a cost-allocation tag on AWS or Azure. What each platform books has a row per platform; Linking connections to initiatives walks through setting one up.
- A vendor mapping on a finance or card connection. The vendor's bills on your books become the initiative's cost, at the share you set.
- An allocation rule on a finance or card platform. A rule splits a platform's bills across initiatives on an approved basis, with journals behind it. See Allocation rules and accounting periods.
- A recurring cost on the initiative — a subscription or a retainer no integration reports. See Vendors, shares and recurring costs.
- A cost entry somebody records, asks the Assistant to record (marked as recorded through the Assistant), imports from a CSV or a tracker workbook, or accepts from a document Roiva read. See Adding costs and value entries.
None of these books anything new into a locked accounting period. A row dated in a locked month, or moved into one, is refused whichever way it arrives, and a bill a sync finds for that month waits until someone reopens it.
Tax on a bill
Roiva takes out only tax your books posted to a tax account. On a bill or expense from QuickBooks or Xero, the cost is the total less that tax. That's usually VAT or GST the company claims back, which was never part of what the initiative cost. The cost entry's notes record the tax left out.
Tax your books leave in the expense stays in the cost. US sales tax a company pays on a software purchase is normally recorded that way, as part of the expense, and so is VAT the company can't reclaim. Roiva doesn't judge whether a tax is recoverable, because your books already have: tax that can't be claimed back isn't entered as tax, so it sits in the expense line.
Where a source can't say what your books posted to a tax account, Roiva books its total, tax included. Source by source:
- QuickBooks and Xero. Bills, expenses and spend money are booked at their total less the tax posted to a tax account.
- NetSuite. Vendor bills and credit card charges are booked at their total. NetSuite's query language can't read tax kept under its Legacy Tax engine, and Roiva doesn't read SuiteTax's tax details.
- American Express statements. Charges are booked at their total. The statement file has no tax figure.
- A card charge your books also carry. It counts from the card platform, at its total, and your books' copy is left out even when that copy is net of VAT. Taking the books' figure would mean matching each charge to its copy, which is the guess Roiva doesn't make (see below). A company that reclaims VAT on card spend books that VAT as cost here. Finance → AI Spend, below its table, and the card connection's page say how much it is, totaled from your books' copies.
- AWS, Azure and Google Cloud. Their connections book usage before tax. AWS lists tax as its own "Tax" line, which no service mapping books, and a connection booking by tag never sees it. Azure's cost data is before tax. Google Cloud counts tax in a budget's own spend, but Roiva leaves it out, so a budget shows less in Roiva than in Google Cloud by its VAT or sales tax.
- GitHub, OpenAI, Anthropic, Snowflake and Databricks. Their usage reports carry no tax, which is added on the invoice. Databricks is priced at its list prices.
- A cost entry a person records or imports. It's the amount they enter.
So US sales tax a cloud or model provider adds to its invoice isn't in what that provider's connection books, even where your books keep it as cost. For five of those vendors you can close that gap yourself, below.
Pricing a linked vendor by your books
For GitHub, OpenAI, Anthropic, Snowflake and Databricks, a connection linked as a cost source counts the vendor's own report and leaves its bill in your books out. The report is usage before tax, and Databricks' is at list price, so what the connection books and your ledger rarely agree.
The vendor's page (open it from Finance → AI Spend) sets the two side by side: what your books hold from it and what its report says, over the last twelve complete months, and the ratio between them. A factor of 1.083 means your books hold 8.3% more than the report. Where a vendor's bills are dated the month after the usage they cover, each is read against the month before. The part of a bill the report never carries, such as Claude Team seats, is left out of the books' side: it's booked from your books already (see What Roiva leaves out, below), and a factor that included it would count it a second time.
An Owner or Admin can accept that factor: on the vendor's page, choose Apply to linked costs. From then on:
- Each month of usage the connection books carries one adjustment at the accepted factor, as its own cost line of type Adjustment. At 1.083, a $1,000 month gains $83. At 0.75, it loses $250.
- The usage lines stay exactly what the vendor reported.
- The accepted factor doesn't move by itself. It's recorded with who accepted it, when, and the figures it was read from.
- If the figures later give a factor more than three points away, the row and your Inbox say so. Accept the new one or stop; nothing reprices until you do.
- A locked accounting period is never adjusted.
Roiva never applies a factor without that acceptance, and offers none where the figures can't support one: books in a different currency from the report, fewer than three months to compare, under $1,000 on the report, or a ratio outside 0.5 to 1.3, which is more likely a prepayment than a price. The row says which.
Stop applying takes the adjustments back, except in locked periods.
Why the same dollar can arrive twice
Because a vendor's spend does not only appear on that vendor's bill.
Anthropic charges you, and the charge also lands on your books as a bill from "Anthropic, PBC" and on a card statement from your card platform. Databricks charges you, and the same usage appears as an "Azure Databricks" line on your Azure bill. Each of those is a real record of the same dollar, held by a different system, spelled differently by each.
Roiva connects to all of them on purpose — that is what makes the total complete — so every one of those pairs is somewhere a cost could be counted twice. There are three honest answers to that, and Roiva gives all three rather than claiming the problem away.
What Roiva leaves out
Where a vendor's name is one no other company's bill carries, Roiva leaves that vendor's bill to the vendor's own connection, in any month it books. "Anthropic", "OpenAI", "GitHub", "Snowflake" and "Databricks" each name one company and nothing else, so a bill on your books whose vendor name contains one of them is that connection's to count.
The connection counts the vendor's own report, though, and a report isn't the whole invoice. So Roiva leaves out only the part of a bill the report also counts. What a vendor bills outside its report is booked from your books beside it:
| Vendor | Its connection counts | Booked from your books beside it |
|---|---|---|
| Anthropic | Claude API usage billed to your Console organization, from Anthropic's cost report | Claude Pro, Max, Team and Enterprise plans, which are billed through claude.ai and aren't in this report, and Priority Tier, which the cost report leaves out |
| OpenAI | API usage, from OpenAI's organization costs | Every ChatGPT plan, which OpenAI bills apart from the API |
| Snowflake | The usage types it maps, from Snowflake's usage in currency | Snowflake Marketplace listings, which Snowflake invoices separately |
| GitHub | Copilot seats, premium requests and AI credits, from GitHub's billing usage | Nothing. The rest of a GitHub invoice, such as plan seats, Actions and storage, isn't an AI initiative's cost unless you name it when you link GitHub |
| Databricks | The products it maps, at list price | Nothing. What the invoice adds is price, which Pricing a linked vendor by your books, above, covers |
Roiva tells the two apart by what the bill says it's for. A bill line or item, or a card charge's descriptor, that names one of those products is booked beside the connection, and the rest of that bill is left to it. On an Anthropic invoice with a $300 usage line and a $250 Claude Team line, $250 is booked and $300 is left out. The part booked is those lines' share of what the bill cost, so tax posted to a tax account comes off it as it would off the whole bill. The cost entry's notes say so, naming the product booked beside the connection and the amount the connection took.
Roiva matches the product's name, never an amount or a date. A bill that doesn't name the product is read as usage and left to the connection, as is every NetSuite bill, because Roiva doesn't read what a NetSuite bill line says it's for. A card charge has no lines, so it's booked beside the connection only when its descriptor names the product. If your books record a seat invoice without saying what it's for, put the plan's name in the line's description or item, or in the vendor's name.
Each vendor's page, opened from Finance → AI Spend, says how much of its bills was left out, and how much of those same bills is still counted because the report doesn't carry it.
If you buy Copilot under a volume or prepaid agreement, those seats may not be in GitHub's billing usage until the agreement ends. Compare your GitHub bills with what the GitHub connection books, on GitHub's vendor page.
Two things take the bill back, and the connection books nothing for that initiative that month:
- An allocation rule for that vendor, because a rule is an approved split with journals behind it, and an approval outranks a heuristic.
- A locked accounting period, which no sync may change — journal entries and auditor packets already reference those numbers.
Each takes the month only when the bill holds usage the connection's report counts. A rule's Claude Team invoice, or a locked row holding only seats, leaves the connection's usage counted.
Both work one initiative at a time. If a rule or vendor mapping books a vendor's bill to one initiative while the vendor's connection books to another, nothing gives way, so the account counts that spend twice. See The same bill and connection on two initiatives, below.
Months before the connection has data still book from the mapping, at the share you set. The same rule runs on a cloud's bill: an "Azure Databricks" line is left to the Databricks connection in any month it books.
Card charges work the same way in the other direction. Where a card platform is connected, its charges are counted from the card platform, and the copies of them posted from that card's account in your books are left out.
What Roiva counts twice on purpose, and says so
AWS, Azure and Google Cloud do not have a name that belongs to them alone. Azure bills as Microsoft, beside your Microsoft 365 invoice from the same name. Google Cloud invoices come from "Google Cloud EMEA Limited", so an exact match fails the other way.
A wrong match there would not double a cost — it would silently drop a real one, and a dropped cost is worse than a doubled one, because a doubled cost is at least visible in the total. So for those three Roiva suppresses nothing. Both copies are booked, and the mapping form warns you.
Claude Enterprise is handled the same way. Its name is on no bill: it bills as Anthropic, and a line on that invoice can't be told apart as seats, which its cost report leaves out, or usage, which it carries. Leaving the line out could drop real seat fees, so both copies are booked.
Roiva reports the size of that overlap rather than leaving you to find it. Say the AWS connection books $1,820 of Amazon Bedrock for an initiative, and an allocation rule books it 25% of each AWS invoice. If the rule takes 25% of every line, Bedrock included, its quarter of the invoice holds $455 of that Bedrock, so $455 is counted twice. Where Roiva can't read what share of the invoice the books took, such as a bill typed in or one a card paid part of, or where the connection books only part of the service, it reports the smaller of the two copies that month and says up to: the most it can be, never the invoice. Bills reaching the initiative through more than one rule or mapping in a month are an up to as well, of their shares together.
Whether the overlap is a mistake depends on what the books' share is meant to be, which only you know. Each initiative's row says what both copies book and links the change for either answer:
- The initiative's part of the whole invoice, AI services included. Then the connection books those services a second time. Change the connection's mapping: remove the service, or set its share to the part the books don't already carry. A share applies from the first of this month, unless an Owner or Admin dates it back over the months already booked. Removing a mapping stops it booking more; what it already booked stays.
The rest of the invoice, without the AI services. Then the books' share holds them too. Lower it on the initiative's Costs → Vendors, where a rule's share and a books vendor mapping's share are both set; the row suggests a share that leaves the doubled part out, on those months' figures. Either share applies to bills dated from today. Someone who approves rules can date a rule's share earlier, which re-splits the bills already booked. A mapping's share can be dated back to the first of this month, and only an Owner or Admin can date it earlier, which re-books those bills.
Both copies are right. For when the books' share was already sized without the AI services, or those services are billed on an invoice the books don't split. Roiva can't check this, so an Owner or Admin records it with a reason, under Both copies are right on the row. The overlap then leaves what may be counted twice and is listed under Already Counted Once, with who, when and why. It is in the audit log and the account export. Roiva asks again if how either copy is booked changes: a mapping or a share on either side, the connection linked or unlinked, or a bill booked through another rule or mapping, or typed in. New months booked the same way don't. Ask again puts it back.
The same bill and connection on two initiatives
Say the Anthropic connection books a workspace to one initiative, and an allocation rule books Anthropic's invoice to another. Each initiative counts its copy once and looks right. The invoice holds that workspace's usage too, so the account's total counts it twice.
Before a rule like that is approved, its page says which initiatives the connection would stop booking for and which it would keep booking for, and whoever approves it ticks a box to say they've read that. Accepting a suggestion from your books and Assign on AI Spend write a rule with no approval step, so they say the same and ask for the same tick before they write it. So do switching an active rule's matching and taking an initiative off it on Costs → Vendors, where the change would leave the connection booking beside invoices the rule books. Each one records it in the audit log. The form for linking the connection says so too, when a rule was there first.
Once it has happened, both initiatives' Costs tabs say so, the vendor's page lists it under Counted Twice Across Initiatives, and Finance → AI Spend marks the vendor as May be counted twice. The figure is up to each month's smaller copy, because a report and an invoice can't be matched line by line. To count it once, take the vendor out of the rule or mapping, or unlink the connection from the other initiative.
A bill all for what the vendor's report doesn't carry, such as Claude Team seats, isn't part of this. A rule is how those seats get booked from your books.
What Roiva only suspects
A person's typed cost and a synced bill for the same vendor and the same month may be the same money or may not, and nothing in the data settles it. The same is true of one invoice reaching Roiva through two books systems.
Roiva matches those on vendor name and month and reports them as candidates. It never picks a winner: nothing is authoritative enough to decide between a person's entry and a bill, and quietly deleting one would be the kind of silent correction this product exists to avoid.
A bill booked as one initiative's cost and another's saving
An initiative that cuts a bill, such as AI Spend Optimization routing requests to cheaper models, counts the drop in that bill as its saving. If another initiative, say an AI coding assistant, books the same provider's bill as its cost, then wherever the drop came off the bills it books, its cost already shows it. Portfolio ROI counts that part twice: once as a smaller cost, and again as a saving. With a $24 Anthropic bill booked and an $8 saving, if the saving came off those bills they would have been $32 without it, and the $8 is counted again on top.
Roiva raises this in the Inbox, naming the provider, and on both initiatives: the booking one's Costs tab and the measuring one's Value tab. Resolve opens a drawer with both figures and the answers; when there is only one such overlap, Home's line opens it too:
- A saving of the measuring initiative. Change how the connection is linked to the booking initiative, so it stops booking that bill. Its cost then reads lower than what it pays, so this is only right if it doesn't use the bill.
- Different dollars: keep both. For when the saving came from a part of the bill the other initiative doesn't book, such as another team's workspace. Roiva can't check this, so an Owner or Admin records it with a reason. It is in the audit log and on the Inbox's Done tab. Roiva asks again if how either side is measured or booked changes: a formula, that provider's connection as a cost source, or the booking initiative's books, or an allocation rule. More cost typed by hand doesn't count as a change.
A cost of the booking initiative. The measuring initiative stops counting the part of the bill the other one books. For Anthropic and OpenAI, where the other initiative books named workspaces or projects, Measure the rest does it in one step for someone who can approve the savings. The connection the measuring initiative has as an activity source leaves out the workspaces or projects the other initiative books: where it measured the whole bill, it then measures every one but those, and where it names the ones it reads, it stops naming those.
Its approved savings in the months the other initiative booked them go back for approval, recalculated on the rest of the bill before the approvers are told. Until it is recalculated, a saving shows as Waiting to recalculate and can't be approved. Some months keep their figures, and the drawer names them before you choose: a locked month, a month Roiva has no usage by workspace or project for in the rest of the bill, and a saving Roiva can't recalculate (its formula since archived, or a figure typed in).
Where the other initiative books a share of a whole bill instead, it books every workspace no other initiative claims, so there are none to leave out: claim the workspaces or projects it uses where its cost source is linked, first.
Anywhere else, Count it once does it: each month, the share of the bill the other initiative books is left out of the saving, because its cost already shows it, and the rest still counts. Where Roiva can't tell that share (bills from your books, an allocation rule, or a workspace or tag), all of the saving is left out, which can understate it but never overstate it. Approved months go back for approval the same way, and the saving's page shows the whole saving, the part left out and whose cost holds it.
The other initiative's cost doesn't change. From then on Roiva raises nothing where the two don't meet. A month approved on the whole bill and not sent back still counts what it measured. A bill that reaches Roiva only through your books can't be measured in part. A cloud saving can be measured on a tagged part of the bill, but this check doesn't read tags yet, so after tagging, keep both and say so.
When one initiative both measures a bill's drop and books that bill, there is only one answer: stop booking it there. Booking part of it, such as one workspace, still counts as an overlap.
Roiva can't tell how much of a saving measured on the provider's whole bill came off the part booked elsewhere: all of it, some, or none. So the figure the Inbox shows is the whole saving: the most that can be counted twice, not a measurement of how much is.
Where your account's own answer is
Finance → AI Spend says it for your account, all time, first on the Outside these figures line under its table: how much of the cost your initiatives record may be counted twice; open the line for how many vendors. Review sets its Status filter to May be counted twice, and each vendor's page lists:
- what is counted twice on purpose, by how much, what each copy books and what to change;
- what Roiva suspects is counted more than once, labeled as a guess;
- what was already settled, and which copy counts.
That note is there only when something may be counted twice.
It is all-time rather than windowed, because "is anything counted twice" is a question about everything recorded, and a reporting period that happened to exclude the double count would answer it wrongly.
It is a figure and the lists behind it rather than a tick, on purpose. "Nothing is double counted" is unfalsifiable, and a green check invites the question again instead of settling it. The enumeration is the part a CFO can audit.
What this does not cover
One connection linked to two initiatives, where both map the same bill, the same service or the same deal, books that item in full for each of them. The syncs fan out, so the portfolio counts it twice.
Roiva finds that in the rows themselves and shows it on the connection's Initiatives tab, but it does not prevent it: which initiative a shared bill belongs to is a judgment about your business, not a fact in the data. Splitting it is what shares and mappings are for.
Related
- Linking connections to initiatives — what each connection books, and the vendor-on-both-sides rule in detail
- Allocation rules and accounting periods — approved splits, journals, and what a locked period refuses
- Vendors, shares and recurring costs — setting a share, and costs no integration reports