Rule-Based Recognition Treatment Adds Criteria-Driven Overrides to ARM Revenue Elements

What changed

The Rule-Based Recognition Treatment feature extends both Advanced Revenue Management (Essentials) and Advanced Revenue Management (Revenue Allocation). Previously, recognition attribute values on a revenue element were inherited from the item record's Revenue Recognition/Amortization subtab. Changing those values for specific scenarios (e.g., returns vs. sales) required manual edits on the revenue arrangement.

This feature introduces a rules engine that automatically overrides the following recognition attributes on a revenue element when configurable criteria are met:

• Create Revenue Plans On
• Revenue Recognition Rule
• Rev Rec Forecast Rule
• Allocation Type
• Revenue Allocation Group

New records

Two records are added under Setup > Accounting > Revenue:

1. Recognition Treatment — Stores a named collection of recognition attribute values. Think of it as a reusable attribute template that can be applied to revenue elements instead of the item-level defaults.
2. Recognition Treatment Rule — Defines the criteria (e.g., Transaction Type equals Return Authorization, Credit Memo, etc.) that determine when a recognition treatment is applied. Rules are evaluated during the recognition treatment lookup process.

New permissions

Both records have corresponding permissions under the Lists category in role configuration:

• Recognition Treatment
• Recognition Treatment Rule

You must grant these permissions to any role that needs to create, edit, or view the new records.

Lookup process

The recognition treatment rule lookup runs automatically during:

• Revenue arrangement creation
• Revenue arrangement merge

It can also be triggered manually from an existing revenue arrangement. When a rule matches, NetSuite replaces the item-level defaults on the revenue element with the values from the associated recognition treatment — no manual arrangement editing required.

What Oracle doesn't clarify

The source documentation does not specify:

• Whether these new records are exposed via SuiteScript N/record (record type IDs are not listed).
• Whether the Recognition Treatment or Recognition Treatment Rule records are available through REST (/services/rest/record/v1/...) or SOAP web services.
• The exact criteria fields available on a Recognition Treatment Rule beyond Transaction Type.
• Whether the lookup process fires a user event or workflow trigger that custom code can hook into.
• Governance impact if the lookup is invoked via script.

What to do

1. Enable the feature — Navigate to Setup > Company > Enable Features. The exact feature toggle name is not stated in the source; look under the Accounting or Revenue Recognition section for Rule-Based Recognition Treatment.
2. Grant permissions — Edit every role that manages revenue recognition. Add Recognition Treatment and Recognition Treatment Rule (both under Lists) with the appropriate access level.
3. Create recognition treatments — Under Setup > Accounting > Revenue, define one or more recognition treatments containing the attribute overrides you need (e.g., different Create Revenue Plans On and Revenue Recognition Rule values for returns).
4. Create recognition treatment rules — Define rules with criteria that match your scenarios. Associate each rule with the appropriate recognition treatment.
5. Test with existing arrangements — Use the manual lookup process on a revenue arrangement to verify that rules match and attribute values are applied as expected before relying on the automatic lookup during arrangement creation.
6. Audit custom scripts — If you have SuiteScript or workflows that modify recognition attributes on revenue elements or revenue arrangements, review them for conflicts with the new automated lookup. The rule engine may overwrite values your scripts set during arrangement creation or merge.
7. Verify API access — If you integrate revenue data via REST or SOAP, test whether the new record types are queryable. Oracle's documentation does not confirm API support; check the Records Catalog (Setup > Records Catalog) in your account after enabling the feature.