Manage Accounting with Netsuite

enabling the netsuite accounting integration with granular gl account mapping transforms your financial operations—automating complex postings, ensuring clean audits, and giving you real time visibility into every sync this solution eliminates manual reconciliation, reduces compliance risk, and accelerates month end close by connecting nue’s flexible billing platform with netsuite’s robust general ledger with product category level gl mapping and dedicated clearing account flows, you gain compliance automation automated, audit ready account postings for sox/gaap compliance seamless reconciliation reconcile stripe payments, ar and more directly in netsuite, with error transparency that lets your team close the books faster setting up the netsuite accounting integration follow these steps to connect your nue workspace to netsuite and configure granular account mapping overview purpose the netsuite accounting integration is available out of the box and the default integration when you connect to netsuite with nue it can be used in the following ways as mentioned in the following document setup your integration use case when you are collecting and accounting in netsuite when you are collecting on stripe and accounting in netsuite when you are collecting with nue payment links and accounting in netsuite when you are collecting with a third party payments collection and accounting in netsuite data model nue's netsuite connector supports the synchronization of the following objects nue object netsuite object direction customer customer one direction sync from nue to netsuite product item one direction sync from nue to netsuite order sales order one direction sync from nue to netsuite (sent at order activation) invoice and invoice item (only applies if using nue billing) invoice one direction sync from nue to netsuite (sent at invoice activation) payment application (only applies if using nue collections/stripe) payment one direction sync from nue to netsuite refund application (only applies if using nue collections) refund one direction sync from nue to netsuite credit memo and credit memo item (only applies if using nue collections) credit memo bi directional created by nue → qbo; cancellations in netsuite → nue the diagram below illustrates the synchronization flow note that products are stored in salesforce but are synchronized to netsuite using nue’s graphql queries, which are automatically routed to salesforce to fetch the required data difference between accounting and payments netsuite integration the netsuite accounting integration is always on when you are working with netsuite the only difference between the two integrations is if you are collecting on stripe, nue payment links or elsewhere, payments will be sent from nue to netsuite if you are collecting with netsuite , payments will be sent from netsuite to nue setup your netsuite accounting integration step 1 connect your netsuite environment authentication connect your netsuite environment using the details on the setup page step 2 enable gl account mapping for items in the netsuite integration settings, locate the record type mapping section on page 4 for products/items the mappings you specify here determine how items in nue are categorized when transferred to netsuite, impacting inventory management, service tracking, and revenue recognition nue field netsuite item types required? nue subscription non inventory sale yes nue entitlement service sale yes nue asset inventory yes nue subscription select the netsuite item type that should represent nue subscription products most commonly mapped to "non inventory" to indicate that subscriptions are not tracked as physical inventory items in accounting nue entitlement choose the netsuite item type for nue entitlements, which typically refer to services provided rather than physical goods commonly mapped to "service" for service based business models nue asset set the netsuite item type for nue assets, usually representing inventoried products usually mapped to "inventory," signaling that these items should be accounted for as stock in netsuite step 3 configure gl account mapping general guidance for gl account mapping in nue quickbooks config always verify each account exists in netsuite and has the correct account type for the intended use map based on both transaction type (inventory, service, non inventory) and your company’s accounting structure to ensure report accuracy use clear, standardized account names to reduce mapping errors and confusion review mappings after any chart of accounts changes in netsuite, and periodically audit mapped transactions for correct classification please note that the netsuite internal gl account ids need to be used subscription income account purpose defines the netsuite income account for subscription related sales (e g , saas or recurring product revenue) setup & usage map to a netsuite income account such as “subscription income” or “recurring revenue” applied to invoice line items tagged as subscription products best practice ensure the mapped account is of type income and aligns with your revenue recognition policy subscription revenue account purpose specifies the netsuite revenue account used for revenue recognition of subscription items setup & usage select a netsuite revenue account where deferred/recognized subscription revenue should post best practice use an account linked to your arm or revenue schedules for accurate recognition entitlement income account purpose defines the income account for entitlement related product sales (e g , support access or usage rights) setup & usage map to a netsuite income account such as “support income” or “entitlement revenue” best practice confirm account type is income and distinct from subscription or asset revenue for clarity entitlement revenue account purpose specifies the revenue account for recognized entitlement revenue setup & usage map to the netsuite revenue account tied to entitlement items in revenue arrangements best practice ensure alignment with your arm rules for entitlement recognition asset income account purpose designates the netsuite income account for tangible or fixed asset product sales setup & usage select an income account such as “product sales” or “hardware revenue” best practice confirm the account type is income and used only for asset type items asset revenue account purpose sets the netsuite revenue account used for recognizing asset based revenue setup & usage choose the account used in arm for asset related revenue schedules best practice keep separate from service/subscription revenue accounts for reporting clarity nue clearing acct purpose acts as a temporary clearing account for transactions synced between nue and netsuite useful for reconciling payments before final deposit setup & usage map to a clearing or suspense account to hold intermediate postings during sync best practice reconcile and clear balances regularly; should net to zero after sync completion step 4 configuring transaction page batch handling for netsuite connector in transaction hub batch handling for netsuite connector introduces a scheduled batch processing mode within nue’s transaction hub for the netsuite integration when enabled, all relevant transactions (orders, invoices, etc ) are first parked in a “not transferred” state every 10 minutes , a batch job processes these transactions and transfers them to netsuite using the existing tray connector, marking them as “transferred” upon success for example , in the case of 20 invoices sent to netsuite concurrently, batch mode would queue them thus ensuring they are all sent to netsuite instead of 15 invoices failing due to netsuite's concurrency limit (as at tier 1 it limits transactions to 5 api calls a minute), 20 invoices would be sent in 1 hour (20 invoices x 3 minute processing time per invoice) impact scalability handles high transaction volumes without hitting netsuite’s api rate limits reliability reduces risk of data loss and partial syncs by queuing and retrying failed transactions auditability provides robust error logging and state tracking for compliance and troubleshooting who is this for? type of customer business reason large enterprises with high volume ✅ must process thousands of transactions daily; cannot risk api throttling or data loss risk of meeting netsuite concurrency limit ✅ if customers have volume higher than 5 api transactions per minute, this batch mode queues records and processes them at a controlled rate, ensuring all transactions sync reliably who this is not for? if concurrent transactions are unlikely then it is best to not use this mode if transaction volume starts increasing, there may be error messages in transaction hub signaling concurrency limits are hit in which case batch processing should be enabled how to step by step setup 1\ enable scheduled batch mode go to the netsuite integration configuration page in nue (ui or api) locate the checkbox labeled “process in scheduled mode ” check the box and save the configuration 2\ create and monitor transactions transactions (customers, orders, invoices) created via nue’s ui or api will now be parked in transaction hub as “not transferred ” 3\ scheduled batch processing every 10 minutes, nue’s batch job picks up all “not transferred” transactions and sends them through the tray connector to netsuite upon successful sync, the transaction hub updates the status to “transferred ” 4\ managing failures and retries if a transaction cannot be transferred (e g , api limit, mapping error), it stays as “not transferred ” errors are logged in transaction hub admins can retry failed records individually or in bulk using the transaction hub ui 5\ verification and audit use the transaction hub ui to verify the status of each transaction cross check in netsuite to confirm successful syncs dependencies and limitations netsuite api limit maximum 5 api calls per minute; batch mode is designed to respect this limit not for data migration for large scale historical migrations, use csv uploads directly into netsuite