Reconcile Payday Super in Xero and MYOB: Australian Guide

From 1 July 2026, super guarantee is paid on payday at the same time as wages, and the contribution must arrive in the employee's super fund within 7 business days. The SG base changes from Ordinary Time Earnings to Qualifying Earnings on the same date, and the ATO's Small Business Superannuation Clearing House closes to all users on 30 June 2026. The ATO guidance on Payday Super is direct on the arrival rule: "From 1 July 2026, an employer's super guarantee must be paid on payday at the same time as salary and wages, and the contribution must be received by the employee's super fund within 7 business days (unless an extended timeframe applies, such as for new employees)."

The reconciliation that used to be a quarterly tidy-up becomes a per-pay-cycle three-way match. Three artefacts have to agree, every cycle: the STP-reported super amount the employer told the ATO they were paying for that pay event, the SuperStream contribution confirmation that comes back from the clearing house line by line, and the bank-account debit that takes the cash out of the employer's account. When those three numbers tie, the cycle is reconciled. When they do not, the bookkeeper has until day 7 to find out why.

This guide shows how to reconcile payday super in Xero and MYOB cycle by cycle — naming the artefacts, walking the checks, mapping the 7-business-day calendar onto realistic detection points, and treating the SBSCH cutover as the precondition rather than a side note. Australian bookkeepers and BAS agents already running parallel compliance rhythms — STP lodgement, BAS preparation, TPAR — will recognise the cadence; the difference is the window. A late BAS is a lodgement issue; a late super contribution is Superannuation Guarantee Charge (SGC) territory from day 8, regardless of any transitional ATO posture, so detection has to live inside the week, not after it.

The workflow below is software-neutral. Xero auto-super and MYOB Pay Super are described in the same shape because the reconciliation problem is the same; bookkeepers running clients on either platform — or working alongside Xero accountants preparing BAS in Xero for Australian businesses while owning the super side themselves — should recognise their own cycle in the steps that follow.

---

Qualifying Earnings Replaces Ordinary Time Earnings

The SG base changes on 1 July 2026. Qualifying Earnings replaces Ordinary Time Earnings as the figure on which super guarantee is calculated, and the practical effect on most pay runs is that the SG amount goes up because the base is broader. QE pulls in categories of pay that sat outside OTE — most notably paid leave loading and several allowance categories that were previously excluded — and applies the SG rate to the larger base.

For a typical AU pay run with a mix of ordinary hours, leave loading on annual leave, and a uniform or tool allowance, the SG amount under QE will be larger than the OTE-based amount the same pay run would have produced before 1 July 2026. The size of the gap depends on the employee's mix of pay components and on whether each allowance is expense-related or remuneration-related under the legislation — for edge cases, the ATO and the relevant award text govern, not the payroll software's default mapping.

The reconciliation consequence is direct. The SG amount on the pay-run report is what gets reported through STP and lodged through the clearing house. If the payroll module is still calculating SG on OTE on the first pay run dated on or after 1 July 2026, the number that flows into the SuperStream contribution batch is short. SuperStream confirms what was paid; STP reports what was reported; neither catches the underlying calculation error against the QE base. The bookkeeper catches it by checking the SG calculation on cycle one against the QE rules, not by relying on the reconciliation alone.

Both Xero and MYOB are updating their payroll modules to switch SG calculation to QE for pay runs dated on or after 1 July 2026. Three checks belong on the first post-cutover pay run: the software has applied the QE base rather than OTE, allowances and leave components are categorised correctly inside the SG calculation, and the SG amount on the pay-run report reflects QE before STP submission. None of those checks are exotic — they are line-item verification of what payroll already produces — but skipping them is how a calculation error compounds across an entire compliance year before anyone notices.

The cleanup risk is asymmetric. A small per-employee underpayment per cycle, multiplied by every cycle for a year, is exactly the shape of an SGC bill that arrives long after the relevant pay runs have been finalised and reported. Catching it on cycle one is the cheapest fix; catching it at year end is not.

---

The Three Artefacts of Payday Super Reconciliation

Three artefacts answer three different questions about the same pay event. Holding them apart in your head — by source, by data point, and by the question each one settles — is what makes the per-cycle reconciliation tractable rather than a swirl of reports and bank lines.

The STP pay event report answers what the employer told the ATO they were paying for that cycle. It is generated when the pay run is finalised and lodged through Single Touch Payroll Phase 2 (STP Phase 2), and it carries the super-guarantee amount per employee for that pay event. Because STP Phase 2 already itemises super amounts at the pay-event level, the reconciliation does not need a second source for the reported figure — it is on file by lodgement. The reconciliation question against STP is whether the amount STP reported per employee matches the amount that was actually paid through SuperStream and accepted by the destination fund.

The SuperStream contribution confirmation file answers what the clearing house, and ultimately each destination super fund, accepted. Clearing houses respond per line, identifying each contribution by member account and Unique Superannuation Identifier (USI), with an acceptance code attached. A line can be accepted (the fund credited the member's account for the full amount), rejected (the contribution could not be allocated and the funds return to the employer), or partially handled (employer-fund routing data is corrected and the contribution is re-routed). The data points the reconciliation pulls from the SuperStream response are the per-employee accepted amount, the destination USI, and any rejection codes for lines that did not land cleanly.

The bank-account debit answers what cash actually left the employer's account. When the employer lodges a contribution batch through Xero auto-super or MYOB Pay Super, the platform debits the employer's bank account for the batch total. In most configurations that debit appears as a single per-cycle line on the bank statement, not as one debit per employee — useful for matching the batch total, less useful for matching per-employee detail. Reconciling the bank debit against per-employee figures requires the SuperStream contribution confirmation as the bridge, because the bank line itself does not break down by member. Bookkeepers used to working with bank statements outside the bank feed — for example, importing bank statements into MYOB for clients on monthly statements rather than live feeds — should expect the same per-cycle batch debit line, just arriving on a different cadence.

The test the cycle has to pass is plain. STP-reported super total, SuperStream-confirmed accepted total, and the bank-account debit value should agree per pay cycle, with no employees on the pay run unaccounted for in the SuperStream response. When all three tie and every employee is represented, the cycle is reconciled. When they do not, the source of the disagreement — calculation difference, fund-side rejection, missing line, late confirmation — is what the reconciliation has surfaced, and the bookkeeper has the rest of the 7-business-day window to act on it.

---

Walking One Reconciliation Pass in Xero and MYOB

A single cycle moves through the same sequence regardless of which payroll platform you are running. Finalise the pay run. Submit STP. Lodge the contribution batch through Xero auto-super or MYOB Pay Super. Watch the bank debit clear. Monitor the SuperStream confirmation responses arriving over the following 1–7 business days. Reconcile each confirmed line against the STP-reported amount per employee. Reconcile the bank debit against the batch total. The whole loop is what the cycle has to complete inside the 7-business-day window — and the steps below are how it lands in each platform's interface.

In Xero auto-super, the contribution batch screen shows pending, accepted, and rejected statuses per employee as the SuperStream responses arrive, with each line tied to its destination fund and member account. The bank debit appears on the bank feed when reconciliation runs against the connected bank account. The reconciliation surfaces are inside Xero: the batch screen, the auto-super history, and the bank-feed reconciliation against the contribution batch.

In MYOB Pay Super, the equivalent surfaces are the Pay Super dashboard with batch status, the response file with per-employee acceptance, and the corresponding bank-feed entry against the connected bank account. The shape is the same — batch status, per-line response, batch-total bank line — even though the screens and the file naming differ from Xero. Both products are updating their auto-super and Pay Super surfaces ahead of 1 July 2026; what each surfaces today is what the bookkeeper works with on cycle one of the new regime, not whatever is on a roadmap slide.

The three reconciliation checks per cycle are operational and fast to articulate, even when the cases that fail them are not.

• Check 1. STP-reported super per employee equals SuperStream-confirmed accepted amount per employee. The pair has to tie at the employee level, not just at the batch total — a $200 over-allocation to one employee balanced by a $200 under-allocation to another nets to zero in the bank line but leaves one employee underpaid and the other over-contributed, with separate corrections needed for each.
• Check 2. SuperStream-confirmed batch total equals the bank-debit value. When the batch total clears as a single bank line, this is a one-to-one match. When the bank debit is smaller than the batch total, one or more lines were rejected at the fund and the rejected amount returned to the employer's account.
• Check 3. Every employee on the pay run has a corresponding accepted SuperStream line. Missing employees are the silent failure mode — the kind that hides until year-end and produces SGC liability for whichever employees were quietly skipped.

When a check fails, the resolution is specific to the failure pattern. STP says one number, SuperStream confirms a different number is most often a fund-side partial acceptance or an employee-data correction the fund applied to allocate the contribution; resolve before the 7-business-day window closes by submitting a correction or a top-up payment to make up the difference. Bank debit smaller than the batch total is a rejected-line scenario — the rejected amount is back in the employer's account, but the SG obligation persists for the employees whose lines bounced, so a re-lodgement to a corrected destination is required inside the same window. An employee on the pay run with no SuperStream line is either a contribution-batch data-entry error (the employee was excluded from the batch when it was generated) or a silent rejection that did not surface as a clean rejected-line response; either way, the line has to be reconstructed and lodged before day 7.

For a small employer with a handful of employees, the native Xero or MYOB reconciliation report and a quick visual scan covers the workflow without any additional tooling. As employee count grows — twenty, fifty, two hundred — visual scanning across the SuperStream response file, the STP-reported super amounts, and the bank statement stops being reliable. A rejected line in row 87 of a 200-line batch is exactly the kind of detail a tired bookkeeper running a Friday-afternoon reconciliation does not catch by eye, and it is exactly the kind of detail that matures into SGC liability if it does not get caught in time.

This is where document extraction earns its place. Per-employee SuperStream confirmation lines, STP-reported amounts, and bank-statement debit lines pulled into one reconcilable spreadsheet via a single prompt — destination USI, accepted amount, rejection code, source file reference per row, one row per employee per cycle — is what our tool handles. Describe what you need, extract data from pay-run reports, clearing-house confirmations, and bank statements together at batch scale, and reconcile the structured output against the pay run rather than scanning three report layouts side by side. Bookkeepers who already run extracting payslip data for finance teams for the gross pay side will recognise the same workflow on the contribution side.

The same volume problem bites in a second context that catches employers off guard: mid-cutover from SBSCH. The new clearing house's contribution-confirmation file is often in a different shape from what Xero or MYOB expect to ingest natively, and the bookkeeper ends up reconciling against a CSV the payroll software does not parse for them. For the first few cycles after the cutover, even small employers can find themselves in the high-volume reconciliation pattern — not because they have many employees, but because the file they are reconciling against is not the one their software was built around.

---

The 7-Business-Day Window as a Calendar With Detection Checkpoints

Counting from payday, the window has shape. Day 1 is payday and contribution lodgement through Xero auto-super or MYOB Pay Super. Days 2 to 4 are NPP and BECS settlement of the bank debit and dispatch of the SuperStream payload from the clearing house out to the destination funds. Days 4 to 6 are fund-side acceptance and the SuperStream confirmation responses returning to the clearing house. Day 7 is the latest day on which the contribution can arrive in the employee's super fund and remain compliant. Day 8 is the cliff: the contribution is late, and SGC obligations begin to attach.

Within that window, three checkpoints catch most of what goes wrong, and each one ties to one of the three artefacts.

• Day 2 to 3 — bank debit cleared? The first signal that something is off is usually the bank line. If the bank debit has not cleared for the full batch total within the first couple of business days after lodgement, the contribution batch may have failed at the clearing house's end before it ever reached the funds. This is not a wait-and-see situation; it is a same-day call to the clearing house, because every day spent waiting is a day closer to day 8 with no SuperStream response yet in the pipe.
• Day 4 to 5 — SuperStream confirmations arriving? By day 5, the bulk of the SuperStream confirmation responses for the batch should have come back. When they have not, the bookkeeper escalates with the clearing house rather than waiting for day 6. Late confirmations are not the same problem as rejected lines, but they consume the remaining buffer at the same rate.
• Day 6 — any rejected lines? This is the last clean checkpoint before the window closes. Rejected amounts are returned to the employer's bank account, but the SG obligation persists for the original employee, so a rejected line on day 6 means a re-lodgement to a corrected destination is needed before day 7. Day 6 is when the bookkeeper goes through the contribution-confirmation file line by line — or against the structured per-employee output if the cycle warrants it — and confirms there are no surprises sitting in the response that have not been actioned.

The failure modes worth recognising on sight are the ones that recur cycle after cycle. Invalid USI — the destination fund identifier is wrong or out of date, often because of a fund merger that has not been reflected in the employee's nominated fund record; the line is rejected and needs re-lodgement to the correct USI. Fund-side member-data mismatch — the member's name, date of birth, or member account number on the contribution does not match what the fund holds, so the fund cannot allocate the payment cleanly. New-employee TFN or data error — incomplete onboarding data sends the contribution out with a missing or incorrect TFN, and the destination fund either rejects the line or holds it pending. Account closed — the employee has rolled their super to a new fund, and the destination account at the original fund is no longer active. Fund merger — the destination fund itself has been absorbed by another fund and the previously valid USI is no longer routable.

Tripping into day 8 is what the cycle is built to avoid. SGC is the unfavourable outcome stack: the SG amount itself, plus nominal interest accrued from day 1 of the missed period, plus an administration fee, payable to the ATO rather than to the employee's super fund, and not tax-deductible to the employer. The cash cost is the SG amount the employer owed in the first place; the additional cost is the interest and fee on top; the structural cost is that SGC is non-deductible, so the after-tax burden is materially larger than the pre-tax SG amount it replaces. The bookkeeper's incentive — and the reason the day-3, day-5, day-6 detection rhythm exists — is to keep every line out of that stack.

The ATO names a narrow exception — extended timeframes apply in defined circumstances such as new employees inside their onboarding window. The default is the 7-business-day rule, and the workflow has to be designed against the default, not the exception.

---

Migrating From SBSCH Before 30 June 2026

The Small Business Superannuation Clearing House closed to new users on 1 October 2025. Existing users have access until 30 June 2026. From 1 July 2026 it is gone. Every employer currently lodging contributions through SBSCH — typically those under 19 employees or under $10 million in turnover — has to complete a migration to a commercial clearing-house alternative before that date. There is no extension and no equivalent free ATO replacement.

The migration work is mostly data work, because commercial clearing houses ask for things SBSCH did not require. Three differences shape the cutover.

• Fund identification by USI rather than name. SBSCH allowed employers to nominate funds by fund name, with the clearing house resolving the routing internally. Commercial clearing houses require a Unique Superannuation Identifier (USI) per fund per employee. Every active employee's nominated super fund needs a confirmed USI captured in the payroll record before the first cycle through the new clearing house.
• Higher employee data quality bar. SBSCH was relatively forgiving on incomplete employee data. Commercial clearing houses enforce a higher bar on TFN, date of birth, address, and member account number, because their downstream funds reject contributions where the member-allocation data is incomplete. Gaps in the employee record that did not bite under SBSCH will surface as rejections under the new clearing house.
• SuperStream-compliant contribution-batch file. SBSCH accepted relatively simple employer-side input. Commercial clearing houses ingest a SuperStream-compliant contribution-batch file — the SAFF (SuperStream Alternative File Format) payload — generated by the payroll software. Confirming that Xero or MYOB is producing the payload format the new clearing house expects is part of the cutover, not an afterthought.

The practical alternatives the SBSCH-migrating employer is choosing between fall into three groups.

Built into payroll. Xero auto-super (built into Xero Payroll, with lodgement and reconciliation in the same surface) and MYOB Pay Super (built into MYOB payroll, with the same single-surface arrangement) keep the contribution lodgement, the SuperStream response, and the bank reconciliation inside the payroll product the bookkeeper is already in. For employers running payroll on Xero or MYOB, this is usually the path of least friction.

Independent clearing houses. ClickSuper and SuperChoice operate independently of any single payroll product and integrate with multiple payroll platforms. They suit employers running payroll in something other than Xero or MYOB, or organisations that prefer to keep the clearing-house relationship separate from the payroll vendor. The lodgement and reconciliation surfaces sit outside payroll, which is an additional swivel-chair for the bookkeeper but a cleaner separation of concerns for larger employers.

Fund-direct portals. Some employers — typically those whose workforce is concentrated in one or two super funds — route contributions directly through a single fund's employer portal. This works narrowly. It is rarely the right answer when employees have varied fund choices, because the employer ends up needing portal access at every fund the workforce nominates and reconciliation fragments across multiple sources.

The cutover checklist the bookkeeper actually runs is short, but each item earns its place. Capture the USI for every employee's nominated super fund, sourced from the employee or from the fund's employer-services page. Verify TFN, date of birth, address, and member account number for every active employee. Confirm Xero or MYOB is configured for the chosen clearing house and that contribution batches generate as a SuperStream-compliant payload in the format the new clearing house ingests. Run a dry pay cycle through the new clearing house ahead of 1 July 2026 — even if it means lodging an unusually small or test batch — so any data-quality failures surface against a small amount before they surface against a real fortnightly contribution.

The reconciliation impact for the first few cycles after cutover is real and worth budgeting for. The new clearing house's contribution-confirmation file is likely to be in a different shape from the SBSCH equivalent, and the per-employee data that flowed cleanly back through SBSCH may need to be extracted from a CSV or report file the new clearing house produces and reconciled against the STP report and bank debit manually until the bookkeeper learns the new file format. The volume scaling problem from the prior section bites soonest here: a 12-employee batch through an unfamiliar clearing-house response file behaves more like a 50-employee batch through a familiar one, just for the first few cycles.

---

The ATO's First-Year Posture: Transitional, Not a Grace Period

The ATO has signalled a supportive, light-touch approach to enforcement for the first 12 months from 1 July 2026, for employers genuinely working to comply with payday super. From 1 July 2027, full enforcement applies. Both halves of that statement matter, and reading only the first half is how employers end up surprised later.

The transitional posture is recognition that payroll systems, clearing-house cutovers, and employer processes need a transition period in a structural reform of this size. It is not a 12-month grace period on the SG obligation itself. The legislation is in force from day one. SGC liability still attaches to late contributions. Nominal interest still accrues from day 8 of any missed cycle, not from day 8 of July 2027. The "light touch" applies to penalties stacked on top of SGC — administrative penalties, director penalties in serious cases, the way the ATO treats first-time inadvertent failures — not to the underlying superannuation guarantee.

Operate as if the regime is fully enforced from 1 July 2026, because the operational rhythm has to be in place by then anyway. Build the per-cycle reconciliation workflow now. Build the day-3, day-5, day-6 detection rhythm into the bookkeeping calendar now. Complete the SBSCH cutover before 30 June 2026 rather than over the first few cycles after. Verify the QE calculation on the first post-cutover pay run rather than a quarter in. The first 12 months is the cheapest time to surface data and process problems, because the ATO's posture rewards employers visibly working the regime correctly. It is not the cheapest time to skip the work; it is the cheapest time to do the work and get caught learning.

The economics for the employee do not change with the ATO's posture either. An employee whose super arrives late still loses contribution timing and the compounding that goes with it, regardless of whether the ATO imposes secondary penalties on top of SGC. SGC, when it does apply, is paid to the ATO rather than to the employee's super fund and is not tax-deductible to the employer — so the cost to the employer of a missed contribution is materially larger than the cost of the contribution itself, and the cost to the employee is the contribution arriving in the wrong place via SGC reconciliation, which is a slower and lower-quality path than a clean SuperStream credit. The bookkeeper's reconciliation job is the same whether the first-year posture is in play or not.

The broader compliance calendar reinforces the same instinct. Practitioners running Australia's TPAR contractor reporting requirements alongside BAS lodgement and now per-cycle super reconciliation will recognise the pattern. Transitional postures across any of these regimes favour the employer who built the workflow correctly from the start, not the employer who waited to see how strict enforcement would actually be. The transitional posture changes how the ATO reads enforcement edge cases in the first year; it does not change the reconciliation rhythm the bookkeeper runs every cycle.