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's Payday Super guidance for software developers says super guarantee must be paid on payday from 1 July 2026, calculated as 12% of qualifying earnings, and received by the employee's super fund within 7 business days unless an extended timeframe applies.

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 walks the Xero and MYOB pay-cycle reconciliation: STP-reported super, SuperStream confirmation, bank debit, 7-business-day checkpoints, and SBSCH migration before 30 June 2026.

---

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.

On the first post-cutover pay run, verify that Xero or MYOB is using QE, that allowances and leave components are categorised correctly, and that the SG amount is correct before STP submission.

---

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.

That makes payday super narrower than a full payroll-to-ledger review. The broader controls in a payroll reconciliation guide still matter, but this workflow adds fund-arrival evidence and a per-employee SuperStream match inside the 7-business-day window.

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.

At higher employee counts, pull the STP amounts, SuperStream confirmation lines and bank debit into one spreadsheet before matching. With data extraction for pay-run reports, clearing-house confirmations and bank statements, one row per employee per cycle can carry the USI, accepted amount, rejection code and source-file reference, which is easier to reconcile than scanning three report layouts side by side.

---

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 recurring failure modes are simple to name: an invalid USI after a fund merger, a member-data mismatch, a missing TFN or onboarding field, a closed member account, or an employee left out of the batch. Each one needs the same response: fix the data, re-lodge the affected line, and confirm acceptance before day 7.

Tripping into day 8 is what the cycle is built to avoid. SGC brings the missed SG amount, nominal interest, an administration fee, payment to the ATO rather than directly to the employee's fund, and no employer tax deduction. The ATO's first-year supportive posture is not a grace period on the obligation itself; the reconciliation rhythm still has to keep every line out of the SGC 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.

Expect the first few cycles after SBSCH migration to take longer: the new clearing house's confirmation file may not match the format Xero or MYOB ingests natively, so reconcile the CSV or report file against STP and the bank debit until the new response format is familiar.