Calxa can be used with a number of different accounting packages and integrates with these packages in different ways. Aside from your initial company setup and subsequent syncs, Calxa behaves in much the same way regardless of the chosen accounting package. There are, however, some important differences to be aware of.

This help note will outline the things you should know about using Calxa with NetSuite and discuss best practices for a smooth integration.

A Calxa Enterprise subscription is required to connect to NetSuite. See Calxa Pricing for more details.

Calxa connects to NetSuite using the OAuth 2.0 Client Credentials Flow (M2M). Configuration for this integration must be performed in both NetSuite and Calxa. Once configured the client credentials flow does not require any user interaction for Calxa to sync data from NetSuite. The certificate used for authentication is valid for 1 year, and therefore must be renewed annually. The certificate may also be revoked at any time in the NetSuite integration configuration. See NetSuite Integration for setup instructions.

A NetSuite administrator is required to configure the Integration and the OAuth 2.0 Client Credentials. The Calxa connection will require access to the following Objects:

Each subsidiary from your NetSuite account will be imported to Calxa as a separate Organisation. Organisation Groups and Business Unit Trees can be configured in Calxa to represent the NetSuite subsidiary structure.

Calxa will import and sync the full Chart of Accounts structure including parent child relationships from NetSuite. This full structure is synced to all connected subsidiaries/organisations.

Calxa references each account on an internal key rather than the account number or name. This means you can safely renumber or rename accounts in NetSuite and Calxa will still recognise it as the same account.

If you mark accounts as Inactive in NetSuite, then Calxa will mark these accounts as inactive. Inactive accounts are filterable from many views in Calxa, however all actual data is still imported and synced against inactive accounts and thus will be included in reports when data is present.

Business units are the broader term in Calxa representing the different methods for segmenting data in NetSuite. The following segments from NetSuite are imported to Calxa.

Business unit names are configurable via the Business Unit Configuration menu.

Calxa references each Business Unit on a key rather than the number or name. This means you can safely renumber or rename these in NetSuite and Calxa will recognise them as the same item.

Calxa is a monthly reporting and budgeting tool and therefore requires monthly financial periods in NetSuite. Other financial periods variations such as 13x4 week and 4-4-5 calendars are not currently supported.

Journal Transactions are summarised and stored in Calxa as monthly amounts on each Organisation and Business Unit Category.

Transaction detail is not saved to Calxa and therefore some transaction-based reports such as the Account Transaction and Aged Receivables/Payables reports are not supported for NetSuite organisations at this stage.

Budgets can be added against all Business Units Categories, however Calxa does not sync these from NetSuite. See Import Budgets for details on importing your NetSuite budgets from a spreadsheet.