The Small Business Superannuation Clearing House closes permanently at 11:59 pm AEST on 30 June 2026. Five weeks from now.
Most of the closure guides circulating right now are written for employers in general. They tell you the SBSCH is closing, list the alternatives, and remind you to download your records. Useful enough if you run a small business with five employees. Less useful if you run an SMSF administration practice with 400 funds on your book.
We work with accounting firms across Australia who handle SMSF admin, and the SBSCH closure has come up in pretty much every conversation we've had this month. The questions they're asking aren't the ones the generic articles answer. So here's what we're actually telling them this week.
The bit you already know
The SBSCH closes 30 June 2026, part of the Payday Super reforms. The ATO recommended that the January-March 2026 quarter (paid by 28 April) be the last quarter employers use the service. After that, employers need a SuperStream-compliant alternative, usually their existing payroll software's built-in clearing house (Xero, MYOB, Reckon), a commercial clearing house like Wrkr or Beam, or their default super fund's clearing house.
That part is in every article on this. The harder problems are below.
Member verification: the thing nobody's talking about yet
Under Payday Super, the first time an employer contributes to a fund, they have to run a Member Verification Service (MVS) request through their electronic service address (ESA) to confirm the fund's details and the member's details are correct. Deloitte SMSF partner Liz Westover raised this at The Tax Institute Super Intensive event in March: it's still not fully clear what action SMSF administrators need to take when one of these verification requests lands.
What it means in practice for your firm is more straightforward. If your ESA receives an MVS request for one of your funds, someone needs to be monitoring that mailbox and responding promptly. If you don't, the contribution can't go through on time, the employer cops the Super Guarantee Charge, and your client (or your client's client) is going to want to know why.
Ask your admin software provider (Class, BGL, Supermate, MyWorkpapers) three things this week. How are MVS requests handled? Who in our firm gets the notification? What's the expected turnaround? If those answers aren't crisp, that's the gap you're working on between now and 1 July.
NPP-compliant bank accounts
Daniel Butler at DBA Lawyers flagged the second operational risk in a recent SMSF Adviser piece. Under Payday Super, contributions need to reach the fund within seven business days of payday. That means SMSFs need bank accounts capable of receiving payments through the New Payments Platform.
Most major bank accounts are NPP-compliant by default these days. The trap is the edge cases. Older legacy SMSF accounts with smaller banks. Specific savings products that don't support NPP. And the one that catches people out: a trustee changing the fund's bank account mid-cycle without telling you. Butler points out that there are around 244,000 SMSFs receiving SG contributions for roughly 366,000 employees. For each of those funds, a bank account change is a small operational matter for the trustee. For the employer contributing into it, it's a Super Guarantee Charge waiting to happen.
Pull your client list this week. Check the bank account on file for every SG-receiving SMSF. Confirm NPP compliance with the bank if you're not certain. Start with funds where the trustee runs their own business and contributes from it. That's where a bounced payment turns into a self-inflicted wound for one of your clients.
The lodgement backlog (still the highest-leverage clean-up)
If a fund's annual return is outstanding, "regulation details removed" appears on Super Fund Lookup. When that happens, the employer can't make a compliant contribution. The ATO has been explicit about this, and Westover hit the same point at the Tax Institute event.
Under the old quarterly model, a fund popping up on the Lookup with regulation details removed was a problem you could untangle over a few weeks. Under Payday Super, with a seven-business-day window, it's a hard fail every single pay run. Every fortnight, the employer is on the hook again.
The single highest-leverage piece of work an SMSF admin firm can do in the next four weeks is run a report across your book to identify any funds with outstanding annual returns, prioritise the ones receiving employer contributions, and get them lodged before the end of June. Nothing else on this list will save you more pain.
SBSCH records: your employer clients are going to forget
This one's less SMSF-specific, but worth flagging because employer clients have a habit of forgetting administrative cleanup until they need something from a system that no longer exists.
After 30 June 2026, the SBSCH portal goes offline. No login, no record retrieval. If your firm handles bookkeeping for clients who currently use the SBSCH, this week is the right time to log in, go to the Payment Instruction tab and the Historical tab, and pull down the full transaction history. Those records will be needed for audit responses, ATO queries, and employee questions for years to come. The ATO has published a checklist for this.
What we keep finding when we sit with admin firms
Most SMSF admin firms are operationally fine with this transition, at least on paper. The software providers are mostly ready. The banks mostly support NPP. The lodgement backlog is mostly manageable on a per-fund basis.
What we keep finding is a visibility problem. When you've got 200 or 500 or 800 funds on your book, knowing which ones have a stale bank account, which ones have a 2024 lodgement query still open, which ones are receiving contributions from employer clients who are also clients of your firm. That information lives in different places. Some of it is in Class or BGL. Some of it is in spreadsheets the team built two years ago. Some of it lives in the partner's head.
Building a single view across all four risks above is the work most firms haven't done. With it, 1 July becomes a checklist. Without it, the first week of July becomes a triage exercise: bounced contributions you could have prevented, employer clients calling because their payroll software threw an error, and your team scrambling to figure out which fund is which.
This kind of operational visibility gap is similar to what we wrote about in our piece on Privacy Act AI compliance for accounting firms. The information exists inside the firm, but it's not in one place where someone can act on it quickly.
What we'd actually do this week if it were our firm
Day one, run the audit: lodgement status, bank account status, MVS process, SBSCH records. Get it onto one page even if the page is ugly.
Lodgement clean-up is the work that has to happen now, because the ATO doesn't move quickly and a return lodged on 28 June won't help you on 1 July.
Bank account verification can happen in parallel. Most of it is desk work and phone calls.
Around the 16th of June, send a one-page summary to your employer clients. What's changing, what they need to do, what you're handling for them. We've watched this single piece of communication cut hundreds of inbound emails out of July.
The final week is for SBSCH record downloads and making sure your alternative clearing house arrangements are live, tested, and known to the people who need to know.
Where we help
We build systems for accounting and SMSF firms, the kind of work that turns "the partner remembers" into "the system tells you." The visibility problem we described above is the type of thing we help firms solve, usually by pulling data from Class or BGL into a single picture alongside lodgement status, bank account checks, and employer contribution flows.
If your firm is looking at the next five weeks and the picture isn't clean, get in touch. Happy to walk through what we've seen work.
