Is the NetSuite integration right for me?
The NetSuite integration is available to admins and bookkeepers. Brex's direct integration with NetSuite aims to make life easier by streamlining the flow of transaction data into one centralized place, saving you hours of manual labor. Here's all you need to know to determine whether our NetSuite integration is right for your business.
How long does it take to set up?
In less than 10 minutes, you can connect Brex to your NetSuite account (Sandbox or production). Once connected, your chart of accounts, departments, locations, vendors, classes, and more will be available in the Brex dashboard.
After you complete the mappings between your Brex fields and your NetSuite fields, you can begin exporting your data right away. This process can be completed in as little as 15 minutes but may take longer depending on how much customization you'd like and the complexity of your NetSuite configuration.
In addition to field mappings, Brex offers custom rules that can be set up to manage your edge cases and custom workflows, helping reduce the overall amount of manual review required and dynamically route your transactions to the correct fields in NetSuite.
What should I know before getting started?
Journal entries vs vendor bills
Brex transaction data is only exported as journal entries. Vendor bills are not an option at this time.
Mapping Brex transaction data to NetSuite vendors is now available. Once mapped, we will populate the Name field of the Journal Entry with the appropriate NetSuite vendor from your list of vendors.
Push vs feed
The NetSuite integration allows you to push transactions to NetSuite by creating one or more journal entries. The export isn't automatic and requires initiation from the Brex dashboard, allowing you to review how your transactions will appear in your chart of accounts to ensure accuracy.
Journal entry creation
Journal entries are created for each export. Brex gives you the flexibility to choose how you want to batch your transactions into journal entries:
Monthly journal entries (default setting)
Weekly journal entries
Daily journal entries
Journal entries for each transaction
If the transactions span multiple calendar months, Brex will break that export into separate journal entries (one for each month with transactions completed).
Preventing duplicate entries
To prevent duplicate entries, Brex won't allow you to re-export a successfully exported transaction. Once you export transactions from the Integrations tab (whether directly to NetSuite or via CSV), you can't export it again. You can, however, export transaction data from the Expenses tab to CSV, PDF, HTML, TXT, or XLSX as often as you'd like.
You can choose one subsidiary when connecting the integration, or you can enable multiple subsidiaries. We'll import accounts, classes, departments, locations, vendors, and other supported fields belonging to your chosen subsidiaries and export journal entries to them. For transactions across multiple subsidiaries, we take on the work of automatically generating the intercompany journal entries for you.
Brex can integrate with your custom fields in NetSuite. See How do I set up custom fields for NetSuite? For more details.
You can set up custom rules to code transactions based on a wide range of fields, including user, budget, department, or more.
To make audits easier, receipts uploaded to Brex are passed directly into NetSuite when you export your transaction data. In NetSuite, you'll see a URL that links to the receipt image, which you can access by signing in to your Brex dashboard.