Your Melbourne health or events group runs four entities and the ERP still can't consolidate them before the board meeting
Custom ERP (Enterprise Resource Planning) development in Melbourne runs $95k to $290k over 4 to 9 months, and most Melbourne groups need it once a NetSuite, SAP, Odoo, or Dynamics rollout stalls against the way they actually operate. A medical-research institute juggling grant funding, a multi-venue events company invoicing in deposits and final balances, or a professional-services firm billing across three trading entities rarely fits the standard finance module. You don't need a heavier ERP. You need the consolidation and project-accounting logic those tools assume you already have.
You're a Melbourne group with a few trading entities, maybe a CBD venue business plus a catering arm, or a health service running clinical and research books side by side. The SAP or Dynamics consultant scoped a year-long rollout, you're eight months in, and the system still can't produce a consolidated P&L without someone exporting to Excel on the last day of the month.
NetSuite and SAP sell a single source of truth that assumes clean, slow, single-currency operations. A Melbourne medical-research institute acquitting NHMRC grant funding, or an events group recognising revenue across deposits taken months before the function, doesn't map onto the off-the-shelf revenue module. So the consultant bills another change order, and the spreadsheet that everyone swore would die at go-live is still the only place the real numbers live.
What erp costs in Melbourne
| Project scope | Typical cost | Timeline |
|---|---|---|
| Consolidation and reporting layer over your existing accounting tool | $95k to $165k | 4 to 6 months |
| Custom grant-acquittal or deposit-revenue ERP module with integrations | $150k to $240k | 5 to 8 months |
| Full multi-entity custom ERP for a venue, catering, and research group | $210k to $290k+ | 7 to 9 months |
The fix: erp built for Melbourne, not rented
The Melbourne case for custom isn't 'rip out SAP,' it's 'stop forcing grant accounting, multi-entity consolidation, and deposit-based revenue through a module that was never built for them.' A custom ERP layer keeps one accounting ledger of record, encodes your actual funding-acquittal and revenue-timing rules in versioned code, and consolidates entities automatically, so the board pack comes out identically every month instead of depending on who built this month's spreadsheet.
- You run two or more trading entities and consolidation is a monthly Excel exercise
- Grant or project funding rules don't fit any off-the-shelf ERP revenue module without heavy hacking
- A SAP, NetSuite, or Dynamics rollout has stalled and finance still closes in spreadsheets
- Deposit-based event billing keeps misstating the period revenue lands in
- You're a single entity with straightforward billing that NetSuite or Dynamics handles natively
- You have no one internally who can own integrations to accounting and payroll long term
- Speed to a passable ledger matters more than fitting your grant or deposit edge cases
- Your revenue is simple invoice-on-delivery with no funding acquittal or multi-entity complexity
The capability list that earns its budget
What we build under ERP in Melbourne
The engagements Melbourne teams bring us most often: manufacturing ERP, distribution ERP, custom ERP modules, ERP API integration, ERP implementation and ERP integration.
How long it takes, phase by phase
Exactly what you get
A working ERP layer that keeps your accounting tool as the ledger and adds what it can't do: automatic multi-entity consolidation, a grant-acquittal engine that matches NHMRC and ARC reporting, deposit-and-balance revenue recognition for events booked ahead, BAS-aligned reporting, and a clean feed into your business intelligence dashboards. You also get the documentation that finally lets someone other than the one finance lead run month-end. It sits next to your custom CRM (Customer Relationship Management) and accounting software rather than replacing your whole back office, and it talks to your project management software so grant projects and their funding stay reconciled.
How to choose a developer in Melbourne
Melbourne has plenty of shops that configure off-the-shelf ERPs and far fewer that have shipped real financial systems for multi-entity or grant-funded groups. You want the second kind. Ask for an acquittal or consolidation engine they built and how they tested it, because a confidently wrong acquittal is worse than a slow one. Skip anyone who opens with a rip-and-replace pitch; the right partner preserves your accounting investment and graduates the logic out of spreadsheets. Given the local preference for polished, low-theatre work, ask to talk to the engineers who'd build it, not just the account lead, and judge them on the questions they ask about your funding rules.
- Multi-entity consolidation runs automatically, so a venue company plus catering arm produces one board P&L without an Excel merge
- Grant and project funding from NHMRC, ARC, or state bodies is acquitted against rules encoded in code, with an audit trail acquittal reviewers accept
- Deposit-then-balance event revenue lands in the correct period, so monthly numbers stop swinging on timing
- Finance closes in days instead of the last-week scramble, because the consolidation isn't manual
- You own a system that fits your trading structure instead of paying change orders to bend SAP toward it
- You take on ownership of the integrations to your accounting tool, payroll, and banking; when one changes an API, patching it becomes your job
- Grant-acquittal and revenue-timing logic has to be exactly right, so the testing burden is real and a sloppy build produces confidently wrong acquittals
- It forces your finance lead to define funding and revenue rules precisely up front, which is slower and more political than people expect
- Budget 15 to 20 percent of build cost per year for maintenance, on top of the accounting tool you keep underneath
- !They've never built grant or fund acquittal; ask for a concrete funding-acquittal example they shipped for a research or NFP client
- !They propose ripping out your accounting tool entirely; ask how they'd keep it as the ledger of record instead
- !No question about how your entities consolidate today; ask who maps the current month-end before any code is written
- !They quote a fixed price before seeing your funding and revenue types; ask which acquittal edge cases change the estimate
- !Vague on audit trail; ask how a grant auditor would sign off on the acquittals the system produces
If erp is on the roadmap, internal tools, shopify, inventory management usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Can't NetSuite or SAP just consolidate our entities out of the box?
They consolidate clean, similar entities fine. They struggle when one entity runs grant-funded research and another runs deposit-based events, because the revenue and acquittal rules differ per entity. Configuring SAP to fit often costs as much as a custom build and still leaves gaps. A custom consolidation layer over a simpler ledger is frequently cheaper and an exact fit for a Melbourne group.
Our SAP rollout is already eight months in. Do we abandon it?
Not necessarily. Often the right move is to keep the ledger SAP gives you and build a thin custom layer for the parts that stalled it, the grant acquittal or deposit revenue. That salvages the investment instead of starting over, and it's usually faster than another year of change orders.
How does grant acquittal differ from normal accounting?
Grant funding from NHMRC, ARC, or Victorian bodies comes with spending rules, reporting periods, and clawback conditions that standard revenue modules ignore. Acquittal means proving the money was spent as the grant required, on time, with an audit trail. A custom module encodes those rules so acquittals come out reviewer-ready instead of being rebuilt in Excel each cycle.
Can it handle events deposits and clinical billing in one system?
Yes, and that mix is a common Melbourne reason to build. Deposit-then-balance event revenue and grant-funded research follow different timing rules, which breaks single off-the-shelf modules. A custom ERP layer applies the right rule per entity and still rolls up to one consolidated board P&L.
What stays in our existing accounting tool?
Your accounting tool stays as the ledger of record for transactions, GST, and BAS. The custom layer sits above it to consolidate entities, acquit grants, and time event revenue correctly, then writes results back. You keep the tool your accountant already trusts and add only the logic it never had.