One of the most common questions we get during MYOB Acumatica evaluations is some version of: "Can it be customised to fit how we work?" The short answer is yes. The longer answer is that "customisation" covers a wide range of things, from configuring a dashboard to writing custom screens that change how the system behaves for your industry. Understanding the difference matters before you start scoping, because the cost and ongoing maintenance implications are very different depending on what you're actually asking for.
This post covers the distinction between configuration and customisation, what the xRP platform makes possible at each level, what custom work typically costs in Australian projects, and how to avoid the mistakes that make custom development expensive to maintain.
Configuration versus customisation: why the distinction matters
MYOB Acumatica draws a clear line between configuration and customisation, and it's worth understanding before you brief a partner.
Configuration is everything you do inside the standard Acumatica interface without touching code. Setting up your chart of accounts, defining approval workflows, building Generic Inquiries (custom reports), configuring Business Events (automated notifications and triggers), setting user roles and access permissions, building dashboards for different roles in your business. Most of what Australian businesses need to make Acumatica work for their operations falls into this category. A well-scoped implementation handles all of this during the standard project.
Customisation is what happens when configuration isn't enough. It means extending or modifying the platform's behaviour using Acumatica's xRP development framework. Adding a custom field to a standard screen. Building a new screen for a workflow that doesn't exist in the core product. Integrating with a third-party system via the REST API. Building industry-specific functionality that Acumatica doesn't include out of the box.
The reason this distinction matters: configuration changes are safe across version upgrades. Customisations need to be tested and sometimes updated with each major version. That ongoing maintenance cost is real, and it's what shapes how we scope any custom development request.
What MYOB Acumatica's xRP platform makes possible
MYOB Acumatica is built on Acumatica's xRP platform, which is designed specifically for extensibility. Unlike some ERP platforms where custom code sits in a separate layer that breaks on every upgrade, xRP customisations are built using a published API and documented patterns that the upgrade process recognises. Custom objects upgrade with the system rather than against it, which is a meaningful difference when you're looking at a platform you'll run for a decade.
Generic Inquiries: custom reporting without code
Generic Inquiries are one of the most underused tools in a standard MYOB Acumatica implementation. They let you build custom reports, pivot tables, and data exports from any table in the Acumatica database, entirely within the standard interface, no code required. If your CFO needs a report that the standard library doesn't produce, Generic Inquiries are almost always the right starting point before commissioning custom development. They also feed into configurable dashboards, so the KPIs your warehouse manager sees when they log in can look completely different from what your finance director sees.
Business Events: automated triggers across the system
Business Events let you define conditions and automated actions across the platform. When a purchase order is approved above a certain value, notify the finance director. When stock falls below a reorder point, create a purchase requisition. When a project milestone is marked complete, send a billing notification. These are all configuration, not customisation, and they cover a significant portion of the workflow automation that businesses assume requires custom code.
REST API for external integrations
MYOB Acumatica's REST API exposes the full range of Acumatica's business logic for integration with external systems. eCommerce platforms, third-party logistics providers, custom portals, and industry-specific tools all connect via the API. According to MYOB's ERP Trends Report 2025, 45% of Australian decision-makers say disconnected systems are limiting their business growth. For most of those businesses, the API is where the answer starts, not a custom module build.
Custom screens and industry-specific extensions
Where the xRP framework goes beyond configuration is in genuinely custom screens and business logic. Examples from Australian projects include: a custom job card screen for a manufacturer that doesn't fit neatly into the standard production order workflow; a client-portal-facing view that surfaces specific project data without exposing the full Acumatica interface; a compliance tracking screen built for a business with regulatory reporting requirements specific to their industry. These are real development projects, scoped, built, and tested like any software engagement.
"The question I ask before we scope any customisation is: if we build this, who maintains it in two years? If the answer is unclear, that's a signal to look harder at what the standard platform already does. We've saved clients significant custom development spend by going back to the Business Events and Generic Inquiry toolset they already had access to."
Bill Alvarez, Practice Manager, Auboros
What customisation typically costs in Australian projects
Custom development in MYOB Acumatica is priced as a professional services engagement. There's no flat rate because the scope varies too widely. A simple custom field or screen modification might take four to eight hours of developer time. A complex industry-specific extension with its own data model, custom screens, and business logic could run to 80 to 200 hours or more.
For Australian businesses planning a customisation budget, the main variables are the number of custom objects involved, whether the customisation needs to interact with multiple Acumatica modules, the complexity of testing and validation required, and how many users are affected. Our guide on choosing the right MYOB Acumatica implementation services covers how to evaluate whether your prospective partner has the technical capability to build and support what you need.
The ongoing maintenance consideration is worth budgeting separately. Each major Acumatica version release requires a compatibility review of any custom code. For well-scoped, well-documented customisations, this is typically a few hours of work per upgrade cycle. For sprawling, poorly documented custom builds, it can become a significant cost that wasn't anticipated at the time of implementation. This is the argument for keeping customisations targeted and for working with a partner who documents what they build.
What to avoid when customising MYOB Acumatica
The mistakes we see most often in custom Acumatica work: customising something the standard platform already handles with the right configuration, building custom code for a one-off requirement that will change in six months, and using customisation to paper over a process problem rather than fixing the process. None of these make the platform better. They add maintenance cost without adding lasting value.
A second common mistake is scoping customisations before configuration is complete. The standard Acumatica toolset is more capable than most businesses expect: Generic Inquiries, Business Events, configurable workflows, role-based dashboards. Many businesses that come to us assuming they need custom development find that what they need already exists, and that the gap was in how their previous implementation was configured rather than what the product can do. Our MYOB Acumatica consulting guide covers what good partner engagement looks like at the scoping stage, including how a partner should challenge customisation requests before committing to build them.
For businesses currently running customisations built by a previous partner and looking for ongoing support, our MYOB Acumatica support services guide explains what a handover review involves and what you should expect from a support partner managing inherited custom code.
Frequently asked questions
What's the difference between configuring and customising MYOB Acumatica?
Configuration uses the standard Acumatica toolset, including Generic Inquiries, Business Events, dashboards, workflow approvals, and user roles, to fit the platform to your business without writing code. Customisation uses the xRP development framework to extend or modify platform behaviour beyond what configuration can achieve. Configuration changes are safe across version upgrades; customisations require a compatibility review with each major release.
Can MYOB Acumatica integrate with our existing systems?
Yes. MYOB Acumatica's REST API provides a published, documented integration layer that connects with eCommerce platforms, third-party logistics systems, industry-specific tools, and custom portals. Most integration projects are scoped as API development engagements rather than platform customisations. The complexity and cost depends on what the external system can expose and how much business logic needs to sit on the Acumatica side.
Do customisations survive version upgrades?
Customisations built using the xRP platform's published API and documented patterns are designed to upgrade with the system rather than against it. In practice, each major version release requires a compatibility review and sometimes minor updates to custom code. Well-scoped, well-documented customisations typically require a few hours of work per upgrade cycle. Poorly documented or workaround-style builds can be significantly more expensive to maintain across versions.
How do I know if I need customisation or just better configuration?
The right starting point is a thorough review of your current configuration against your requirements. Generic Inquiries, Business Events, and configurable workflows cover more than most businesses realise. If you've had an implementation that didn't configure these tools well, what looks like a product limitation is often a configuration gap. A partner should always assess configuration options before recommending custom development. If you're being pushed toward custom code without that conversation happening, that's a signal to ask more questions.
Evaluating MYOB Acumatica customisation for your business?
Auboros is an official MYOB Acumatica Partner based in Brisbane, supporting businesses across Queensland, NSW, and Victoria with implementation, configuration, and custom development. You can see the full range of our MYOB Acumatica services on our solutions page. We scope customisations honestly, which means telling you when the standard platform already does what you need.
If you want to understand what's genuinely custom versus what's configuration, book a free consultation. We'll give you a straight answer on both.
One of the most common questions we get during MYOB Acumatica evaluations is some version of: "Can it be customised to fit how we work?" The short answer is yes. The longer answer is that "customisation" covers a wide range of things, from configuring a dashboard to writing custom screens that change how the system behaves for your industry. Understanding the difference matters before you start scoping, because the cost and ongoing maintenance implications are very different depending on what you're actually asking for.
This post covers the distinction between configuration and customisation, what the xRP platform makes possible at each level, what custom work typically costs in Australian projects, and how to avoid the mistakes that make custom development expensive to maintain.
Configuration versus customisation: why the distinction matters
MYOB Acumatica draws a clear line between configuration and customisation, and it's worth understanding before you brief a partner.
Configuration is everything you do inside the standard Acumatica interface without touching code. Setting up your chart of accounts, defining approval workflows, building Generic Inquiries (custom reports), configuring Business Events (automated notifications and triggers), setting user roles and access permissions, building dashboards for different roles in your business. Most of what Australian businesses need to make Acumatica work for their operations falls into this category. A well-scoped implementation handles all of this during the standard project.
Customisation is what happens when configuration isn't enough. It means extending or modifying the platform's behaviour using Acumatica's xRP development framework. Adding a custom field to a standard screen. Building a new screen for a workflow that doesn't exist in the core product. Integrating with a third-party system via the REST API. Building industry-specific functionality that Acumatica doesn't include out of the box.
The reason this distinction matters: configuration changes are safe across version upgrades. Customisations need to be tested and sometimes updated with each major version. That ongoing maintenance cost is real, and it's what shapes how we scope any custom development request.
What MYOB Acumatica's xRP platform makes possible
MYOB Acumatica is built on Acumatica's xRP platform, which is designed specifically for extensibility. Unlike some ERP platforms where custom code sits in a separate layer that breaks on every upgrade, xRP customisations are built using a published API and documented patterns that the upgrade process recognises. Custom objects upgrade with the system rather than against it, which is a meaningful difference when you're looking at a platform you'll run for a decade.
Generic Inquiries: custom reporting without code
Generic Inquiries are one of the most underused tools in a standard MYOB Acumatica implementation. They let you build custom reports, pivot tables, and data exports from any table in the Acumatica database, entirely within the standard interface, no code required. If your CFO needs a report that the standard library doesn't produce, Generic Inquiries are almost always the right starting point before commissioning custom development. They also feed into configurable dashboards, so the KPIs your warehouse manager sees when they log in can look completely different from what your finance director sees.
Business Events: automated triggers across the system
Business Events let you define conditions and automated actions across the platform. When a purchase order is approved above a certain value, notify the finance director. When stock falls below a reorder point, create a purchase requisition. When a project milestone is marked complete, send a billing notification. These are all configuration, not customisation, and they cover a significant portion of the workflow automation that businesses assume requires custom code.
REST API for external integrations
MYOB Acumatica's REST API exposes the full range of Acumatica's business logic for integration with external systems. eCommerce platforms, third-party logistics providers, custom portals, and industry-specific tools all connect via the API. According to MYOB's ERP Trends Report 2025, 45% of Australian decision-makers say disconnected systems are limiting their business growth. For most of those businesses, the API is where the answer starts, not a custom module build.
Custom screens and industry-specific extensions
Where the xRP framework goes beyond configuration is in genuinely custom screens and business logic. Examples from Australian projects include: a custom job card screen for a manufacturer that doesn't fit neatly into the standard production order workflow; a client-portal-facing view that surfaces specific project data without exposing the full Acumatica interface; a compliance tracking screen built for a business with regulatory reporting requirements specific to their industry. These are real development projects, scoped, built, and tested like any software engagement.
"The question I ask before we scope any customisation is: if we build this, who maintains it in two years? If the answer is unclear, that's a signal to look harder at what the standard platform already does. We've saved clients significant custom development spend by going back to the Business Events and Generic Inquiry toolset they already had access to."
Bill Alvarez, Practice Manager, Auboros
What customisation typically costs in Australian projects
Custom development in MYOB Acumatica is priced as a professional services engagement. There's no flat rate because the scope varies too widely. A simple custom field or screen modification might take four to eight hours of developer time. A complex industry-specific extension with its own data model, custom screens, and business logic could run to 80 to 200 hours or more.
For Australian businesses planning a customisation budget, the main variables are the number of custom objects involved, whether the customisation needs to interact with multiple Acumatica modules, the complexity of testing and validation required, and how many users are affected. Our guide on choosing the right MYOB Acumatica implementation services covers how to evaluate whether your prospective partner has the technical capability to build and support what you need.
The ongoing maintenance consideration is worth budgeting separately. Each major Acumatica version release requires a compatibility review of any custom code. For well-scoped, well-documented customisations, this is typically a few hours of work per upgrade cycle. For sprawling, poorly documented custom builds, it can become a significant cost that wasn't anticipated at the time of implementation. This is the argument for keeping customisations targeted and for working with a partner who documents what they build.
What to avoid when customising MYOB Acumatica
The mistakes we see most often in custom Acumatica work: customising something the standard platform already handles with the right configuration, building custom code for a one-off requirement that will change in six months, and using customisation to paper over a process problem rather than fixing the process. None of these make the platform better. They add maintenance cost without adding lasting value.
A second common mistake is scoping customisations before configuration is complete. The standard Acumatica toolset is more capable than most businesses expect: Generic Inquiries, Business Events, configurable workflows, role-based dashboards. Many businesses that come to us assuming they need custom development find that what they need already exists, and that the gap was in how their previous implementation was configured rather than what the product can do. Our MYOB Acumatica consulting guide covers what good partner engagement looks like at the scoping stage, including how a partner should challenge customisation requests before committing to build them.
For businesses currently running customisations built by a previous partner and looking for ongoing support, our MYOB Acumatica support services guide explains what a handover review involves and what you should expect from a support partner managing inherited custom code.
Frequently asked questions
What's the difference between configuring and customising MYOB Acumatica?
Configuration uses the standard Acumatica toolset, including Generic Inquiries, Business Events, dashboards, workflow approvals, and user roles, to fit the platform to your business without writing code. Customisation uses the xRP development framework to extend or modify platform behaviour beyond what configuration can achieve. Configuration changes are safe across version upgrades; customisations require a compatibility review with each major release.
Can MYOB Acumatica integrate with our existing systems?
Yes. MYOB Acumatica's REST API provides a published, documented integration layer that connects with eCommerce platforms, third-party logistics systems, industry-specific tools, and custom portals. Most integration projects are scoped as API development engagements rather than platform customisations. The complexity and cost depends on what the external system can expose and how much business logic needs to sit on the Acumatica side.
Do customisations survive version upgrades?
Customisations built using the xRP platform's published API and documented patterns are designed to upgrade with the system rather than against it. In practice, each major version release requires a compatibility review and sometimes minor updates to custom code. Well-scoped, well-documented customisations typically require a few hours of work per upgrade cycle. Poorly documented or workaround-style builds can be significantly more expensive to maintain across versions.
How do I know if I need customisation or just better configuration?
The right starting point is a thorough review of your current configuration against your requirements. Generic Inquiries, Business Events, and configurable workflows cover more than most businesses realise. If you've had an implementation that didn't configure these tools well, what looks like a product limitation is often a configuration gap. A partner should always assess configuration options before recommending custom development. If you're being pushed toward custom code without that conversation happening, that's a signal to ask more questions.
Evaluating MYOB Acumatica customisation for your business?
Auboros is an official MYOB Acumatica Partner based in Brisbane, supporting businesses across Queensland, NSW, and Victoria with implementation, configuration, and custom development. You can see the full range of our MYOB Acumatica services on our solutions page. We scope customisations honestly, which means telling you when the standard platform already does what you need.
If you want to understand what's genuinely custom versus what's configuration, book a free consultation. We'll give you a straight answer on both.