Usage-based pricing shouldn't break your accounting stack

Credits are one of the places billing-to-ERP integrations break down most visibly. A running balance doesn't tell finance what was consumed, when, or against what commitment. Orb tracks the full lifecycle and creates the downstream structures to match.

• Customer deposits for prepaid balances — credit purchases land as proper deposit records, not a memo line
• Drawdown tracking — consumption is recorded as it happens, not reconstructed at close
• Expiration and breakage treatment — credits that expire are handled explicitly so finance isn't left with unexplained balances
• Downstream structure for credit-heavy models — the accounting shape reflects how credits actually work, not how invoices do

Revenue accounting shouldn't have to fill in what the billing system left out. The problem is when service periods are missing, usage treatment is vague, and records don't map cleanly to existing NetSuite items. Orb gives rev rec a better starting point instead.

• Line-level service periods — exact period dates on every line so ARM doesn't have to infer them
• Mapping to existing NetSuite items — Orb maps to the items finance already uses, not a parallel structure to maintain
• Cleaner revenue arrangement inputs — the downstream record structure ARM needs is already there
• Separation between billing and revenue recognition — billing timing and revenue timing stay distinct, period by period

Most billing systems send NetSuite a summary line finance can't trace, reconcile, or explain. Orb creates standard transaction records: the native objects NetSuite already knows how to handle and finance already knows how to audit.

• Native sales invoices — standard invoice records with service period dates attached, not imported billing approximations
• Sales orders — for teams with order-based workflows, the downstream structure finance already expects
• Credit memos and credit notes — proper credit records that trace back to the originating transaction
• Payments — payment records that stay aligned with the invoice they settle
• Full audit trail inside NetSuite — finance can trace any record back to what Orb produced without leaving the ERP

Billing integrations that overwrite accounting policy or bypass ARM create problems that are hard to unwind. Orb is designed around the opposite principle: the integration adapts to how finance already runs, not the other way around.

• One-way sync from Orb to NetSuite — Orb pushes finalized records in; NetSuite stays the system of record
• Direct mapping to existing NetSuite items — no parallel item structure to maintain or reconcile
• Existing ARM logic stays intact — Orb feeds ARM the inputs it needs; the revenue recognition logic stays with finance
• Configurable record structure — mappings, downstream shapes, and workflow choices reflect the environment finance already owns