Release 2505 - 07/24/2025

release highlights introducing netsuite and quickbooks accounting integration introducing netsuite and quickbooks accounting integration netsuite and quickbooks accounting integrations are now live! set up your integration use cases in a flexible way for maximum configurability dynamic option support for self service dynamic option support for self service the flexibility of dynamic options is now available for self service implementations configure and reconfigure bundles with dynamic options to unlock omnichannel revenue feature enhancements lifecycle manager enable central and individual grid layout resets managing user interface consistency just got easier administrators can now centrally reset any user customized grid layouts such as product & pricing list views and line editors back to system defaults for all users with a single action from platform settings additionally, individual users can self serve and reset their own line editor layouts (on nue on salesforce) to default directly from their working screen why it matters ensures all users see the correct, intended ui instantly after admin or compliance driven changes reduces support tickets and manual troubleshooting, saving admin and user time maintains strong ui/ux consistency and compliance, especially after major updates or releases learn more customer use cases use case as a system administrator, taylor manages a large sales organization where users frequently personalize their grid views and filters after a critical update—adding a new compliance required field—taylor uses the reset to system default reset to system default action in the system admin settings instantly, all users’ layouts revert to the system default, ensuring compliance and eliminating the need for each user to clear their own cache or miss important changes use case jordan, a sales rep, experiments with customizing the quote line editor for personal workflow after accidentally hiding critical fields and misconfiguring filters, jordan uses the new reset (layout) reset (layout) button within the editor with a simple confirmation, their editor reverts to the standard company layout, saving time and avoiding a support ticket use case a customer support lead at vroom notices several reps have outdated list configurations after a ui refresh instead of walking each agent through manual fixes, the support lead triggers a global reset from the system admin console, ensuring all agents operate from a consistent, up to date layout—improving data accuracy across the team dependencies and limitations requires admin access to perform central resets; end user resets limited to their own layouts only layouts tracked via local storage are affected; does not revert changes outside supported list/edit views for salesforce side layouts, relies on custom settings and the associated refresh api related resources read further documentation on this feature here user interface settings docid\ vwjaijenmbi0ndlbihwn6 configure decimal places displayed for pricing fields on line editor system and revops administrators can now configure the number of decimal digits—between 0 and 3—displayed for key pricing fields (like list price, sales price, net sales price, discount, subscription term) in the nue quote and order line editors precision can be set individually for each field, currency, and unit of measure (uom), making it easy to match your quoting experience with backend calculation accuracy and external system requirements this change ensures that price granularity is both visible and auditable for customers with advanced pricing and integration needs why it matters eliminates manual workarounds and reduces confusion by letting admins match ui precision to backend and external system requirements reduces pricing disputes, invoice errors, and reconciliation issues with payment and revenue platforms (e g , stripe, rightrev) enhances quoting accuracy for products with granular pricing or complex multi currency requirements, supporting enterprise sales and compliance needs learn more customer use cases use case a revops admin at an ai provider needs to quote a product with a unit price of $0 065 per api call previously, rounding forced them to display only two decimals, resulting in confusion and mismatches between backend calculations and the ui with the new decimal places configurator, they can display up to three decimals for this sku in the quote line editor, ensuring reps and customers see the actual price used for all calculations—reducing quote disputes and improving trust use case a global saas provider sells subscriptions in both usd and jpy their finance team requires all usd prices to show two decimals (e g , $100 00), but jpy should show no decimals (¥5000) with this feature, the admin can configure field level decimal places for each currency, ensuring compliance with local expectations and reducing manual adjustment on exports to payment or revenue systems use case a billing operations manager regularly deals with tiered pricing for high volume customers some tiers use prices with three decimals to ensure accurate billing over large quantities they can use the decimal places configurator to set three decimals for net sales price net sales price in the quote line editor for specific uoms, making quotes and invoices precise and reducing the risk of under/over charging due to rounding how it works find the decimal places configurator under nue settings > quotes & orders select the field (e g , list price, net sales price, discount) and currency you wish to configure; optionally filter by uom (unit of measure) choose the desired decimal precision (0–3) using the standard number selector; default is 2 once saved, the updated decimal precision is immediately reflected in the quote and order line editor for all users—affecting only the ui display, not the backend calculation if no custom setting exists, precision falls back to uom or currency system defaults depedencies and limitations only available for select fields in the quote and order line editors (unit/tiered prices, not aggregates or all fields) maximum precision is 3 decimals; configurations above this aren’t supported currencies and uoms must be present in salesforce and nue, respectively related resources read further documentation on decimal places configurator decimal places configurator within the quotes & order section in system settings docid\ np misfd5uisidyfq8lnl enable automatic propagation of billing & payment settings from quote header to line buckets managing billing settings during the quote to order process is now more reliable and configurable a new system level setting allows organizations to automatically sync changes made to billing related fields (like billing period and payment term) on the quote header to all associated line buckets before finalizing an order this eliminates mismatches and billing errors when sales reps update billing details during negotiation, ensuring consistency from quote through to order conversion the feature brings nue’s approach in line with industry best practices and significantly reduces manual corrections for revenue teams why it matters dramatically reduces billing errors and manual order corrections caused by misaligned billing periods or payment terms between quote and orders saves hours of support and customer success effort each week, especially for high volume or complex quoting environments supports both strict billing policy enforcement and flexible, exception based selling—scaling to diverse customer needs and sales processes learn more customer use cases use case a sales operations manager at a saas company frequently negotiates contract terms with enterprise clients after saving a quote and creating line buckets for different business units, the customer requests annual instead of monthly billing with the new setting enabled, the manager updates the billing period on the quote header, and the system automatically syncs this change across all line buckets—ensuring the final order accurately reflects the negotiated terms and avoiding hours of manual bucket edits use case a customer success team supporting a high volume customer previously spent hours each week manually correcting orders because payment method changes made after a quote was saved did not update line buckets now, when the sales rep adjusts payment terms or billing periods in the quote header before finalizing, the updated values seamlessly propagate to all existing buckets streamlining order creation and virtually eliminating billing disputes and rework use case a revenue operations admin at a multinational company needs to enforce strict billing policy alignment across all deals but also supports complex cases where some line buckets require unique billing periods (e g , for subsidiaries billed differently) by keeping the override setting enabled, admins ensure all buckets default to the latest header values, while still allowing reps to manually override settings at the bucket level for special scenarios—ensuring both control and flexibility dependencies & limitations only those fields which are configured in the object mapping between the quote object & line bucket object will be copied over when the setting is enabled e g billing period is not configured to copy over by default by default, the setting is off organizations must enable it to gain automatic propagation related resources for more details, refer to the override setting use case in quote and order split docid\ uywunaqmbqgsrpessui68 enable programmatic reconfigure support for dynamic product options the global method ruby globalchangeorderservice now supports dynamic product options in bundles with this enhancement admins and automation can programmatically add, remove, or reconfigure subscription add ons that are defined dynamically (via product and price filters) the api accepts both a productoptionid and a pricebookentryid, allowing support for composite ids and making it possible to automate complex, evolving bundles with minimal manual maintenance this is crucial for customers with large catalogs, multiple currencies, or frequently changing skus, as it ensures bundles always present the right options in both ui and api driven workflows use case an admin automates subscription renewals and upgrades for customers by using the global method api, they can add new add ons or change quantities on bundles based on the latest dynamic product options the api references eligible options using composite productoptionid and pricebookentryid, ensuring the right sku and price are always used for each customer’s region and account type learn more how it works in the change order service, users can create ruby globalreconfigurenewproductrequest objects, specifying productoptionid and pricebookentryid, and add them to reconfiguration requests the backend resolves available options dynamically at runtime, based on the latest catalog and filter logic (including nested/bundle within bundle and multi attribute pricing scenarios) for more information, please check out this example in apex global methods and services docid\ upanqs 1lf0n z1z uh55 for more details enable programmatic sync of primary quote to opportunity admins and integration engineers can now programmatically synchronize a primary quote with its associated opportunity in salesforce using a new apex global method this feature eliminates the need to manually toggle the primary quote primary quote checkbox—a process often blocked by contract approval workflows and validation rules—streamlining exception handling, automation, and bulk operations for authorized users use case an enterprise salesforce admin is tasked with resolving data inconsistencies where a primary quote’s updates are not reflected in its opportunity due to locked records or ongoing approval processes instead of unchecking and rechecking the primary quote primary quote box (which would violate business logic and trigger unwanted approval flows), the admin calls the global method to force a sync, ensuring the opportunity reflects the latest quote details while staying compliant with company policies learn more how it works located in salesforce as a global apex method callable by admins, automation, or integration users (e g , via apex script, flow, or process builder) accepts either a single quote id or a list of quote ids; only primary quotes are processed (non primary quotes are skipped or trigger error messaging as appropriate) for more information, please check out apex global methods and services docid\ upanqs 1lf0n z1z uh55 for more details switch primary quote to different opportunity and synchronize quote line items enables sales representatives to move a primary quote from one salesforce opportunity to another and ensures all quote line items are re synchronized as opportunity products on the new opportunity this workflow maintains sales data integrity, supports sales agility, and ensures downstream pipeline, forecasting, and order generation accuracy this feature requires the “create quotes without a related opportunity” setting to be enabled in your connected salesforce org to turn it on, log in to salesforce and go to setup → quotes → settings why it matters improves crm data accuracy and auditability by ensuring that quotes and their associated products are always linked to the correct opportunity, reducing pipeline reporting errors and revenue misattribution increases sales efficiency and flexibility by allowing sales teams to correct data entry mistakes or realign opportunities and quotes as account strategies evolve, without manual rework or data loss minimizes revenue leakage and downstream operational risk by automatically syncing quote line items to the new opportunity’s product list, ensuring consistent pipeline, order, and revenue recognition processes learn more dependencies and limitations standard salesforce restricts editing the opportunity field on a saved quote; this feature requires “ create quotes without a related opportunity ” to be enabled or custom logic to support switching only one primary quote can be active (and synced) per opportunity at a time when switching, the new opportunity’s products are overwritten with those from the moved primary quote, and the opportunity's original primary quote, if there exists any, will be replaced by the new primary quote sync failures can occur if product mappings are missing, users lack edit permissions, or custom flows/triggers in salesforce interfere; robust error handling and admin override are required closed won opportunities may have additional sync restrictions, depending on system setting in nue connect or reconnect your salesforce org to your nue tenant effortlessly nue now enables admins to connect or reconnect a nue sandbox tenant to a salesforce sandbox org through a dramatically simplified, automated process previously, this required many manual, error prone steps—now, the entire integration can be accomplished with just a few clicks via an intuitive ui, with all critical syncs and error handling built in this enhancement covers both new connections and reconnections (e g , after a salesforce sandbox refresh), ensuring that all system critical objects and configurations are processed automatically why it matters reduces admin time and friction for salesforce integration from over an hour to just minutes, freeing up cs and implementation teams for higher value work enables rapid, reliable onboarding, testing, and troubleshooting for enterprise customers who need to maintain multiple salesforce sandboxes and aligned nue tenants ensures business continuity and data accuracy by handling data merges, sync, and error resolution automatically how it works the nue on salesforce setup and configuration guide docid\ bb flgeq o4hyjmbqrxd5 has been updated to reflect this change please refer to this article for more details everything billing edit subscription billing fields directly in lifecycle manager managing and correcting subscription billing details is now faster and more flexible sales and customer success teams can directly view and edit billing fields—such as billing account, billing period, bill cycle day, payment method, and more—right from the lifecycle manager ui, without needing a full change order all updates are instantly synchronized across nue and connected systems, reducing operational overhead and accelerating customer support why it matters reduces time and risk by eliminating the need for full change orders when only billing details need updating empowers business teams to self correct onboarding or legacy data errors, reducing engineering intervention improves data integrity and integration with external billing/erp systems through real time, auditable updates learn more customer use cases use case as a sales rep at a saas company, alex receives a customer request to transfer a subscription to a different billing account due to a corporate acquisition previously, this would require a full change order, risking accidental term or quantity changes with this new feature, alex opens the lifecycle manager, selects the affected subscription, clicks “update fields,” and updates the billing account in seconds the change is securely propagated to all downstream systems, ensuring invoices and integrations are always accurate use case a revops admin needs to empower the finance team to manage which subscription billing fields are editable by end users using nue’s configurable “subscription fields” field set, the admin includes “payment term” and a custom “po number” field, making only those fields editable for non admins this ensures compliance and auditability while enabling efficient updates through both ui and api based processes how it works accessed via the “more…” menu on each subscription card in the lifecycle manager ui; select “update fields” to open a popup with all editable fields fields displayed are defined by the admin in the “subscription fields” field set; only those appear for editing changes are validated and synchronized in real time to nue via patch api; related objects (asset, billing asset, usage subscription) are automatically updated unsupported or uneditable field changes are blocked, with clear error messages returned to users dependencies and limitations editing of asset or entitlement fields is not yet available in the ui only fields added to the “subscription fields” set by admins are available on the fields edit page related resources for more details of this feature, please refer to lifecycle manager overview docid 5ssag0lkcdwbdhypx0wn configure billing job batch size at system level managing large scale billing operations is now faster and more flexible administrators can configure the “billing job batch size” at the system level, tailoring how many billing accounts are processed in each batch run this update empowers customers to optimize billing performance for their data volume—reducing billing cycle time for high volume enterprises and ensuring smooth operation for smaller tenants settings are validated and take effect immediately for new jobs, with a safe, admin friendly experience why it matters reduces billing run time for large customers, improving cash flow and customer satisfaction enables operational agility—admins can self tune system performance without engineering support lowers operational costs and risk by preventing out of memory errors and minimizing job failures learn more customer use cases use case as a billing administrator at a global saas provider with thousands of customers, i need to process monthly invoices quickly without running into system slowdowns by increasing the batch size to 2000, i reduce the number of batches and complete billing runs in a fraction of the time, ensuring customers get invoices on schedule and our finance team meets internal slas use case a system admin at a mid sized company notices that billing jobs are taking longer as their customer base grows without waiting on engineering, they adjust the job batch size from 300 to 500 in the nue system settings, instantly improving runtime and freeing up it resources for other critical tasks how it works access “billing job batch size” in nue system settings → billing default batch size is 300; users can enter any integer between 20 and 2000 when an out of range value is entered, the ui and backend both prevent saving and display a clear error message the new setting is stored system wide and is immediately used for any billing jobs started after the change dependencies and limitations only available at the system (tenant) level—no per job or per user customization out of range entries (below 20 or above 2000) are not accepted changes only affect billing jobs started after the update; active jobs continue with prior configuration related resources for more details of this setting, please refer to this article enable automated recovery of in progress billing jobs after service restart the nue billing engine now automatically detects and resumes any ongoing billing jobs that were interrupted due to a service restart, redeployment, or crash this enhancement is fully automated—no manual intervention is required—and is designed for enterprise customers who run large, recurring, or multi batch billing schedules the outcome uninterrupted, reliable billing operations even during infrastructure events, with robust safety in multi tenant and distributed cloud environments why it matters dramatically reduces the risk of revenue leakage or operational errors after service interruptions reduces the burden on support and engineering teams by eliminating the need for manual reruns or recovery after restarts how it works billing job recovery is triggered automatically on service startup or at periodic intervals, requiring no user action jobs in "cancelled," "completed," or "error" states, or lacking required session context, are not resumed and are marked appropriately for auditing enhance invoice and quote pdf generation to ensure data quality nue now generates text based invoice and quote pdfs instead of image based files this improvement ensures that pdfs downloaded are consistently clear, readable, and small in size—even after passing through email security filters or compression with this change, end customers can reliably process invoices and quotes, reducing support issues and payment delays why it matters dramatically improves the quality and reliability of invoice and quote pdfs, reducing payment cycle delays and customer complaints reduces file size by >95%, lowering storage and email transmission costs and enabling faster delivery learn more how it works access the “generate pdf” feature for invoices and quotes from their detail pages in the nue ui pdfs are generated as text based files with embedded standard fonts (e g , arial, helvetica) for maximum compatibility and clarity generated pdfs can be attached automatically to salesforce quotes or opportunities, or delivered as secure smart/magic links for external recipients dependencies and limitations legacy image based pdfs are no longer supported for new document generation synchronize credit types and credit pools when connecting nue tenant to salesforce managing cross platform credits just became automatic with this feature, nue tenants gain seamless synchronization of credit types and credit pools with connected salesforce orgs—ensuring both platforms have an identical view of core credit data this minimizes billing errors, eliminates manual reconciliation, and provides a reliable foundation for advanced product and billing workflows why it matters reduces manual work and eliminates errors associated with out of sync credit data between nue and salesforce accelerates tenant provisioning, migration, and sandbox testing—cutting operational friction and support tickets learn more customer use cases use case a revops manager provisions a nue sandbox tenant from production to test new billing configurations upon connecting the sandbox to a new, empty salesforce org, the manager needs all existing credit types and credit pools copied over automatically the sync ensures the sandbox and salesforce org are instantly aligned, so product testing and billing operations proceed without data mismatches or manual imports use case an admin connects a nue tenant to a salesforce org that already contains its own set of credit types and credit pools, such as a freshly refreshed sandbox or one created from a trialforce template the admin worries about conflicts or duplicates the sync feature reconciles and merges all credit objects, ensuring unique identifiers are harmonized and no billing or order sync errors occur how it works the feature is triggered automatically when connecting or switching a nue tenant to a salesforce org; admins can also invoke the sync manually via post /billing/credit types\ sync please refer to api documentation for details the synchronization process detects discrepancies—if one platform is missing credit types or pools, it copies them from the other; if both have data, it merges based on composite keys (id, name, category/type) all enabled credit types and credit pools are guaranteed to match in both nue and salesforce post sync, supporting downstream billing and product configuration no special configuration is needed; it’s enabled by default for tenants using salesforce integration dependencies and limitations requires salesforce integration to be active only enabled credit types and credit pools are synchronized propose standalone credit memos for disputes the standalone credit memo for disputes feature enables finance operations users to create credits directly on a customer account, independent of any specific invoice this allows teams to issue credits for disputes, goodwill, post sale discounts, or operational corrections, and later apply those credits to open invoices as needed standalone credit memos support granular control—users select the customer and one or more active products, set transaction amounts these memos can be saved as drafts and automatically synced to salesforce, and available for application to eligible balances why it matters streamlines dispute resolution by providing a flexible, auditable workflow for customer credits not tied to specific invoices supports compliance and accounting requirements by syncing all standalone credit memos (draft or active) to salesforce, ensuring a clear audit trail increases operational agility by enabling rapid, proactive credits for customer satisfaction or account management needs, without waiting for invoice reversal or refund processes learn more customer use cases use case a customer experiences a service disruption and is granted a goodwill credit by the account team instead of adjusting a past invoice, finance creates a standalone credit memo for the affected product(s), saving it as a draft for internal review before activating once approved and activated, the memo is applied to the customer’s next open invoice, reducing the amount owed and providing clear documentation for both parties use case a sales team negotiates a post sale discount on an annual contract after renewal is finalized rather than reissuing the invoice, finance issues a standalone credit memo for the discount amount and applies it to the next billing cycle’s invoice, ensuring accurate reporting and customer satisfaction use case a customer dispute leads to a credit being issued for overages or billing errors that span multiple invoices finance creates a standalone credit memo, selecting the relevant products, and later applies portions of the credit to several outstanding invoices as the investigation is resolved, with full tracking in both nue and salesforce how it works users create a standalone credit memo from the credit memo list page, selecting the customer and any active products for crediting the memo can be saved as a draft, edited (including items, amounts), and then activated when ready due date for standalone memos is set to 2999 12 31 by default to flag as “never expires ” once activated, the memo is locked for edits and can be applied to any invoice for that customer all status changes (draft, activated, canceled) are automatically synced to salesforce for compliance dependencies and limitations netsuite/quickbooks full support for syncing standalone credit memos to these platforms is planned for a post 2505 release; manual adjustment may be required in the interim only active products are eligible for selection when creating memo items; at least one product item is required per memo due date is fixed far in the future (2999 12 31) to avoid ar confusion related resources please refer to collections credit memos and debit memos for more details about this feature support mapping stripe payment metadata nue now supports api driven mapping of invoice—both standard and custom—directly into metadata on stripe payment objects through a dedicated rest endpoint, users can automate population of stripe payment metadata using either dynamic data (pulled from nue fields at runtime) or predefined static values the mapping configuration is flexible, enforces validation, and streamlines integration with downstream financial operations why it matters streamlined accounting and integrations automatically populate stripe payment metadata necessary for reconciliation and downstream sync with systems like netsuite and quickbooks no manual data entry required reduce risk eliminates manual steps and associated errors for finance and implementation teams by automating business critical field population greater flexibility customer success, finance, and it teams can rapidly adapt stripe payment metadata mappings to changing business requirements—without engineering support learn more customer use cases use case set up a mapping that writes a custom field—"block downstream—into stripe invoice metadata, and the downstream integration checks this value to block the downstream process how it works mapping is configured via a rest api (post /stripe/metadata mapping) specifying source object/field (e g , invoice custom field), optional fixed value, and target stripe object/field (e g , payment metadata key) validation restricts mappings to allowed objects/fields; descriptive errors are returned for invalid configurations the mapped values are automatically written into stripe metadata related resources please refer to this stripe integration setup article for more detailed information about this feature developer experience publish and use bundles with dynamic options admin users can now publish product bundles with dynamic options, where bundle options are determined by flexible, filter based rules instead of static lists customers can use apis to subscribe to these bundles or reconfigure active bundle subscriptions—adding/removing options—by placing initial or change orders this unlocks flexible options when working with different prices, attributes, and currencies why it matters dramatically reduces operational effort—new products, currencies, or prices are auto included in bundles after a republish, eliminating manual updates enables true customer self service customers can subscribe, reconfigure, and upgrade bundles via api, accelerating time to value and reducing support load learn more customer use cases use case a saas customer wants to offer their end users the ability to quickly subscribe to bundles that always include the latest set of integration add ons matching specific criteria (such as “all integrations available in usd”) by leveraging the self service api, their onboarding flow allows users to pick from up to date bundle options—no delays or manual updates required—ensuring that the right add ons are available in every subscription use case a customer success team wants to empower existing customers to reconfigure their bundles on demand—adding or removing features as their needs change using the api, customers can place change orders against their subscriptions, selecting from all eligible options based on the latest published bundle—keeping their subscriptions current and reducing support cycles for common requests how it works admins define dynamic options on bundle products using flexible product and price filters within the ui (e g , “all products in category x, all currencies except jpy”) on publish (or republish), the system generates concrete product options in the catalog based on the filter criteria only published options are available to end users product option id's for dynamic options have the structure of productoptionid pricebookentryid an example would be a0grt0000047sqhia2 01urt000005bexliam dependencies and limitations api clients must use the composite option id format and reference only currently published options enable adding product options to bundle subscriptions via self service api self service users can now add new product options (add ons) directly to existing bundle subscriptions using the api this feature supports complex business rules—such as quantity constraints, eligibility, and validation of hierarchy—mirroring the controls available in nue on salesforce customers gain flexibility to upgrade their bundles as needs evolve without sales or support intervention why it matters reduces manual intervention—customers self serve mid term upgrades, driving faster adoption and reducing support workload increases average order value and retention by enabling flexible, real time upsell/cross sell of add ons learn more customer use cases use case a saas operations manager at a mid size company needs to quickly enable an additional analytics module for their team instead of submitting a ticket or waiting for a sales rep, they log into the self service portal, select their current bundle subscription, and add the analytics add on the system instantly validates eligibility and quantity, updates the quote, and activates the change—enabling the team to use the new feature right away use case an it lead at an enterprise with a multi level bundle structure needs to add a nested security add on to a sub bundle they use the api to specify the new add on at the appropriate hierarchy the system recursively checks maximum nesting depth, validates parent child relationships, and returns an error if the add on is not eligible for that bundle level—preventing mistakes before they happen how it works submit a “reconfigure” change order via the api with the target assetnumber and desired add ons “linktobundlequantity” add ons automatically update their quantities if the bundle quantity changes; non linked add ons must be updated directly real time validation and error handling return specific messages for invalid configurations—e g , exceeding allowed options, missing required add ons, or invalid dates dependencies and limitations “reconfigure” change orders cannot be combined with other change types (e g , renewal) in a single transaction maximum supported nesting is one level; deeper configurations are not permitted related resources read further documentation on this feature here integrations enable granular gl account mapping configuration for your erp integrations managing financial sync just got smarter nue now allows admins to configure detailed account mappings between nue product categories and both quickbooks online (qbo) and netsuite item types and gl accounts —down to the income, cogs, asset, and deferred revenue account level with new clearing account logic, payments collected in stripe or other gateways will also be routed seamlessly to dedicated “nue clearing accounts” in the erp, ensuring accurate reconciliation, compliance, and error transparency for hybrid collection and accounting workflows why it matters enables audit ready, sox/gaap compliant financial reporting by automating detailed account level postings at scale reduces manual reconciliation time and eliminates spreadsheet errors—especially for hybrid stripe/erp collection flows surfaces errors and sync issues in real time, reducing close cycles and supporting faster, more accurate financial operations learn more customer use cases use case a finance manager at a saas company needs to automate posting of all sales and billing activity from nue into netsuite for sox compliant, audit ready reporting they configure product by product mappings to ensure every invoice and payment is attributed to the correct gl account, and use the transaction hub to monitor sync status and resolve errors before close—eliminating manual spreadsheet work and audit risk use case a billing operations lead uses stripe for collections but relies on quickbooks as the system of record for accounting when stripe collects payment, nue creates a corresponding payment in quickbooks, debiting a user defined clearing account and crediting ar this enables their team to reconcile bank deposits, handle stripe fees, and keep ar in balance—without duplicate payments or missed revenue use case a revops admin needs to issue a credit memo for a customer dispute and wants the credit to sync from nue to netsuite, hitting the correct revenue and clearing accounts they activate the credit memo in nue, which syncs downstream with line level gl mapping, tracked status, and all error logs visible in transaction hub for end to end transparency how it works admins configure product category to erp item type and gl account mappings in a guided setup ui, with dropdowns to select from active accounts (by name for qbo, by id for netsuite) payments collected through stripe or other third party gateways are routed into a dedicated “nue clearing account” in the erp, configurable during setup only active (non draft) products and bundles are synced; product updates trigger mapping updates in erp as needed invoices, payments, credit memos, and refunds are transferred downstream, each line item referencing the mapped product/item and account for precise gl impact transaction hub tracks every sync event with statuses not transferred, transferred, or failed errors are logged and surfaced, with retry functionality netsuite allows customer level ar account mapping; qbo uses its global default ar account for customer sync technical details supports full object sync products, customers, invoices, payments, refunds/credit memos tray io is used as the orchestration layer for api connectivity, batching, and error handling custom field mapping allows synchronizing additional business attributes (e g , tax codes, user fields) between nue and netsuite automated batching and throttling manage netsuite api concurrency limits (default 4 concurrent requests) related resources read further documentation on this feature here configure your integration use case with ease enable payment and collections and revenue recognition in your netsuite and quickbooks integrations nue now allows admin users to independently enable and configure payment/collections and revenue recognition use cases directly from the integration settings ui for the netsuite and quickbooks integrations the accounting integration is activated by default as part of the integration and sets the accounting status this granular control means organizations can route invoices, credit memos, and related financial transactions to the correct downstream system, with clear, auditable status for each integration type real time status visibility and conflict prevention help eliminate double entry and manual reconciliation, supporting flexible, compliant finance operations why it matters supports hybrid and evolving finance stacks, allowing organizations to scale or change systems from without downtime or data confusion for each invoice and credit memo, nue surfaces “payment status,” “accounting status,” and “revenue status” in the ui, with values such as “not transferred,” “transferred,” or “error/failed,” updated based on responses from the external system reducing manual reconciliation and risk of double entry by providing clear, auditable status for each transaction and integration learn more customer use cases use case as a finance systems admin at a saas company, priya is migrating from a single erp to a hybrid stack where stripe handles collections and netsuite arm is used for revenue recognition with nue’s new integration toggles, she enables only the payment/collections flow to stripe and the revenue recognition flow to netsuite arm this ensures invoices are paid through stripe but revenue schedules sync to netsuite arm, eliminating double data entry and giving her team real time status tracking for each transaction use case david, a director of revops, needs to onboard a new business unit that uses quickbooks for accounting and collections, but will implement rightrev for revenue recognition he configures nue to enable both payment/collections and revenue recognition integrations, mapping each business unit’s transactions to the appropriate systems this setup allows each entity to operate independently while maintaining consolidated audit trails and compliance across the organization use case samantha, an implementation consultant, is working with a client who previously had payment syncs enabled in both stripe and netsuite during setup in nue, the system detects the conflicting configuration and surfaces a warning, preventing duplicate payment records she updates the settings to enable only revenue recognition with netsuite and keeps payments in stripe, ensuring clean, non overlapping transactional flows and simple reconciliation how it works integration settings admins navigate to integration settings, select an integration (e g , netsuite or quickbooks), and see checkboxes for payments/collections, accounting, and revenue recognition tooltips provide workflow guidance and warnings mandatory selection at least one integration type must be enabled before proceeding; the ui highlights if none are selected and prevents accidental misconfiguration real time status for each invoice and credit memo, nue surfaces “payment status,” “accounting status,” and “revenue status” in the ui, with values such as “not transferred,” “transferred,” or “error/failed,” updated based on responses from the external system transaction routing the system automatically routes transactions to the correct external api (e g , payment or revenue api) based on integration settings, ensuring only relevant data is synced error handling & retry failed syncs are clearly surfaced in the transaction hub, with error codes/messages and a manual retry option for granular correction technical details integration metadata is stored with each instance, driving both api routing logic and ui display (status, type, function) status polling and push mechanisms keep invoice and credit memo status fields synchronized in real time with external systems admin only controls protect integration settings from unauthorized changes; role based access enforces security related resources read further documentation on this feature here display revenue status for invoice and credit memo with rightrev integration nue now automatically displays a “revenue status” field on every invoice and credit memo when rightrev is enabled for revenue recognition this status—"not transferred", "transferred", or "error"—shows if each transaction has been synced with your external revenue recognition system, making it easy for finance and admin users to confirm real time sync, monitor for issues, and maintain compliance the status is updated automatically via api and is filterable in the transaction hub, streamlining audit, close, and troubleshooting workflows why it matters dramatically improves transparency and compliance for revenue recognition, supporting asc 606/ifrs 15 requirements reduces manual effort in reconciliation, error tracking, and period end close—saving finance and revops teams time and reducing audit risk centralizes error handling for revenue sync, making troubleshooting faster and more reliable learn more customer use cases use case a finance manager at a saas company is preparing for month end close and needs to confirm that all invoices and related credit memos have been recognized in the revenue accounting system (rightrev) by filtering on “not transferred” and “error” statuses in nue’s transaction hub, they can quickly identify which transactions require attention, reducing manual checks and ensuring a smooth, compliant close use case an admin responsible for financial integrations receives an alert about failed revenue syncs they use the “revenue status” field to spot invoices or credit memos marked as “error,” review error details directly in nue, and coordinate with it to resolve the mapping or authentication issue—accelerating root cause analysis and minimizing revenue leakage use case during an external audit, an auditor requests evidence that all revenue events have been properly recognized the admin pulls a report from nue, leveraging the revenue status filter to show which invoices and credit memos are “transferred,” providing a clear, auditable trail for all revenue events synced to rightrev how it works the “revenue status” field appears on every invoice and credit memo record in nue when rightrev (or netsuite arm) is enabled for revenue recognition 1 status values are set automatically “not transferred” (default), “transferred” (upon successful sync), or “error” (if the sync fails, with api error details) api endpoints allow batch or individual updates to revenue status fields (patch /billing/invoices\ update revenue status) no manual intervention is needed for status changes—backend automation manages updates based on integration events and sync results only transactions relevant to revenue (i e , tied to orders/invoices) are included; ar only or standalone credit memos not impacting revenue are excluded from rightrev sync technical details integration supports both rightrev and netsuite arm, with future extensibility for additional systems historic (pre feature) transactions retain a null revenue status unless customers choose to backfill via api all status changes are logged in transaction hub for full auditability, and errors are propagated from the api with actionable messages automate quickbooks online field mapping for payment terms, product skus, and line item descriptions managing your quickbooks online (qbo) integration just became more powerful and flexible nue now automates the mapping of payment terms and product skus, and introduces a configurable description builder for invoice and credit memo line items—directly from your nue or salesforce data these enhancements eliminate manual re entry, increase audit clarity, and enable finance teams to surface critical business information in qbo with no code field mapping learn more customer use cases use case a finance manager at a saas company needs every customer’s negotiated payment term (e g , “net 30” or “due upon receipt”) to flow from salesforce into quickbooks online without manual intervention before this enhancement, mismatches or missing terms required manual fixes in qbo, leading to delayed invoices now, as soon as a customer or invoice is created in nue, the system automatically maps and syncs the correct payment term—significantly reducing errors and streamlining collections use case a revops admin regularly updates the product catalog in salesforce and relies on accurate sku tracking in quickbooks for inventory and reporting previously, skus had to be checked and manually updated in qbo each time a new product was billed with sku mapping automated, every new product’s sku is now synced from nue to qbo the moment an invoice is activated, ensuring inventory and revenue reconciliation are always current and correct use case an auditor requests a detailed breakdown of service timelines for every invoice and credit memo, including start and end dates, product names, and custom fields the finance team configures nue’s line item description mapping to concatenate all required fields into qbo’s line item description, making compliance reviews and client reporting straightforward—no more digging through disconnected systems or custom workarounds how it works admins configure field mappings in nue’s ui for payment terms, product skus, and line item description details (e g , start/end dates, amount, product name) when a customer, product, invoice, or credit memo is created or updated in nue or salesforce, the integration automatically applies these mappings as records sync to qbo line item descriptions are built dynamically according to admin defined rules, concatenating any mapped fields as key value pairs (e g , “start date 2025 07 01 | end date 2025 07 31 | product api connect”) if a mapped field (like payment term) is missing or unmatched, error handling logic skips the mapping and logs a warning for admin review all sync operations and mapping statuses are visible in transaction hub for monitoring and troubleshooting supports both invoices and credit memos, including multi line items and special formatting requirements bug fixes everything billing correct default time zone applied to usage objects when account time zone is unset in salesforce previously, when the account’s ruby timezone c field in salesforce was left blank, the system would not reliably use the intended default time zone instead, despite having “gmt” (greenwich mean time) set on the nue integration user, the connected nue user, or even at the tenant level, the zoneid on newly created usage objects would default to “america/los angeles ” this caused confusion, as the zoneid did not reflect the configured tenant or user defaults when the account specific setting was missing with this fix, whenever the ruby timezone c field on the salesforce account is null, nue now correctly assigns the tenant’s default time zone as the subscription time zone for usage objects this resolves prior inconsistencies, ensuring that time zone data is handled predictably and aligns with your organizational defaults, even when account level settings are not provided billing schedulers and catchup bill run apis now correctly filter by billing account without sql errors previously, both the billing schedulers and catchup bill run api did not allow users to generate invoices based on the billing account, which was particularly problematic for customers with different "sell to" and "bill to" accounts the system could only filter invoices by the sales account this issue has been resolved the fix updates the filtering logic and underlying graphql library, ensuring that filters on billing accounts work correctly without causing sql errors customers can now reliably use billing account filters in both apis, making invoice generation for complex account structures accurate and efficient quote document line item filters now working as expected previously, when customers used filters on the quote line items section specifically targeting fields like quantity, delta mcv, delta acv, and total amount these filters did not function correctly we have resolved this issue in this release filters applied to the quote line items section now work as intended customers can confidently refine their quote documents, ensuring that only the desired line items appear according to their selected filter values integrations credit memo amounts now correctly reflected in rightrev integration previously, credit memos sent from nue to rightrev were recorded as positive amounts, incorrectly increasing invoice totals now, credit memos are sent as negative amounts, properly reducing invoice values in rightrev and ensuring accurate billing and reporting quickbooks launch button restored in transaction hub the "launch" button for quickbooks now works for customers, products, and invoices in transaction hub this fix resolves previous errors and enables seamless access to quickbooks from all object types, ensuring a smoother workflow and improved integration salesforce now accurately reflects quickbooks transaction status prior to this update, the transaction hub component in salesforce did not automatically update with changes made in quickbooks online (qbo) for example, when a transaction was successfully transferred to qbo or when an invoice generation failed, these status updates were not reflected in salesforce’s transaction hub view with this fix, salesforce’s transaction hub now reliably displays the latest quickbooks status updates for account transfers, invoices (including failed and subsequently successful invoices), and credit memos improved error messaging for failed einvoice submissions previously, when submitting einvoices, all invoices would fail without providing any error message or descriptive feedback with this update, failed einvoice submissions now clearly display error messages and relevant details when a problem occurs, such as access issues to required salesforce objects this enhancement makes troubleshooting much easier, allowing users to quickly identify and resolve the root causes of submission failures