There are several key nuances from a SuiteBilling perspective to consider when diving into solution architecture and implementation. This article discusses a handful of those nuances to watch out for.
Amendments on Same Day:
A common reason subscription change orders fail to get created via integration or via the UI is a NetSuite limitation. It only allows 1 subscription change order per day for each subscription line. This is the case if the status of the change order is not ‘Voided’.
A common scenario we see often between CPQ and NetSuite integrations is sales reps entering amendments incorrectly or on the wrong date. The sales rep then creates a new amendment in CPQ with the expectation to override the old one and that is not the case. For customers with a CPQ and NetSuite integration, consider building out a process to handle these exceptions.
Linking Credit Memo from SuiteBilling Charges to Specific Subscription Change Order
Recently a client of ours requested a credit memo analysis on hundreds of credit memos. They wanted to see credit memos created from SuiteBilling and the related change orders that caused the charges. Unfortunately, the SuiteBilling data model does not provide the ability to link these together. Linking these through several reports is possible if your organization only has 1 change order per contract/subscription item. But in our customer’s case, they can have anywhere from 5-10 different change orders on a single subscription making this connection not possible unless you are to review each credit memo manually.
Units Type on Non-Inventory or Service Items
You cannot assign Unit types to the items related to Subscription plans. You cannot also add service or non-inventory items to a new or existing subscription as an add-on when the Unit type is assigned to them. When trying to create an add-on subscription line or a new subscription, items will not show in the dropdown if they have a unit type assigned. If you try and process a new order, renewal order, or add-on via integration you will see an error such as ‘Invalid item reference Key (internal ID) for the item.’
31st Bill Date Bug:
A known bug that NetSuite has acknowledged is around billing accounts with a start date that falls on the 31st of the month. This causes unusual behavior among charges regarding charge bill dates. See below for an example:
There are numerous other nuances with SuiteBilling not mentioned in this article. These are just a few that we have uncovered in the past couple of years working with our clients. We can solve these via creative custom solutions. But Potential solutions may vary depending upon client requirements. If you are planning to implement Suitebilling then, consider these nuances and discuss them with the client before proceeding with the potential solutions. We can solve these via creative custom solutions. But Potential solutions may vary depending upon client requirements.