How to merge revenue arrangements for linked sources in NetSuite

Preview an ordinary revenue arrangement merge in NetSuite, check the allocation, and verify moved elements and retained source arrangements.

The quick answer

Open Merge Revenue Arrangements for Linked Sources, filter to the eligible source records, and leave Only Merge Residual Revenue Amounts cleared for an ordinary merge. Select the intended elements and inspect Preview before clicking Merge. Verify the new arrangement's allocation and source links, then open the original arrangements to confirm that only the selected elements moved.

The example combines RA4101 and RA4102 for Cedar Point Analytics. The new arrangement is RA4103. Person and operating-company names are fictional example data.

Before you start

Enable Advanced Revenue Management and use a role permitted to view and edit revenue arrangements and run the merge process. Viewing an arrangement alone does not establish access to merge or update plans. Finance must approve combining these elements into the same performance obligation. Sharing a customer does not establish that decision.

Check matching subsidiary and currency, compatible accounting-book scope, and Effective Start Dates that are all blank or match. Resolve invalid sources and exclude arrangements associated with unsupported posting discounts. Contract acquisition costs add matching cost-account requirements; this example has no contract costs. Its source records use Cedar Point UK, British pound, and Primary Accounting Book.

This walkthrough demonstrates selection, preview, merging, and new/source verification. The account uses manual revenue-plan updates, but that follow-up is explained separately and is not performed in the recording.

01. Check the source arrangements

Open RA4101 and RA4102. Confirm the customer, subsidiary and currency, plus accounting-book scope where Multi-Book Accounting is enabled. Inspect each intended element's source transaction, Effective Start Date, discounted sales amount and revenue amount. The example uses REVE08201 from SO7301 for 1,200.00, and REVE08202 from SO7302 for 1,800.00. Both Effective Start Dates are blank.

RA4101 is shown here. Repeat the same scope checks for RA4102.

02. Select the intended elements

Open Merge Revenue Arrangements for Linked Sources from your center’s revenue-arrangement area, or use global search for the page name. An older center may place it under Transactions > Financial.

Select Customer = Cedar Point Analytics, then verify Subsidiary and Currency. Choose the intended accounting book if the field appears. Here the source date filters are 10/1/2026 through 10/2/2026, and the new Revenue Arrangement Date is 10/5/2026.

Keep Only Merge Residual Revenue Amounts cleared. Select RA4101 and RA4102 and review their individual element rows. Selecting an arrangement selects its elements by default. Use Mark All only when every displayed row belongs in the approved merge.

Review the individual elements included by each arrangement selection.

If Advanced Cost Amortization exposes Contract Cost Accrual Date, use its finance-approved date too. That feature is disabled in this example.

03. Review the proposed allocation

Click Preview. Check the customer, scope, source transactions and elements on Preview Revenue Arrangement. Preview does not save a new arrangement. Review Transaction Total, Total Revenue Amount and Total Carve-Out, then compare each selected element's calculated fair value and revenue amount before and after the merge.

The two example allocations remain 1200 and 1800 with zero change.

In this example, each element keeps its amount: 1,200.00 and 1,800.00. The displayed Transaction Total and Total Revenue Amount are both 3,000.00, and Total Carve-Out is 0.00. The preview's change columns show zero. Other inputs can produce a different allocation; adding discounted sales amounts alone does not establish Total Revenue Amount.

If the selection or allocation is wrong, click Cancel, correct it, and preview again.

04. Verify the new arrangement

Click Merge when the preview agrees with the approved scope. This run opens RA4103 directly. If your submission opens Process Status, refresh until it finishes and resolve any reported failure. Do not submit another merge merely because processing is delayed.

Verify the new date, amounts and Created From Merged Arrangements flag. Merged Into New Arrangements remains cleared on this new record.

The new arrangement carries the created-from merge flag.

On Revenue Elements, verify both moved elements and their Last Merged From Arrangement references. The links point to RA4101 and RA4102; the source sales orders and amounts remain associated with their elements.

Last Merged From Arrangement identifies each element source.

05. Check the retained source records

Follow each source-arrangement link. RA4101 and RA4102 still exist, with Merged Into New Arrangements checked. Their Revenue Elements tables show No records to show. because all their elements moved in this example. If you selected only some elements, the unselected elements should remain on their source arrangement.

RA4101 remains after its element moves. Repeat this check for RA4102.

Return to RA4103 and record its number with the source links. This verifies the merge and the retained records.

Follow-up: Update revenue plans

The recording stops with Revenue Plan Status = Not Started. With Revenue Plan Update Frequency = Manual, run Update Revenue Plans on the new arrangement after the merge, resolve processing errors, and use View Revenue Plans to inspect the resulting amounts and dates. Complete any required approval before recognition processing. These actions are outside the recorded sequence.

A completed merge does not prove that recognition journals were created or that downstream approval finished.

Common questions

Which revenue arrangements can be merged?

Source arrangements should have matching subsidiaries and currencies, compatible accounting-book scope, and Effective Start Dates that are either blank or match. Invalid sources, unsupported posting discounts, and incompatible contract-cost requirements must be resolved or excluded first.

What does Only Merge Residual Revenue Amounts do?

For an ordinary merge, leave Only Merge Residual Revenue Amounts cleared. Residual-only merging is a separate process for a prospective contract modification; verify its requirements before using it.

Does Preview create the new arrangement?

No. Preview only shows the proposed allocation and comparison values. Review the selected elements, transaction total, total revenue amount, total carve-out, and before-and-after amounts before clicking Merge.

Will the merged elements keep their original amounts?

Not necessarily. The allocation depends on the selected elements and their fair values. In the fictional example, the amounts remain 1,200.00 and 1,800.00, with a 0.00 carve-out and no change shown in the preview. Other selections or inputs can produce different results.

What happens to the source arrangements after the merge?

The source arrangements remain available, and Merged Into New Arrangements is checked. In the demonstrated example, all elements moved, so the source Revenue Elements subtabs are empty. If only some elements were selected, the unselected elements should remain on their original arrangements.

Does merging update revenue plans or create recognition journals?

Plan updates depend on the account’s update settings. The demonstrated sequence ends with the new arrangement’s Revenue Plan Status = Not Started. If revenue-plan updates are manual, run Update Revenue Plans afterward, review View Revenue Plans, and complete any required approval before recognition processing. A completed merge alone does not prove that plans or recognition journals were created.