Release 2507 - 10/23/2025

🙌 release 2507 is now live in sandbox ! 🗓️ production deployment is scheduled for october 23, 2025 ✨ nue ai is now available in preview , bringing intelligent, context aware automation to revenue workflows it connects nue’s structured data and salesforce objects with ai agents through mcp servers and agentic services , enabling assistants to summarize records, answer questions, and take guardrailed actions directly in salesforce and nue feature enhancements nue ai (preview) ✨ nue ai docid\ c smcz4sfxb8btidngp0n is a new ai powered layer within the nue platform that brings context aware agentic services to your entire revenue lifecycle by combining structured revenue data, salesforce objects, mcp (model context protocol) servers, and agentic chat interfaces, nue ai enables sales, revops, and finance teams to work faster and smarter — without stitching together data manually or building brittle automations ✨what’s new 1\ mcp servers lifecycle manager mcp server exposes subscription, order, and invoicing tools (e g , getcustomersubscriptions, generatecustomersummary, renew, upgrade, swap) to ai agents model agnostic layer works with gpt 5, gpt 4o, anthropic, and other providers, allowing flexible orchestration without embedding business rules into prompts 2\ agentic services (chatbots) customer chatbot embedded in both salesforce (via account page or lifecycle manager) and the nue app , enabling conversational workflows natural language commands let you list subscriptions, invoices, credit memos identify renewals and act on them generate ai summaries for accounts perform subscription changes inline (e g , convert free trial, co term, set pricing, add quantity) context aware navigation supports account hierarchies and cross account queries 3\ customizable prompts & summaries admins can define custom prompts for quote, order, and customer summaries summaries are generated using these prompts via ui buttons (e g , “generate quote summary”) customer chatbot conversations nue chat api in salesforce, summaries are rendered in non streaming mode due to platform constraints, which may appear slower 4\ secure access & permissions mcp tools are controlled via nue api keys and associated user roles chatbot access inherits permissions from salesforce or nue login all chats are timestamped and persisted for auditing and review 🚀 why it matters no more manual data stitching mcp servers expose live, structured tools—no need to sync data into a separate warehouse flexible ai orchestration works across ai providers, avoiding vendor lock in human + ai workflows teams use chat based interfaces to act on real data, not just get text answers ⚠️ availability nue ai is currently in preview to enable nue ai and participate in the pilot program, contact your nue account executive node 20+ is required for mcp server compatibility integrations enable scheduled batch mode and enhanced error handling for netsuite connector the netsuite connector now supports two critical enhancements a scheduled batch processing mode for transaction syncs and improved, actionable error handling these updates are designed to make high volume transaction integrations significantly more reliable, scalable, and transparent for finance, revops, and it teams why it matters reduces api failures and throttling scheduled batch mode prevents exceeding netsuite’s strict concurrency and rate limits, ensuring large transaction volumes (invoices, credit memos, payments) sync reliably, even during peak periods delivers error feedback errors for each transaction are now logged and flagged in detail (with error code and message) in nue’s transaction hub learn more use case 1 high volume invoice syncing a saas company processes thousands of invoices at month end previously, syncing these to netsuite would often fail due to api rate limits, leaving finance teams with incomplete records and manual re work with batch mode enabled, invoices are queued and processed in scheduled intervals, ensuring all invoices sync without hitting netsuite limits errors are clearly logged in transaction hub, so any failures can be quickly identified and retried use case 2 large order import and catch up during a major data migration, a customer imports thousands of historical orders without batch mode, simultaneous sync attempts would fail or queue up indefinitely now, the batch processor picks up orders every 10 minutes, syncs them in manageable chunks, and logs any errors with codes/descriptions—enabling efficient, error resilient migration use case 3 automated financial operations monitoring a finance admin wants immediate visibility into integration health with enhanced error handling, any failed transaction (such as a credit memo sync) posts a clear, actionable entry in transaction hub and, if configured, sends an email notification to the admin and support team for rapid triage enable invoice cancellation and reversal sync to netsuite this release introduces robust support for syncing invoice cancellations from nue to netsuite across all payment states—unpaid, partially paid, and fully paid invoices when a user cancels an invoice in nue, the integration now automatically determines the correct reversal action and reflects it in netsuite using credit memos and customer refunds, all posted with the cancellation date as the transaction date this enhancement ensures compliance with accounting period rules, maintains a clear audit trail, and automates complex workflows for credit memos and refunds the process is fully automated, supports multi currency and multi line invoices, and is aligned with netsuite and erp best practices for handling closed accounting periods why it matters ensures accounting compliance by always posting reversals in the current open period, never making retroactive changes to closed periods, thereby preserving audit integrity and preventing compliance risks automates and standardizes complex cancellation workflows, eliminating manual intervention and reducing the risk of errors or discrepancies between nue and netsuite provides a fully auditable process, with all reversal actions logged and traceable in both nue and netsuite, enhancing operational transparency and supporting finance, audit, and customer service needs learn more customer use case use case a finance user in a saas business discovers an active invoice that was issued in error and remains unpaid they cancel the invoice in nue, which triggers the creation and application of a credit memo in netsuite for the full amount, dated as of the cancellation date the invoice is automatically closed in both systems, with no impact on ar, and the reversal is reflected in financial reporting for the current period use case a customer requests a refund for a fully paid invoice due to service cancellation the revops team cancels the invoice in nue, which generates a credit memo and a customer refund in netsuite, both linked to the original payment the refund is processed, the invoice is closed and marked as refunded, and the customer’s balance is accurately adjusted—all with a clear audit trail use case in a case where an invoice is partially paid (e g , multiple payments or credit memos applied), the finance team cancels the invoice in nue the integration automatically creates a customer refund for the paid portion and a credit memo for the unpaid balance in netsuite, both dated as of cancellation both are applied, fully offsetting the invoice and ensuring accurate reporting and customer reconciliation how it works invoice cancellation in nue is triggered from the ui or via api the system checks invoice status and payment state to determine the correct reversal path if unpaid generates and applies a credit memo in netsuite, dated today if fully paid generates a credit memo, applies it, and issues a customer refund linked to the payment if partially paid issues a customer refund for payments, a credit memo for the unpaid amount, and applies both all transactions are dated with the cancellation date, ensuring compliance with open accounting periods support transport field for avalara tax this feature introduces a "transport" field across products, quotes, orders, invoice items, and credit memo items in nue and salesforce the transport field specifies who is responsible for the transportation of physical goods in vat transactions, a regulatory requirement for vat compliance in many jurisdictions (notably europe) the selectable options are seller (default), buyer, thirdpartyforseller, thirdpartyforbuyer, and none why it matters ensures full vat compliance for cross border transactions by capturing the required transport responsibility in all avalara vat tax calculations reduces manual errors and enforces data integrity by restricting entries to a validated picklist, defaulting to seller if not explicitly set seamlessly integrates into existing sales and finance workflows, allowing sales reps to configure the field during quoting and order generation and ensuring downstream consistency for finance, audit, and reporting learn more customer use case use case a sales rep at a european saas company is configuring a quote for a customer in another eu country during the quote process, they must specify whether the seller, buyer, or a third party is responsible for transport selecting the correct option ensures that vat is calculated accurately and that all required information is sent to avalara for compliance, eliminating delays in closing the deal and reducing the risk of audit issues use case a finance operations user is preparing invoices for monthly reconciliation they need to verify that every invoice and credit memo item includes the correct transport field value for vat audit trails with this feature, they can easily see and report on transport responsibility directly in nue and salesforce, ensuring compliance and readiness for audits use case an admin is onboarding a new product line that involves third party logistics providers when setting up new products in the catalog, they configure the default transport responsibility as "thirdpartyforseller " this default cascades to all quotes and orders unless changed, streamlining setup and ensuring consistent application of company policies how it works the transport field appears as a dropdown in nue and a picklist in salesforce on products, quote line items, order products, invoice item details, and credit memo item details sales reps can view and edit the transport value during quote and order creation; finance can view it on invoice and credit memo items only the five defined values are accepted; invalid/free text entries are rejected at both ui and api levels if transport is not set, it defaults to seller on save the transport value is included in all avalara tax calculation requests for vat transactions support cancel full obligation in rightrev nue now supports the explicit differentiation between full and partial cancellations when syncing order or subscription changes to rightrev when a customer cancels the entire contract (full obligation), nue will send an amendment reason of "cancel full obligation" to rightrev for partial cancellations (such as adjusting the sell price for only the remaining term), the amendment reason "cancel" will continue to be used this distinction ensures rightrev can process full cancellations with retrospective revenue treatment and partial cancellations prospectively, aligning with revenue recognition best practices why it matters ensures accurate and compliant revenue recognition by distinguishing between full and partial cancellations, supporting retrospective revenue treatment for full obligation cancellations improves transparency and auditability for finance and revops teams, making it clear in downstream systems how and why revenue is reversed or adjusted learn more customer use case use case customer x, a customer using the nue–rightrev integration, previously had to manually update revenue recognition for full contract cancellations at every month end with this new feature, when customer x cancels an entire contract, nue sends "cancel full obligation" to rightrev automatically this ensures that revenue is reversed for the full contract as per accounting requirements, saving significant manual effort and reducing reconciliation errors use case a finance user at a subscription based company cancels an entire multi year contract due to customer churn instead of treating this as a partial cancellation (which would only affect future periods), the system now properly marks it as a full obligation cancellation in rightrev this triggers retrospective revenue reversal, ensuring accurate financial reporting use case in another scenario, a revops user processes a mid term subscription adjustment (e g , reducing seats for the remaining term) the system retains the "cancel" amendment reason for this partial change, ensuring rightrev only adjusts revenue for the unfulfilled portion, not the entire contract how it works when a user cancels an order or subscription in nue or salesforce if the entire contract is cancelled (full obligation), nue sends amendmentreason "cancel full obligation" to rightrev if only part of the contract is cancelled (partial), nue sends amendmentreason "cancel" the determination of full vs partial cancellation is automated based on whether the action covers the total sell price or only the remaining term the process is seamless and does not require extra configuration from the end user unapply credit memo to quickbooks finance users can now unapply credit memos from invoices within nue, with the unapply action fully mirrored in quickbooks this process updates the balances and payment statuses of both the credit memo and the invoice, retains audit trails, and ensures all changes are reflected in both systems the feature includes robust error handling, intelligent concurrency management, and is fully integrated with transaction hub for compliance and transparency why it matters ensures accurate financial records unapplying credit memos instantly updates balances in both nue and quickbooks, eliminating manual reconciliation and reducing the risk of financial discrepancies enhances auditability and compliance all unapply actions are logged in transaction hub, providing a clear audit trail and supporting compliance requirements for external financial audits learn more customer use case use case a finance operations manager notices an over application of a credit memo to a customer’s invoice using the nue ui, they select the applied credit memo and click “unapply ” the system confirms the action, updates both nue and quickbooks, and reflects the correct balances transaction hub logs the event, ensuring the change is visible for review and audit use case during a quarterly close, a finance team discovers that multiple credit memos have been incorrectly applied to an invoice they use the batch unapply feature in nue to select and unapply several credit memos at once all balances are updated in both nue and quickbooks, and downstream systems are notified via webhook use case a customer’s information is missing in transaction hub, causing an error when attempting to unapply a credit memo the system surfaces a clear error message and logs the failure for the admin to resolve, ensuring that data issues are caught early and can be addressed efficiently how it works users with correct permissions can unapply credit memos via the invoice detail page in nue the workflow validates all records before proceeding the system updates quickbooks via api, retains $0 payment records but removes the link between the invoice and credit memo all actions are logged in transaction hub, with errors and status changes surfaced to admins and users a dynamic delay mechanism serializes unapply events to prevent race conditions on the same invoice send invoices and credit memos to netsuite/qbo from transaction hub this feature enables finance and admin users to directly send (“transfer”) invoices and credit memos in an "active" and "not transferred" state from the nue app to netsuite or quickbooks online (qbo), without requiring access to salesforce or the lifecycle manager the button was previously only available in the lifecycle manager, and this release brings full parity and streamlined accounting operations to users who work solely in the transaction hub why it matters reduces dependency on salesforce and the lifecycle manager, allowing users to complete end to end accounting workflows entirely within the nue app improves efficiency for finance/admin teams by surfacing the "send/transfer" button only when records are eligible, reducing errors and duplicate transfers enhances auditability and compliance by logging all actions, errors, and transfer attempts in the transaction hub, supporting troubleshooting and regulatory needs send credit memo whose source is credit conversion to netsuite this feature enables credit memos in nue that originate from "credit conversion" to be sent and integrated into netsuite, closing a critical gap where these credit memos were previously blocked and not transferred now, all credit memos follow identical integration flows, ensuring they are accurately reflected in netsuite for financial reporting, compliance, and audit requirements why it matters eliminates manual workarounds for credit conversion credit memos, reducing operational friction and risk ensures financial records in netsuite are complete and accurate, supporting compliance and audit requirements improves user trust in the nue–netsuite integration by providing support for all credit memo types, lowering the risk of revenue leakage or reporting errors learn more use case 1 a finance user creates a credit memo in nue with the source type "credit conversion" when a customer has unused credits that need to be converted into a monetary adjustment previously, this adjustment could not be reflected in netsuite, requiring manual entries and increasing the risk of errors with this feature, the credit conversion credit memo is automatically sent to netsuite, appearing alongside regular credit memos and ensuring the customer account is up to date across all systems use case 2 a revops manager needs to ensure compliance for audit purposes during a financial review, auditors require proof that all credit adjustments—including conversions—are present in netsuite now, the system ensures that credit conversion credit memos entered in nue are seamlessly transferred and logged in netsuite, supporting a complete and auditable financial record use case 3 an organization operating in multiple currencies issues a credit conversion credit memo with taxable and non taxable lines the integration handles multi currency, tax mapping, and partial application scenarios, ensuring the memo is accurately represented in netsuite with correct currency and tax details how it works users create a credit memo in nue, selecting "credit conversion" as the source/type the integration service detects the credit conversion type, constructs the netsuite compatible payload, and sends it to netsuite using established endpoints the status of the transfer and any errors are managed and surfaced in nue, with success/failure updates as per standard logic all relevant fields (amount, currency, tax, etc ) are mapped and visible in netsuite automation and templates ensure credit memos can be generated, previewed, and sent to customers with minimal manual intervention add netsuite bundle fields for nue integration enables consistent, auditable, and automated field mapping between nue and netsuite for all key business objects why it matters ensures every record created or updated in netsuite by nue is unmistakably marked, enabling fast, reliable compliance audits and internal reporting dramatically improves operational efficiency by automating the mapping of essential fields (e g , transaction number, sync status, cross system links) across customers, products, orders, invoices, payments, and more supports flexible business processes and future proofing by allowing custom field overrides, static value assignments, and duplicate detection learn more customer use cases use case 1 as a finance user, i need to quickly identify which customers, orders, and invoices in netsuite originated from nue versus those created manually or by other integrations with the “created from nue” field, i can filter and report on integration driven records, automate audit workflows, and ensure sox compliance without manual intervention use case 2 as an operations or support analyst, i often need to investigate discrepancies between salesforce and netsuite records the “nue transaction id” and “nue url link” fields allow me to click directly from netsuite into the corresponding salesforce record, speeding up root cause analysis and customer issue resolution use case 3 as an admin, i want to customize my integration field mappings for unique business requirements by using custom field overrides and static value assignments, i can ensure netsuite receives the data my downstream processes require (e g , always setting a tax code, or tracking a custom compliance flag) without sacrificing auditability or risking data errors how it works adds the following custom fields to all core netsuite objects (customer, product/item, sales order, invoice, credit memo, payment, return authorization, customer refund) created from nue (checkbox) nue transaction # nue transaction id (salesforce/nue id) nue sync status (running log) nue sync last (timestamp) nue url link (direct link to salesforce record) on each sync event, the integration automatically updates these fields to reflect the latest state and provides error logs if sync fails map nue product type to netsuite gl account this enhancement allows nue admins to directly map each nue product type (such as subscription, asset, or entitlement) to a specific netsuite general ledger (gl) account, rather than being limited to mapping only by netsuite item type this design provides greater flexibility, accuracy, and compliance in revenue recognition and reporting, while preserving backward compatibility for existing integrations why it matters enables granular and accurate accounting by allowing different nue product types to be mapped to distinct netsuite gl accounts—even when mapped to the same netsuite item type—ensuring correct revenue categorization and reporting for complex business models supports best practices for revenue recognition compliance (asc 606, ifrs 15), especially for companies using netsuite arm, by conditionally mapping deferred revenue accounts and automating correct journal entries reduces manual work and friction during upgrades by relabeling existing configuration fields instead of replacing them, preserving historical mappings and minimizing the need for customers to redo their setup learn more customer use case use case a saas company sells both recurring subscriptions and entitlement based products previously, both were mapped to the same netsuite noninventoryitem type, forcing revenue from both product types into a single gl account with the new mapping, the company can direct recurring revenue to one gl account and entitlement revenue to another, supporting separate revenue recognition schedules and more precise financial reporting use case a business that offers hardware (assets) and software subscriptions (subscriptions) needs each to post to different gl accounts, but both product types are mapped to the same netsuite item type the new feature enables direct mapping from each product type to its proper gl account, without restructuring the item types in netsuite, saving significant administrative overhead use case an organization enables netsuite arm to automate revenue recognition with this feature, the deferred revenue account is automatically selected for product types when arm is enabled, ensuring correct deferred revenue accounting and compliance with company policy, while using the standard revenue account when arm is not in use how it works admins configure netsuite integration in nue by selecting, for each nue product type, the target netsuite item type and gl account from drop down menus when orders or items are synced to netsuite, the integration checks the mappings and applies the correct gl account(s) based on the current configuration and arm status field relabeling in the ui avoids breaking changes—existing integrations continue to work without reconfiguration system validates that selected netsuite account ids are valid before saving configuration if an invalid mapping is detected, the system logs a clear error and prevents the sync, ensuring data integrity bug fixes everything billing lookup field sync issue resolved for active orders previously, when updating a lookup field value on an existing active order, changes made in salesforce were not being re synced to nue this meant that updates performed in salesforce did not reflect in nue for active orders, potentially leading to data inconsistencies between the two systems with this fix, updates to lookup field values on active orders in salesforce will now correctly sync to nue this ensures that data remains consistent across both platforms, improving reliability and reducing the risk of discrepancies for customers managing orders through salesforce and nue duplicate invoices displayed issue resolved previously, when users filtered invoices by customer or sales account within the billing platform, the system would sometimes display duplicate invoice entries this issue was identified in the sandbox environment and could cause confusion or errors when reviewing or reconciling invoice data with this fix, filtering invoices by customer or sales account now correctly displays each invoice only once this improvement ensures that users see accurate, non duplicated invoice lists, making it easier to manage billing records and reducing the risk of mistakes during financial reviews improved sorting stability on invoice item details page previously, when users sorted the invoice item details page by the "sales account" column in the nue app, the page would unexpectedly turn or change, disrupting the user’s workflow with this fix, sorting by sales account on the invoice item details page now works as intended users can reliably sort their invoice items without the page unexpectedly turning or changing, resulting in a smoother and more predictable experience when managing billing details improved stripe webhook handling for nue initiated payments and invoices previously, the stripe webhook in the nue platform processed all payment and invoice events received from stripe, regardless of whether those transactions were actually initiated within nue this could result in unintended or irrelevant payment and invoice data being handled by the system, potentially causing confusion or incorrect billing records for customers with this update, the stripe webhook now exclusively processes payments and invoices that were initiated through the nue platform this ensures that only relevant billing events are handled, improving data accuracy and reducing the risk of processing unrelated stripe transactions customers can expect more reliable billing records and a smoother collections experience as a result of this fix developer experience performance enhancement faster client side pricing engine input fetch previously, the client side pricing engine input endpoint fetched all available price tags to derive line level price dimensions, which led to slow response times—especially for catalogs with many tiers or price tags this could delay calculations and degrade the user experience when configuring or pricing orders with this enhancement, the endpoint now fetches only the price tags relevant to the current order context this targeted retrieval significantly reduces payload size and processing time, improving responsiveness for pricing operations and accelerating ui flows that depend on pricing engine input benefits improved responsiveness of the client side pricing engine endpoint for large catalogs reduced data transfer and processing overhead during pricing requests smoother configuration and pricing experience across self service workflows enhanced “convert free trial” flow we’ve made several improvements to ensure converting a free trial to a paid subscription works smoothly and consistently related pricing and sync behaviors are more reliable across systems what’s improved evergreen conversions set the correct actual subscription term (e g , 1 for evergreen), aligning with expected policies start dates honor free trial conversion timing to prevent off by one or premature effective dates pricing and tax behavior during conversion is more predictable, reducing edge case errors downstream syncs (e g , salesforce) behave more consistently after conversion these changes provide a smoother path from trial to paid, reduce the chance of discrepancies, and improve confidence when activating converted subscriptions