Release 2602.1 - 03/19/2026

🚀 release 2602 1 is now live in sandbox and production ! this release introduces powerful programmatic quote and order creation apis — both apex global methods and rest — that run the full pricing engine, enabling ai agents, self service portals, and automated workflows to create and manage the complete revenue lifecycle subscription management gets a major upgrade with subscription level renewal uplift now applied automatically, the lifecycle manager embedded directly into the quote line editor by default, and conditional e sign recipients that route deals to the right signers based on quote and account data billing operations are also improved with autocharge on invoice due date to honor net terms, a setting to suppress zero amount invoices from salesforce sync, and several bug fixes covering multi currency arr accuracy, dynamic bundle price tag preservation, and a streamlined subscription change workflow feature enhancements lifecycle manager create quote/order global method & revenue lifecycle apis this release introduces comprehensive programmatic quote and order creation capabilities developers and ai systems can now create fully priced new business quotes, orders, and lifecycle changes — renewals, expansions, cancellations, upgrades — through two complementary api surfaces docid\ zhw7oqjusp3vwhnyohvr for salesforce native integrations and https //api docs nue io/create quote overview for external systems both apis execute the same pricing engine used by the nue ui, ensuring pricing fidelity across all channels additionally, docid\ zhw7oqjusp3vwhnyohvr have been published alongside the apex documentation, enabling ai agents to generate correct, runnable apex code from plain english business scenarios why it matters revenue operations at the speed of code until now, creating quotes and orders with accurate pricing required manual entry through the nue ui or complex low level api calls these new apis collapse what used to be multi step, error prone workflows into single semantic calls — describe what you want (products, quantities, terms, discounts), and the pricing engine handles the rest ai first design — structured error codes, warning messages, and preview mode enable ai agents to create, validate, and self correct quotes autonomously, reducing manual intervention in automated workflows full pricing fidelity — every api call runs the complete pricing pipeline product resolution, bundle expansion, discount propagation, price tag evaluation, tax calculation, and business rule validation — identical to the nue ui preview before commit — non destructive preview mode lets teams validate pricing, run what if scenarios, and catch errors before persisting records, de risking automated and ai driven workflows complete lifecycle coverage — from initial quote creation through renewals, expansions, price adjustments, and cancellations, the apis cover the full revenue lifecycle in a composable, programmatic interface channel flexibility — apex global methods for salesforce native automation (flows, triggers, custom uis) and rest apis for external integrations (storefronts, partner portals, erp systems, ai agents) — same pricing engine, two access patterns learn more customer use cases ai driven quoting — ai agents use these apis to generate and validate quotes from natural language instructions, leveraging structured error feedback to self correct self service portals & e commerce — build checkout experiences that create orders directly via rest, with real time pricing previews before commitment automated renewals & lifecycle management — programmatically renew subscriptions with price uplifts, expand seat counts, or cross sell new products — all in a single composable api call integration middleware — connect nue pricing to external cpq, erp, or billing systems via rest, ensuring consistent pricing across all revenue touchpoints salesforce native automation — trigger quote/order creation from salesforce flows, apex triggers, or scheduled jobs using the global methods, with full access to the pricing engine bulk operations — batch create quotes or orders from imported deal data, migration scripts, or automated pipeline processes technical details apex global methods ruby globalquoteserviceapi createquote() , ruby globalorderserviceapi createorder() , and ruby globalchangeorderservice changeorder() — covering new business and lifecycle changes with full preview and commit mode support rest apis post /cpq/quotes , post /cpq/quotes\ preview , and get /cpq/quotes/{quoteid} — authenticated via nue api key header, supporting the same product resolution, bundle expansion, and pricing pipeline ai coding skills published as part of the apex documentation, these skills enable ai systems to translate business scenarios into correct apex code — covering new business quotes/orders and change orders (renewals, expansions, cancellations, upgrades) with interaction patterns, examples, and mistake avoidance rules documentation apex global methods https //docs nue io/create quote global method revenue lifecycle rest apis https //api docs nue io/create quote overview enable "allow subscription lifecycle management from new or existing quotes" in the line editor by default the “allow subscription lifecycle management from new or existing quotes” setting is now enabled by default , making it easier than ever to manage subscription changes directly within the quote line editor building on the capabilities introduced in docid\ yq86ln5oaexnlkzwwyjpp , this enhancement reflects a more streamlined and intuitive workflow where reps can handle renewals, mid term price adjustments, co terming, quantity and term updates, etc all without leaving the quote lifecycle manager functionality is now seamlessly embedded into the quoting experience, allowing reps to update existing subscriptions (including bundles) and instantly see prorations and pricing impacts, powered by the pricing engine running directly in the browser why it matters this change significantly simplifies the quoting and amendment process while reducing errors reps no longer need to switch between lifecycle manager and the quote, enabling all subscription changes to be managed in a single, unified interface built in safeguards also prevent duplicate subscriptions by alerting reps when a product already exists on a customer’s subscription and guiding them to amend instead of creating a new one the result is faster deal execution, greater pricing transparency with real time calculations, and a more intuitive user experience that aligns with how modern sales teams operate apply subscription level uplift on renewal nue lifecycle manager now supports contractually agreed, subscription level renewal uplift percentages that are applied automatically during renewal, visible to sales reps in the renewal modal and line editor, and persisted across quotes, orders, and subscriptions uplift is implemented as an automatic adjust price (negative discount) on top of the net sales price, works alongside net sale price–based renewal pricing, and can differ per subscription & applied on net renewal price instead of being a single global setting in form of a tag why it matters prevent revenue leakage by automatically enforcing annual renewal uplifts that were negotiated in contracts (e g , 1 5% per year), without requiring reps to manually calculate and apply adjust price lines for each subscription it honors existing subscription level uplift rates while keeping renewal pricing anchored to contracted net sale price rather than fluctuating list prices, which is critical for customers migrating with tens of thousands of uplift bearing subscriptions for more details read docid\ cbl2nm4uiqkcbv1lvxgqy everything billing configure conditional e sign recipients in the template builder this feature lets template designers and admins configure e signature recipients with conditions so that additional signers (e g , legal, finance, procurement) automatically appear or stay hidden based on quote and account data, without needing separate quote templates or admin intervention why it matters reduce dependency on revops/admins for adding new signers by allowing conditional additional recipients to be configured once in the template builder and reused dynamically across deals improve compliance and risk management by ensuring extra approvals (e g , legal on high value or long term deals) are automatically enforced using rules like quote amount, term, or account type, rather than relying on reps to remember separate templates or playbooks learn more customer use cases use case 1 – high value deal with legal as a conditional signer a sales rep is closing a large enterprise deal revops has configured an internal “legal” recipient in the template builder with visibility criteria quote amount > 10000 and a dedicated tag, signing order, and role when the rep sends an order form for e signature, the system evaluates the current quote total because this particular quote exceeds 10,000, the legal signer is automatically included in the e signature recipient list if the rep sends a smaller deal later, the legal recipient will not appear at all the rep never has to switch templates — legal participation simply follows the rules revops defined once in the template use case 2 – long term contracts requiring extra approval an account team negotiates a 36‑month contract in the template builder, revops has defined an additional “finance approver” recipient with the visibility condition of subscription term >= 24 when the quote term is 12 months, the finance recipient is hidden, and the envelope only includes the standard customer and internal signers when the same template is used for a 36‑month quote, the finance approver is automatically added in the appropriate signing order this ensures long‑term commitments always route through finance, driven by the quote term rather than manual checks or separate “long term” templates use case 3 – different signers for direct vs channel customers a customer success team works with both direct customers and channel partners revops creates conditional internal recipients tied to account type criteria like “contains direct” and “contains channel partner/reseller ” for direct accounts, the legal entity signer and standard internal approver are shown; for channel partner quotes, a different internal contact (e g , channel ops approver) appears instead the sales rep simply clicks “send for e‑signature” and sees the correct recipients based on the account, without choosing different templates or manually editing signer lists prevent sending zero amount invoices to salesforce this feature introduces a tenant level invoice setting that prevents invoices with a total amount of exactly $0 from being sent from nue to salesforce when enabled under system settings → invoices, any newly generated zero amount invoices remain fully visible in nue for audit purposes but are excluded from salesforce sync and do not show a salesforce sync icon in the transaction hub previously synced zero amount invoices continue to sync for backward compatibility, so existing salesforce data is not broken why it matters reduces manual cleanup of invoice lists in salesforce finance and billing operations teams no longer need to constantly filter out or ignore $0 invoices when reviewing invoices or exporting invoice data from salesforce, directly lowering recurring reconciliation effort lowers reporting and communication risk by preventing $0 invoices from appearing in salesforce, customers can avoid misinterpreting zero amount documents as billing errors or missing charges, improving trust in billing reports and customer communications preserves audit trail while de‑cluttering downstream systems zero amount invoices are still generated and stored in nue to maintain a complete billing and usage audit trail, but are selectively filtered at the salesforce integration boundary this balances strong internal controls with a clean operational experience for revops and finance users learn more customer use cases use case 1 – finance team runs monthly billing schedules that can produce hundreds of invoices for a single account, including some with a $0 total amount before this feature, every one of those $0 invoices was pushed into salesforce, where finance analysts had to build custom filters and manually ignore them during reviews of invoice lists, exports, and reconciliation after enabling “do not send invoices to salesforce with $0 total amount,” the same billing schedule still generates all invoices in nue, but only the non zero ones flow into salesforce finance users see a concise, meaningful set of invoices in salesforce, while auditors can still access the full trail inside nue use case 2 – revops admin is responsible for keeping the invoice pipeline in salesforce aligned with actual billable activity they previously saw a mix of positive, negative, and $0 invoices mapped from nue and had to verify whether zero amount entries were genuine credits, alignment artifacts, or errors by turning on the this setting, the admin ensures that only invoices with a non zero financial impact appear in their invoice related dashboards in salesforce autocharge invoices on due date (nue invoicing + collections) why it matters align collections with enterprise customers to use net 30 terms and expect payment to be collected on the invoice due date, not on the activation date this feature fixes the prior behavior where stripe collection happened immediately at activation, ensuring we respect net terms and reducing disputes about being charged too early reduce manual work for finance and ar teams previously, finance users had to either accept immediate charges or manually manage when to collect past due invoices with autocharge on due date, the system automatically evaluates invoice due dates and charges when they become due, while still allowing ar to accelerate or delay collection simply by editing the due date learn more customer use case a finance manager at an enterprise saas company uses nue to bill customers on net 30 terms with stripe connect for collections when they activate an invoice , nue immediately makes a payment link available to the customer (via email or customer portal) this gives the customer a review period from activation until the due date at any time during this window, the customer can open the link and pay the invoice manually using their preferred method if the customer pays before the due date, the invoice is marked paid , and no further action is taken if the due date arrives and the invoice is still unpaid , nue checks whether there is a payment method on file (for example, a saved card or bank account in stripe) when a valid payment method exists, nue automatically initiates a charge via stripe on the due date , aligning with the agreed payment terms if no payment method is on file, the invoice simply remains open past due, and the finance team continues collection through standard dunning flows or manual outreach how it works finance or admin users enable stripe or stripe connect for the tenant so nue can create charges in stripe on their behalf a payment method is saved for the customer via a payment link ; nue stores the stripe customer and default payment method reference against the account for future collections finance configures autocharge timing and selects “charge on the due date” instead of charging on activation when an invoice is created and activated with net terms (for example, net 30) , nue calculates a due date (invoice date + net term) and keeps the invoice open without attempting to charge at activation the end user customer can pay the invoice anytime they want before the due date via the payment link otherwise, nue will autocharge the invoice on the invoice due date developer experience buy now from quote configurable customer & contact checkout forms we’ve expanded buy now from quote with a configurable customer & contact checkout form builder, multi‑contact and lookup‑field support, and richer self‑service configuration, so admins can control exactly what information is collected (and what remains read‑only) before a customer pays design the customer & contact section of buy now from quote choose which fields to show, their order, labels, and whether each contact field is required , optional , or view only from the self service page in settings collect multiple contact roles (e g , billing, accounting, technical ) in a single flow as long as they are connected to the same account as lookup fields, and map them to the correct salesforce contact lookups on the account when orders and related objects sync to salesforce, custom lookup contacts stay correctly linked, avoiding broken references or manual fix‑ups admins can override the default “buy now” label with any custom call‑to‑action (e g , “complete purchase” , “accept quote” , “start subscription” ) to better match their brand and sales motion why it matters prevent revenue leakage by automatically enforcing annual renewal uplifts that were negotiated in contracts (e g , 1 5% per year), without requiring reps to manually calculate and apply adjust price lines for each subscription it honors existing subscription level uplift rates while keeping renewal pricing anchored to contracted net sale price rather than fluctuating list prices, which is critical for customers migrating with tens of thousands of uplift bearing subscriptions customer (account) fields are always read‑only in the live checkout admins can still include or hide them in the layout, but end customers cannot change core customer data without talking to their sales rep bug fixes lifecycle manager subscription's today’s arr/cmrr today’s arr/cmrr values now calculated accurately in multi‑currency enabled orgs today’s arr and today’s cmrr on subscriptions in non‑corporate currencies are now correctly stored in the subscription’s own currency (for example, gbp), matching the values shown in lifecycle manager and on the underlying order products account‑level arr rollups and any reports, dashboards, or automations that rely on subscription today’s arr/cmrr will now reflect accurate figures again as the nightly job runs after deployment, previously understated account rollups will self‑correct based on the updated subscription values price tags now preserved for dynamic bundle options on recalculate previously, when users worked with bundles that included dynamic add on products in the quote line editor (qle), any price tags or discount tags configured on the add on’s price book entry were lost after clicking recalculate recalculate for customers using bundles with dynamic add ons and price book entry level tags price and discount tags tied to price book entries will now display correctly on dynamic add on lines when the quote is created remain correctly applied after using recalculate in qle, instead of being removed this restores expected pricing behavior customer scenarios where bundles include dynamic product options discounts and pricing rules are managed via tags on price book entries rather than preconfigured on the bundle options manage subscriptions in qle fewer clicks, clearer actions when applying subscription changes to streamline the experience and reduce unnecessary clicks, we’ve updated the actions in the subscription drawer as follows renamed the primary button from add changes to quote to add to quote add to quote updated add to quote add to quote so that, when clicked, the configured changes are immediately applied to the quote no additional review changes review changes step needed to finalize those changes added a new secondary button review and add more review and add more this button returns users to the subscriptions list it adds the current changes to the change cart and behaves like the old add to quote add to quote flow, allowing users to review and add additional changes from the same subscription before finalizing the quote impact for customers fewer clicks to update quotes users can now apply subscription changes to a quote in a single, clear step clearer labeling and behavior the new button labels ( add to quote and review and add more ) better match what actually happens, reducing confusion more efficient change workflows users who need to layer multiple changes from the same subscription can still do so via review and add more , while those making straightforward updates can move faster with add to quote lookup selections now display correctly in line buckets earlier on the line bucket edit page in the quote split lines workflow, certain lookup fields (custom fields) would let users search and select a value, but then the input appeared blank after selection (no label was shown) only the clear (x) icon was visible, indicating a value was technically stored after the fix, selected lookup values on the line bucket edit page now reliably display their labels instead of appearing blank custom lookup fields used on line buckets (for example, location or contact lookups) are now fully functional and behave consistently with lookups elsewhere on the quote users can confidently complete line bucket configuration without being blocked or confused by invisible selections or console errors