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 MYOB Acumatica and discuss best practices for a smooth integration.

Calxa authenticates to Acumatica using the OAuth 2.0 Authorisation Code Flow. Configuration for this integration must be performed in both Acumatica and Calxa.

Once configured this flow does not require any user interaction for Calxa to sync data from Acumatica. The secrets used as part of the authentication flow have a configurable expiry date and therefore, periodic renewal may be required based on the expiry date chosen. The connection may also be revoked at any time from the Acumatica configuration.

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

A Full Access API licence is required. A free limited API licence is not suitable as the limited number of API calls per day will cause sync failures.

An Acumatica administrator is required to configure the Connected Application and Web Service End Points in Acumatica. The Calxa connection will require access to the following Objects and related Screen IDs:

Each company and branch from Acumatica is imported to Calxa as a separate Organisation.

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

If you mark accounts as Inactive in Acumatica, 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 Acumatica. The following segments from Acumatica 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 Acumatica and Calxa will recognise them as the same item.

Subaccounts are mapped as individual Business Units in Calxa. These can contain their own budgets and budgets can also be imported from Acumatica. Marking Subaccounts as Inactive will also mark them as Inactive in Calxa.

Subaccounts in Acumatica can be made up of configurable segments. Each segment may be considered its own Business Unit Category, such as a Region, Department or any other segmentation of your choosing. Currently Calxa does not import each segment independently, however since the Subaccounts already have the breakdown of each combination, each segment such as a Region or Department can be built using a Business Unit Tree.

Projects are mapped to a Business Unit header in Calxa, while Project Tasks are mapped as individual business units within each Project Header. Each task can contain its own budget which is easily rolled up to the overall Project Budget.

Marking Project Tasks as Complete will mark the Business Unit as Inactive in Calxa. Inactive tasks are filterable from many views in Calxa, however all actual data is still imported and synced against inactive tasks and thus will be included in reports when data is present.

Journal Transactions are summarised and stored in Calxa as monthly amounts on each combination of Business Unit and Account.

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 Acumatica organisations at this stage.

You can select a single budget to be synced from Acumatica to Calxa at both the Organisation and Subaccount level. This will create a Read Only budget in Calxa. See Use your Accounting system Budget in Calxa for more details.

While you can budget on Project Tasks in Calxa, the Task budgets cannot be synced from Acumatica.