New Acquisition Date Field on Customer Record for SaaS Cohort Reporting

What changed

The Customer record now includes an Acquisition Date field on the Financial subtab. This field feeds into SaaS metric reporting and cohort analysis across SuiteAnalytics and Subscription Metrics.

Field behavior

• Manual entry — You can set the Acquisition Date directly on each customer record.
• Auto-population (no value set) — If the field is left blank, NetSuite backfills it with the date of the customer's first transaction.
• Analytical Impact import override — If analytical impact data has been imported for the customer, NetSuite sets the Acquisition Date to the earliest start date from those imports, overriding the first-transaction fallback.

Derived field: Acquisition Month End Date

A calculated Acquisition Month End Date field is exposed on Analytical Impact records. It represents the last day of the month in which the customer's Acquisition Date falls. SuiteAnalytics and Subscription Metrics use this value to group customers by acquisition month for cohort reporting.

Update propagation

Any change to the Acquisition Date immediately cascades to all related reporting records. There is no delay or scheduled refresh — downstream SuiteAnalytics and Subscription Metrics data reflect the updated value right away.

Bulk loading via scheduled jobs

For environments with a large customer base, scheduled jobs can load or update the Acquisition Date field in bulk. Oracle's documentation references an "admin docs tool" to manually trigger these jobs, but the release note does not specify the exact script type, deployment ID, or whether this is a system-provided scheduled script vs. a custom one. Verify in your account under Customization > Scripting > Script Deployments or check the SuiteAnswers article linked to this feature for the system script identifier.

What to do

1. Review existing Customer records — If you already track acquisition dates externally, plan a CSV import or scheduled script to populate the new field so cohort reporting is accurate from day one.
2. Check Analytical Impact imports — If you use analytical impact data, confirm that the earliest start dates on those imports reflect the true acquisition dates you want. The auto-population logic will use those dates over first-transaction dates.
3. Update saved searches and SuiteAnalytics workbooks — The new Acquisition Date and derived Acquisition Month End Date fields are now available for use in saved searches, workbooks, and datasets. Add them to any SaaS metric or cohort-analysis reports.
4. Audit integrations writing to the Customer record — If external systems create or update customer records via REST (/services/rest/record/v1/customer) or SuiteTalk SOAP, determine whether you need to set the Acquisition Date explicitly or rely on auto-population. The field's internal ID is not specified in the release note — inspect the record in the UI or use N/record to enumerate fields and confirm the ID before updating integration code.
5. Test downstream impact — Because changes propagate immediately to reporting records, validate that bulk updates in Sandbox do not cause unexpected spikes or shifts in Subscription Metrics dashboards before running in Production.