Business Central

Business Central accounting in Australia: GST, BAS, EFT, payroll, and Peppol checks before rollout

A practical Australian buyer guide to Business Central finance localisation, covering GST, BAS, EFT bank files, payroll operating model questions, and Peppol checks before rollout.

Australian finance teams evaluating Business Central need to separate Microsoft-documented local capability from partner extensions, payroll providers, and project promises before rollout scope is approved.

Microsoft's current documentation gives a clearer answer than many buyers expect. Business Central has explicit Australian local functionality across GST, BAS structure, electronic funds transfer, eInvoicing, and payment-times support. At the same time, the payroll story in Microsoft's own docs is more integration-led than "native Australian payroll is fully solved inside ERP". That distinction matters before rollout scope is signed off.

What Microsoft officially documents for Australia today

• Microsoft's Australia local functionality page groups the Australian version into Tax, Electronic documents, Banking and Payments, Core Finance, and General features.
• That page specifically lists Goods and Services Tax posting, Electronic Funds Transfer, setting up business units for Business Activity Statements, eInvoicing in Peppol PINT A-NZ format, and Payment Times Reporting support.
• For buyers, that matters because it shows Australia is not being represented only through partner slides. There is real Microsoft-documented localisation coverage to test.

Priority 1: treat GST and BAS as a finance design exercise, not a checkbox

• Microsoft's GST setup article says GST paid and received during a period is reported in the Business Activity Statement and that GST posting must be set up before generating the BAS report.
• Microsoft also documents BAS business-unit setup for groups. The article says you can consolidate the financial statements of various companies into one financial statement and set up parent companies, subsidiaries, and affiliates for a group BAS structure.
• The ATO says businesses registered for GST need to lodge a BAS to report and pay GST, PAYG instalments, PAYG withholding, and other taxes.
• The practical buyer implication is that Business Central can support Australian GST and BAS structure, but the project still needs careful ownership for tax mapping, intercompany treatment, reconciliation, and the actual lodgement workflow.

Priority 2: EFT support is useful, but bank-file testing should happen early

• Microsoft's EFT article for Australia says Business Central can export EFT files that you then upload to your bank's website for processing.
• The same article says you must add EFT information to bank accounts, enable EFT payment on vendors, and create EFT files from the payment journal. It also notes that EFT handling interacts with withholding-tax logic and EFT register records.
• That is commercially relevant because many finance teams still care more about dependable payment execution than polished dashboards.
• The buyer lesson is simple: do not leave bank-file testing until late UAT. Prove the exact bank accounts, remittance workflow, approvals, exception handling, and withholding-tax edge cases early.

Priority 3: payroll should be treated as an operating-model decision

• Microsoft's payroll documentation is telling in a useful way. It says salary payments and related transactions are imported from your payroll provider into the general ledger, then mapped and posted from the General Journal.
• The same article says an extension for payroll import must be installed and enabled, and references preinstalled payroll file import extensions.
• The cautious reading is that Business Central can account for payroll transactions, but buyers should not let a generic "HR and payroll" claim blur the difference between payroll processing, payroll compliance, and payroll accounting import.
• If payroll is in scope in Australia, force the partner to name the payroll product, the file or integration path, the owner of STP and super obligations, and what remains outside Business Central.

Priority 4: Peppol is supported, but the provider relationship still matters

• Microsoft's Australian eInvoicing article says the E-Document framework for the Australian localisation supports only the Peppol PINT A-NZ format.
• Microsoft also says you can select any service provider available for the Australian market with whom you have an agreement.
• The ATO says businesses can register for eInvoicing through eInvoicing Ready software, an eInvoicing service provider, or a low-cost online solution depending on business needs.
• The operational takeaway is that Business Central has a documented Australian Peppol path, but rollout still depends on provider choice, onboarding ownership, and support boundaries. "Supported" is not the same as "commercially and operationally solved".

Priority 5: larger groups should not overlook payment-times reporting design

• Microsoft's current Australian Payment Times Reporting article says entities above the relevant revenue thresholds must report how they pay small business vendors.
• That same article makes an important limit explicit: Business Central does not have a dedicated Payment Times Reporting Scheme report, even though the required underlying data is present. For more automated reporting, Microsoft says you must find and install a partner add-in.
• If your group sits near the reporting threshold, this should be part of the finance architecture conversation before partner selection is closed, not an afterthought once AP is already live.

The shortlist questions that matter most

• 1. Show one BAS cycle from transaction posting through GST mapping, review, reconciliation, and final values ready for lodgement.
• 2. Show one payment run using our real bank accounts and vendor scenarios, including EFT export, approval flow, remittance, and exception handling.
• 3. Name the payroll operating model explicitly: which product runs payroll, how transactions enter Business Central, and who owns compliance and support.
• 4. If Peppol is in scope, name the Australian service provider, the onboarding sequence, and the support boundary between Microsoft, partner, and provider.
• 5. If we may fall into Payment Times Reporting, show whether the reporting path stays manual, uses Excel, or depends on a specific add-in.

Where Business Central programmes usually go wrong in Australia

• Teams assume localisation removes the need for finance design discipline.
• Buyers validate dashboards and workflow screens but leave GST mapping, bank-file execution, and payroll ownership until late design.
• Partners say "Business Central supports payroll" without being precise about whether they mean payroll accounting import or a complete payroll operating model.
• Finance and IT agree that Peppol is supported but fail to define the service-provider agreement, onboarding path, and ongoing support model early enough.

What Australian buyers should conclude now

• Business Central has stronger Australia-specific finance documentation than many buyers assume. GST, BAS structures, EFT, Peppol PINT A-NZ, and payment-times support are all part of Microsoft's current documented local functionality.
• The real caution is not absence of localisation. It is where the operating model still sits outside the core product or outside one clean Microsoft-owned workflow, especially in payroll, partner add-ins, and eInvoicing provider dependency.
• If Business Central is on your shortlist, the best next step is a finance-led design workshop. Make the partner prove tax mapping, bank-file execution, payroll boundaries, and Peppol onboarding using your own Australian scenarios before scope is locked.

FAQ

• Does Business Central support BAS and GST for Australia? Yes. Microsoft documents Australian GST posting and BAS-related setup, including group business-unit structure for BAS scenarios.
• Can Business Central create Australian bank payment files? Yes. Microsoft documents Australian EFT export from the payment journal for bank-file processing.
• Is Australian payroll fully native inside Business Central? Microsoft's current documentation emphasises importing payroll transactions from a payroll provider into the general ledger, so buyers should treat payroll as a separate operating-model decision rather than assume a complete native payroll stack.
• Does Business Central support Peppol eInvoicing in Australia? Yes. Microsoft documents Australian eInvoicing through the E-Document framework using the Peppol PINT A-NZ format, but it also requires a service provider agreement.

Sources used

• Microsoft Learn Australia local functionality page for feature coverage across GST, EFT, BAS, eInvoicing, and Payment Times Reporting.
• Microsoft Learn articles for GST posting setup, EFT in Australia, BAS business units, electronic invoicing in Australia, Payment Times Reporting in the Australian version, and Import payroll transactions.
• Australian Taxation Office guidance on how to lodge your BAS and eInvoicing for businesses.