SaaS Metric Tracking: New Checkbox and Date Fields on Item Records

What changed

A new SaaS Metric Tracking feature lets you flag individual items for automatic SaaS metric calculation. When enabled on an item, NetSuite generates impact data for new, upsell, downsell, and churn across transactions and subscriptions that include that item.

New fields on the Item record

Three new UI elements appear on the Sales/Pricing subtab of the item record:

• SaaS Metric Tracking — checkbox that opts the item into metric generation.
• SaaS Metric Start Date — controls when tracking begins. Can be set in the past to backfill historical transaction data that already references the item.
• SaaS Metric End Date — controls when tracking stops, preventing stale items from polluting reports.

Related records

Two supporting records are referenced in the documentation but not fully detailed in this source:

• SaaS Metric Record — presumably stores the computed metric values per item/period.
• SaaS Metric Reporting Impact Subcategory Record — likely categorizes each metric impact (new, upsell, downsell, churn).

Note: Oracle's documentation does not specify the internal IDs of these records, whether they are exposed via SuiteScript/SuiteTalk, or what fields they contain. Verify their scriptability by inspecting the Records Catalog (Setup > Records Catalog) or querying SELECT * FROM customrecordtype WHERE scriptid LIKE '%saas%' via SuiteQL.

What to do

1. Identify items to track. Determine which service/subscription items should generate SaaS metrics.
2. Enable per item. Edit each item record, navigate to the Sales/Pricing subtab, check SaaS Metric Tracking, and set the start date. Use a past date if you need historical backfill.
3. Set an end date where appropriate. For items being sunset or replaced, populate the end date to keep reports clean.
4. Verify record access. Check the Records Catalog or use N/record to confirm whether the SaaS Metric and Impact Subcategory records are scriptable. If you plan to build custom dashboards or integrations, you need to know the record type IDs and available fields.
5. Review saved searches and SuiteAnalytics. If you have existing ARR/MRR reporting, evaluate whether these new records can replace or supplement your current approach.
6. Test with historical data. If you backfill by setting a past start date, validate the generated metrics against your existing calculations before relying on them in production reports.

The release version for this feature is not stated in the source documentation. Check the Release Notes portal or your account's release version to confirm availability.