New Analytical Impact Record Automates SaaS Metric Consolidation

What changed

A new Analytical Impact record type is now available at Lists > SaaS Metric > Analytical Impacts. These records consolidate recurring-revenue data from multiple transaction types into a unified SaaS Metric Reporting pipeline.

Automatic creation via nightly job

A scheduled nightly job runs at 1:00 AM server time using the bulk processing framework. It scans qualifying source lines and creates Analytical Impact records without user intervention. Source lines can originate from:

• Subscriptions (subscription lines)
• Sales orders with billing schedules
• Contract renewal transactions
• Standalone sales orders
• Invoices
• Cash sales

Downsell events are also generated from return authorizations, credit memos, and cash refunds linked to qualifying transactions.

Eligibility criteria

All of the following must be true for a source line to generate an Analytical Impact record:

1. The item on the transaction or subscription line has Track SaaS Metrics enabled.
2. The line's Start Date falls within the item's SaaS Metric Start Date and SaaS Metric End Date.
3. Both Start Date and End Date are populated and the term is at least one month.
4. The transaction or subscription status is in an accepted state (e.g., Sales Order: Pending Fulfillment through Closed; Invoice: Open through Closed; Subscription Line: Active, Suspended, Terminated, Closed; Cash Sale: Not Deposited, Deposited, Closed).

Adjustments and reclassification

Analytical Impact records support manual adjustment:

• Split an impact: Enter a partial amount in the Adjust Monthly Impact field and select an Adjust Impact category/subcategory. NetSuite creates two events on the SaaS Metric record for the split.
• Reclassify: Enter the full amount in Adjust Monthly Impact and choose a different category/subcategory.
• Ignore: Check the Ignore checkbox on the record. This deletes any linked SaaS Metric records and suppresses future generation from that impact.

Edits to source records (line amounts, dates, linked records) automatically propagate to the associated Analytical Impact records.

Customization

The default Analytical Impact form supports custom fields. Records imported via CSV can be deleted if they should not appear in reports.

What to do

1. Verify item setup: Confirm that items intended for SaaS metric tracking have Track SaaS Metrics enabled and that SaaS Metric Start Date / SaaS Metric End Date are correctly configured.
2. Audit transaction dates: Ensure qualifying transactions have both Start Date and End Date populated with a term of at least one month, or they will be silently skipped by the nightly job.
3. Review generated records after go-live: After the first nightly run, navigate to Lists > SaaS Metric > Analytical Impacts and verify records were created as expected. Use the Ignore flag on any that should be excluded.
4. Plan for scripting and integration: The release notes do not specify the internal record ID (e.g., analyticalimpact) or confirm SuiteScript/REST API support. If you intend to read or write these records programmatically via N/record, N/search, or the REST API (/services/rest/record/v1/...), test access in Sandbox first. Check the Records Browser for the record's script ID and field IDs.
5. Custom fields: If your SaaS metric workflow requires additional data points, customize the Analytical Impact form with custom fields now so the nightly job populates a record you can immediately use downstream.
6. Downstream dashboards: Split and reclassified impacts surface as separate events on SaaS Metric records. Update any saved searches, workbooks, or SuiteAnalytics datasets that consume SaaS Metric data to account for the new event structure.

Open questions

Oracle's documentation does not clarify several details that matter for implementation:

• The internal record type ID and script-accessible field IDs are not listed. Check the Records Browser in your account.
• It is unclear whether SuiteScript beforeSubmit/afterSubmit user-event triggers fire on nightly-job-created records or only on manual edits.
• Governance cost of bulk operations against these records via N/record is not documented.
• Whether the nightly job respects SuiteCloud processor limits or runs under a system context is not stated.