MYOB Acumatica Reporting and Dashboards: What You Can Build Without a Developer

Ask a finance team why they bought an ERP and the honest answer is usually some version of “so we stop rebuilding the same spreadsheet every month.” The MYOB ERP Trends report found 45% of Australian decision-makers say disconnected systems are limiting their growth, and the report’s case studies describe teams winning back the equivalent of a day a week once reporting comes out of spreadsheets and into the platform.

MYOB Acumatica reporting is one of the platform’s stronger suits, but the toolkit has several layers and it isn’t obvious from the outside which layer does what. Here’s how the pieces fit, what you can build yourself, and where you’ll want help.

The four reporting layers in MYOB Acumatica

Most reporting questions land in one of four tools, and knowing which one saves a lot of wandering.

• Financial statements. The Analytical Report Manager builds your P&L, balance sheet and cash flow layouts directly from general ledger data, with the structure and comparatives your accountant expects.
• Generic inquiries. The workhorse of the platform. A generic inquiry is a reusable query over any data in the system, built through configuration rather than code, and Acumatica’s documentation confirms inquiries feed reports, dashboards, Excel exports and OData connections.
• Dashboards. Role-based screens assembled from inquiry data: charts, tables, KPIs and trend tiles that update in real time and drill down to the underlying transactions.
• External BI. When analysis outgrows the platform, inquiries publish through OData to tools like Microsoft Power BI, so your analysts work on live ERP data rather than last week’s export.

The pattern worth noticing: generic inquiries sit underneath almost everything. Get comfortable building them and most reporting requests stop needing anyone’s help at all.

Dashboards that match how people actually work

The dashboard layer is role-based, which matters more than it sounds. A warehouse manager logs in to open orders and stock alerts. The financial controller sees cash position, overdue receivables and unreconciled accounts. Neither wades through the other’s numbers, and access follows the same security roles that govern the rest of the platform, so nobody sees figures they shouldn’t.

Dashboards are built by configuration. Pick an inquiry, choose a widget type, set the filters. In our experience the first few are worth building alongside someone who knows the data model, after which most teams maintain their own.

Consolidated reporting across companies

For groups running multiple entities, this is where the platform earns its keep. MYOB Acumatica posts intercompany transactions and produces consolidated financials without the spreadsheet merge ritual, and dashboards can show group-wide or per-entity views from the same inquiries. We covered the underlying structure in our guide to MYOB Acumatica multi-entity and intercompany accounting, including how GST groups change BAS lodgement.

One boundary to keep clear: consolidated management reporting is not the same thing as your statutory obligations. Your BAS still gets built from the tax data underneath, and the ATO’s business activity statement guidance remains the reference for what has to be lodged and when. Good dashboards make BAS preparation calmer; they don’t replace it.

“The reporting conversation I have most often isn’t about a missing feature. It’s a business that has owned the platform for two years and still runs month end out of Excel because nobody showed them generic inquiries in week one. The capability was sitting there the whole time.”

Bill Alvarez, Practice Manager, Auboros

What you can build yourself, and where the edges are

A realistic split, based on the implementations we support:

• Configuration territory. New inquiries, dashboard changes, pivot tables, Excel and OData connections, side panels on existing screens. A capable finance user handles all of this after a day or two of guided practice.
• Partner territory. Reports that need new calculated fields across modules, performance tuning on inquiries over very large tables, and anything touching the customisation layer. Our post on MYOB Acumatica customisation explains where configuration ends and development begins.

Worth knowing on the roadmap front: Acumatica’s 2026 R1 release adds AI-assisted anomaly detection on inquiries and live Excel export of analytical reports. MYOB packages global releases for Australia and New Zealand on its own schedule, and the current ANZ release is 25 R2, so treat those features as coming rather than available until they appear in MYOB’s local release notes. The reporting layers above are core platform and have been shipping for years.

Getting more out of the reports you already own

If your MYOB Acumatica reporting still leans on exports, the fix is usually sequencing, not software. Start with the five numbers each role checks weekly, build one inquiry and one dashboard per role, and retire the matching spreadsheet the same week. Momentum does the rest.

Make MYOB Acumatica reporting earn its subscription

We build reporting and dashboard setups as part of MYOB Acumatica implementations and as standalone engagements for businesses already on the platform, from our base in Brisbane across Queensland and beyond. If month end still lives in spreadsheets, book a free consultation and we’ll map your current reports to the tools you’re already paying for. Bring your worst spreadsheet; we’ve seen worse.