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 Subscription
A Calxa Enterprise subscription is required to connect to MYOB Acumatica. See Calxa Pricing for more details.
Supported Versions
MYOB Acumatica (Australia and New Zealand)
MYOB exclusively partners with Acumatica in Australia and New Zealand to bring you MYOB Acumatica, built on top of the technology that Acumatica provides.
Acumatica (Global)
SaaS deployments of Acumatica are fully supported.
Private Cloud deployments must allow public access to the required Web Service Endpoints.
Note: MYOB Business is also supported but covered in the following separate help article: Calxa and MYOB Business
Integration (connection) to Acumatica
Calxa authenticates to Acumatica using the OAuth 2.0 Authorisation Code Flow. Configuration for this integration must be performed in both Acumatica and Calxa. See MYOB Acumatica Integration for setup instructions.
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.
Acumatica Licence Requirements
The user authenticating Calxa via the OAuth connection flow requires a Full Access API licence. A free limited API licence is not suitable as the limited number of API calls per day will cause sync failures.
User Role Requirements
An Acumatica Administrator role is required to configure the Connected Application.
The user authenticating Calxa via the OAuth connection flow will require the ODatav4 user role.
Companies and Branches
Each company and branch from Acumatica is imported to Calxa as a separate Organisation. Organisation Groups and Business Unit Trees can be configured in Calxa to represent the company structure.
Chart of Accounts
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
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.
Subaccounts
Subaccount segments
Projects / Projects Tasks
You can enable/disable or rename any of the Business Unit Categories 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
Subaccounts are mapped as individual Business Units in Calxa. Marking Subaccounts as Inactive will also mark them as Inactive in Calxa.
Subaccount segments
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. Calxa imports each segment as its own Business Unit Category providing budget and report capabilities on each Subaccount segment.
Projects & Projects Tasks
Projects and Project Tasks are each mapped to Calxa as a separate Business Unit Category so you can easily choose to budget and report at the Project level or granularly at the Task level. Project Tasks include a header to group by Project, which allows task budgets to be rolled up to the overall Project Budget.
Financial Periods
Calxa is a monthly reporting and budgeting tool and therefore requires monthly financial periods in Acumatica. Other financial periods variations such as 13x4 week and 4-4-5 calendars are not currently supported.
Actuals
Journal Transactions are summarised and stored in Calxa as monthly amounts on each combination of Business Unit, Account and reporting month.
Transaction Detail
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.
Budgets
Budgets can be added against all Business Units Categories, however Calxa does not sync these from Acumatica. See Import Budgets for details on importing your Acumatica budgets from a spreadsheet.