Release 2509 - 01/06/2026

this release introduces key enhancements including a unified credits and commits page for monitoring customer credit flows, entity level invoice auto numbering for multi jurisdictional compliance, automated dunning and collections for overdue invoices, and improved e signature capabilities with enforced default templates and customizable text/title fields in docusign workflows this release also enriches the ai chatbot with product catalog contexts , which enables whitespace analysis for upsells and cross sells, real time active/published products and prices visibility, and automated publish/unpublish controls across products, bundles, and price tags you can now find credits , commits , and usage under the revenue manager menu usage was previously located in lifecycle manager → assets action required action required all customers with quickbooks integrations must re authenticate and reconfigure gl account mappings by december 31 to avoid service disruption due to intuit's oauth deprecation feature enhancements nue ai ai enable product catalog this release enriches the ai chatbot with product catalog context it empowers organizations to seamlessly analyze product whitespace, publish and unpublish products and price tags for self service channels, and surface all active and published products, bundles, and their prices in real time the feature supports multi currency, advanced bundle management, and granular price tag operations, all accessible via both docid\ rua3gafej p9h4wdpr2l2 and docid\ zb2o1kijmkwhoweqhagc for human users and ai agents ensuring that customers, partners, and sales teams always have up to date, compliant, and actionable product and pricing information enable automated opportunity close/won and quote management with mcp tools this release introduces a comprehensive set of docid\ zb2o1kijmkwhoweqhagc that allow users to create, query, and update salesforce opportunities and update quotes directly within nue key enhancements include the ability to close/win opportunities, update quote details (such as setting a quote as the primary quote for an opportunity) these mcp tools are available in the customer chatbot as well why it matters accelerates sales cycles and reduces manual effort by automating opportunity management and quote updates, including marking opportunities as closed/won and ensuring primary quote synchronization improves data integrity and compliance by enforcing business rules (such as single primary quote per opportunity), logging all changes, and surfacing detailed error notifications for failed syncs or invalid field combinations enhances integration between nue and salesforce, enabling revops and sales teams to manage, audit, and troubleshoot quote to opportunity syncs in real time, all via natural language conversations learn more customer use cases a revops manager notices that the latest quote for a strategic deal needs to be set as the primary quote using nue’s api, they set the quote as primary, which automatically synchronizes the quote line items to the opportunity—updating totals and ensuring that all reporting and product records are accurate a sales representative leverages the nue chatbot to update an opportunity’s stage to “closed/won” immediately after securing a customer agreement this action triggers downstream processes in salesforce, ensuring that the related opportunity products, pipeline metrics, and forecasting reports are instantly updated without manual intervention after a quote update fails due to a custom salesforce validation rule, an admin receives a detailed error notification through nue they quickly review the logged error, identify the cause, and resolve the issue all in the chatbot lifecycle manager enforce default quote template/pdf selection during e signature (preview) this feature adds a system level setting that, when enabled, enforces the use of a default quote pdf or template for e signature transactions in the nue platform when this setting is active, sales reps are no longer presented with the option to manually select a template or pdf while sending documents for e signature (e g , via docusign) instead, the system automatically chooses the appropriate document according to a strict priority order the latest generated pdf, the quote level default template, the entity level default template, or the system default template, admins can configure this setting in nue system settings → integrations → docusign integration why it matters ensures all signed documents use company approved templates, improving compliance and auditability reduces manual errors and accidental use of outdated templates by sales reps streamlines the e signature workflow, saving time and providing a consistent experience for both internal teams and customers learn more customer use cases use case 1 a global saas company requires all order forms sent for e signature to strictly follow approved legal and brand standards by enabling the enforced default template setting, sales teams can confidently send order forms, knowing compliance is automatically maintained and accidental use of outdated templates is prevented use case 2 a revops manager at a fast growing organization wants to minimize support tickets caused by sales reps sending the wrong pdf or template for signature after enabling this feature, instances of document mix up drop to zero, and onboarding new sales reps becomes much simpler use case 3 a finance team needs to ensure that all signed contracts are generated with entity specific templates, supporting regulatory requirements in different countries by configuring entity level default templates and enabling the enforcement toggle, every e signed document is routed through the correct template, even for multi entity deployments for more details, please read docid\ i2uoxjkirteiel rez4ua add text and title fields to e signature template (preview) this feature enables revops managers to add new docusign compatible "text" and "title" fields to order form and quote templates in the nue platform’s template builder when docusign integration is enabled, these fields allow for richer and more customizable data capture in e signature workflows "text" fields can collect any signer supplied input, while "title" fields display the recipient’s job title, auto filled where possible both support configurable styling and validation, and are mapped to docusign anchor tags for seamless placement during the signing process why it matters enables businesses to capture additional signer information—such as job title or custom notes—directly in signed documents, supporting compliance and operational requirements reduces manual errors and streamlines the e signature process by automating field mapping and default value handling between the nue template and docusign provides flexibility for revops and sales teams to tailor e signature templates to specific business needs, improving customer experience and supporting downstream workflows learn more customer use cases use case 1 a revops manager needs to ensure that every executed quote includes not just signatures, but also the signers’ official job titles and any additional information (such as a purchase order number or custom instructions) supplied by the customer by configuring "text" and "title" fields in the template builder, these details are collected seamlessly during docusign signing, reducing the need for follow up emails and manual data entry use case 2 a sales rep sends a quote for e signature using a template that includes a required "text" field for the customer to specify special billing instructions the customer fills this in as part of the docusign workflow, and the instructions are captured in the final signed pdf, making fulfillment and billing more efficient use case 3 during onboarding with a new enterprise customer, the legal team requires that all signers’ job titles be recorded in executed agreements for audit purposes the "title" field auto populates from the signer's docusign profile (or must be manually entered if missing), ensuring compliance and reducing back and forth for more details, please read docid\ i2uoxjkirteiel rez4ua enable customization of email subject and message for e signature quotes (preview) this release introduces the ability to customize the email subject and message sent to recipients when a quote is sent for e signature via docusign admins can configure organization wide defaults in system settings → integrations → docusign integration, while sales reps can override these values on a per quote basis directly from the quote detail page the feature ensures both system level consistency and per transaction flexibility, with robust validation to meet salesforce and docusign length constraints the customization is available through both the ui and api, supporting advanced automation and integration scenarios why it matters strengthens brand consistency ensures all e signature communications follow your company’s branding and tone, increasing customer trust and engagement increases sales flexibility empowers reps to tailor the message for specific quotes, enabling personalization for high value deals or sensitive negotiations reduces integration errors automated enforcement of docusign and salesforce length limits prevents failures due to technical constraints, streamlining operations learn more customer use cases use case 1 a revops manager at a saas company wants every e signature email to reflect the company’s brand guidelines they set the default subject and message under docusign integration settings, so all outgoing quote signature requests are consistently branded use case 2 a sales representative is closing a large deal and wants to add a personal touch to the e signature request on the quote detail page, they override the default email subject and message to address the customer by name and reference specifics about the deal, making the communication more engaging use case 3 an enterprise customer uses automation to trigger e signature requests via api from their crm they programmatically set the email subject and message per transaction, ensuring tailored, context aware communication for each recipient without manual intervention for more details, please read docid\ i2uoxjkirteiel rez4ua send quote for e signature via api (preview) this feature enables developers, admins, and sales users to send quotes or order forms for electronic signature using a dedicated api, integrating directly with docusign it supports enforcement of default templates, intelligent recipient pre population, customizable email content, and robust error handling the solution is designed to streamline contract workflows, ensure compliance, and support both ui and api based flows why it matters streamlines contract execution by eliminating manual, paper based processes for quotes and order forms, reducing turnaround times and administrative burden ensures business and legal compliance by allowing organizations to enforce default templates and recipient rules, minimizing user error and satisfying audit requirements provides a developer friendly, api first approach that enables automation of high volume e signature workflows and integration with broader business systems learn more customer use cases use case 1 a developer integrates nue’s e signature api into a custom workflow when a new quote is generated in their crm, an automated process triggers the api to send the quote for signature, with the system defaulting the template and recipients according to business rules the integration enables scalable, zero touch contract execution how it works post to /cpq/quotes/{quoteid}\ esign to initiate an e signature job provide templateid, recipients, and email (subject/message) in the payload; if omitted, system defaults are applied the api returns a jobid for asynchronous processing use get /cpq/quotes/e sign/jobs/{jobid} to poll for job status, including envelopeid, recipient status, and error messages system settings allow enforcement of default templates and email content, and validation ensures recipient/tag consistency please refer to the https //api docs nue io/send quote for e signature for details apply latest pricing for raw usage rating by turning off price tag snapshot this feature introduces a system level toggle in nue settings (under settings > quotes & orders), allowing administrators to disable the automatic saving of price tag snapshots on order products for usage based products when the toggle is on (default), the system saves a snapshot of the original price tag at order activation, which is then used for usage rating and change orders when toggled off, the system stops saving snapshots, and usage rating references the latest published price tag configuration at rating time this provides flexibility for customers to choose between contractual rate preservation or always using the current pricing structure, which is especially valuable for customers with large, complex price tags that exceed salesforce field limits why it matters unblocks customers with high volume, high complexity usage products whose price tag snapshots exceed salesforce field size limits, eliminating order activation errors supports dynamic pricing strategies by allowing usage rating to always reflect the latest price tag, instead of locking to the original contract rate, which many customers prefer reduces support burden and manual intervention for both customers and nue by automating the choice between contractual and current pricing models learn more customer use cases use case 1 a system admin for a saas company managing a large credit burndown product catalog faces errors when activating orders with complex tiered pricing by disabling price tag snapshots, the admin ensures smooth order processing and allows the sales team to bill usage with up to date pricing use case 2 a sales rep works with a customer who negotiates frequent mid term price changes for usage based services with the snapshot toggle off, the sales rep can ensure that all new usage is rated with the most recent negotiated pricing, supporting customer transparency and satisfaction how it works admin accesses lifecycle manager > settings > quotes & orders and locates the save & apply a snapshot of the original price tag save & apply a snapshot of the original price tag toggle when on (default), the system snapshots the price tag at order activation and uses it for rating and change orders when off, the system does not save a snapshot; usage rating and change orders always reference the latest published price tag if the snapshot is off, the system relies on the publish everything publish everything feature to ensure the latest price tag is always published and available for rating 35 api flows and ui behaviors are automatically updated based on the toggle state everything billing credits and commits page for all customers admins can now view and manage credits and commits flows across all customers from a single, centralized credits page in the nue app this includes visibility into credit burndown (prepaid credits), the new committs burndown (commits), and all associated billing activity previously, viewing customer credits required navigating to each customer's individual lifecycle manager this new page provides a unified view of commit/credit activity across the entire customer base on this page, the system displays commit flows for commit type credit pools, and credit flows for other credit or cash pools why it matters unified visibility into credits and commits , allowing admins to monitor both prepaid credit burndown and committed spend agreements from a single view eliminates context switching by consolidating all customer credit flows instead of navigating customer by customer track commit utilization in real time by seeing inflows (provisioned on order activation) and outflows (from rated usage, recurring subscriptions, professional services, or other drawdowns) monitor underspend and overspend by identifying customers approaching commit thresholds or with unused commits nearing expiration accelerate troubleshooting with powerful filtering by customer, subscription, credit pool, currency, and transaction type learn more customer use cases use case 1 a revops admin wants to understand total credit consumption across all enterprise customers for quarterly reporting using the new credits page, they select the credit pool, use the customer filter with autocomplete to narrow to enterprise accounts, and view the aggregated metrics showing total grants, consumed credits, and active credits they export the data to csv for their financial report use case 2 a finance director needs to identify all customers with potential underspend billing at quarter end using the credits page, they select the committed cash pool, view the active and pending credits across all customers, and export the data to identify which customers have significant remaining balances that will be billed as underspend how it works navigate to the credits page – go to nue app → lifecycle manager → assets > credits select a credit pool – use the dropdown to choose between your configured credit pools credit pools (unit based) cash pools (currency based) committed cash pools (for commit contracts) view credit metrics – the top section displays key statistics for the selected pool total grants – all credits ever provisioned available today – credits currently usable total balance – active + pending credits interactive status bar – a color coded bar shows the breakdown expired (gray), consumed (purple), canceled (red), active (cyan), pending (dark blue) click any segment to filter the credit flow list filter by customer or subscription – use the autocomplete search fields to narrow results to specific customers or subscriptions quick filter tabs – one click filtering for all, issued, expired, inflow, or outflow transactions configure view – refresh data, or configure which columns to display enable entity level auto numbering for invoices and billing objects this release introduces the ability to configure and manage auto numbering schemes (such as invoice prefixes and numbering formats) at the entity level in nue organizations can now assign custom invoice number formats to specific legal entities (e g , subsidiaries, country branches), ensuring each entity’s invoices, invoice items, and related records use the correct prefix and sequence this capability is available both via the ui and api, supports fallback to the org level default when needed, and enforces uniqueness so that each entity is linked to only one numbering scheme at a time why it matters enables local compliance organizations operating in multiple jurisdictions can ensure invoices and credit memos adhere to local legal, tax, and audit requirements by assigning entity specific numbering schemes (e g , “de2025xxxxx” for germany, “us2025xxxxx” for the us) improves customer experience & legacy migration customers can maintain invoice formats familiar to their clients and migrate smoothly from legacy erp or billing systems without disrupting downstream processes or integrations reduces manual errors and administrative overhead automated scheme enforcement and fallback logic minimize the risk of duplicate, incorrect, or non compliant invoice numbers, streamlining operations for billing and revops teams learn more customer use cases use case 1 a multinational saas company operates subsidiaries in the us, germany, japan, brazil, and china each entity must issue invoices with unique prefixes—such as “us2025xxxxx” for the us and “de2025xxxxx” for germany—to meet local compliance rules with entity level auto numbering, the finance team configures the correct numbering scheme per entity, ensuring seamless audits and regulatory alignment use case 2 a single entity business has recently migrated from an on premise erp where invoices used a branded prefix (e g , “acme {00000}”) the admin customizes the default numbering format in nue to match legacy expectations, preserving continuity for both internal processes and external customer communications use case 3 a revops admin is tasked with updating the invoice numbering scheme for a newly acquired subsidiary through the nue ui, they quickly add a custom auto numbering rule, link it to the new entity, and verify that all subsequent invoices follow the new format—without affecting other entities or requiring code changes how it works users access system settings → business objects → fields; “auto number” fields display a configuration link a modal lets users view, edit, or add auto numbering schemes, including display format, starting number, and associated entities only one scheme can be linked to each entity; deleting a scheme reverts affected entities to the org level default the feature is available via both ui and patch api endpoints (with “entitysettings” support) dependencies and limitations only available for billing objects that support auto numbering invoice, invoice item, invoice item detail, credit memo, credit memo item, and credit memo item detail an entity can be linked to only one auto numbering scheme per object for integrations (e g , stripe), be aware of external system character limits—if an invoice number exceeds the third party’s max length (e g , 26 chars for stripe), the external system may default to its internal scheme and the invoice sync may fail related resources please refer to docid\ o 0igphmo7s rhoz26g0i for more details automate invoice dunning and collections nue dunning automates the process of overdue invoices through configurable, multi stage email reminders, dynamic customer segmentation, and seamless integration with nue payment link administrators can define custom dunning strategies by segment, schedule escalating reminders with default predefined templates or other email templates, and enable payment links for fast resolution the feature supports robust monitoring, export/import of settings for migration and sandbox management, and is designed to minimize manual collection efforts and involuntary churn why it matters reduces manual collections workload by automating reminders, and escalation for overdue invoices and failed payments, freeing finance and revops teams to focus on higher value activities improves cash flow and revenue retention by segmenting customers and tailoring dunning strategies to risk, region, or value, resulting in higher recovery rates and lower involuntary churn learn more customer use cases use case 1 a global b2b business configures dunning rules by region and currency when an invoice becomes overdue, customers receive reminders in their local language and time zone, using salesforce based templates finance teams monitor dunning effectiveness in real time dashboards, enabling them to adjust segmentation use case 3 a multi entity organization uses nue dunning’s export/import apis to migrate its collections policy from production to a new sandbox environment after testing new reminder templates and segmentation filters, the admin imports the configuration back to production for a seamless rollout, ensuring consistency and compliance across all business units how it works admin enables dunning and configures up to 10 customer segmentations segmentation can be based on risk tier, region, size, payment history, and more each reminder rule specifies timing (e g , 7, 15, 30 days overdue) and email template automated workflow triggers reminders only for eligible, active invoices in open, transferred, partially paid, or transfererror status dependencies and limitations requires collections module access and appropriate permissions ("view invoice dunning" and "manage invoice dunning") only active invoices with payment status open, transferred, partially paid, or transfererror are eligible for dunning maximum of 10 segmentations and 10 reminders per segment integration with downstream payment systems (stripe, netsuite, quickbooks) must be configured for payment links and activity updates related resources please refer to docid\ hwi064p69fwlgik8m3flr for more details integrations action required quickbooks integration oauth upgrade & required re‑authentication quickbooks integration oauth upgrade summary all quickbooks integrations using tray’s shared oauth app were at risk of disruption due to intuit’s deprecation of shared oauth credentials we have migrated to a new quickbooks connector to ensure continued reliability and improved security what’s changed authentication has been upgraded to use a new quickbooks connector, ensuring continued access to the quickbooks integration and strengthening oauth security existing workflows have been validated to continue working as expected once re authentication is completed with the new connector customer impact reauthentication required all customers with an active quickbooks integration must reauthenticate using the new connector gl account mappings must be reconfigured as part of this change, customers will need to redo their quickbooks gl account mappings and should validate that their nue authentication is still present when reconfiguring the integration, as this is technically a breaking change customer communication & deadline we have sent a customer email titled “action required quickbooks integration” outlining the exact steps required to update the integration this update requires immediate attention from all customers currently using a quickbooks integration cut off date all quickbooks customers must complete the migration by december 31 to avoid any risk of integration failure or disruption after this date developer experience update quotes, set primary, and automate lifecycle actions via nue object api this release delivers comprehensive object apis to https //api docs nue io/update objects and delete quotes and opportunities, including setting and toggling the primary quote flag, updating discounts, start dates, and addresses and to manage quote lifecycle actions such as updating a quote's start date and closing won an opportunity when an opportunity is marked as close won, the system automatically generates subscriptions, assets, and entitlements from the primary quote, aligning with industry best practices for automated quote to cash flows the apis also enable querying and deleting of quote, quote line item, and opportunity metadata for downstream integrations and reporting these nue object apis are easy to use and fully compatible with salesforce metadata including https //api docs nue io/manage custom fields while relying on a nue api key that uses the existing oauth integration with salesforce, making the apis straightforward to authenticate and access these apis also fully honor the salesforce object and field permissions granted to the integration user why it matters dramatically reduces manual intervention and streamlines sales, finance, and revops processes by automating key lifecycle actions on quotes and opportunities, including downstream provisioning of subscriptions and entitlements improves data quality and compliance by enforcing only one primary quote per opportunity and providing robust validation, recalculation, and error/warning messages for all updates enhances integration flexibility, enabling both ui and api driven workflows for internal teams and partner systems, and providing full auditability for automated quote to cash operations learn more example scenarios patch /quotes/{id} updates header fields ( discount, start date, isprimary, status, opportunityid, addresses, custom fields ) with smart recalculation and validation setting isprimaryquote=true synchronizes opportunity lines and amount, enforcing one primary quote per opportunity patch status="accepted" updates quote lifecycle state post /opportunities/{id}/ finalizes the primary quote into an order and, upon activation, provisions subscriptions, assets, and entitlements get endpoints for quotes, quote line items, and opportunities support metadata querying for reporting and integration comprehensive validation conflicts (e g , trying to set both template and primary), invalid fields, and mutually exclusive discounts are flagged with clear error messages patch endpoint supports all updateable quote header fields (name, description, discounts, dates, billing/shipping, isprimary, status, opportunityid, custom fields) bug fixes everything billing non admin users can now send docusign envelopes from salesforce non admin users can now successfully access and use the “send for e‑signature” feature in salesforce to initiate docusign envelopes this restores expected functionality for all user roles, ensuring that sales representatives and other non admin team members can efficiently send documents for e signature without encountering errors invoice pdf download header and item alignment issue resolved previously, when downloading invoice pdfs, some customers experienced a formatting problem where the invoice line headers and items extended beyond the page margins with this fix, all invoice components—including headers and line items—now consistently appear within the correct margins in downloaded pdfs, matching the layout shown in the preview improved sorting for quote line items using the sort order field users were unable to sort quote line items using the sort order field within the order form – e signature integration module with this update, users can now reliably sort quote line items by the sort order field this enhancement streamlines the quoting process, making it easier to present and manage line items in the desired order pdf generation now honors selected template on quotes previously, when generating or previewing a pdf from a quote, the system would always use the template set as the quote’s default—even if that template was unpublished or a different template was explicitly selected by the user with this fix, the generate pdf component now correctly uses the template explicitly selected by the user, regardless of any default template set on the quote if the default template is unpublished, it will be ignored, and only published, user selected templates will be rendered improved invoice sync for self service customers with salesforce integration previously, invoices generated for customers created via the self service api were not being properly synchronized to salesforce during the invoice daily sync job with this fix, invoices for customers created through the self service api are now reliably included in the invoice daily sync job and correctly synchronized to salesforce this ensures that all invoice data is consistently reflected in salesforce, improving data accuracy and supporting seamless financial operations developer experience fix call stack overflow in bundle configurator ui component nue self service ui’s bundle configurator component (nueproductdialogbundleconfigure) previously caused a call stack overflow when users changed configuration inputs, causing crashes in specific configurations with the release of nue self service ui version 0 0 80, input changes are now handled gracefully, and the bundle configurator enforces all product option and validation rules in real time enable client side pricing engine to honor grandfathered price tags the nue client side pricing engine now fully supports "grandfathered" price tags—private, customer specific pricing or discount tags inherited from legacy contracts or prior agreements previously, when a subscription with such a tag was updated (for example, quantity changed) through the self service portal, the client side engine failed to recognize and apply the grandfathered tag, leading to incorrect pricing with this release, all relevant price tags—including grandfathered/private tags—are included in the pricing input, and the client side engine honors them in all calculations