Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
ARM + SuiteBilling mixed arrangement - orphaned deferred revenue on partially cancelled OTR lines
We are running NetSuite Advanced Revenue Management with SuiteBilling for a mixed subscription and one-time revenue model. We are hitting a wall on a specific edge case and looking for anyone who has solved this cleanly.
Our Setup
- SuiteBilling for subscription items, each on standalone arrangements
- One-time revenue (OTR) items sold on standard Sales Orders
- When a deal includes both, we merge the SuiteBilling arrangement and the Sales Order arrangement into a single merged Revenue Arrangement per ASC 606 multi-element allocation requirements
- Fair Values and SSPs are configured, allocation works correctly on initial setup
The Problem
When a SuiteBilling subscription is modified, the Change Order mechanism adjusts the element value directly on the arrangement and ARM recalculates cleanly. The subscription side sorts itself out.
0