Release 2506 - 09/23/2025

this release streamlines subscription and billing management with expanded quote editing, granular product and pricing controls, real time payment failure webhooks, and enhanced integrations, such as supporting avalara tax for quickbooks and netsuite, automated qbo invoice write offs, and instant qbo payment links in salesforce, while improving auditability, compliance, and sales efficiency through seamless draft order sync, improved metadata visibility, and accurate data updates feature enhancements lifecycle manager add additional subscription changes on quote phase ii this capability was initially introduced in release 2505 1 08/07/2025 docid 5qgswydfdautpj7qnw 9s , allowing limited change types renew and update quantity to be added directly within the quote line editor with this release, we’re expanding support to include the following change types renew with quantity update adjust price update term reconfigure convert free trial cancel sales reps can now stack stack , edit, and manage all supported subscription changes directly within the line editor edit, and manage all supported subscription changes directly within the line editor , without navigating away this enables a seamless, multi action workflow complete with undo/redo capabilities for fast, accurate, and flexible lifecycle management why it matters minimizes errors and training time by surfacing validations and error messages immediately, preventing incompatible change combinations before they reach backend systems learn more customer use case use case 1 a sales rep working on a renewal quote for a standalone saas subscription realizes that the customer also needs to increase license quantity and adjust pricing instead of navigating back to lifecycle manager, they click the 'add additional changes' icon in the line editor, stack all needed changes (renewal, quantity update, price adjustment), review visual status messages, and apply them instantly the system tracks each change and allows quick undo/redo for corrections, leading to a one pass quote and faster deal closure use case 2 for a customer with an add on product's tiered price tag linked to a bundle quantity, the rep can update the bundle quantity and adjust the add on's price usung true up to current quantity tier true up to current quantity tier in one flow the modal drawer filters available actions, ensuring only eligible changes are shown the rep receives clear feedback about incompatible actions, ensuring data accuracy and compliance use case 3 sales reps can now seamlessly process bundle renewals and reconfigurations in a single, streamlined workflow directly within the line editor ahead of renewal, reps can swap out bundle components—such as upgrading analytics modules or expanding security features—while receiving real time validation and compatibility checks both the renewal and reconfiguration actions are tracked through instant status messages, supporting undo/redo as needed the result is an accurate, consolidated quote for the updated bundle, reducing manual steps, minimizing errors, and improving customer onboarding efficiency how it works add additional changes add additional changes icon displays for each eligible subscription line in the line editor grid user selects a change from the side drawer which opens up, fills in details, and clicks add change to quote add change to quote additional changes panel tracks up to three most recent changes, with undo/redo actions per subscription system blocks incompatible change combinations and provides real time error feedback dependencies and limitations standalone products, add on products & bundles are fully supported in 2506; bundled products and assets/entitlements are not yet available for additional changes in the line editor only one line editor change can be stacked at a time before saving; users must save after each change to reset the undo/redo queue some change type combinations are blocked per business logic (e g , stacking update term with renew) get more details & examples here https //docs nue io/lifecycle manager overview#uqsds enable product filters for change order pricing logic this release introduces the ability for revops admins to precisely configure which subscriptions and products should carry forward their net sales price (nsp) on renewal and change orders versus which should use conditional recalculation logic based on current price tags and discounts using advanced product and subscription filters, admins can set granular policies by product, revenue model, category, or other criteria why it matters empowers admins to apply granular, filter based logic—supporting complex pricing, compliance, and business requirements across product lines, revenue models, and customer segments learn more customer use cases use case a saas company’s revops admin can use advanced pricing controls to set different pricing logic by product type and revenue model for usage based products (e g , api call overages), the reuse net sales price reuse net sales price setting ensures the net sales price is carried forward automatically on renewals and change orders, providing rate consistency and reducing manual errors for traditional recurring products (e g , subscriptions), the system applies recalculate using pricing logic recalculate using pricing logic to update prices based on current list price, tags, and discounts, keeping pricing up to date admins configure these policies using product and revenue model filters in the lifecycle manager, allowing granular, automated control that matches complex business requirements how it works admins can navigate to change order pricing change order pricing settings in the quotes & orders section, enabling the reuse net sales price reuse net sales price or/and recalculate using pricing logic recalculate using pricing logic settings advanced filters for each of these settings allow targeting by revenue model, product, start date, or category (advanced filters override simple ones) if no tags/discounts qualify, fallback logic reuses previous term’s net sales price, preventing unwanted resets dependencies & limitations by default, enabling any single setting applies to all products; advanced filters must be configured for granular control on renewal/change order, if both reuse net sales price reuse net sales price and recalculate using pricing logic recalculate using pricing logic are enabled for a product, reuse net sales price reuse net sales price takes precedence edge cases discounts/tags must be present and active for recalculation logic if filters are misconfigured or left unset, default logic applies to all products for imported orders lacking nsp, fallback may revert to list price if no qualifying conditions exist users must ensure that discount fields are used appropriately; if no discount is entered, nsp will match the list price & any previously applied price tag will be carried forward related resources read more here change order pricing docid\ kfvznlsd7qf saxljp il define product access rules for custom user groups product access configurator lets system admins define granular rules based on which specific users, salesforce profiles, or roles can view and select specific products in nue's quote and order builder this feature provides a direct, admin facing ui to configure product visibility, with advanced logic to target individual users, multi select profiles and roles, or combinations thereof rules are enforced dynamically, with instant updates to product lists for sales reps based on active access rules the configurator bridges a gap where salesforce only supports object level security, enabling true product level permissions for enterprise and partner channel sales why it matters enables enterprise grade control over product catalog visibility, helping companies comply with sales policies and regional restrictions reduces quoting errors and unauthorized product sales by ensuring sales reps only see eligible products and pricebook entries supports scalable, secure partner and multi channel enablement, critical for companies with complex sales organizations learn more customer use case use case 1 a company launches a new upsell bundle, but only wants its senior sales team and partner channel to access it during the launch phase the admin defines an access rule restricting access to this bundle for those other users, profiles, and roles only the targeted group can see and sell the new bundle, while others remain restricted until the rule is updated or deactivated use case 2 a global organization with multiple partner channels needs to restrict certain skus to specific users in different regions, ensuring compliance with local pricing and product regulations the admin uses advanced rule logic in the configurator, selecting multiple profiles and roles per region, and sets product visibility accordingly when rules are updated, the product list for each user instantly reflects the changes how it works admin accesses product access configurator via price builder settings new access rules are created using a ui modal, with options for simple (user level) or advanced (profile/role based) targeting product and pricebook selection is performed with dynamic multi select modal, supporting granular sku level restriction all rules start inactive and must be explicitly activated; only inactive rules can be deleted the rule engine enforces dynamic product filtering for end users, updating add products panels in real time dependencies & limitations requires up to date salesforce profile and role mappings; any org configuration changes may impact rule effectiveness deleting active rules is not permitted—must deactivate first legacy access logic migration needs careful mapping to avoid gaps or disruptions currently we are offering only product level control, we are working on enabling price book entry level control for more details on set up, use cases & configuration refer to product access rules docid\ rsezy8zarqwa7l2svkud6 everything billing raise payment error webhook events this feature introduces real time webhook notifications whenever a payment attempt (such as a credit card charge or ach debit) fails in the recurring payment process each failure triggers a detailed, structured webhook event ("payment failed") containing the payment context, customer info, payment application details, error codes, etc why it matters enables seamless integration integrations (e g , hubspot, custom ipaas) can instantly trigger dunning, workflow, or alerting actions based on failure events, minimizing manual work and lowering operational overhead learn more customer use case use case 1 a saas provider integrates nue’s webhook with their crm and support platforms when a customer's credit card payment fails, the webhook instantly triggers a support ticket, sends a personalized email via hubspot, and tags the account for sales follow up the customer receives a clear notification with a link to update their payment method, and the support team can proactively assist if issues persist how it works upon payment failure (e g , stripe, ach), a "payment failed" webhook event is assembled, including payment, customer, payment application, and error attributes event is published to a durable outbox and delivered to all configured webhook endpoints for the tenant dependencies and limitations enablement requires webhook endpoint(s) to be registered and enabled for the tenant edge cases if the payment gateway does not return a detailed error code, error context may be limited webhook delivery can be delayed in rare cases of system outage or network partition developer experience sync draft orders between nue and salesforce this feature enables seamless, bi directional synchronization of draft (unactivated) orders—including all line items, discounts, and billing settings—between nue and salesforce draft orders can be initiated from either direct sales (salesforce) or self service (nue), with configurable settings to control automatic or manual sync this supports use cases such as tracking self service cart abandonments for sales follow up, pushing direct sales draft orders to the billing portal for customer self checkout, and ensuring that any changes made to draft orders propagate accurately before activation why it matters increases revenue capture by enabling reps to monitor and follow up on abandoned self service carts, reducing missed opportunities streamlines deal closure by allowing reps to initiate draft orders in salesforce and push them to the billing portal for customer self checkout, reducing sales cycle friction learn more customer use case use case 1 a saas customer’s end user begins a self service checkout in the billing portal but abandons the cart before completing payment the system automatically syncs the draft order to salesforce, where a sales rep can see the abandonment the rep reviews the customer’s cart, initiates a follow up call, offers a sign up discount, and successfully closes the deal by activating the order directly from salesforce use case 2 a sales rep working a complex enterprise deal in salesforce prepares a quote, then finalizes it into a draft order using the sync draft order button, the rep pushes the draft order to nue’s billing portal, where the customer completes self checkout and payment after getting sign off from the decision maker the system updates the status in both salesforce and nue, ensuring both teams remain aligned how it works admins enable sync settings for nue > salesforce sync draft orders can be synced manually with a “sync order” button from salesforce to nue activation respects the system of origin, meaning a self service order activated in salesforce always activates from nue and syncs back to salesforce and vice versa integrations supporting avalara tax in quickbooks online invoices this feature enables nue to accurately transfer avalara calculated sales tax to quickbooks online (qbo) invoices—despite qbo’s limitation that prevents line level or custom tax overrides when enabled, the integration disables qbo’s native tax engine and adds a summary “sales tax” line item (using a configurable qbo service item) for the total avalara tax, mapped to the correct gl account admins can configure tax item, tax codes, and automation settings to ensure accurate, auditable invoice tax representation and full compliance with u s and global tax laws why it matters ensures tax compliance and audit trail invoices in qbo now exactly reflect avalara’s tax calculation, which is critical for financial audits, regulatory filings, and customer trust solves a core quickbooks limitation automates a widely accepted industry workaround for external tax (avalara) in qbo, eliminating manual workarounds and reducing errors reduces risk of double taxation clear configuration disables qbo’s tax if avalara is on, so tax is not accidentally compounded—protecting your customers and your company learn more customer use case use case 1 a saas company operating in multiple u s states uses avalara for sales tax because rates and rules vary by product and location when they generate an invoice in nue, avalara calculates the correct tax previously, this tax total could not be pushed into qbo due to quickbooks’ tax engine constraints with this feature, the full avalara calculated tax is now displayed as a “sales tax” line on the qbo invoice, matching nue’s calculations, ensuring compliance and making reconciliation seamless use case 2 a finance team audits invoices to prepare state sales tax returns they need a reliable record of the exact tax collected by jurisdiction with the avalara summary tax line in qbo, they can trace every invoice’s tax to the avalara system for reporting and audit, even though qbo’s own sales tax reports do not include these manual lines use case 3 a company issues a refund or negative invoice the same logic applies if avalara tax is involved and the summary tax line feature is configured, the refund is accurately represented as a negative tax amount line in qbo, ensuring downstream accounting and compliance remain correct how it works admins choose in nue whether to send the avalara tax summary line to qbo or use qbo’s native tax calculation if enabled, nue calculates the tax, disables qbo’s tax engine (sets a 0% header tax code), and adds a summary “sales tax” line item for the avalara tax amount the qbo service item for tax must be mapped to the sales tax payable gl account optional configuration allows all invoice lines to be marked as “taxable” for qbo reporting if configuration is missing or invalid (e g , missing tax item or tax code), the invoice sync fails with a clear error to the admin user for further documentation, please refer to quickbooks integration setup docid 6ry9nsmzdwog ci2judm1 supporting avalara tax in netsuite invoices this release automates the mapping of avalara tax totals, calculated in nue, directly to the tax total field at the header level on netsuite invoices previously, avalara tax was only visible on the nue invoice or required custom field mapping at the line item level in netsuite, leading to reporting and reconciliation gaps with this enhancement, the tax calculated by avalara is always included in the main tax summary of every synced netsuite invoice, ensuring compliance, reducing manual work, and supporting large scale migrations—no custom mapping required why it matters ensures 100% tax data fidelity between nue and netsuite for all invoices, supporting audit ready, accurate revenue recognition and compliance reduces manual setup, configuration errors, and ongoing admin effort—no more custom field mapping or line level workarounds for tax supports high volume customers with large scale migrations, enabling automated, scalable tax handling for every invoice and credit memo learn more customer use case use case 1 a finance operations manager at company x activates an invoice in nue with avalara tax when the invoice syncs to netsuite, the tax total appears automatically in the netsuite invoice header, matching nue’s calculated amount this allows pdq’s accounting team to close books and prepare tax filings without manual reconciliation or risk of audit discrepancies use case 2 during a stripe/nue/netsuite workflow, a customer pays via stripe, but the final accounting is done in netsuite with this feature, the avalara tax is present at the header level in netsuite, ensuring the payment and accounting records always align, even across systems use case 3 when a subscription is refunded and a credit memo is generated, the header level tax mapping ensures the credit memo in netsuite accurately reflects the original tax, supporting correct reversals and downstream reporting how it works avalara tax is calculated during invoice creation in nue and is recorded at both the line and header levels the netsuite integration (via tray workflow and bundle script) automatically maps the avalara tax total to the tax total field at the netsuite invoice header the process supports both tax inclusive and tax exclusive models, and maps $0 tax lines unless suppressed by configuration custom item level mappings for tax are now deprecated and automatically disabled when header level mapping is active additional metadata such as “created from nue” and “nue transaction #” is also synced for audit trails and reconciliation technical details requires nue’s avalara integration and the updated netsuite bundle (nue tax user event script) deployed in your netsuite instance script runs on both create and edit events in netsuite, ensuring header level tax is always mapped tax mapping is always on for customers using avalara and netsuite—no additional setup required the transaction hub tracks sync status (transferred, not transferred, error) for invoices and provides actionable error messages and retry options redundant custom field mappings for tax at the item level are turned off to avoid double mapping write off invoices to quickbooks online (qbo) this feature ensures that when a finance user writes off an invoice in nue, a corresponding credit memo is created and applied to the invoice, the balance is zeroed out, the payment status is updated to “written off,” and the same write off is mirrored in qbo the process is fully automated, audit tracked, and prevents race conditions, ensuring financial accuracy and compliance across both systems why it matters ensures ar and bad debt accuracy uncollectible invoices are properly written off in both nue and qbo, maintaining accurate accounts receivable and bad debt tracking in line with gaap and audit requirements eliminates manual double entry finance teams can initiate and complete write offs directly in nue, and the workflow ensures that qbo is updated automatically, reducing manual work and risk of errors improves audit trail and operational efficiency all write off actions, downstream syncs, and errors are logged in transaction hub, supporting full auditability and fast identification of issues learn more customer use case use case 1 a finance operations user identifies an overdue invoice in nue that is deemed uncollectible from the collections ui, they select "write off " the system generates a credit memo for the invoice’s remaining balance, applies it, and sets the invoice status to “written off ” instantly, a webhook triggers the creation and application of a matching credit memo in quickbooks, zeroing out the invoice there as well use case 2 a partially paid invoice remains with an outstanding balance after several collection attempts the user writes off the remainder nue creates and applies a credit memo for the remaining amount, which is then mirrored in qbo via integration, ensuring both systems reflect the written off status for proper ar and bad debt reporting use case 3 during an audit, the finance team must prove all ar write offs are compliant and synchronized across systems transaction hub provides a history of every write off action, the downstream sync status, and any error traces, supporting full audit requirements and reconciliation how it works write off is available for active invoices with a non zero balance user triggers the write off in nue collections ui or via api nue creates and applies a credit memo of type “writeoff ” invoice balance is set to zero; status is marked “written off ” a webhook event (invoice written off) is fired, triggering the downstream sync to qbo qbo receives the credit memo, applies it to the invoice, and marks it as paid by credit/write off all actions, including sync failures, are logged in transaction hub for review and troubleshooting supporting quickbooks payment link within nue on salesforce invoices enables salesforce users to access and share quickbooks online (qbo) payment links directly within salesforce invoice records, streamlining customer collections and bringing feature parity with stripe integration the solution automatically syncs the qbo payment link (invoicelink) to the custom field ruby paymenthostedurl c on salesforce invoices whenever payment collection is enabled and a valid email exists on the customer or bill to contact why it matters accelerates payment collections by allowing sales reps to instantly share qbo payment links with customers from within salesforce, reducing manual steps and delays improves customer experience by making payment instructions clear and immediate, decreasing confusion and friction in the collections process enhances operational efficiency for finance and sales teams, providing direct access to qbo invoices for audit, reconciliation, or error resolution—without switching platforms learn more customer use case use case 1 company a's sales team regularly sends invoices from salesforce and needs to provide customers with a secure, one time payment link with this feature, when an invoice is synced with qbo and payment collection is enabled, the system automatically retrieves the invoicelink and adds it to the salesforce invoice record sales reps open the invoice record, copy the payment link, and send it to the customer, who can pay online immediately—reducing payment lag use case 2 finance users responsible for collections and reconciliation can view the qbo payment link directly in salesforce, click through to the qbo invoice for deeper investigation, and resolve payment issues or disputes without manual lookup or system toggling this cuts down investigation time and improves accuracy use case 3 administrators configuring salesforce for new product launches or markets can ensure payment fields are visible on invoice layouts they update the salesforce invoice page layout to include ruby paymenthostedurl c, enabling their teams to benefit from automated payment link population for every qbo enabled invoice how it works qbo payment link (invoicelink) is automatically synced to ruby paymenthostedurl c on salesforce invoice records when payment collection is enabled and a valid bill to email is present integration logic only populates the field if qbo is the payment system and the invoice has a valid invoicelink, preventing blank or placeholder urls salesforce admins must add the custom field to their invoice page layout for reps to access it; once configured, links show on new or updated invoices field population is automated through nue’s integration, leveraging api support for payment link updates (not externalinvoiceid, which is deprecated) for further documentation, please refer to https //docs nue io/collect payments via quickbooks#sbfuw defaulting email recipient mapping from billtocontact on invoices to qbo invoices and credit memos this feature automates and enhances how recipient email addresses are managed for invoices and credit memos sent from nue to quickbooks online (qbo) previously, billemail address in qbo was only set for invoices when “save and send later” was selected, and it always used the customer’s primary email with this release, billemail address is always set when possible, using a smarter mapping it first checks for a billtocontact on the invoice (and uses their email if available); if not, it falls back to the customer’s primary email this same logic is now applied to credit memos, not just invoices additionally, users can now configure whether invoice/credit memo emails are sent immediately, saved for later, or not sent at all, via a new integration setting why it matters ensures correct recipient is always used for both invoices and credit memos, reducing risk of misrouted or undelivered financial documents and improving collection efficiency supports more complex customer structures (such as third party billing contacts, subsidiaries, or dynamic recipient management) without requiring manual intervention or custom scripting unlocks downstream automation and integrations—such as qbo’s invoicelink (hosted payment link in salesforce, etc )—which require billemail address to be set for their features to work learn more customer use case use case 1 a saas company with multiple bill to contacts per customer account needs to ensure that the correct billing recipient gets the invoice—even when the person handling billing changes from month to month with this enhancement, whenever a new invoice is generated, the integration checks the billtocontact on the invoice; if an email is present, it’s used for delivery if not, it falls back to the main customer email—ensuring no manual updates or missed invoices use case 2 a consulting firm often issues credit memos for adjustments, disputes, or refunds previously, these were sent only to the account owner now, the system uses the bill to contact from the original invoice when available, so the right finance contact always receives credit memos—reducing confusion and speeding up resolution use case 3 a finance team wants to manually review invoices before sending them to customers, but occasionally needs to send batches automatically for recurring subscriptions the new configuration setting allows them to choose between “send now,” “save and send later,” or “save only” for each scenario, improving compliance and reducing accidental sends how it works on invoice or credit memo creation, the integration queries invoice for billtocontact; if found, uses that email for billemail address if billtocontact is absent, uses the customer’s primary contact email if both are missing, leaves billemail address empty (and invoice is not sent) applies to both immediate send and “send later” workflows; behavior is configurable via integration settings all actions are auditable in the ui for transparency and compliance bug fixes lifecycle manager fix for “primary quote” checkbox sync issue on opportunities previously, when users unchecked the “primary quote” checkbox, the primary quote field on the related opportunity continued to display the previous value instead of being cleared as expected this led to confusion, as opportunities could appear to have an active primary quote even after the corresponding checkbox was disabled with this update, unchecking the “primary quote” checkbox now correctly clears the primary quote field on the opportunity this ensures opportunities always reflect the current state of quote selection, improving accuracy for sales teams and enhancing confidence in opportunity data updated propagation rules for price/discount tags from bundles to child products the updated business logic for propagating price and discount tags from bundles to add ons ensures that quantity based tags are only pushed to add ons sharing the same quantity dimension (such as “user/month” to “user/year” or “user”), while term based tags are only applied to add ons with a term dimension (like “each/month”), and never to one time products or services lacking this structure this refined approach increases flexibility for term based tags but maintains strict rules, so tags are never propagated to incompatible add ons, resulting in improved pricing accuracy and clearer discount applications across bundle structures everything billing auto charge metadata visibility restored previously, the 'auto charge enabled' property was not exposed in the system metadata as intended this meant users and integrators could not readily see or leverage this setting within their workflows, leading to potential confusion and reduced transparency regarding automatic charging configurations with this update, the 'auto charge enabled' attribute is now properly displayed in the metadata customers will gain clear visibility into whether auto charge is active on applicable items, resulting in better clarity and easier management of charging settings