NetSuite

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Financials (Income Statement)

Invoices (AR)

Vendor Bills (AP)

• Track revenue and expense trends attributable to AI initiatives against your NetSuite income statement
• Measure AR invoice volume and collection rate improvements from AI-assisted billing or collections workflows
• Monitor AP vendor bill throughput to quantify AP automation ROI
• Compare net income trends before and after broad cost-reduction AI initiatives

1. In NetSuite: Go to Setup → Integration → Manage Integrations → New and create an Integration record with Token-Based Authentication (TBA) enabled; copy the Consumer Key and Consumer Secret shown once on creation
2. In NetSuite: Go to Setup → Users/Roles → Manage Roles and assign the integration user a role with Read access to Transactions, Financial Statements, and SuiteAnalytics Workbook
3. In NetSuite: Go to Setup → Users/Roles → Access Tokens → New, select the integration record and the integration user, and copy the Token ID and Token Secret shown once on creation
4. In NetSuite: Find your Account ID in the URL when logged in (the numeric value) or under Setup → Company → Company Information
5. Back in Roiva: Enter all five values — Account ID, Consumer Key, Consumer Secret, Token ID, Token Secret — in the form fields above and save
6. Back in Roiva: The connection page checks the sign-in and the role, and says which is missing. Once it's all ticked, click Test Connection
7. Back in Roiva: After connecting, link this connection to an initiative and select the object types relevant to your initiative

• Roiva syncs 12 months of historical data on first connect — income statement aggregates per month, plus individual invoice and vendor bill records
• Financials produces three observations per month (revenue, expenses, net income); use net income for broad cost-reduction initiatives, revenue for sales-impact initiatives
• Invoice metrics (count, volume, paid count) are ideal for AI-assisted collections or billing automation initiatives; compare paid count ratio before and after deployment
• Vendor bill metrics (count, volume) are ideal for AP automation initiatives; a falling bill count with stable volume signals improved processing efficiency
• The income statement aggregates across all subsidiaries by default; for subsidiary-specific measurement, combine with a manually entered observation scoped to that business unit