Dynamics 365 Business Central ships with no Australian payroll engine. The AU localisation covers GST, BAS and the local chart of accounts, but the moment you need to pay an employee you are pushed to a separate payroll product, a spreadsheet, or a bureau — and then you are manually journaling wages, PAYG withholding, superannuation liability and leave provisions back into Business Central every cycle. That reconciliation is where the errors live: a pay run posted to the wrong dimension, a super accrual that never clears when the clearing house pays it, an STP submission whose year-to-date figures no longer agree with the general ledger. With payday super taking effect from 1 July 2026, contributions must reach the fund within seven days of the qualifying earnings day rather than 28 days after the quarter — a monthly-or-worse manual process simply cannot hold that window.

This extension puts the payroll cycle inside Business Central. We build an AL extension — delivered as a per-tenant extension for SaaS, or as an app package where you run on-premises — that adds employee payroll cards, pay-item and award-rate setup, pay cycles, timesheet-to-pay-line capture, and a pay run that produces a posted payroll journal against your real G/L accounts, dimensions and job/project codes. Pay items are records rather than hard-coded logic: ordinary hours, overtime multipliers, penalty and shift loadings, allowances (taxable and non-taxable, expense-reimbursement or otherwise), salary sacrifice, RESC and deduction categories each carry their own STP Phase 2 disaggregation code, PAYG treatment and OTE flag. Superannuation is calculated per pay line from the OTE flag at the current SG rate, with maximum contribution base capping, employee-level fund and USI/ESA details, and configurable minimum-contribution and stapled-fund handling. Leave accrues per pay period against NES-aligned entitlement types — annual, personal/carer's, long service by state rule, and unpaid categories — with balances, leave loading and cashing-out shown on the employee card and on the payslip.

Technically the build is conventional Business Central AL. Payroll masters and transactions live in new tables with their own list, card and document pages; Employee, Vendor (for super funds and clearing houses) and Dimension are reached through table and page extensions so no base object is modified. Calculation lives in codeunits with a documented event-publisher surface — OnBeforeCalculatePayLine, OnAfterCalculateSuperannuation, OnBeforeBuildSTPEvent — so award changes and enterprise-agreement quirks are handled by a small subscriber extension rather than a fork. Posting goes through the standard journal posting stack, so payroll respects your allowed posting dates, approval workflow and audit trail. STP submissions are prepared as pay-event and update-event payloads with employer and employee YTD sets, submitted through your chosen SBR gateway or digital service provider, and every submission is stored with its request, response, receipt id and status so an ATO query can be answered from the record. Payment output covers ABA bank files for net pay and super, plus payday-super scheduling that groups qualifying earnings by payment date and raises the contribution batch inside the statutory window. Job queue entries run the recurring work — accruals, super batch preparation, submission status polling — and API pages exposed over REST API v2.0 / OData v4 give Power BI, Power Automate and Dataverse access to pay run, leave balance and super contribution data. Permission sets separate payroll administrators from approvers and from ordinary users, because payroll is the one dataset in Business Central that everyone can read by default if you are careless with it.

This is build-to-order, not an AppSource download. Nothing installs today. We start with a scoping call to establish which awards or enterprise agreements you pay under, your pay frequencies and cut-offs, how many employees and entities, your super clearing house and STP gateway, whether you need long service leave by state, and how payroll should map to your existing G/L and dimension structure. You get a fixed scope and a fixed quote before any code is written. Typical delivery is two to four weeks from confirmed scope, built against your Business Central version and release wave, tested on your sandbox with a parallel pay run against your current payroll output, and handed over with the source code and the git repository.

We are an implementation partner, not a registered tax or BAS agent and not an SBR software provider. The extension calculates and reports what your configured rules and rates say; your payroll officer or registered agent remains responsible for lodgement and for award interpretation. We build the mechanism, and we keep it current with the ATO's published schedules and the payday-super timetable.