Release 2505.1 - 08/07/2025

🚀 release 2505 1 is now live in both sandbox and production environments this release introduces several key enhancements, including one of the most highly requested features add and stack subscription changes directly in the quote or order line editor with real time updates and undo/redo support in addition, this release adds support for setting the net sales price of usage products with a quantity of 0, the ability to send payment links to multiple contacts per account, and configure payment link expiration policies new capabilities also include rich text formatting in template builders, custom webhook headers for authentication, and quote based self service checkout that allows end customers to convert quotes directly into orders additionally, the release adds automated refund processing, apply and unapply credit memos with both netsuite and quickbooks, show a centralized overview of the entire integration stack, along with various bug fixes feature enhancements lifecycle manager add additional changes directly on the line editor inside a quote or order sales reps can now add and stack additional subscription changes such as renew and update quantity directly within the quote or order line editor, without switching back to the lifecycle manager a new add additional changes add additional changes icon appears in the actions column for eligible subscriptions clicking it opens a modal, mirroring the lifecycle manager’s subscription card, where reps can select and apply available changes changes are merged into the line editor in real time, and users can undo/redo up to three recent changes this dramatically streamlines multi step subscription changes and eliminates major sources of user friction why it matters increases sales rep efficiency by enabling in context, multi change editing of subscriptions within a single ui, reducing clicks and context switching reduces user errors and support tickets by enforcing change deduplication, limiting undo/redo complexity, and providing clear in app status messaging helps make the renewal flow much easier and simpler to implement learn more customer use case use case 1 a sales rep is working on a renewal quote for a customer after initiating the renewal, they realize an upsell is possible instead of navigating back to the lifecycle manager, they click the new add additional changes add additional changes button in the line editor, select update quantity, and immediately add the renewal change both changes are now reflected in the grid, and the rep can undo or redo either change before saving the quote use case 2 during a quote amendment, a sales rep accidentally applies the wrong quantity update using the status panel, they quickly undo the most recent change and re apply the correct update—all without leaving the line editor or losing their prior work use case 3 a sales rep performs an update term change on the lcm for a bundle & checks out in the quote, that's when their customer says they would like to add some new seats for a specific ai add on product for the increased term rep can just click add additional changes add additional changes right in front of the corresponding add on and update quantity just for that specifically in case this add on is configured to be connected to bundle quantity user will see the corresponding message prompting them to update quantity at the bundle level how it works navigate to settings > search for ' allow addition of subscription changes, directly inside the line editor allow addition of subscription changes, directly inside the line editor ' > enable the setting a new add additional changes add additional changes icon appears in the actions column for eligible subscriptions in the line editor clicking the icon opens a modal showing the subscription’s details and all available change actions (e g , renew, update quantity) up to three recent changes are tracked in a status panel; users can undo or redo them in a linear sequence changes are only persisted to the server when the quote or order is saved if applying a change fails, the ui displays a toast notification and reverts the state dependencies and limitations the add additional changes add additional changes button is hidden unless enabled by a system admin in the general settings panel for quotes & orders only renew and update quantity change types are available in v1 (2505 1); support for other change types will be added in future releases only one change of a specific type per subscription is allowed in the change queue at any time; duplicate or conflicting changes are automatically replaced functionality is only available for bundles, standalone, and add on products (assets, entitlements, and bundled products as children are not supported in v1) undo/redo queue is limited to three changes; users must save or discard to reset the queue all changes are client side until the quote/order is saved; navigating away or refreshing without saving will lose unsaved changes related resources for more details checkout the lifecycle manager overview support net sales price configuration for zero quantity usage products this enhancement enables configuration of net sales price (nsp) for usage based products quoted or ordered with a quantity of 0 it resolves a long standing issue where net sales price for these usage products would revert to the list price and there would be no way to alter the list price of the usage product without using price tags now, the net sales price can be explicitly set for zero quantity usage products standard discount percentage and discount amount fields can also be used to automatically calculate and apply to the net sales price, even when no committed usage is present why it matters ensures accurate, transparent, and auditable usage rates for subscriptions with usage products, crucial for users adopting usage based pricing reduces operational overhead and eliminates reliance on manual workarounds or error prone price/discount tags learn more customer use cases use case a sales rep can now apply a discretionary discount (e g , 10%) to a usage based product with a quantity of 0 while creating a quote with the latest enhancements, the system automatically calculates and displays the correct net sales price (e g , $4 50 from a $5 00 list price), ensuring the discounted rate carries forward to future renewals or change orders this allows the sales team to confidently quote usage subscriptions without requiring a prepaid commitment, while avoiding price resets during renewal dependencies & limitations users must ensure that discount fields are used appropriately; if no discount is entered, the net sales price will match the list price related resources checkout more details here to understand how the pricing calculations have been enhanced everything billing account level auto charge the feature now enables finance users and end customers to set and manage a default payment method at the account level end users paying via payment link can choose to save their payment method for future use, set it as the default for their account or subscription, and enable automatic invoice payments (auto charge) the most specific default (subscription) always takes precedence, with account level fallback for all other invoices all settings and payment method updates are synchronized between nue and salesforce, with robust automation, auditability, and privacy controls why it matters streamlines payment collection and increases on time payment rates by reducing manual intervention for recurring and one time invoices empowers customers to control how and whether their payment methods are stored and used, supporting both privacy and automation needs learn more customer use cases use case 1 a finance team at a saas vendor wants all new customer invoices to be automatically paid by a default corporate credit card, unless a specific subscription (e g , a premium plan) should be charged to a different method they configure the account level default payment method in nue when a customer pays via payment link and saves their payment method, this can instantly become the new default for future transactions the system ensures that subscription level defaults always take precedence, so specialized billing needs are always respected use case 2 an end customer receives a payment link for a new invoice they pay with a new card and are given the option to save it for future use, set it as default for the account or just the current subscription, and opt in to auto charge for future invoices they decline to save, ensuring privacy for a one time payment for recurring customers, they enable auto charge and default settings, automating all future billing with a single click use case 3 a billing admin updates the default payment method in salesforce after a customer requests a change over the phone the new method is automatically synchronized to nue, ensuring that all future invoices (except those with subscription specific overrides) are charged correctly without manual reconciliation or risk of missed payments how it works payment links present options to save a payment method, set as account or subscription default, and enable auto charge subscription level default payment methods always take precedence over account level defaults for invoice payments account level defaults are used for all subscriptions/invoices that do not have their own default set dependencies and limitations "save payment method for future use" must be enabled to allow auto charge; auto charge cannot be set without a default payment method subscription level defaults override account defaults for all auto charges defaults are only updated if the relevant default is currently unset, unless explicitly overridden by the user/admin edge cases manual payment links or invoices without saved payment methods will not be auto charged; the customer must complete payment manually related resources please refer to this collect payments via nue payment links article for more details about this feature send payment link to multiple contacts this feature enables finance users to send invoice payment links and related notifications to multiple contacts within a customer’s organization, instead of relying on a single recipient it expands the traditional, single recipient billing workflow by introducing a configurable list of additional email addresses (“email recipients”) at the account level—improving both the reliability and speed of enterprise collections why it matters accelerates enterprise collections by ensuring all relevant billing, finance, and procurement contacts receive payment requests, reducing delays from absent or changed primary contacts reduces operational risk and payment delays by eliminating the “single point of failure” in invoice delivery—especially critical in large, distributed organizations improves customer experience and satisfaction by providing flexible, proactive, and secure billing communications, supporting complex approval chains and organizational requirements learn more customer use cases use case 1 an enterprise saas vendor’s finance team enables the “email recipients” field on a customer’s account, entering all relevant ap and procurement contacts’ emails when a quarterly invoice is activated, every listed contact—along with the primary contact—immediately receives the payment link and can pay directly, ensuring payment isn’t delayed if the primary is unavailable use case 2 a customer’s finance director is out of office, but payment responsibility rotates to the controller because both are on the recipients list, the controller receives the payment link and is able to pay before the due date, avoiding late payment penalties and service disruption use case 3 a global organization needs all regional ap leads to get notified of renewal invoices the account manager bulk pastes a comma separated list of emails into the field when the invoice is activated, each stakeholder receives the payment link, and the system logs successful delivery to all parties for compliance how it works a new text area field (“email recipients” / billtoemaillist) is added to the account object; users enter one or more emails separated by commas or newlines on invoice activation (manual, api, ui, or bulk job), the system aggregates order primary contact email order’s bill to contact email all emails from the billtoemaillist field payment link emails, payment receipts, and failure notifications are sent to every address in this list admins can configure templates, link expiration policies, and security settings (e g , requiring the recipient to enter their email before accessing the payment link) dependencies and limitations the feature requires the “email recipients” field to be configured on the account object users must enter valid email addresses using supported delimiters security enhancement (requiring recipient email authentication before payment) is optional—admins must enable it for additional protection, especially if emails are forwarded only the emails listed at the time of invoice activation will receive notifications; changes to the list after activation require link regeneration to notify new contacts only the emails listed at the time of invoice activation will receive notifications; changes to the list after activation require link regeneration to notify new contacts full visibility and reporting on notification delivery depends on email infrastructure and may vary across integrations related resources please refer to collect payments via nue payment links docid 9 rcffm0h ptxhwub01u for more detailed information about this feature configure payment link expiration this feature enables system administrators to control how long nue payment links remain valid admins can require links to expire immediately after first access (by external users) or stay active for a configurable number of days this setting is managed from settings → collections → payment links → payment link expiration strategy expiration policies apply only to newly created payment links and ensure payment collection is both secure and flexible for a variety of enterprise and customer scenarios why it matters strengthens payment security by reducing the risk of unauthorized or fraudulent payments if a link is leaked or left unused improves operational efficiency by offering predictable, automated expiration and minimizing manual intervention for link management enhances customer trust and compliance with regulatory standards by providing clear, auditable controls over payment link accessibility learn more customer use cases use case a finance operations manager at a saas company configures all payment links to expire after 7 days when invoices are sent, recipients have a week to complete payment if a link is forwarded or left open, it becomes unusable after the set period, ensuring only intended users can pay within a controlled window use case a system administrator at an enterprise with strict compliance needs enables "expire immediately after first access" for payment links when a customer opens the payment link from their email, the link is instantly invalidated for any subsequent access, preventing accidental or malicious reuse—even if the email was forwarded use case a billing specialist manages payment collection for multiple recipients on a large account they use the ‘email recipients’ field to distribute the payment link to several contacts each recipient gets a link that expires according to the configured policy, ensuring the invoice can be paid promptly by any authorized party, but never past the allowed time frame how it works admin navigates to settings → collections → payment links → payment link expiration strategy two options are available expire immediately after first external access link becomes invalid after a non nue user opens it and does not complete payment expire after x days link remains valid for a specified number of days after creation changes apply only to newly generated payment links; existing links are unaffected expiry state is enforced by backend logic, and end users receive clear notifications if a link is expired payment links are sent to all emails listed in the ‘email recipients’ field on the account dependencies and limitations the expiration setting only affects payment links created after the setting is changed; existing links are not retroactively updated links expire either immediately after first external access or after x days—no mixed mode per link edge cases if a user opens a link but does not complete payment, the immediate expiry policy will prevent further attempts; users must request a new link from the sender payment link expiration does not override downstream payment rules or auto charge behavior but works in harmony with those features related resources please refer to collect payments via nue payment links docid 9 rcffm0h ptxhwub01u for more detailed information about this feature support rich text in template builder we now enable administrators to add, configure, and control a rich text component within the template builder for invoices, quotes, order forms, and credit memos this enhancement allows users to insert richly formatted text blocks (with headings, fonts, colors, alignment, bullets, links, and more), embed dynamic merge fields from any supported object, and apply conditional logic to decide when each component is shown—directly from the interactive ui rich text components can be freely added, edited, moved, and personalized, with live preview and support for business rules that automate content display, all without developer intervention why it matters accelerates customer go live by enabling non technical admins to fully design, personalize, and automate document templates—removing bottlenecks and the need for engineering resources delivers highly dynamic, contextual, and compliant communications—supporting branding, regulatory, and customer specific requirements on invoices, quotes, and order forms reduces support and implementation costs by empowering business users to maintain and update templates, minimizing the need for custom code or manual workarounds learn more customer use cases use case a global saas company needs to include custom “terms and conditions” in their invoices—sometimes showing additional clauses only for customers in regulated industries or for deals above a certain value with the new rich text component, their billing administrator configures richly formatted legal text, inserts dynamic fields like customer name and invoice number, and sets rules so the section only appears for specific customers or invoice amounts this ensures compliance and personalization without code use case a finance team wants every order form to display “draft” as a diagonal watermark and an explanatory rich text note if the order status is not yet finalized the admin adds both a conditional watermark and a rich text block, using the drag and drop builder and status based rules when an order form is previewed or sent, these elements appear only when relevant—removing manual steps and mistakes use case a finance team wants every order form to display “draft” as a diagonal watermark and an explanatory rich text note if the order status is not yet finalized the admin adds both a conditional watermark and a rich text block, using the drag and drop builder and status based rules when an order form is previewed or sent, these elements appear only when relevant—removing manual steps and mistakes how it works configure formatting (headings, fonts, color, alignment, bullets, borders) and insert merge fields for invoice, quote, customer, or system data (e g , {!invoicenumber}, {!customer name}, {!$company name}) set component visibility to “always” or “conditionally” based on any field (e g , only display if status = draft), using the built in filter editor see changes and conditional logic in a real time preview; rearrange components via drag and drop when generating or previewing a document, merge fields are replaced with live values and conditional logic is applied automatically dependencies and limitations requires template builder enhancement to be enabled for the tenant merge field support in rich text component depends on field availability and correct business object mapping; some custom field types may require additional setup or may have display limitations (see known issues under investigation) rich text content and field rendering are subject to limits of pdf generation (e g , extremely large content blocks may impact layout or pagination) conditional logic cannot (yet) control visibility of individual lines within a rich text block; it applies to the entire component watermark, header, footer, and related features must be configured separately but share the same conditional logic engine related resources learn more about this feature from quote builder docid\ vefkb3pyyyh5fpedaiswz developer experience add custom webhook headers for outbound authentication this feature allows administrators to configure additional custom http headers—including authorization tokens—in webhook requests, beyond the default nue secret token administrators can define any number of custom headers to meet integration requirements for third party or internal provisioning systems, with secure storage and masking of sensitive values why it matters unlocks integrations with enterprise and third party systems (e g , retool, zendesk) that require custom or multiple authentication headers not supported by default reduces or eliminates the need for middleware or manual workarounds, saving time in onboarding and maintenance for it and development teams learn more customer use cases use case a saas customer is integrating nue with retool for automated provisioning retool mandates the use of a custom header (e g , x workflow api key) for webhook authentication with this feature, the customer configures the required custom header in the nue ui, ensuring secure and seamless delivery of provisioning events without changes on the retool side use case an enterprise it team needs to pass both a static api key and a rotating jwt token in separate headers for compliance with their security policy on inbound provisioning webhooks using nue's custom header support, they add both headers, manage secret rotation centrally, and mask values in the admin ui, meeting both automation and audit requirements how it works admins add/edit custom http headers (name/value) to any webhook endpoint via the ui or api up to 10 headers can be set per endpoint secret values are masked in the ui and audit logs headers are securely stored (kms/encrypted db) dependencies and limitations feature is backwards compatible existing webhooks with no configured headers remain valid and operational if a header is left unset, it will not be sent, ensuring no breaking changes for legacy endpoints related resources webhooks docid z6xbd98qskku1fifbj5y accelerate deal closure with quote based self service checkout this feature enables end users to seamlessly convert a quote received via magiclink from your sales rep into an active order directly within the magiclink experience when the "buy now" button is enabled, customers can review their quote, enter payment information, and complete their purchase independently—without waiting for sales rep intervention the system securely creates an order from the quote, processes payment, and ensures all relevant fields and relationships, streamlining the quote to cash journey why it matters accelerates deal closure by removing manual steps and sales rep dependency, reducing sales cycle time and increasing conversion rates delivers a modern, frictionless buying experience that empowers buyers to act immediately through self service supports both product led (plg) and sales led (slg) growth strategies, allowing organizations to scale and blend sales motions for diverse customer segments learn more customer use cases use case a saas prospect receives a custom quote from a sales rep via a magiclink the decision maker clicks the link outside of business hours, reviews all pricing and options, and immediately completes the checkout and payment without needing to contact the sales rep again the order is created, the sales team is notified, and fulfillment begins instantly—no delays, no friction use case a customer in a hybrid gtm motion (mix of direct sales and self service) wants to upgrade from a free trial to a paid subscription they receive a quote via magiclink, click "buy now," confirm details, and enter payment—all in one flow—converting instantly from prospect to paying customer how it works when enabled via org level setting, a "buy now" button appears on quote magiclinks clicking "buy now" launches the embedded checkout ui payment details are collected securely (supports stripe invoicing and nue collections) on activation, order data is synced to salesforce, linking the order as the primary for the quote and blocking duplicate finalization dependencies and limitations currently supports stripe invoicing and nue collections related resources buy now from quote docid\ wgrjqj29nmaqhvseuiyht integrations process customer refunds to netsuite this feature enables automated, configurable, and audit ready synchronization of refund events from nue (including refunds initiated via stripe or directly in nue) into netsuite when a refund is processed in nue, the system creates a corresponding credit memo in netsuite and issues a customer refund (if applicable) with all required gl/account mappings the integration supports both full and partial refunds, handles edge cases (such as prior credit memo applications), and logs all events and errors in nue’s transaction hub for traceability, compliance, and customer support configuration options allow admins to select whether to use credit memos or negative invoices and to set up custom netsuite forms to handle netsuite specific requirements (e g , refund method fields) why it matters automates refund reconciliation and auditability by ensuring all refunds from nue/stripe are correctly posted in netsuite, reducing manual finance workload and the risk of missed or duplicate transactions ensures compliance and financial integrity by matching every refund with a credit memo, applying it to the proper gl account, and reflecting the correct status across both systems enhances customer experience and support by enabling real time, transparent status tracking in nue’s transaction hub, with full retry and error handling workflows for failed syncs learn more customer use cases use case after processing a full refund for a customer’s paid invoice in stripe, the finance team needs netsuite to reflect this refund for accurate accounting, audit, and downstream revenue recognition with this feature, the refund event triggers automatic creation of a credit memo in netsuite and a customer refund is issued all records and statuses update in transaction hub, eliminating reconciliation headaches and manual adjustments use case a customer requests a partial refund for a subscription charge, and this is processed in nue the system automatically generates a partial credit memo in netsuite and issues the corresponding refund if multiple partial refunds are requested over time, the system manages multiple credit memos and maintains a clear audit trail, ensuring all balances and statuses in netsuite exactly match the customer’s record in nue use case the finance team creates a standalone credit memo in nue (not tied to a specific invoice) for a customer dispute or goodwill adjustment this credit memo is synced to netsuite and can be applied to future invoices or used for a direct refund, supporting advanced reconciliation and audit scenarios required by enterprise accounting policies how it works listens for refund events in nue, including those triggered by stripe or self service apis creates a credit memo in netsuite (or negative invoice, based on workspace setting) linked to a return authorization handles netsuite custom forms (e g , making refund method optional) to bypass or satisfy mandatory netsuite fields logs every event, status change, and error in nue’s transaction hub, supporting retries and audit trails supports multi entity and multi currency setups, mapping each transaction to the correct netsuite gl account as configured dependencies and limitations requires that netsuite is connected and configured with the appropriate gl account mappings (including clearing accounts for stripe/nue originated payments) workspace level setting must specify whether to use “credit memo” or “negative invoice” as the refund mechanism; some edge cases (e g , legacy negative invoice flows) are not supported if “credit memo” is not enabled refunds cannot be processed to a closed accounting period in netsuite; errors are surfaced and must be resolved before retry multi entity and multi currency handling require that all mapping and segmentation is correctly configured; otherwise, syncs may fail or create misallocated records process customer refunds to quickbooks this release introduces automated, auditable synchronization of customer initiated refunds from nue to quickbooks online (qbo) when a refund is processed in nue—whether for the full or partial amount of a paid invoice—the integration creates the appropriate credit memo (or negative invoice) and expense in quickbooks, linking all records for strict auditability refunds are mapped to your configured “nue clearing” account, with all status changes and errors tracked in nue’s transaction hub for complete financial traceability this approach ensures both operational accuracy and compliance with financial best practices, while supporting complex customer requirements and minimizing manual effort why it matters eliminates manual reconciliation automates the end to end refund process between nue and quickbooks, reducing the risk of manual entry errors and saving significant time for finance teams ensures accurate, auditable records all refunds are linked to invoices, credit memos, and a clearing account in qbo, supporting robust audit trails and compliance requirements supports flexible business scenarios handles full and partial refunds, multiple refunds per invoice, and both credit memo and negative invoice workflows—accommodating diverse customer and accounting needs learn more customer use cases use case 1 after a customer fully pays an annual subscription invoice, they cancel part of their service midway through the year the finance team in nue processes a partial refund for $500 nue generates a credit memo and applies it to the original invoice in quickbooks, then creates an expense mapped to the “nue clearing” account all records are linked, and the refund status updates automatically in both nue and quickbooks the finance team sees the new refund in their qbo ledger immediately, with no manual steps required use case 2 a customer makes multiple partial payments and subsequently requests two separate refunds for a single invoice nue tracks each refund event, creating distinct credit memos and expenses for each in qbo, and updates the cumulative refund status on the invoice this allows the customer and finance team to see exactly which amounts were refunded, and when, across both systems use case 3 a company uses stripe for collections but wants refunds to flow into quickbooks for accounting when a stripe refund is triggered, nue orchestrates the refund event, ensuring the correct credit memo/expense is created in qbo, mapped to the clearing account, and visible alongside all related invoices for a unified financial record how it works refund event in nue triggers workflow validates that customer and invoice records exist in qbo; retries up to 5 times if not creates credit memo or negative invoice in qbo and applies it to the original invoice generates an expense in qbo mapped to the configured clearing account all actions are recorded in nue’s transaction hub, with external ids and status updates dependencies and limitations required settings quickbooks integration must be active and properly configured in nue, including the “nue clearing” account mapping upstream customer, invoice, and product mappings must be complete for seamless sync choice between credit memo or negative invoice routing is determined by system settings edge cases / limitations quickbooks refund receipts cannot be linked to credit memos; this workflow always uses credit memo + expense for proper auditability not all legacy qbo accounts may support advanced mapping or clearing account features—review your quickbooks setup if you encounter limitations apply and unapply credit memo to netsuite the netsuite integration now adds full two way support for applying and unapplying credit memos—including standalone credit memos—between nue and netsuite, with robust ar, gl, and audit synchronization this includes full and partial apply of credit memos to invoices, as well as full unapply (removal) of credit memo applications from invoices in both the nue ui and via api standalone credit memos (not created from an invoice) are also now seamlessly synced and available for application/unapplication to any eligible invoice in netsuite all actions are logged in transaction hub, reflect in real time status, and are fully auditable why it matters enables accurate, real time accounts receivable and credit ledger sync between nue and netsuite—reducing manual reconciliation, errors, and audit risk supports modern finance operations standalone credit memos, dispute resolution, and write offs are now streamlined for both billing and revenue management teams aligns with netsuite and industry best practices ensures all credit applications/unapplications are reflected with correct status, ar movement, and compliance logging (no gl entries created for non cash credit applications) learn more customer use cases use case 1 a finance user issues a standalone credit memo in nue to resolve a customer dispute unrelated to a specific invoice once activated, the credit memo is automatically synced to netsuite later, the credit is applied to an open invoice chosen by the finance team all actions, including later unapplication (if the dispute is reopened), are tracked and synced use case 2 a customer overpays and receives a credit memo for the excess the finance team can now apply that credit to any open invoice in netsuite if an application is later reversed, the credit memo balance is restored and the invoice balance increases, with all changes automatically reflected in both systems use case 3 during a year end write off for bad debt, the finance team uses nue to generate a credit memo for the uncollectible amount (“payment operation” type) and applies it to the invoice for a clean ar closeout netsuite receives the credit memo and application, ensuring books are properly reconciled and audit compliant how it works apply or unapply a credit memo to/from an invoice via the nue ui or api standalone credit memos can be created, saved as draft, activated, and applied to one or more invoices on unapply, the full unapplied amount is restored to the credit memo and invoice (partial unapply not supported in this release) all application/unapplication actions are logged as payment applications (operation apply/unapply) in transaction hub, and webhook events (credit memo applied, credit memo unapplied, etc ) are raised for integrations no netsuite customer payment record is generated for pure credit applications/unapplications—this matches netsuite’s ar process for non cash credits all actions are visible in nue transaction hub for reconciliation, retry, and error tracing dependencies and limitations netsuite integration must be configured as the ar/gl or collections endpoint for correct routing partial unapply (removal of only part of an applied credit memo) is not supported in this release—only full unapply is available via nue ui/api if a customer, invoice, or credit memo does not exist in netsuite or transaction hub, the sync fails gracefully with error logging and user notification gl entries are not created for apply/unapply unless there is an actual cash movement, per netsuite best practice write off scenarios use a credit memo with “payment operation” as the source, not a void or delete operation sync and manage credit memos to netsuite this release enables comprehensive support for creating, applying, unapplying, and synchronizing all major types of credit memos (cms) from nue to netsuite —including standalone credit memos, credit memos generated directly over invoices, and write offs the feature ensures that all credit memo lifecycle actions—drafting, activation, application, reversal, and status tracking—are mirrored accurately in netsuite, with robust sequencing and error handling built in standalone cms support full draft/edit/activate lifecycles, with custom fields and tax calculation; invoice generated and write off cms are auto applied with strict controls to prevent over application or improper write off of fully paid invoices all application states and failures are surfaced in transaction hub for transparency and audit why it matters reduces accounting risk ensures all credit memo actions (creation, application, reversal, write off) are synced in real time to netsuite, eliminating manual reconciliation and reducing the risk of financial reporting discrepancies accelerates collections and dispute resolution enables finance teams to resolve disputes, process adjustments, and write off bad debt efficiently, directly from nue, with immediate downstream impact on a/r and customer balances supports enterprise audit and compliance provides full audit trail and error recovery, with all sync and application events traceable in transaction hub—addressing critical requirements for large customers and public companies learn more use case 1 a finance team identifies a customer dispute requiring a partial credit on a previously issued invoice they create a credit memo directly from the invoice in nue the system auto fills the invoice details and calculates the allowable credit upon activation, the credit memo is auto applied to the invoice, instantly updating balances and reflecting the transaction in netsuite for accounting use case 2 a customer requests a refund for an overpayment unrelated to an invoice the revops manager creates a standalone credit memo in draft, customizes fields and tax details, and, after internal review, activates it the memo is then applied to an open invoice, or left for future use, and the sync to netsuite confirms proper revenue and receivables adjustments use case 3 collections identifies an invoice as uncollectible after partial payment the finance user selects "write off," and nue generates a write off credit memo for the unpaid balance, applies it, sets the invoice status to "written off," and syncs the action to netsuite, ensuring proper bad debt accounting and audit compliance how it works standalone credit memos are created in draft, supporting edit, tax calculation, and custom fields before activation credit memos can be created directly from invoices ("generatefromtransaction") or as write offs, each with strict system checks to prevent over application or race conditions activation auto syncs the cm to salesforce and netsuite and, if from invoice, applies it immediately all cm application, unapplication, cancellation, and reversal actions are tracked and synced, including error retries via transaction hub api and ui flows enforce validation credit amounts cannot exceed invoice balances; write offs cannot be performed on fully paid invoices technical details supports all cm sources standalone, generatefromtransaction, payment operation (write off), and more draft/active/applied/unapplied/transferred/write off statuses are mapped and synced to netsuite sync failures and errors are logged in transaction hub, with batch/manual retry options dependencies and limitations requires netsuite integration and relevant nue roles/permissions standalone credit memos must be activated before they can be applied; only draft status is editable credit memos cannot be written off for fully paid invoices; applications are system limited to available balances sync failures (e g , netsuite downtime) will surface in transaction hub and require manual retry some advanced edge cases (e g , creditconversion type) may require special downstream mapping per integration show centralized snapshot of the entire integration stack this feature enhances the integration overview dashboard in nue by allowing admin users to see all available integration types—such as crm, payment, accounting, revenue recognition, taxation, and e invoicing—along with their associated integration instances each instance is clearly marked as “connected” or “not connected ” the interface uses a card based layout, so each integration instance is visually separated by type, and users can immediately identify which business process (e g , payments, accounting) each integration powers some integration types (crm, taxation) are auto managed, while others (payment, accounting, revenue recognition, e invoicing) can be manually configured and managed by users with appropriate permissions why it matters reduces configuration errors and ensures compliance centralizing integration management with clear type labeling and connection status prevents misconfigurations, duplicate integrations, and non compliant setups this is especially critical for audit readiness and financial controls improves operational transparency and troubleshooting admins and finance/ops teams can see at a glance which systems are powering each business process, making it easier to troubleshoot, trace data flows, and support business continuity enables flexible, modern revenue operations supports hybrid and omnichannel setups (e g , stripe for payments, qbo for accounting, netsuite for revenue recognition), letting organizations align integrations to their real world operations and growth needs learn more customer use case use case 1 a saas company uses stripe for collections (payments), quickbooks online for accounting, and avalara for taxation with the new integration overview, the admin logs in and sees each integration instance grouped by type, with “stripe” shown as “connected” under payment, “qbo” as “connected” under accounting, and “avalara” under taxation the admin cannot accidentally assign avalara to both taxation and e invoicing, since business rules enforce one active instance per type when a payment issue arises, they quickly confirm which system is responsible and navigate directly to the relevant rules or settings page from the dashboard use case 2 a finance team at a multi entity enterprise manages separate quickbooks instances for different subsidiaries in integration overview, they see each instance grouped by type and entity, with clear connection status this helps ensure transactions for each business unit are correctly routed, and auditors can verify integration status at any time use case 3 during an audit, a compliance officer needs to verify which system is the source of truth for tax calculations they use the dashboard to confirm only one taxation integration (avalara) is active and that salesforce is the sole crm, both auto managed by the system, reducing risk of accidental misassignment how it works the integration overview dashboard displays a card for each integration type (crm, payment, accounting, revenue recognition, taxation, e invoicing) each card lists connected integration instances, with a purple ribbon for “connected” and clear indicators for “not connected ” admins can add, activate, or deactivate integrations for most types, except crm and taxation, which are auto managed only one instance per integration type can be active at a time; business rules block duplicates or misassignments “payment rules” are directly hyperlinked for rapid configuration for multi entity use cases, quickbooks and netsuite can have multiple instances, each with its own configuration bug fixes everything billing improved word wrapping for long text fields in invoice templates this fix ensures that long text in invoice templates is now wrapped appropriately, even when email addresses or other fields contain extensive content users will see the full text neatly contained within the template layout, resulting in clearer, more professional looking invoices developer experience change order creation no longer fails for customers with long names change orders can now be created for customers with names longer than 64 characters using self service apis the process is seamless regardless of customer name length accurate prorated credit for self service cancellation of monthly subscriptions mid term credits for mid term cancellations of monthly subscriptions through the self service api are now precisely prorated this ensures customers receive the correct amount for unused subscription time integrations improved support for nue self service customer id in /stripe/import/customer mapping endpoint the /stripe/import/customer mapping endpoint now fully supports nue self service customer ids this enhancement ensures customer mapping imports proceed smoothly, regardless of whether the customer record originates from salesforce or is created via nue’s self service functionality