ERPNext Consultant in Australia

GST and BAS on ERPNext: what to set up and verify

ERPNext handles GST through sales and purchase tax templates, item tax templates and tax categories. That covers the mechanics of charging and claiming GST on invoices and bills. What it does not give you, in a standard install, is a ready-made Business Activity Statement with each label filled in, so that part needs to be designed.

I approach it in three steps with your accountant:

1. Classify supplies. Taxable, GST-free, input-taxed, imports and capital purchases each get a clear template, so every transaction carries a treatment that can be traced.
2. Map to BAS labels. Each template is linked to the BAS labels it feeds, and a report sums posted transactions by label. Depending on your installed version and apps, this may be an existing report or a custom one.
3. Test a full period. Before go-live, we run a sample quarter through ERPNext and compare the results with what your accountant would lodge.

ABNs are held on customer and supplier records, and tax invoice print formats are checked so they show the details your accountant requires. If you report on a cash basis, the report logic has to reflect that, which is easy to overlook. Please confirm current GST and BAS requirements with your accountant. The wider Australian picture is on my ERP consultant in Australia page.

Moving from MYOB or Xero and retiring add-on apps

The typical Australian ERPNext migration replaces more than the accounting file. Alongside MYOB or Xero there is usually an inventory app, a job management tool, a purchasing approval flow and a few spreadsheets. Part of the project is deciding which of these ERPNext replaces and which stay, connected through its REST API.

I start with an app inventory: what each tool does, who uses it, what data it holds and what it costs to keep. Then the migration itself:

• The chart of accounts is mapped, often simplified with cost centers and accounting dimensions instead of tracking categories.
• Contacts become customers and suppliers, with ABNs, addresses and payment terms checked for duplicates.
• Items come from the inventory app, with units, valuation and opening stock by warehouse.
• Open invoices and bills move across at a period end that lines up with your BAS cycle.
• Trial balance, aged receivables, aged payables and stock value are reconciled with your accountant after each trial load.

Bank processes need attention too. Batch supplier payments usually go out as ABA files, which ERPNext does not produce in a standard install, so I plan a custom report or community app and test it with your bank. Bank statement imports support reconciliation. The ERP data migration service covers the method in more depth.

Payroll, super and STP: keep them in a specialist product

Australian payroll is demanding. Single Touch Payroll reporting, superannuation guarantee contributions, leave accruals and, for many businesses, modern award interpretation with penalty rates and allowances all need to be right every pay run. Frappe HR does not provide Australian STP reporting or award interpretation as a standard feature, and building them would be a large, risky custom project.

My usual recommendation is simple: run payroll in an STP-enabled payroll product, and connect it to ERPNext. The design work is in the connection:

• Employee records and cost allocations are kept consistent between the two systems.
• Payroll journals post into ERPNext by job, department, location or state, so labor costs show up in project and branch margins.
• Timesheets captured in ERPNext projects or a field app can feed payroll, reducing double entry.
• Super and PAYG liabilities are reconciled monthly between payroll and the ledger.

Frappe HR can still help with leave requests, attendance or expense claims if that suits you, but payroll calculations stay in the specialist product. This split keeps compliance with a vendor whose job is Australian payroll, while ERPNext focuses on stock, jobs and accounts. Where field technicians are involved, the field service page explains how jobs, labor and materials connect.

Industries, hosting and working with Australian implementers

ERPNext tends to fit Australian wholesalers and importers, small manufacturers, food producers and trade or service businesses that run many small jobs. Long distances and imported stock make landed costs, multi-state warehouses and freight lead times important, and ERPNext handles these with landed cost vouchers, transfers and reorder rules. Small manufacturers can plan production and trace batches in ERPNext manufacturing. The wholesale page covers the wider industry picture.

Hosting deserves a deliberate choice. If onshore data matters to your customers, confirm whether Frappe Cloud currently has an Australian location before signing up. Running ERPNext on your own account with an Australian cloud region is the alternative, with patching, monitoring and upgrade testing then sitting with you or a managed provider. Review either option against the Privacy Act obligations that apply to you.

The Australian ERPNext implementer market is small, and many projects use developers based elsewhere. That can work well when someone on your side owns the requirements and checks the build. I take that role as an independent consultant, owning the requirements, checking each proposal and custom app against them, and running acceptance testing with your people. I work remotely, and my working hours overlap well with the Australian business day, including across the eastern and western states.

Where ERPNext struggles for Australian businesses

Here are the Australian situations where I usually recommend something other than ERPNext:

• Your accountant lives in the Xero or MYOB ecosystem: if advisors, bookkeepers and lodgement workflows depend on those products, the change cost can be higher than the gain.
• The business is mainly services with light stock: an accounting package with a job management add-on may be enough.
• You want payroll and awards inside the ERP: that needs a platform with supported Australian payroll, not ERPNext.
• BAS must be produced without any custom reporting: plan for some configuration or reporting work on ERPNext.
• Nobody to look after it: open-source ERP needs a named person or provider for upgrades, apps and backups, or it slowly degrades.

If two or more of these sound familiar, a lighter accounting-plus-add-on stack or a different ERP may serve you better, and I will say so. My Zoho and ERPNext comparison is a useful starting point for Australian service firms, while Odoo against ERPNext suits stock-heavy businesses. Background on the platform sits on my ERPNext consulting page, and the Australia hub explains how remote engagements run.