Start with the policy, not the software
Standards such as ASC 606 and IFRS 15 describe a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate it, and recognize revenue as obligations are satisfied. Before configuring anything, document how your company applies these steps to each type of offering. Your accountants decide these judgments; the system implements them.
- List each product and service type and when control passes to the customer.
- Decide which items are distinct performance obligations.
- Document how standalone selling prices are determined and evidenced.
Contracts, orders and arrangements
In an automated setup, the sales transaction creates an arrangement that groups the elements of the deal. The system then allocates the total price across the obligations and generates recognition schedules. The quality of the output depends on the quality of the input: item records must carry the right recognition rules, and sales staff must create transactions the way the design expects. Training the order desk and finance team on the arrangement concept prevents most downstream errors.
Allocation and standalone selling prices
When a deal bundles items sold at a discount, the discount is allocated across obligations in proportion to their standalone selling prices. Maintain a controlled list of those prices, review it periodically, and keep the supporting evidence. Auditors will ask how you set them and whether you applied them consistently, so a documented, repeatable method is more important than a perfectly precise number.
Our NetSuite ERP practice →Schedules: point in time, over time and usage-based
Some revenue is recognized at a point in time, such as a delivered product; some over time, such as a subscription or support period; and some on usage, such as transactions processed. Each requires different schedule logic. Test each pattern with real examples, including partial periods, mid-term starts, and renewals, and compare the results to what your accountants calculate by hand. The edge cases reveal configuration gaps quickly.
Modifications, cancellations and credits
Real contracts change: customers upgrade, downgrade, cancel early, or receive credits. Each change may require recalculating allocation and recognizing a catch-up or adjusting future revenue, depending on the nature of the modification. Define the rules for each common change type and test them before go-live, since manual corrections multiply risk and audit questions.
Implementation and integration services →Decisions to settle before you configure
- Policy memo. Have your accountants document revenue policies by offering, to be approved by auditors if appropriate.
- Item setup. Define recognition rules and schedule types on each item so transactions inherit them automatically.
- Review process. Decide who reviews schedules and exceptions each period, and what evidence is retained.
- Reporting. Specify the deferred revenue, waterfall, and reconciliation reports finance and auditors need.
A realistic first 90 days
- Days 1 to 30. Document the policy, list contract patterns, and agree standalone selling prices with accountants.
- Days 31 to 60. Configure items and schedules, then test each contract pattern, including modifications, against manual calculations.
- Days 61 to 90. Run a parallel period, reconcile deferred revenue to the ledger, and train order and finance teams.
Pitfalls to avoid
- Configuring before agreeing policy. Changing the policy later means reworking items, schedules, and sometimes historical entries.
- Untrained order entry. If sales transactions are created inconsistently, schedules will be wrong no matter how well the system is set up.
- Ignoring modifications. Upgrades and cancellations are common. Test them thoroughly.
- Spreadsheet side calculations. Manual adjustments outside the system create audit risk. Aim to keep calculations inside it.
