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

Allocation rules and accounting periods

Split a vendor's bills across initiatives with allocation rules, and lock, reopen and reconcile a month, with or without a finance connection.

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 9, 2026

Allocation rules decide which initiatives a finance system's bills book to, and in what shares. Accounting periods let your finance team sign off a month so its costs and approved value can't change afterwards. Both come with every plan, Free included. Allocations appears under Finance in the sidebar once your account has an active QuickBooks, Xero, NetSuite or American Express connection. Without one, Accounting Periods appears there instead, so an account whose figures are typed in or imported closes its months too. QuickBooks, Xero and NetSuite bills book by rules alone. On American Express, vendor mappings on each connection book its charges until you write a rule: see Vendors, shares and recurring costs.

What an allocation rule does

A rule covers one platform (QuickBooks, Xero, NetSuite or American Express) and, optionally, one vendor. Every bill it matches is split among the initiatives in its splits, and each initiative's part is booked as a cost entry. The rule covers everything that platform's sync brings in, bills and card or bank transactions alike.

On QuickBooks, Xero and NetSuite, a bill no rule matches books to no initiative. A card platform's rules take over from its vendor mappings: once your account has an active rule for it, its charges go through rules only, and every vendor mapping on its connections stops booking. A connection whose platform has an active rule says Booked by rules on its Integrations → Connections card, and on Integrations → Needs Action a finance connection with no rule yet offers New allocation rule.

So write a rule for every vendor you want booked. A bill that no rule matches shows under Unmapped Bills in that month's reconciliation. If two rules match the same bill, the older rule books it.

A vendor with its own connection

Anthropic, OpenAI, GitHub, Snowflake and Databricks can book their own spend through a connection linked as a cost source, so you usually don't need a rule for their bills. A rule that takes them changes what those connections book:

  • On the initiatives the rule books to, the connection stops booking in the months a bill holds usage, and gives up what it booked there. The invoice figure replaces it, and any split by workspace or project goes with it.
  • On every other initiative, the connection keeps booking. That spend is also on the invoice the rule books, so the account counts it twice.

The rule's page says which of these applies, and approving it takes a tick to say you've read that. Accepting a suggestion from your books and Assign on AI Spend ask the same before they write a rule, since neither has an approval step. So do switching an active rule's matching and taking an initiative off it on Costs → Vendors, where the change would leave a vendor's connection booking beside invoices the rule books. A rule for what the vendor's report doesn't carry, such as Claude Team seats, doesn't conflict: it's how those seats get booked from your books. See How costs reach an initiative.

When shares from other spend can misbook

The rule form warns about two setups on Shares from other spend, when it can tell from the vendor's name and the fields you've filled in. The rule's page says exactly, from the bills and connections your account holds, and approving it takes the tick. Neither is refused, and you can change what the rule shares by to avoid both.

  • A vendor's connection books what the rule shares by. The rule takes a vendor's usage bills, names an initiative linked to that vendor's connection, and shares by a cost type that connection books. Once the rule books a bill to that initiative, the connection gives up what it booked in that bill's month, and the rule's own bookings don't count toward its shares. So a later bill can read the initiative as having none of that spend. The rule's other initiatives can then take all of that bill, and the connection can book that month again on top, so any of that spend it also reports counts twice. If the rule names no other initiative, that bill can stay unbooked. Share by a cost type the connection doesn't book, or use fixed shares.
  • Two rules share by what the other books. Each rule's shares wait on the other's bookings on their initiatives. If neither has booked within its lookback and their initiatives have no other spend of those cost types, both rules' bills stay unbooked. Change what one of them shares by, or use fixed shares on one.

Assign on AI Spend writes its rule with no approval step, so it asks too: once you've chosen what to share by, it says which setup that makes and takes a tick before it writes the rule. You can change what you chose there instead. Accepting a suggestion from your books, changes on Costs → Vendors and merging initiatives can make either setup without asking, and so can linking a connection after the rule is active, though the form and drawer for linking it mention this. From then on the rule's page says so.

Creating a rule

Open Finance → Allocations → Rules and choose New Rule:

  • Effective from — the first bill date the rule covers. A new rule starts on the earliest bill on your books and card connections that nothing has booked yet, so it also books what they've already synced. It never starts in or before a locked month. Clear it to start the rule the day it's approved.
  • Source Filter — the Platform, and the Vendor name match: Exact name ignores case, punctuation and endings like Inc or LLC, and Contains matches any vendor name with it in. Leave the vendor empty to match every vendor on the platform.
  • Split Method — Fixed shares gives each initiative its percentage of every bill. Shares from other spend works each bill's percentages out from other spending, using the two fields under Splits.
  • Splits — one row per initiative, with its Share on fixed shares. Add initiative adds a row. Fixed shares can add up to less than 100%: what they leave is unassigned, booked to no initiative, and stays on the bill's account in your books.
  • Share by spend on and Lookback (days) — on Shares from other spend, each bill is shared by what each initiative spent on this cost type over the days before the bill. What the rule booked itself doesn't count, except on a credit note, which refunds it. An initiative with no such spend takes no part of the bill, and if none of them has any, the bill stays unbooked. A bill keeps these shares once it books: if its amount changes, the new amount follows them. See When shares from other spend can misbook.
  • Book As — the Cost type and Category the bills count as, which needn't match Share by spend on. A monitoring bill can book as Software and still be shared by Infrastructure spend. Roiva picks the cost type for AI vendors it knows, and the category from the cost type; you can change either. A rule saved with different cost types for its initiatives shows these on each row instead.
  • More Options — Effective to, the last bill date the rule covers, which you can leave empty to keep the rule open. And the rule's Name: left empty, the rule is named after its vendor and initiatives and renamed when they change. Type your own to keep it.

Create rule saves it as a draft, which books nothing. Anyone in the account can view and draft rules.

Approving and changing rules

Click a rule in the list to open it in a panel beside the list, with Approve, Edit and Archive. Approving or archiving a rule takes an Owner, an Admin, or a finance reviewer.

  • Approving a new rule makes it active from its start date, and starts a sync of its platform's connections, which books the bills dated from then that nothing has booked yet. Bills something already booked stay where they are. With no start date, the rule starts the day it's approved and books no earlier bills.
  • Editing an active rule saves your change as a draft revision (Save as draft revision), and the rule keeps booking as it was. Once the revision is approved, it books bills dated from that day on, and the old version keeps the bills dated before. A rule can only have one revision waiting at a time.
  • Archiving stops the rule booking new bills. Bills it already booked stay booked. An archived rule, including one replaced by an approved revision, drops out of the list; Show archived on the Rules tab brings it back, and Export still includes it. When a card platform has no active rule left, its vendor mappings book again. Archive is also on an active rule's Edit page, for when you opened Edit meaning to end the rule.

Bills already booked never move on their own when a rule changes. To re-split a vendor's past bills at new shares, use Set share on the initiative's Costs → Vendors tab and date the change back. A bill that carries the share of an initiative since taken off the rule, as dismissing one takes it off, stays as booked at its split. A rule that has stopped booking can't take a share from a later date.

Rules made for you

When an Owner, Admin or finance reviewer accepts vendors under Suggested from Your Books, which an initiative's Costs tab opens, Roiva creates a rule for each vendor, routing its bills dated from that day to the initiative. The rule is active straight away, with no separate approval. Anyone else who accepts adds the past bills only. A rule made this way says so under Origin on its page. When the vendor already has a rule, the initiative joins it instead.

On an initiative's Costs → Vendors tab, an Owner, Admin or finance reviewer can also change a rule's share or matching for that initiative, or take the initiative off it. Those changes take effect straight away, from bills dated that day.

When an initiative is dismissed

Dismissing an initiative takes it off every draft or active rule that splits to it, from bills dated that day, and the audit log records each change. A rule it was alone on is archived. A rule it shared is replaced by one without it. With fixed shares, its share books to no initiative, so the others' costs don't change. A rule that shares by cost splits each bill among the rest. A vendor's own connection on the initiative keeps booking, so where a rule it leaves goes on booking that vendor's invoices for the others, any of that spend the connection also reports counts twice, and the dismiss dialog says so.

Bills it already booked stay booked. A bill dated before that day that arrives later still books under the version of the rule it's dated in, unless that rule was archived: an archived rule books nothing more, so the bill shows under Unmapped Bills. A rule whose end date has passed is left as it is, and one that hasn't started yet is replaced from its own start date.

A draft revision of a rule it replaces is set aside, because it could no longer be approved: draft it again from the new rule. If the platform has no other active rule left, other initiatives' vendor mappings on it book its bills again, as when you archive its last rule. The dialog lists each of these.

If a rule can't be saved without the initiative, for example because one of its other rows uses a cost type that's no longer offered, the dismissal is refused and names the rule to correct. A dismissed initiative can't be added to a rule, and a draft rule naming one can't be approved. Pausing or completing an initiative leaves its rules as they are.

Accounting periods

Finance → Allocations → Accounting Periods lists each month an allocation rule has booked bills in, and each month someone has opened to close, with its status: Open, In review, Locked or Reopened. Open a month to see its allocations: each bill, the rule that split it and each initiative's share. In an account without a finance connection the page is Finance → Accounting Periods.

Below the list, Months to close names the last twelve finished months that have no period yet. Choosing one opens it, ready to lock.

Preparing, locking and reopening take an Owner, an Admin, or a finance reviewer:

  • Prepare for lock appears on an Open or Reopened month once journal posting is set up (see GL Mapping below). It builds a proposed journal entry for each bill, which reclasses the bill's amount to each initiative in your books, and moves the month to In review.
  • Lock and post to your books, on a month in review, posts those journal entries and locks the month. The button names the books the entries post to: QuickBooks, Xero or NetSuite. Lock period locks a month without posting anything. If a post fails, the month isn't locked and stays in review, and the journal entry shows why it failed. Entries that posted before it stay posted, because your books kept them. Fix the problem and lock again: it posts the rest, starting with the one that failed.
  • A month in review still books bills as they sync. A bill booked into it after it was prepared has no journal entry, and one whose amount, split or account in your books changed, or whose initiative's dimension value changed, no longer matches its entry. The month won't lock while it holds either: the month's page lists those bills, and so does the message when you try to lock.

    Prepare again rebuilds the month's journal entries from its bills as they stand: it adds entries for new bills, rebuilds changed ones, and drops entries for bills that were re-split or moved to another month. Then lock it.

    While a month is locking or reopening, including while its entries or reversals post, synced bills and figures, recorded costs, approvals and changes to the GL mapping across your account wait until it's done. A change you save waits up to ten seconds; if the month is still posting then, Roiva stops and asks you to check what was saved and try again in a minute. A sync waits up to ten minutes, and a bill or figure still waiting then is written on a later sync. An entry your books already accepted, from a lock that stopped partway, stays as posted, and Roiva keeps its bill as booked.

  • A month that holds amounts in another currency waits for the European Central Bank's rates for that month before it locks. Until the last of them is published, a cost in another currency counts at the latest rate, and approved value in another currency has no dollar figure yet. Locked then, both would stay that way. The month's page says so, and so does the message when you try to lock. The rates are usually in within two working days of the month's end. An amount in a currency the ECB doesn't publish never converts, so it doesn't hold the lock. A tracker import that closes such a month leaves it open, with a note.

  • If your books don't answer a post, for example because it timed out or a server between Roiva and your books failed, they may have kept the entry anyway. The month's page lists it as Sent, no answer. Roiva won't rebuild, re-key or drop it, and keeps its bill as booked, so the bill can't go into your books twice.

    Lock the month again to send it again under the same key: Xero and QuickBooks answer with the entry they kept, if they kept one. NetSuite refuses an entry it already has, and the page then shows why it was refused.

    Or check your books and use the buttons beside the bill, such as It's in Xero or It isn't in Xero, to record what you found. An entry you mark as missing is sent again, under a new key, the next time the month locks. A reversal that got no answer while reopening works the same way: choose Approve reopen again, or record whether your books have it.

  • Request reopen needs a Reason to reopen. The month stays locked until someone else who can lock months (an Owner, an Admin or a finance reviewer) chooses Approve reopen on it, or Decline. They're notified, the request waits in their Inbox, and once it has waited longer than the Approval SLA (days) their Inbox shows it as overdue, as it does approvals. You can Withdraw request. If nobody else can lock months, the button is Reopen and the month reopens at once, and the audit log says nobody else could approve it.

    Reopening posts a reversing entry for each journal the last lock posted, unlocks the month and records the reason, who asked and who approved. If a reversal fails, the month stays locked, and the request stays for Approve reopen to post the reversals that are left; it can't be declined or withdrawn once a reversal has posted. To post corrected journals, prepare the month and lock it again.

Card charges from a card platform, such as American Express statements, get no journal entry, because Roiva doesn't know which account in your books holds them. They show a No journal badge. Tag them to their initiatives in your books.

What locking prevents

Locking freezes every cost entry in your account dated in that month, whether a rule booked it or someone recorded it by hand, and every approved value entry dated in it:

  • Nobody can change or delete those cost entries until the month is reopened.
  • Nothing new is recorded in the month. That covers a bill that arrives late or that a vendor mapping or rule matches after the close, past costs you add from your books, a CSV import and a cost recorded by hand. Syncs leave those bills unbooked. Add selected costs says how many past bills it left out, an import fails the row and says why, and the cost form won't save a date in a locked month.
  • Nobody can edit, send back or delete an approved value entry whose period starts in that month, and no entry dated in it can be approved. An entry with no period belongs to the month it was approved in.
  • A formula still calculates the month's entries, but they wait for a person, and approving them waits for the month to be reopened.
  • A sync doesn't change or remove a figure it already recorded for the month, such as a ticket count or a month's cloud spend, so the readings its entries were calculated from stay as they were. A sync can still record the month's first figure for a metric, from a connection added after the close or a metric moved to a warehouse query.
  • If a reading an approved entry in the month was calculated from changes, or a CRM deal it was booked from, the entry's page and the Inbox say so, but it can be sent back only once the month is reopened.
  • A formula's Value type can't change while any of its entries are approved as another type (see How value is calculated), and the month's approved entries can't be sent back until it's reopened, so they keep the type they were reported as.
  • A recurring cost skips the locked month and says so.
  • Re-splitting a vendor's past bills leaves that month's bills as booked.
  • An allocation rule books no new bills in that month, even one whose start date reaches back past it.
  • Reopening the month starts a sync of every connection. It books the bills the lock held back, and brings the month's synced figures up to date if the month is within the stretch each connection reads again on every sync. That differs by platform: twelve months on most, and as few as three where the provider reports a shorter window. An older month keeps the figures it had when it locked. Past costs from your books are offered again on the initiative's suggestions panel.

Reconciliation and PBC packets

Reconciliation on a month's page ties it out, one currency at a time: the source bills total, what's unassigned, what's allocated, and posted journal entries. It lists Variances, allocations whose lines don't add up to what their rule assigned, and Unmapped Bills.

Generate PBC packet on the reconciliation page builds a ZIP for your auditors, with a cover sheet and CSVs of the month's summary, rules, allocations, source bills, journal entries and audit log. You get a notification when it's ready, and it's under Recent PBC Packets on the month's page to Download. Generating one takes an Owner, Admin or finance reviewer. A packet stays, as it was generated, when the person who generated it deletes their Roiva user.

Finance settings

An Owner or Admin finds these under Finance in Organization Settings, or by typing their name into Search… at the top of the page:

  • Finance Reviewers — lets people approve allocation rules, lock and reopen periods, and generate PBC packets without being an Admin. Owners and Admins can always do these, and the page lists them by role. Choose someone and Add reviewer.
  • GL Mapping — how journal entries post to Xero, NetSuite or QuickBooks: the dimension that tags each initiative (a Xero tracking category, or a NetSuite department, class or location), a default account code, and each initiative's dimension value. Turn on Enable posting to the GL and Save GL mapping. Leave posting off while you check the proposed journal entries. A month's page links here with Set up the GL mapping until it's done.
  • Auditor Links — a time-limited, read-only link for your external auditor, who needs no Roiva account. They see every locked month and can download PBC packets, and each visit is logged, counted under Views. Set Expires in (days) (90 by default) and Generate, then copy the link: it's shown only once. Revoke cuts it off.

Next