We Built a SuperStream File Converter. Here's the Gap That Made Us Do It.
We Built a SuperStream File Converter. Here's the Gap That Made Us Do It.
The ATO's free clearing house closes for good on 30 June. Here's the problem we kept seeing in the NDIS and NFP space — and why "buy better payroll software" wasn't always the right answer.
Every employer in Australia has to pay superannuation through a SuperStream-compliant channel. For years, the easiest on-ramp for small employers was the ATO's Small Business Superannuation Clearing House (SBSCH) — free, simple, government-run, and good enough that a lot of organisations never had to think about super payment mechanics at all.
That free option closes permanently at 11:59pm AEST on 30 June 2026, the night before Payday Super begins. I've written about the Payday Super transition itself a few times on this blog. This post is about a narrower, more practical problem that kept landing on my desk while I was helping organisations think through that transition — and what we ended up building because of it.
|
30 June
SBSCH closes permanently at 11:59pm AEST — no extensions, no late access to records.
|
3
Common situations we kept seeing where "just use your payroll software" wasn't a real answer.
|
The Problem We Kept Running Into
If you're already running Xero, MYOB, or KeyPay, the SBSCH closure is mostly a non-event. Those platforms generate SuperStream-compliant SAFF (SuperStream Alternative File Format) files natively and send them straight to a clearing house. For most mainstream payroll users, this whole post won't apply to you — and I'd rather say that upfront than waste your time.
But across NDIS and not-for-profit organisations specifically, I kept running into the same three situations, often within weeks of each other:
- No real payroll software at all. Smaller organisations running payroll out of spreadsheets, who relied on SBSCH precisely because it was the one part of the process simple enough not to need a system.
- A non-standard payroll source. ERPs like Microsoft Business Central handle payroll calculations fine but don't natively export SuperStream files — so a third-party module or manual workaround was needed every quarter.
- Multiple payroll sources to consolidate. Multi-site operators running different systems across locations (a common pattern in NDIS and aged care, where acquisitions and regional autonomy mean nobody standardised the back office), needing one combined SAFF file.
For these organisations, 30 June isn't a minor administrative inconvenience. It's a compliance cliff edge with no obvious next step — and "go and buy proper payroll software" is true in theory but rarely realistic inside a six-week runway, especially for organisations already absorbing Payday Super's cash flow shift.
Why Not Just Build a "Generator From Scratch"?
Our first instinct was to question whether this tool was even necessary, given how many payroll platforms already handle SuperStream natively. The honest answer is: for Xero, MYOB, and KeyPay users, it generally isn't — and we say that plainly on the product page itself, because we'd rather someone not sign up for something they don't need.
What was actually missing was narrower than a full payroll system: a converter and validator — something that takes whatever payroll export an organisation already has (a CSV, an Excel sheet, a Business Central report) and turns it into a compliant SAFF file, catching the kind of formatting errors that cause clearing house rejections before they're ever uploaded.
That reframing — bring your own export, we'll handle the format — became the actual product. It's a much smaller, more honest promise than "replace your payroll system," and it's the one that actually matched the gap we kept seeing.
What the SAFF Format Actually Demands
SuperStream files look deceptively simple — they're just CSVs — but the validation rules underneath are unforgiving. A few examples that caused most of the "rejected file" pain we'd heard about from clients over the years:
- No currency symbols or thousands separators in amount fields. Excel adds these by default, and they cause silent rejections.
- Exact date formats. A date saved by Excel can quietly reformat itself and break the entire file without any visible warning.
- ABN checksums. Every Australian Business Number has a built-in mathematical check digit, validated in real time.
- USI verification. A super fund's Unique Superannuation Identifier has to match a real, active fund registered with the ATO's Super Fund Lookup service.
- Different rules for SMSFs vs regulated funds. A Self-Managed Super Fund has no USI at all — it needs an ABN, an Electronic Service Address, and bank account details instead. Get the fund type wrong and the whole contribution fails.
Almost all of the rejected-file frustration I've seen from clients over the years comes down to exactly these kinds of small, avoidable errors — usually introduced by Excel reformatting something behind the scenes without anyone noticing. Catching them before upload, rather than after a clearing house bounces the file, is the entire value proposition.
Building It the Right Way, Not the Fast Way
A few decisions shaped how we approached this, and they're the ones I'd actually stand behind if you asked me to justify them.
Your payroll data never leaves your browser. Employee names, tax file numbers, contribution amounts — none of it touches our servers. All the CSV parsing, column mapping, and file generation happens client-side. The only thing we ever send externally is a fund's ABN or USI, purely to verify it's a real, active fund — never anything that identifies an employee.
A credit-based pricing model, not a flat subscription. We considered flat annual tiers first, but they create an obvious gaming problem — split a file into smaller pieces, dodge the limit. A credit model (one credit per employee per pay run) scales with actual usage and matches how the industry already prices comparable services.
Live validation against government data, not just format checking. Rather than only confirming a USI looks structurally correct, we check it against the ATO's Super Fund Lookup service in real time — so an employer finds out immediately if a fund has gone inactive, not after a clearing house rejects the whole batch.
A proper database for the things that actually need one. Credit balances and purchase history live with a full transaction log, so both the customer and we can see exactly when credits were purchased, used, or adjusted. If something needs a refund or correction, there's an audit trail rather than a black box.
Who This Is Actually For
We've been deliberate about not overselling this. If you're already on Xero, MYOB, or KeyPay, you probably don't need it. It's built for:
- Small employers who used SBSCH and now need a replacement before 30 June
- Organisations on systems that don't export SAFF directly — Business Central being a common one across the NDIS and NFP space
- Multi-site operators consolidating payroll from more than one source into a single compliant file
What's Next
The tool is live now, alongside a credit purchase flow, full transaction history, and the privacy-first architecture above. We're already thinking about what comes after it — a compliance-checking assistant for payroll teams, and eventually direct API integration with clearing houses for organisations that want a fully hands-off experience. Both are still on the drawing board. But building this taught us a lot about where the real friction actually sits in Australian payroll compliance, and that's where we want to keep building.
Comments
Post a Comment