Quick answer
Open the Feed Console in Class Super and read the status against the affected feed — it tells you exactly which stage it's stuck at. If the authority hasn't been signed or the feed dropped, send or reauthorise the authority (and confirm any adviser is linked). After that, a feed can take up to around 10 business days to start loading, because the bank, broker or platform sets it up on their side.
WHY IT HAPPENS
It's the authority, not the software.
A Class Super data feed is a standing arrangement with a third party — a bank, broker, or wrap/platform provider — to send transactions automatically. When one stops, the software is rarely at fault; the authorisation behind the feed is what's broken. Common causes: the authority form was never signed and returned by the account holders, an adviser-authorised feed isn't linked to an adviser in Class, or the provider revoked or let the authority lapse. And because the provider controls the feed at their end, even a correct reauthorisation takes time to take effect — so some "not updating" cases are simply a normal provider-side delay.
THE FIX
Work through these in order.
- Read the status in the Feed ConsoleOpen the Feed Console in Class Super and check the status against the affected feed. Statuses such as "waiting on authoriser" or an error state tell you whether the feed is mid-setup, waiting on a signature, or genuinely broken — start from there rather than guessing.
- Confirm the authority form was signed and returnedIf the status is "waiting on authoriser", the authority form needs to reach the account holders and come back signed. Send it, and update the status once it's out so Class knows the request is in progress.
- Check the adviser is set and linkedFor a feed authorised via a third party (adviser), make sure the adviser exists as a contact in Class with the adviser role, the correct adviser code is entered against the product, and the adviser is actually linked to the feed. A missing link silently stops the feed.
- Reauthorise a dropped feedIf a feed that was working has stopped, the authority may have lapsed or been revoked at the provider. Reauthorise it through Class following the process for that feed type, then allow time for it to re-establish.
- Give it time to loadAfter a new or reauthorised feed is approved, transactions generally begin importing automatically within about 10 business days. Don't reauthorise repeatedly during this window — that can reset the clock.
- Check for a provider-side or feed outageIf several funds using the same bank or broker are all missing data, it's likely an issue at that provider or with the feed service rather than your setup. Check Class's status page for any reported feed incident.
- Contact the feed providerIf the authority is clearly in place and the normal lead time has well passed, the hold-up is on the provider's side. Contact the bank, broker or platform (or Class Support for guidance) to have them investigate and re-establish the feed.
Feeds are a workflow, not a switch. Because every SMSF data feed depends on a signed authority and a third party actioning it, the fastest fix is knowing precisely which stage each feed is stuck at and chasing that one thing. If your practice is regularly losing feeds across many funds, that's usually a process or account-setup gap worth reviewing rather than fighting fund by fund.
