NetSuite ACS Renewal Evaluation Checklist

ACS renewal is typically treated as a default. This checklist turns it into a decision. Work through each section before committing to another year.

Quick answer

Before renewing NetSuite ACS, audit what your account actually called support for over the past 12 months and categorize each request: within ACS scope (standard feature guidance, Oracle bug escalation, release notes review, proactive health checks) or outside ACS scope (SuiteScript development and debugging, third-party integration maintenance, custom SuiteFlow workflow logic, Advanced PDF templates, saved search builds, implementation-partner configurations). ACS covers the standard NetSuite platform layer and Oracle escalation access. It does not cover the technical customization layer at any tier from Advise through Architect. If more than 50% of requests were outside ACS scope, ACS is funding a support layer that could not address most of what the account needed. If Oracle escalation was rarely or never used and produced no resolution that standard support could not have achieved, that specific value driver is also absent. The renewal decision should be based on actual usage data against the six checklist sections below, not assumed value or automatic contract default.

Section 1: Usage audit

Pull your support records from the past 12 months. Include ACS case submissions, cadence call notes, and any requests that were redirected because they fell outside scope.

For each request, categorize it:

Within ACS scope: Standard feature guidance, Oracle platform questions, release notes review, health check findings, Oracle bug escalation
Outside ACS scope: SuiteScript issues, integration failures, workflow changes, custom record configuration, Advanced PDF templates, saved search builds, implementation-partner configurations

Tally your results:

Total support requests in the past 12 months: ___
Requests handled within ACS scope: ___
Requests redirected or outside ACS scope: ___
Percentage of requests within scope: ___%

What this tells you:

If more than 50% of requests were outside ACS scope, ACS is not the primary support mechanism your account needs. If fewer than 20% were outside scope, ACS is well-matched to your account's actual support pattern.

Section 2: ACS engagement quality

Evaluate the quality of the engagement you actually received, not the tier you are paying for.

Named contact (Monitor and above):

Do you know who your named ACS contact is?
Have you spoken with them in the past quarter?
Do they have meaningful familiarity with your account's configuration?

Proactive value:

Did ACS proactively flag issues in the past 12 months before they became problems?
Did ACS guidance materially change a business decision or configuration choice?
Did the release readiness guidance from ACS prevent a production issue?

Oracle escalation:

Did you escalate a genuine platform defect to Oracle engineering through ACS in the past 12 months?
Did that escalation result in a resolution you could not have obtained through standard support?

Hours utilization (Monitor and above):

Did you use most of the included hours in the past engagement period?
Were hours left unused because requests were redirected as out of scope?
Were hours left unused because the account did not have active guidance needs?

Section 3: Scope gap assessment

Identify what you needed support for that ACS could not provide.

List requests that were redirected as outside ACS scope in the past 12 months:

For each redirected request, identify:

Where did the request go instead? (Implementation partner, internal team, third-party consultant, unresolved)
Was it resolved? If so, how long did it take?
What did the resolution cost (time, money, or business impact)?

Identify recurring gaps:

SuiteScript development or debugging is a regular need
Integration maintenance or failure resolution happens multiple times per year
Workflow changes require external help regularly
Custom records or field configuration frequently needs specialist attention
Advanced PDF template changes are needed periodically

If you checked three or more of these, the ongoing technical support need is structural, not occasional.

Section 4: Cost comparison

Calculate what ACS is actually costing against what it covered.

ACS cost this year: $___

ACS tier: Advise / Monitor / Optimize / Architect

Requests handled within scope: ___ (from Section 1)

Effective cost per in-scope request: ACS cost ÷ in-scope requests = $___

External support cost for out-of-scope work this year: $___ (Consultant invoices, implementation partner time, internal developer time)

Total support cost (ACS + external): $___

Questions this raises:

Is the combined support cost appropriate for the value delivered?
If ACS was not renewed and that budget was redirected to technical managed support, would coverage improve for the majority of requests?
Is there a hybrid arrangement that makes more financial sense?

Section 5: Oracle escalation dependency

ACS provides Oracle-internal escalation access that no third-party firm can replicate. This section determines how much that specific value matters to your account.

In the past 12 months:

We submitted at least one ACS case that resulted in Oracle engineering involvement
Oracle engineering resolved a platform defect that affected our production environment
The escalation path through ACS was faster than standard support would have been
We regularly benefit from Oracle's proactive platform monitoring

If none of these apply: Oracle escalation access is not a primary driver of value for your account. ACS renewal should be evaluated purely on whether the scope of functional guidance it covers matches your actual needs.

If one or more apply: Oracle escalation is a genuine value driver. The question becomes whether the escalation value justifies the full ACS cost, or whether a lower tier or hybrid arrangement would preserve that value at lower cost.

Section 6: Renewal decision framework

Use your answers from Sections 1-5 to identify the appropriate path.

Renew at the same tier if:

60% or more of requests were within ACS scope
The named contact demonstrates ongoing familiarity with your account
Included hours are consistently utilized
Oracle escalation has been used and delivered value

Upgrade a tier if:

Requests within scope are exceeding current tier hours
A more dedicated contact would improve response time for in-scope work
The account's standard feature usage is growing and needs more proactive guidance

Downgrade a tier if:

Hours are consistently underutilized
The engagement is not receiving proactive value commensurate with the tier cost
Most ACS interactions are limited to release notes review

Supplement ACS with SuitePacific if:

ACS covers Oracle platform value and Oracle escalation that the account genuinely uses
The majority of technical requests (SuiteScript, integrations, workflows, administration) fall outside ACS scope
The current situation requires paying separately for both layers, and SuitePacific covers the technical layer ACS cannot

Replace ACS with SuitePacific if:

The majority of requests are outside ACS scope
Oracle escalation has not been used or has not delivered value in the past year
A single technical retainer covering SuiteScript, integrations, workflows, and administration at $799 per month would cover more of the actual support workload than ACS does
Month-to-month terms without an annual contract are preferable to the ACS annual commitment

Consider not renewing ACS if:

Fewer than 30% of requests were within ACS scope
Hours went largely unused because the work the account needed fell outside what ACS could address
The combined cost of ACS plus external technical support is disproportionate to what either delivers
SuitePacific covers the majority of the actual support workload at a lower combined cost

What to do with your findings

If the evaluation points toward replacement or supplementation, begin that process two to three months before the ACS end date. Do not create a coverage gap by canceling ACS before a replacement arrangement is active.

If the evaluation supports renewal, use the findings to get more value from the engagement: formally request that your ACS contact address the specific areas where the account needs guidance, and track whether those needs are being met throughout the next contract year.

If your evaluation shows that most requests fell outside ACS scope, SuitePacific covers that layer. SuiteScript 2.x development and debugging, Celigo and third-party integration maintenance, SuiteFlow workflows, NetSuite administration, saved searches, Advanced PDF templates, release impact testing, and ongoing enhancements, all covered within a single monthly retainer. Oracle SuiteCloud Developer II and Administrator Professional certified. US-based, direct developer access, no annual contract. Plans start at $799 per month.

View SuitePacific support plans or compare ACS alternatives in detail.

Frequently asked questions about ACS renewal

What happens if I let ACS lapse without renewing? Your ACS access ends at the contract expiration date. You retain access to standard Oracle NetSuite support, but lose ACS-specific benefits: named or dedicated contact, proactive reviews and health checks, and the accelerated Oracle escalation path. Ensure any replacement support arrangement is active before the ACS end date to avoid a coverage gap.

Can I renew ACS at a lower tier to reduce cost? Yes. If hours are consistently underutilized or the account does not need the engagement model of the current tier, downgrading at renewal is an option. Confirm with your Oracle account representative whether the tier change can be applied at the current renewal date or requires a separate contract amendment.

Does NetSuite ACS automatically renew? ACS does not auto-cancel, but whether renewal is automatic or requires affirmative action depends on your Oracle agreement. Do not assume the contract lapses at expiration without your involvement. Contact your Oracle account representative in advance of the end date to confirm the non-renewal process and any required notice period.