Tabs <> NetSuite Integration

Last updated: March 9, 2026

Use the Tabs and NetSuite integration to sync customers, invoices, payments, credit memos, and tax information to maintain your financial records.

Overview

Tabs maintains a bidirectional sync with NetSuite. To keep ERP data consistent, Tabs pulls updates from NetSuite daily at 12:00 AM ET and automatically pushes new information from Tabs to NetSuite as it’s created.

Data Pulled from NetSuite:

  • GL Accounts

  • Items

  • Currencies

  • Customers

  • Invoices

  • Payments

Data Pushed to NetSuite:

  • Customers

  • Sales Orders (if enabled)

  • Invoices

  • Credit Memos

  • Payments

  • Journal Entries

Customers

NetSuite → Tabs: Existing NetSuite customers are automatically imported into Tabs during daily sync.

Tabs → NetSuite: You can create new customers in Tabs and push them to NetSuite. If a customer exists in Tabs (e.g. from CRM) but not NetSuite, you can manually push them from the dashboard.

CRM → Tabs → NetSuite: Customers from your CRM (HubSpot, Salesforce) sync to Tabs, then to NetSuite.

Requirements:

  • Customer name is required for import from external systems.

  • Primary address and email must be populated before sending an invoice via Tabs.

  • If you require multi-currency, it must be enabled in your NetSuite account.

  • Parent and sub-customers must have matching currencies—NetSuite will reject invoices in currencies that don’t match the customer’s set currency.

  • NetSuite subsidiary configuration must be properly set in the account mapping settings.

Invoices & Credit Memos

When an invoice is sent in Tabs, it automatically syncs to NetSuite.

The customer receives one email from Tabs; NetSuite will not send a duplicate.

Note: If an invoice fails to sync (typically due to a NetSuite configuration issue), a notification will appear in Tabs. The invoice will not be sent to the customer until the error is resolved.

Note: If an invoice failed to sync or the customer wasn’t yet linked to NetSuite, you can manually re-sync from the dashboard.

Invoice Creation Flow

For customers with contracts and recurring billing:

  1. A Sales Order is created in NetSuite when the first invoice for respective Tabs contract is first sent to the customer.

  2. Subsequent invoices are transformed from the Sales Order

  3. Line items are linked between the Sales Order and Invoice

For standalone invoices:

  1. Invoices are created directly in NetSuite without a Sales Order

  2. Line items are created fresh on each invoice

Credit Memos

Tabs maintains a one-directional sync for credit memos.

  • Applying a credit memo in Tabs will automatically sync to NetSuite.

  • Credit memos created in NetSuite will not sync to Tabs.

Payments

Tabs maintains a bidirectional sync for payments:

  • When a partial or full payment is applied in Tabs, it syncs to NetSuite.

  • Payments applied via Stripe or Plaid sync to NetSuite and back to Tabs.

  • Payments manually applied in NetSuite also sync back to Tabs during the daily pull.

  • Removing a payment in Tabs syncs the removal back to NetSuite.

Items and Products

Tabs products map to existing items in NetSuite. To add a new product, create and configure the item in NetSuite first.

Tabs does not support creating new items directly, as this could affect data consistency between the two systems.

Items are synced daily from NetSuite and include:

  • Item ID and display name

  • Income account reference

  • Tax mapping information

  • SKU

  • Sales description

  • Active/inactive status

GL Accounts

Tabs pulls GL accounts from NetSuite but does not modify or add them. When sending an invoice, the GL impact is determined by the accounts mapped to the NetSuite item.

For cash reconciliations and month-end close journal entries, you can configure which GL accounts Tabs pushes to within the Tabs account mapping settings.

Supported Account Fields:

  • Account number

  • Account type

  • Full name and display name

  • Currency

  • Active/inactive status

  • Subsidiary

Currency

If multi-currency is enabled in NetSuite, Tabs will:

  • Use the customer’s currency on invoices

  • Store currency information for all transactions

  • Support journal entries in multiple currencies

Note: Currency must match between parent and sub-customers. NetSuite will reject transactions if currencies are mismatched.

Tax Integrations

Tabs supports multiple tax providers when integrated with NetSuite:

NetSuite Native Tax

  • Tax amounts are calculated by NetSuite’s built-in tax engine

  • Tax fields are mapped automatically from NetSuite invoice line items

  • Uses the taxAmount field from NetSuite

Avalara Tax

  • Tabs can calculate tax using Avalara before sending to NetSuite

  • Tax amounts are stored in custom fields (e.g., custcol_ava_taxamount)

  • Item tax codes are mapped to Avalara tax categories

  • Supports address-based tax calculation

Ceratax

  • Alternative tax provider supported through NetSuite custom fields

  • Uses rate-based fields (e.g., custcol_ct_ceretax_rate)

  • Tax rates are applied to line items during invoice creation

Custom Fields

Tabs supports syncing custom fields between NetSuite and Tabs for:

  • Customers

  • Sales Orders

  • Sales Order line Items

  • Invoices

  • Invoice line items

  • Payments

Subsidiaries

Multi-subsidiaries is supported on Tabs.

  • 1 Tabs instance maps to 1 subsidiary in NetSuite

  • For example, 3 subsidiaries in NetSuite requires 3 Tabs instances.

Journal Entries

For month-end close and revenue recognition, Tabs can push journal entries to NetSuite.

Requirements:

  • Subsidiary must be properly configured

  • GL accounts must exist in NetSuite

  • Currency must be specified (if multi-currency is enabled)

Supported Journal Entry Fields:

  • Transaction date

  • Currency

  • Subsidiary

  • Memo

  • Line items with debit/credit amounts

  • GL account references

Invoice Field Mapping

NetSuite Field

Tabs Field

Customer

Customer

Customer email

Primary billing contact email

Billing address

Customer address

Transaction date

Invoice issue date

Due date

Due date

Transaction ID

Invoice number (with prefix)

Line item: Item

Tabs Integration Item

Line item: Description

Line item name and description

Line item: Tax Amount

Tax code (NetSuite, Avalara, or Ceratax)

Line item: Quantity

Line item quantity

Line item: Rate

Line item unit price

Line item: Amount

Line item total

Memo

Invoice memo

Subsidiary

Manufacturer subsidiary

Start date

Earliest line item start date

End date

Latest line item end date

Sales Order Field Mapping

For customers with contracts, Tabs creates Sales Orders in NetSuite:

NetSuite Field

Tabs Field

Customer Name

Customer

Transaction date

Contract created date

Start date

Earliest billing term start date

End date

Latest billing term end date

Line item: Item

Billing term line item product

Line item: Quantity

Billing term quantity

Line item: Rate

Billing term rate

Line item: Amount

Billing term amount

Subsidiary

Manufacturer subsidiary

Error Handling

When an invoice, payment, or other entity fails to sync:

  1. An error notification appears in the Tabs dashboard

  2. The error details are logged and can be viewed by Tabs

  3. The entity remains in Tabs with a failed sync status

  4. Manual retry is available from the dashboard once the issue is resolved

Common sync errors:

  • Customer not found in NetSuite

  • Missing required custom fields

  • Currency mismatch

  • Invalid subsidiary reference

  • Item not found or inactive

  • Permission issues in NetSuite

Support

For NetSuite integration issues:

  • Verify NetSuite permissions and configuration

  • Contact Tabs support.