Release 2508 - 11/27/2025

this release introduces a new revenue model docid 7xktonrc8c65mkx9wip j , that allows customers to pre commit to spending amounts with flexible usage based billing, automated true ups, and tiered discounts for overspend, enabling predictable enterprise revenue while reducing manual billing errors the release also includes bug fixes for netsuite invoice syncing issues related to change orders and enables proper editing of einvoice mandates in credit memo mapping in addition, nue now supports docid\ i2uoxjkirteiel rez4ua for order forms, allowing teams to generate, send, and track signed documents directly in nue this streamlined workflow removes manual handoffs and external tools, enabling faster, more consistent quote to signature cycles the feature is currently available in preview preview feature enhancements lifecycle manager introducing commit burndown commit burndown revenue model nue will soon support a brand new revenue model commit burndown, commit burndown, introducing first class support for committed spend contracts, allowing customers to commit to a specific spend or credit volume (e g , $2m/year) and draw down against that commitment via subscriptions, usage, or one time charges this model supports granular periodization (monthly, quarterly, annually), automated ramp line management, dynamic discounts based on total committed credits, flexible mid term changes (increases only), end of term billing and reconciliation, and clear separation of committed versus recognized revenue the feature is ideal for enterprise saas, ai, and data platform vendors with complex deal structures and is natively integrated into nue io’s cpq, billing, and lifecycle manager platforms why it matters unlocks predictable revenue businesses can secure baseline revenue commitments from customers, improving forecasting and supporting long term planning enables flexible enterprise deals supports complex, multi period, and usage based commitments, adapting to customer requirements for both predictability and flexibility automates billing and reduces manual errors complex scenarios like true up, overspend discounts, ramped pricing, and credit rollovers are fully automated, decreasing operational overhead and risk learn more customer use cases use case 1 a global ai platform offers its enterprise customers $2m in annual committed spend, split into quarterly periods the customer receives service discounts that scale with higher commitment tiers as customer usage grows mid year, the sales rep increases the committed amount for future quarters—without impacting past periods at renewal, any unused credits are either billed or rolled over to the next term, as contractually agreed this supports both customer flexibility and predictable revenue for the vendor use case 2 a saas vendor’s revops manager configures a bundle of recurring and usage products, all tied to a committed cash credit pool when the total committed credits across all products in a quote exceed $1m, a 10% discount automatically applies as the sales rep updates quantities or adds products, the system instantly recalculates and applies the correct discount tier, ensuring the end customer always receives the right contract price use case 3 a finance team needs to strictly track committed spend versus recognized revenue for compliance and forecasting by using the new total committed amount field (excluded from total price), they can forecast under or overspend, automate end of period true up/rollover billing for unused commitment, and ensure any credits rolled over are always billed before being extended into the next committed period how it works admins create a cash type credit pool and mark it as committed committed configure a product with the commit burndown revenue model, enable period ramping for periodized commitment (e g , quarterly, monthly) add the commits products to quotes/orders the system automatically splits committed amount into ramp lines per period (e g , four quarters for a 12 month subscription) as users edit commit amounts or terms, ramp lines and committed fields (total committed amount, delta committed arr/cmrr) update in real time discount tags for eligible products calculate and apply dynamically based on the aggregated committed credits across all products in the same pool at period end, under spend is billed (or rolled over if configured) dependencies and limitations committed spend can only be of cash type credit committment will be supported in future versions price tags or discounts are not allowed directly on commit burndown products in this release, only services/products that burn commits can have commit driven discounts commit burn down is not supported for evergreen subscriptions (end date is required) reductions to committed amounts are only allowed for future periods; current and past periods are locked for more details read docid 7xktonrc8c65mkx9wip j e signature integration with docusign this feature is currently in preview to access it, users must have the following permission enabled integration → docusign integration this feature introduces robust electronic signature (e signature) capabilities to the nue order form workflow, leveraging docusign integration administrators can embed e signature components (signature, initial, date signed, full name) directly into order form templates using the template builder sales representatives can send order forms for signature to both internal and external recipients this streamlines contract execution, enhances compliance, and improves user experience for all stakeholders why it matters accelerates contract execution by digitizing the signature process, reducing turnaround time and eliminating manual paperwork reduces errors and compliance risks by ensuring all required signatures are captured, tracked, and auditable, with detailed event logs learn more customer use cases use case 1 an admin at a saas company uses the template builder to add “signature” and “date signed” fields to an order form template when a sales rep sends a contract, these fields are automatically placed for each signer, ensuring all legal requirements are met without manual editing use case 2 a sales rep closes a deal and needs both the client and an internal legal reviewer to sign they select the order form, add a cc for the finance team, and send the document both signers receive customized emails and can e sign from their devices dependencies and limitations docusign integration must be configured and activated in nue system settings before use webhook event tracking requires enabling docusign connect and proper endpoint configuration for more details read docid\ i2uoxjkirteiel rez4ua programmatic order activation and cancellation with custom field propagation this feature allows external systems to activate or cancel salesforce orders programmatically via the docid\ fszpzsvfhrmb7ycrzmh l it enables the population of custom fields on both the order header and order line items before activation or cancellation when an order is activated, the subscriptions, assets, or entitlements are created and the custom fields are carried forward when an order is activated or canceled, these custom fields are included in the webhook event payload, making them available for downstream integrations such as billing, analytics, and erp systems this supports automation, ensures data continuity, and enables real time integration with platforms like stripe, netsuite, qbo or fulfillment and provisioning systems why it matters enables seamless, automated order management across salesforce, nue, and downstream systems ensures accurate and consistent custom field data throughout the order to cash process, reducing manual work and errors powers real time, event driven workflows for provisioning and external billing by including enriched custom field data in activation and cancellation webhooks to use the lifecycle api to patch an order or order product, you will need the following permission nue on salesforce > manage salesforce orders sample api payload note note custom fields must be synced to nue prior to being included in the payload for more information, please reference docid\ dqcjiqzg3qpur31dj7ag activate an order while setting a custom field activate an order while setting a custom field curl location globoff request patch '{{endpoint}}/objects/order/{{orderid}}' \\ \ header 'content type application/json' \\ \ header 'nue api key {{nue api key}}' \\ \ data '{ "stripe subscription id c" "sub 1234567890abc", "status" "activated" }' set a custom field of an order product set a custom field of an order product curl location globoff request patch '{{endpoint}}/objects/orderproduct/{{orderproductid}}' \\ \ header 'content type application/json' \\ \ header 'nue api key {{nue api key}}' \\ \ data '{ "ruby stripe subscription id c" "sub 1234567890abc" }' learn more customer use cases use case 1 a saas company uses a stripe powered self service portal to automate subscription creation for new customers before the subscription is created, their provisioning flow generates a stripe subscription id and writes it via the api to custom fields on the nue order header and nue order product when the nue order is activated, subscriptions are created, the resulting webhook includes these custom fields, enabling downstream billing and provisioning systems to immediately use the stripe subscription id for further processing use case 2 an enterprise integrates salesforce orders with netsuite when a sales order is programmatically canceled via api (e g , due to a failed payment), a custom field indicating the cancellation reason is set on both the order and its line items the order canceled webhook event includes this field, allowing netsuite to record the reason and trigger appropriate financial workflows use case 3 a revops team needs to ensure that custom entitlement or configuration metadata (e g , feature flags, customer specific tags) are consistently propagated from salesforce orders to subscriptions and all downstream billing/erp systems by populating these fields before activation, and having them included in webhook payloads, the team eliminates the need for manual intervention or post processing scripts bug fixes lifecycle manager order activation now blocked when order contains at least one expired subscription resolved an issue where orders containing an expired subscription meaning a subscription already versioned due to another order’s activation were incorrectly allowed to activate with this fix, activation of such orders now correctly fails the system validates subscription eligibility during activation and prevents processing when the subscription has already been superseded auto renewal job reliably restored with this fix, the auto renewal job now successfully processes renewals, ensuring that opportunities, quotes, and orders are created as expected subscriptions will be renewed automatically, preventing unintended lapses in service the fix has been deployed to production (version 2507 2 2) and will be available in the upcoming sandbox release (2508) additionally, efforts are underway to address any subscriptions that were not renewed during the period when the bug was active, ensuring all affected customers are brought up to date accurate discount application and total calculation for bundle quotes resolved an issue where a few quotes with bundles didn’t apply the overall discount consistently, which could make the quote total look off now, discounts are applied evenly across all items in a bundle, and the quote total matches the itemized amounts and the previewed invoice this improves quote accuracy and reduces confusion when reviewing or approving pricing integrations netsuite managing change order reliability between nue and netsuite this fix resolves the previous failures and allows invoices—including those with complex change orders or renewals—to sync reliably to netsuite previously, when syncing invoices from nue to netsuite in the case of a change order, the process could fail with a generic error message, and invoices would not be transferred successfully the root cause was a mismatch between the number of order lines and invoice item details being synced with this fix, the invoice sync process now correctly groups and matches transaction entries by netsuite sales order id, ensuring that all relevant invoice lines are accurately mapped and transferred improved error handling for netsuite integrations some error messages from netsuite were unclear or generic, making it difficult to identify and resolve integration issues error messages from netsuite are now clearer and more descriptive, helping users quickly understand and address issues during integration this enhancement improves troubleshooting efficiency and overall user experience quickbooks improved payment sync reliability for quickbooks integration previously, payments from quickbooks to nue would fail entirely if any payment in a batch exceeded the invoice balance with this fix, successful payments in a batch are now processed even if others fail, and both successful and failed transactions are accurately tracked this ensures more reliable payment syncing and better visibility into payment processing outcomes fixed error when setting up and editing integration setup previously, users encountered an unexpected error when attempting to edit integration setups, resulting in a json parse error and failed updates as well as integrations being left in draft mode with this fix, editing integration configurations now works as expected, eliminating the error and improving reliability for integration management rightrev order cancellation not synced to rightrev due to cancellation date not being saved previously, some order cancellations in nue were not syncing to rightrev due to the cancellation date not being fully saved before the sync process began with this fix, all new order cancellations will reliably sync to rightrev, ensuring accurate and timely revenue recognition this update prevents missed cancellations and reduces the need for manual intervention avalara e invoicing improved editing for einvoice mandates in credit memo mapping previously, users were unable to edit the einvoice mapping for credit memos (cm) in the dk b2b peppol integration with this fix, users can now reliably edit einvoice mandates for credit memos updates to the buyerreference field and other mapped fields are correctly reflected in the xml output improved invoice delivery for nemhandle network previously, invoices with amount fields showing only one decimal place were rejected by the nemhandle network and not delivered to end customers with this fix, all relevant amount fields in generated invoices now consistently display two decimal places, ensuring successful delivery and compliance with nemhandle requirements transaction hub salesforce launch button now functional from credit memo previously, clicking the salesforce launch button from a credit memo in transaction hub did not redirect users to salesforce as expected with this fix, users are now correctly redirected to the salesforce login and the relevant credit memo page developer experience and platform buy now from quote integration with rightrev previously, the buy now from quote experience was not syncing relevant data to rightrev this fix updated the buy now from quote activation path to publish the rightrev sync message consistently, ensuring order product and invoice item data is ingested by rightrev