Release 2509

🚀 release 2509 is live in sandbox ! 🗓️ production deployment is scheduled for january 6, 2026 this release introduces key enhancements including a unified credits page for monitoring customer credit flows, entity level invoice auto numbering for multi jurisdictional compliance, and improved e signature capabilities with enforced default templates and customizable text/title fields in docusign workflows multiple bug fixes address pdf generation issues, invoice syncing for self service customers, and developer experience improvements including call stack overflow and grandfathered pricing tag support 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 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 everything billing view all customer credit flows in a unified credits page admins can now view and manage credit 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 credit activity across the entire customer base 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 integrations action required quickbooks integration oauth upgrade & required re‑authentication 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 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