Australia

Payday Super before 1 July 2026: ERP checklist for Business Central, NetSuite, and Odoo teams

An Australian ERP checklist for Payday Super before 1 July 2026, covering system ownership, payroll integration, clearing-house changes, and proof points for Business Central, NetSuite, and Odoo teams.

The most important date is fixed: from 1 July 2026, the ATO says employers must pay super guarantee on payday, at the same time as salary and wages, with the contribution received by the employee super fund within 7 business days unless an extended timeframe applies. If your business runs Business Central, NetSuite, or Odoo, the real question is whether the end-to-end operating model can meet that rule repeatedly under normal and exception scenarios.

What changes on 1 July 2026

• The ATO Software Developers Payday Super page says super guarantee will be calculated as 12% of an employee's qualifying earnings, a new term that combines ordinary time earnings and other payments.
• The same ATO page says super must be paid on payday and received by the super fund within 7 business days, which means "payment initiated" is no longer the useful control point on its own.
• The ATO also says the Small Business Superannuation Clearing House closes from 1 July 2026, with existing users only able to use it until 11:59 pm AEST on 30 June 2026.
• For ERP and finance leaders, that means three things must be true together: pay-run timing, payment rails, and receipt visibility all need a documented owner.

Why ERP teams should care, even if payroll sits elsewhere

• Most mid-market ERP programmes split responsibility across payroll software, ERP finance, banking, and a clearing house or payment intermediary.
• Payday Super makes those boundaries more dangerous because a failure in one handoff can still create an employer compliance miss, even if the ERP general ledger looks correct.
• If your implementation team cannot show where qualifying earnings are calculated, where super files or payment instructions are generated, and how receipt within 7 business days is evidenced, the design is not ready.

Priority 1: remove any hidden dependency on the ATO clearing house

• The ATO says the SBSCH is closing permanently from 1 July 2026 and tells existing users to choose an alternative payment method, switch before 1 July 2026, and download their records.
• That means projects still assuming "we will sort out the super clearing piece later" are already late.
• Confirm now whether your post-30 June model uses payroll-native super processing, a commercial clearing house, a fund-offered service, or a bank-supported route.

Priority 2: prove the operating model by product, not by slideware

• Microsoft Learn says Business Central payroll transactions are imported from your payroll provider into the general ledger, mapped, and posted from the General Journal. That is a useful reminder that Business Central buyers should treat payroll and super as an explicit integration and ownership question, not assume a complete native Australian payroll stack.
• Oracle NetSuite documentation says SuitePeople U.S. Payroll supports only U.S. payroll, while the Paycheck Journal feature can integrate with external payroll systems or custom payroll solutions for any country. For Australian NetSuite teams, the important question is which external payroll and super path will actually carry the compliance burden.
• Odoo's Australia payroll documentation says it is still in the process of becoming compliant with STP Phase 2 and SuperStream, and specifically notes that companies can process super contributions more frequently in preparation for Payday Super. That means Odoo shortlists should separate current payroll localisation progress from the production model they intend to rely on in July 2026.

Priority 3: test qualifying earnings and exception paths, not only the happy path

• The ATO has introduced qualifying earnings as the basis for super calculation, so pay categories, allowances, leave cases, and contractor edge cases deserve renewed scrutiny.
• Test weekly, fortnightly, and off-cycle pay runs. Also test new employees where an extended timeframe may apply, reversals, late master-data changes, and failed or returned payments.
• Finance should be able to reconcile three views quickly: payroll-calculated liability, ERP-posted liability, and fund-received contribution.

Priority 4: cash flow and close discipline matter more under higher payment frequency

• Quarterly super payment habits can hide weak approval timing, weak payroll cutoffs, and weak bank-process ownership. Payday Super exposes those weaknesses much faster.
• Businesses moving from quarterly to weekly or fortnightly settlement need a clearer treasury rhythm, not just a software patch.
• Month-end close should include a specific control over unpaid or in-transit super by pay date, because cash movement, payroll journals, and fund receipt can now sit much closer together.

The shortlist questions that matter most

• 1. Show the full super path from pay-run approval to employee-fund receipt, including timestamps, owners, and exception queue.
• 2. Name the product that calculates qualifying earnings and the product or provider that sends contributions to funds.
• 3. Confirm what replaces the SBSCH after 30 June 2026 and who supports that service commercially and operationally.
• 4. Show one failed-payment scenario, one new-starter scenario, and one off-cycle-pay scenario end to end.
• 5. Confirm how finance will reconcile payroll, ERP, bank, and clearing-house or fund-confirmation data in the first three cycles after 1 July 2026.

Where Australian ERP programmes are most likely to fail here

• Sponsors assume Payday Super is a payroll-team issue and leave ERP finance, treasury, and integration owners out of the design conversation.
• Project teams prove journal posting and reporting but do not prove fund receipt within the new timing rule.
• Buyers let vendors say "supported" without making them name the exact payroll product, clearing-house model, or SuperStream path.
• Teams underestimate the operational impact of losing the SBSCH at the same time the new rule starts on 1 July 2026.

What Australian buyers should conclude now

• Payday Super is one of the most immediate Australia-specific ERP risk topics on the market because it combines a hard compliance date with practical architecture and process consequences.
• Business Central, NetSuite, and Odoo buyers should all resist the same mistake: assuming the ERP brand answers the payroll and super operating-model question by itself.
• The best next step is a short readiness workshop with payroll, finance, implementation, and banking owners in one room. Do not ask whether the stack is "supported". Ask whether it can be demonstrated, reconciled, and recovered under pressure before 1 July 2026.

FAQ

• When does Payday Super start? The ATO says the new requirement starts on 1 July 2026.
• What is the most important timing rule? The contribution must be paid on payday and received by the super fund within 7 business days, unless an extended timeframe applies.
• Why should ERP teams care if payroll is outsourced or handled in another system? Because the compliance obligation still depends on joined-up data, payment execution, reconciliation, and exception handling across payroll, ERP, banking, and any intermediary.
• Is this only a small-business issue? No. The SBSCH closure is one visible trigger for smaller employers, but the design risk around qualifying earnings, payment frequency, and fund receipt applies more broadly.

Sources used

• ATO Software Developers Payday Super page for the 1 July 2026 start date, qualifying earnings, and the 7-business-day receipt requirement.
• ATO Small Business Superannuation Clearing House page for the 30 June 2026 final-use timing and 1 July 2026 closure.
• Microsoft Learn Import payroll transactions article for Business Central payroll-provider import workflow.
• Oracle NetSuite documentation for SuitePeople U.S. Payroll scope and Paycheck Journal support for external payroll solutions.
• Odoo 19.0 Australia payroll documentation for STP Phase 2 and SuperStream status plus preparation for more frequent super processing.