Linking connections to initiatives
Why a connection books nothing until it's linked, the role each platform is linked in, mappings and allocation rules.
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
Connecting a platform lets Roiva read your account. Linking that connection to an initiative tells Roiva which initiative its costs or value count toward. A connection that isn't linked keeps syncing, but nothing it brings in reaches any initiative's ROI.
Integrations → Needs Action lists every live connection with something still to do before it counts: a bill no initiative books, data no initiative uses, or a rule it needs. The ones with the most synced spend come first. Each one's Inbox row opens it, and so does its No initiative on Finance → AI Spend, which keeps the record of what no initiative books, including connections set aside, or whose bill a formula measures, that this list doesn't ask about.
The figure at the top is what those connections bill that no initiative books, counted as AI Spend counts it. It says AI spend when every dollar of it is a provider's AI: a cloud's AI services, say, and not its whole bill. A finance system's or card's total counts whole, so then it says synced spend.
What's missing
Each row says what isn't happening yet: it books no costs to an initiative, it books no value, or no initiative uses its data. The line under it says what linking it does. That depends on the role it's linked in, which the row picks for you:
Cost source — the provider's bill is booked as the initiative's cost, so give it only the part of the bill the initiative runs on. AWS, Azure, Google Cloud, Snowflake, Databricks, OpenAI, Anthropic, Claude Enterprise and American Express are cost sources.
A card platform books the vendors you pick, each at the share you set. QuickBooks, Xero and NetSuite book their bills from Finance → AI Spend instead (see below). A cloud account books the services or tags you pick, Google Cloud the budget you name, Snowflake the usage types you pick, and Databricks the products or custom tag you pick.
OpenAI and Anthropic book their API usage, from the vendor's own cost report, unless they're linked for only some projects or workspaces, or at a share. Claude and ChatGPT seat plans are billed apart and aren't in that report, so they come from your books (see How costs reach an initiative).
Claude Enterprise books what usage cost, from Anthropic's beta cost report, by the user groups or Projects an initiative claims, or at a share. Seat fees aren't in that report, and on a seat-based plan it holds only usage credits, so seats still come from your books.
GitHub books only the AI line items on its bill — Copilot seats and AI credits — unless you name other products when you link it, such as Actions, Codespaces or Storage.
Any connection whose bill pays for the initiative needs linking as a cost source, even one that usually plays another role, such as GitHub. A connection that reports usage but no spend, such as Microsoft 365 Copilot or ChatGPT Enterprise, can't be a cost source: its cost comes from the invoice in your finance system, or a recurring cost on the initiative.
Value source — what the connection syncs becomes the initiative's value: tickets deflected in Zendesk, Freshdesk or Intercom, or Salesforce conversations an AI agent handled without a person (see How deflection value is booked), deals won in HubSpot, Salesforce or Pipedrive, payments in Stripe, invoices in QuickBooks, Xero or NetSuite. A won deal, a payment or an invoice is revenue, so it books at your contribution margin, not its full amount (see Revenue books at your margin below). Jira, GitHub, n8n, Make and Zapier can be linked as a value source too, for an initiative with no formula reading those figures: it adds a freed-capacity formula that turns resolved issues, accepted Copilot suggestions or successful automation runs into value. An initiative whose formula already measures that work, such as one made from the AI Coding Assistant Rollout template, gets nothing more from it.
Activity source — a platform that only feeds usage data to the initiative's formulas and books no dollars itself, such as Microsoft 365 Copilot, ChatGPT Enterprise, Gemini in Google Workspace, Gemini Code Assist, Glean, Google Workspace or Looker. It's linked as an activity source, the only role it can take.
OpenAI, Anthropic, Claude Enterprise, Gemini and GitHub figures reach an initiative's metrics whatever role the connection is linked in, so linking one as a cost source is enough to feed them. Link one as an activity source alone when the cost is booked elsewhere: another initiative or your books hold it, or this initiative measures savings on the bill. Link Anthropic or OpenAI as an activity source as well only to read cost per unit from certain workspaces or projects.
A data warehouse can hold both roles at once. Snowflake and Databricks can be a cost source for one initiative and an activity source for another, or both for the same one. Linking Snowflake, Databricks, BigQuery or SQL Server as an activity source is also what lets you write a metric query for that initiative alone, whose readings are the initiative's own. See Metrics from your own data warehouse.
The form for linking offers only the roles a connection can book. A platform that can only be an activity source says so in a line, with where its cost comes from. Any other role a platform can't book is left out, so HubSpot offers no Cost source and Anthropic no Value source. A finance system's Cost source is shown but can't be chosen, with a tip saying its bills book from AI Spend.
A help desk, CRM or payments link in the value role reads the connection's metrics too, so the choice is whether its records book as dollars. Link it as an activity source when a formula of your own prices those figures instead.
The Synced column
For a connection with a bill, Synced shows what the provider billed over the reporting period, none of which is attributed to an initiative yet. Click it to see the months or bills behind it.
A value or activity connection has no dollar figure until it's linked, because its value is what an initiative's formula makes of the data. For those, Synced counts the records or metric entries the connection has brought in, so you can see it has data waiting.
Linking in the row, in the full form, or by customer
Most connections link in their row: choose the initiative and click Link. Linking syncs the connection, so it starts booking within a few minutes. Changing the role it's linked in, or its mappings, tag or share, syncs it the same way.
Link on an OpenAI, Anthropic, Claude Enterprise, Gemini or GitHub row on Needs Action first asks how much of the bill is the initiative's, and so does linking an initiative anywhere else while no initiative takes a share of the bill: Add on the connection's Initiatives tab, or picking the connection under an initiative's Connections → Link a Connection. The question offers All of it, Only some projects, workspaces or user groups (OpenAI, Anthropic and Claude Enterprise), each booked in full, or A share of every charge. An API key, a chat Project, a product or a percentage of a user group is claimed on the full form, which Role and options opens. An AI coding assistant initiative takes only Only some on Anthropic: the workspaces Claude Code bills to, since the rest of the bill is other API usage.
Whatever the initiative doesn't take stays unattributed.
If you aren't sure, open See what's on the bill first. Claim the initiative's own projects or workspaces if it has them; otherwise estimate a share from who uses it, such as seats or requests by team. You can change it later on the connection's Initiatives tab, and a changed share applies from the first of that month.
Where other initiatives only claim projects or workspaces, those stay theirs and the question is about the rest: All the rest instead of All of it. The full form, which Role and options opens, asks the same, one way or another: All of it, Only some projects, workspaces or user groups, or A share. Only the one you choose has fields to fill in, and GitHub and Gemini, which have neither projects nor workspaces, ask only for the share. So does editing a link while no other initiative takes a share, when the edit makes it a cost source or unticks every project or workspace it claims.
Once an initiative takes a share of the bill, Add links another in one step with an even share, and you set every initiative's share together on the Initiatives tab.
If someone else would know, choose Not sure yet: ask someone, pick a teammate, and add a note if it helps. Any member of the account can ask, and any other member can be asked. Asking links nothing and books nothing: the connection stays on Needs Action, with who you asked and when under its row, and its bill still counts as unbooked. The teammate gets an Inbox row that opens the same question for the same initiative. Their answer makes the link, and the initiative's activity and the audit log record them as the one who set the share, and you as the one who asked. If anyone links the connection as a cost source before they answer, or sets it aside, the question closes. Asking again, of anyone, replaces the question already open, which is how to re-ask a teammate who has left.
The rest need to know which part of the account belongs to the initiative, so Link to an initiative opens the full form:
- AWS and Azure — pick the services (Bedrock or SageMaker, say), or a tag: a cost-allocation tag on AWS, a resource tag on Azure. The cloud bill covers everything on the account, not just your AI work. Tagging takes a little setup in the cloud first: see Counting one initiative's AWS costs and Counting one initiative's Azure costs. A service several initiatives use, such as Amazon Quick, can be split by share (see Sharing a cloud service below).
- Google Cloud — name the Cloud Billing budget that covers the initiative. Create one budget per initiative in the Google Cloud console, limited to the projects, services or label it uses, and the connection matches it by name. Only its scope is used: its amount isn't the initiative's approved budget (see Budgets and budget vs. actual).
- Snowflake — pick the usage types: Compute, Storage, Cortex and so on. Snowflake has no tag to split a type by initiative, so a mapping books the account's whole spend on that type. Map a type only when all of it is the initiative's.
- Databricks — pick the products, or a custom tag on its clusters, jobs and warehouses.
Switching an AWS, Azure or Databricks link between its services and its tag books its spend again the new way and takes out what the old way booked, in past months as well as this one. Linking the connection to the initiative again does the same to what it booked for the initiative the other way before. A month or service the new way doesn't cover then books nothing for the initiative: a tag's spend is fetched for this month and the 12 before it at most, and only from when the tag was on your resources, and a service no mapping names isn't booked. A locked month keeps what it booked, and so does a month still measured under the tag the initiative had before, until its new tag is measured. The audit log records what Roiva takes out.
HubSpot, Salesforce and Pipedrive — pick which won deals count, by a deal mapping or a deal property, and how each is recognized.
Where a connection has more than one pipeline, Deal Pipelines on the connection page also says which count as sales, and in Salesforce Opportunity Record Types does the same for record types: deals in the others reach no reading and book nothing more, for any initiative.
A one-time deal books on its close date. A recurring deal books as it's earned: ACV ÷ 12, or the MRR, each month for the 12 months from its close date, the close month by its days. Each month books once it has ended, never ahead. A deal that stops being won books no further months.
Each deal books in its own currency: HubSpot's deal currency, else the portal's company currency; Salesforce's opportunity currency in a multi-currency org, else the org's; Pipedrive's deal currency. Roiva counts it in dollars at the European Central Bank's rate.
A recurring deal an earlier version of Roiva booked as one year at close keeps that entry once it's approved or its month is locked, and stays out of the months; send the entry back, and reopen a locked month, and the next sync replaces it with its months. An approved entry isn't rewritten when its deals change; the Inbox lists it under Changed in the CRM since approval for someone to send back (see Approving value and initiatives).
Salesforce — first choose what the connection books for the initiative: won deals, or the Messaging conversations an AI agent handled without a person. For conversations, pick the Agentforce agent or Einstein Bot whose conversations count. See How deflection value is booked.
QuickBooks, Xero and NetSuite bills are booked by allocation rules alone. An Owner or Admin assigns each vendor to the initiatives it serves, with their shares, from Finance → AI Spend, and Roiva writes the rule. On an initiative's Costs → Vendors, anyone can find the vendor in your books. An Owner, Admin or finance reviewer routes its future bills there at once. A Member's routing is saved as a draft rule, which books once one of them approves it from their Inbox.
Linking one of these connections books no bills. Link one as a value source to book its invoices from the customers you map. That fits when all of a customer's billing is due to the initiative, since each mapping books every invoice from that customer.
Formulas read the Profit & Loss, invoice and bill figures of the account's main books whether or not they're linked. Link one as an activity source for two cases: reading another connection's figures for one initiative, with Read Metrics from This Connection under More Options, or computing a baseline from a connection's readings. The connection's Initiatives tab lists the initiatives its rules book to as well, marked By rule.
Until a rule covers the platform, its row on Needs Action says No allocation rule covers it.
An American Express connection starts with an allocation rule rather than linking: see Allocation rules below. The vendor mappings on its Initiatives tab book only while no rule covers its platform.
Stripe shows Owners and Admins Map customers instead: its Customers tab lists the customers it has synced, and you choose the initiative each one's payments count toward. A Member gets Link to an initiative and types each customer's name or ID. Stripe books nothing for customers that aren't mapped.
A connection that's linked but maps nothing shows Add mappings. It looks linked, but it books $0 until something is mapped.
Revenue books at your margin
A won deal, an invoice or a Stripe payment is revenue, and revenue isn't what your company keeps from it. So each one books its amount at your contribution margin: the part of each dollar left after the costs that grow with a sale, such as cost of goods or delivery, commissions and payment fees. A $50,000 deal at a 40% margin books $20,000.
Roiva ships no default for the margin, because no published figure is your company's. Until it's set, a CRM, finance system or Stripe linked as a value source books nothing, and saving the link warns you. The margin also shows as missing on the initiative and under Method → Assumptions. Set it once for the account, and change it there. An initiative whose added revenue keeps more or less of each dollar than your average sale can set its own margin on its Health tab, and the connections linked to it book at that instead. Each entry records the margin it was booked at. The same figure is what Roiva's revenue formulas read (see How Roiva calculates value).
A vendor that is both a cost source and a mapping
An initiative can have a vendor's own connection as a cost source and, on its books, a vendor mapping for the same vendor. The connection books what the initiative runs on — GitHub's AI line items, the workspaces or projects a model provider claims for it, the usage types Snowflake maps for it — while the invoice in your books is the vendor's whole bill. Booking both counts the same spend twice.
For GitHub, Anthropic, OpenAI, Snowflake and Databricks, the invoice is left to the vendor's connection in any month it books, and a row booked there earlier is given up. Where that reaches a month before this one, only an owner or admin can link it (see Who can link below). Two things keep the invoice instead, and the connection books nothing that month: an allocation rule for the vendor, which is an approved split with journals behind it, and a locked period, which no sync may change.
Months before the connection has data still book from the mapping, at the share you set, so set the share to the part of the bill the initiative runs on. A bill line or card charge for a product the vendor's report doesn't carry, such as Claude or ChatGPT seats or a Snowflake Marketplace purchase, still books from your books beside the connection.
AWS, Azure and Google Cloud work differently. Your books spell those vendors the same way as their other products — an Azure invoice comes from Microsoft, beside your Microsoft 365 bill — so leaving an invoice out could drop a cost the connection never booked. Both are booked, the mapping form warns you, and you set the share for the part the connection doesn't already count.
Claude Enterprise also keeps both, for a different reason. Its invoice comes from Anthropic, and a line on it 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 are booked, and Counted Twice warns where they're on one initiative. If the invoice holds usage the connection already books, lower its share to the part the connection doesn't count.
Allocation rules
Allocation rules can decide where a platform's bills go instead of linking, on every plan, and for QuickBooks, Xero and NetSuite they're the only way. A connection whose platform has an active rule leaves Needs Action, with nothing to link, and its card on Connections says Booked by rules. A finance connection with no rule for its platform yet says No allocation rule covers it, and its button is New allocation rule.
Connections that don't need linking
Some connections don't need linking, so Needs Action leaves them out. Each one's card on Integrations → Connections says why, and All statuses above the cards narrows the page to one kind:
Feeds formulas — a formula already reads what the connection syncs, and the connection has no bill, none of its bill is AI, or its bill is what the formula reads, so it's doing its job unlinked. A cloud bill an initiative measures itself by is the usual case: the bill is the figure being measured, not a cost of the initiative, and linking it as a cost source would book the very spend you're tracking. Roiva works this out on its own, and the chip names the formulas reading it. Link it from its Initiatives tab if you do want it booking costs as well.
A formula that reads only a connection's usage, such as Claude Code acceptances or Copilot suggestions, doesn't take its bill off Needs Action: the formula values the usage, and the bill is what that usage cost. Nor does one that reads the revenue or invoices of QuickBooks or Xero, since those aren't its bills.
Booked by rules — see above.
Not used — linking it would book no dollars and feed no formula, so there's nothing to do. The chip says why: no formula can read the platform yet, or none in your account reads what it syncs.
Set aside — company-wide overhead, or a tool on trial, that an owner or admin has set aside with Not for an Initiative in its row's menu on Needs Action. Its spend still counts as unattributed in the Board Brief, unless allocation rules book its platform. An owner or admin can click the chip to see who set it aside and why, and Put back on the list to undo it.
One connection, several initiatives
The … menu at the end of each row has Link to Several Initiatives, which opens the connection's Initiatives tab, where you can link it to more than one initiative, and Not for an Initiative, which sets it aside.
A model provider like OpenAI or Anthropic, or GitHub, divides its bill by share, or by the projects or workspaces each initiative claims. Claude Enterprise divides its usage cost by share, or by the user groups or chat Projects each initiative claims. Splitting Anthropic and Claude cost, below, sets those two side by side.
OpenAI also lists each project's API keys under it. Claiming a project books its keys with it, so another initiative can't claim them. An initiative can instead claim a key alone: it books exactly what that key was billed, and the rest of the project stays open for other initiatives.
GitHub's share is of its AI line items, such as Copilot seats and AI credits, not the whole GitHub bill: Actions minutes, Packages and storage stay out. A cloud or finance connection divides it by what each initiative maps.
The first share on a bill applies to every charge, since there is no earlier split to keep. After that, a share applies from the first of the month you set it in. Charges booked before then keep the split they were booked at, and an initiative added beside others that share the bill by share takes its share from then on. An owner or admin can choose to re-split every charge instead, which applies the shares to the charges already booked too.
Claiming or giving up a project, workspace, API key, user group or chat Project never changes a charge in a locked month, which stays as booked. Otherwise a project, workspace, user group or chat Project moves its charges whenever they were made, but an API key's part reaches back only as far as its report does: about 3 months for OpenAI, and for Anthropic a year before its first sync, never earlier than January 2026. Earlier charges stay with the project or workspace.
Splitting Anthropic and Claude cost
Anthropic bills API use and claude.ai use separately, and Roiva reads them through two connections. Connect both if you have both.
| Anthropic | Claude Enterprise | |
|---|---|---|
| What it reads | API spend in your Claude Console organization | Usage in your claude.ai Enterprise organization |
| Key it needs | An Admin API key | An Analytics API key |
| What an initiative can claim | Workspaces and API keys | User groups, or chat Projects and products, not both on one connection |
| Where the figure comes from | Anthropic's cost reports | Anthropic's cost report. Chat Projects and chat outside any Project are estimates |
| Sharing one claim | Not possible: a workspace or key books in full to one initiative | Each claim can take a percentage, and what's left stays unattributed |
| What no initiative claims | Split between the initiatives that take a share of the bill, or unattributed if none does | Split between the initiatives that take a share of the cost, or unattributed if none does |
| The invoice in your books | The usage on it is left to the connection in any month it books, unless an allocation rule or a locked period keeps it. Seats still book from your books | Stays booked, and Counted Twice warns where both are on one initiative |
Workspaces and API keys. Claiming a workspace books all of its cost and its keys with it, so another initiative can't then claim one of those keys until the workspace is given up. Claiming an API key books only that key's part, and the rest of the workspace stays open: an initiative can still claim the workspace, which books all of it less that key. A key's part is what Anthropic's cost report by API key says it cost, as long as that report is within 1% of the workspace's bill for the day, and it never comes to more than the charge. A day further apart than that, or that Anthropic hasn't reported by key yet, stays with the workspace until a sync can read it, and so does usage in the Console, which no key makes. If no initiative holds the workspace or a share, that part books to no initiative until then.
User groups. These figures come straight from Anthropic's report. Anthropic counts someone in two groups in both, so Roiva counts their cost once, at the average where one initiative holds their groups at different percentages. If two initiatives claim different groups that person is in, that cost books to neither. The connection's next sync says so, until a sync after one claim changes.
Chat Projects and products. Anthropic doesn't report cost by Project, so a Project's cost is an estimate, flagged as one: each person's chat cost, split by their share of chat and Cowork messages that month. A Project of large files or long chats reads low, and one of many short messages high. Chat outside any Project is worked out the same way, and each other product, such as Claude Code, is what Anthropic reports. User groups and Projects split the same dollars, so ticking the first Project or product moves every initiative on the connection to them. A month with no Project or product figure yet keeps what it booked.
Seats and other plans. Seat fees aren't in Anthropic's cost report, and on a seat-based Enterprise plan the report holds usage credits only, so seats come from your books and a Project within its members' seat allowance shows nothing. Claude Team, Pro and Max have no API Roiva can read cost from. Book them from the invoice or your books, and split them with an allocation rule.
Sharing a cloud service
A cloud mapping books all of each service it matches unless you give it a share: the percentage beside the mapping on the form for linking. Each mapping has its own, so one initiative can book all of Bedrock and 15% of Amazon Quick. Roiva won't save shares of one service across initiatives that add up to more than 100%, and what they leave books to no initiative. Initiatives that each mapped a service in full before shares existed keep booking it in full until one of them lowers its share, and the connection's Initiatives tab warns while a service is booked for more than one initiative beyond what it cost. Finance → AI Spend counts the service as AI spend whole, with the shares' part booked and the rest unbooked.
An Amazon Quick mapping can take its share from Quick's seats instead of a typed one, where the AWS connection counts them (the AWS setup guide gives the permissions it needs). Pick the Quick groups the initiative covers beside the mapping: each month's share is those groups' seats at Quick's list prices, over every seat and Quick's account fee, or over the line billed if that's more. A person in groups of two initiatives is split evenly between them, and a group can belong to one initiative's mapping only. The seats sync sets this month's share and, while last month is still open, last month's. Seats in no group, the account fee and the rest of the line book to no initiative.
A share applies from the first of this month, unless an owner or admin dates it earlier, which re-books the months between at the next sync. Months in a locked period stay as booked. A new mapping books its share of every month the connection has billed, unless you date it, or other initiatives book the service already: then it books from the share's month on, so their past months aren't booked twice. To make room, lower the other initiatives' shares first, each on its own form: saving one initiative's mappings never changes another's costs.
Who can link
Any member of the account can link a connection to an initiative, change its mappings and shares, and unlink it, just as they can edit the initiative. Connecting a platform, syncing, reconnecting, disconnecting and setting a connection aside as Not for an initiative are for owners and admins.
Moving costs a sync already booked before this month is for owners and admins too, and the audit log records who did it. A member's change that would do it isn't saved, and the form says why. That covers:
- re-splitting a model provider's or GitHub's charges from before this month, or claiming or giving up a project, workspace, API key, user group or chat Project those charges were booked in, or moving a Claude Enterprise connection between user groups and Projects;
- changing the cost type of a cloud connection's service mapping, or its tag or the tag's cost type, or switching it between its services and its tag, or linking it again to book the other way from before, once that way has booked spend from before this month, or dating a mapping's share before this month;
- linking GitHub, Anthropic, OpenAI, Snowflake or Databricks as a cost source, or claiming its projects or workspaces, where your books hold that vendor's bills for the initiative from before this month, since the connection takes them over;
- a finance connection's vendor mapping dated before this month, or a changed cost type on bills it booked before then (see Vendors, shares and recurring costs).
The form for linking lists the vendors, customers and deals a connection has synced but no mapping claims yet, and only owners and admins see those lists, because they come from the synced records. A member types the name into a mapping instead.
Next
- Connecting your first integration — connecting a platform in the first place
- Adding costs and value entries — the entries a linked connection books
- Allocation rules and accounting periods — splitting bills with rules, and locking a month
- Managing a connection — sources, syncing, disconnecting and deleting