MYOB Acumatica Performance Improvements

MYOB Acumatica Tips and Tricks #21

Wednesday June 10th, 2026 MYOB Acumatica

Executive Summary
> Poorly configured background processes and unnecessary data loads are frequent root causes of system slowdowns.

> Check Generic Inquiries and automation schedules as top areas for improvement.

> Regularly archive old documents and perform quarterly checks on your system health.

MYOB Acumatica is a powerful, end-to-end business management platform that collects data from across your organisation. It is a sophisticated system of record with tools to visualise, analyse, and act on this data in real time.

However, the role of MYOB Acumatica in an organisation is changing. As new Artificial Intelligence functionality is introduced, MYOB Acumatica shifts to become a System of Intelligence. It will interpret stored data in real-time to surface insights across the organisation and inform timely decision-making.

Your organisation will also grow and change throughout your journey with MYOB Acumatica. This places an additional burden on your system’s processing power and may compromise productivity and your ability to make timely, data-informed decisions. For the best possible outcome as a System of Intelligence, MYOB Acumatica should be finely tuned and optimised for performance.

Key Areas of Performance Improvement

Even small changes and optimisations can have a noticeable impact on processing speed and performance. MYOB Acumatica is the data-fuelled engine that drives your business. Just like your car or other machinery, it requires regular servicing and maintenance to keep it running smoothly. The most effective improvements come from reducing system load and streamlining data retrieval.

Our team has identified several areas you can explore to improve system performance.

Managing tenants and snapshots

MYOB Acumatica is a multi-tenant platform, meaning organisations can run multiple environments on a single application instance. A “tenant” is an independent organisational environment within the broader ERP platform, designed to hold its own data, users, configurations, and business processes.

Each tenant includes:

Its own database
Unique company and financial data
Independent user access and permissions
Customisations and configurations specific to that tenant

While it is necessary to have a separate tenant for training, testing, debugging, and integration development, each additional tenant consumes resources and affects overall performance.

A snapshot is a user-created point-in-time export of your system that lets you move or reuse data safely. Depending on how it is configured, a snapshot can include:

Full transactional data and history
System configuration and settings
Master data such as customers, suppliers, and inventory

Snapshots are helpful for creating sandbox environments or backing up information. This essentially duplicates the data within your tenant, though you can control what is copied.

Tips for managing tenants and snapshots:

System Administrators can delete unused snapshots on the Delete Snapshots and Tenants form.
Once you have deleted tenants or snapshots, you can request a database reindex from MYOB.
Do not keep snapshots on your site. You can delete them once they are downloaded.

Generic Inquiries

A Generic Inquiry (GI) in MYOB Acumatica is a configurable reporting and data-retrieval tool. GIs let you quickly pull information from one or more tables and display it on-screen without building or coding a custom report. As a query to extract live data, it forms the building blocks of reporting and intelligence in MYOB Acumatica. Designing and managing your own GIs can reduce the resources they consume.

Tips for managing Generic Inquiries:

Filtering settings are available to site administrators and other power users to reduce the amount of data returned by a GI, which speeds up processing.
Avoid editing primary list GIs. Instead, create purpose-specific copies and add extra fields to meet the narrower scope.
When joining separate GIs, InnerJoin is typically more efficient than LeftJoin, as it returns only matching fields rather than all fields from one table and matched results from the other.
A GI will run faster when returning precomputed fields rather than calculated fields in joins, particularly when those fields are marked as DBScalar or DBFormula in the data access class (DAC).
Limit the use of Quick Search fields to the most frequently used ones to reduce the number of database queries.
We offer Generic Inquiry-focused training packages to help improve your skills.

Automation Schedules

An automation schedule is a way to make a system process run automatically at set times or intervals, rather than being started manually by a user. They are user-friendly ways to process batches and transactions, prepare documents, or send updates.

Tips for managing automation schedules:

Audit your automation schedules to spot failures or long-running schedules
Avoid overlapping automation schedules, including a 15-minute buffer between them.
Time schedules are run manually to set the appropriate schedule interval, including a buffer for volume growth. When the time to run the process exceeds the time until the next process starts, the automation can get stuck in a loop, causing the Next Execution Date and Next Execution Time fields to be in the past.

API Integrations

Application Programming Interface (API) integrations are a key aspect of expanding the scope of MYOB Acumatica, letting it collect data from all areas of your organisation. These third-party systems increase the volume of data in your database, which can also affect GIs and automation schedules. However, API integrations should also be reviewed to spot inefficient data sync processes and high-volume API calls that could compromise system performance.

Tips for managing API integrations:

Monitor integration logs to spot repeated failures or long-running API calls.
Contact the Kilimanjaro Consulting support team and the relevant integrated product developer for assistance in resolving these issues.

Other areas to look for performance improvement

Set an archival policy for documents so the system does not search them in queries in day-to-day operations.
Check the default dashboard for inefficient widgets.
We do not recommend turning on the email archive function.

MYOB Acumatica Ultimate Compilation of Tips and Tricks eBook

Download now

Interested in other ways to optimise MYOB Acumatica?

Check out our handy MYOB Acumatica Tips and Tricks blogs here:

New Tips and Tricks from the Latest Version

MYOB Acumatica is always being developed and updated to meet the evolving requirements of larger, more complex organisations. Discover what is coming in the next MYOB Acumatica Release and how you can use these exciting new features to improve efficiency in your business. Our team can support your upgrade process and ensure your customisations and integrations remain stable on the latest version.

Next steps

Please note that MYOB regularly restarts MYOB Acumatica sites to make sure they run smoothly. All sites are scheduled to restart between 1 and 3 am AEST (3 and 5 am NZT). Avoid using MYOB Acumatica during this time, especially for importing data or similar tasks.

We hope these tips and tricks were helpful to you! If you have any questions about improving the performance of MYOB Acumatica, our friendly team is here to help. Email acsa@kilimanjaro-consulting.com or call 1300 857 464 (AU) or 0800 436 774 (NZ).