Available for the following plans: Standard, Premium
Available for the following User Access levels: Admin
The SuperStream system requires employers to verify that an employee's details match the records held by their superannuation fund before super contributions can be processed. To fulfil this requirement automatically, the platform utilises an automated background verification system that processes requests and displays results across different stages of payroll management.
This article will show you how to manage the following:
- Review verification statuses on employee records
- Identify issues via dashboard alerts
- Track pay run verification warnings
- Further information
Review verification statuses on employee records
The Member Verification Request (MVR) process transmits an automated background query to an external Member Verification Service (MVS) whenever relevant details change. No manual submission is required.
The automated verification process initiates when you complete any of the following actions:
- Add a new superannuation fund for an employee through administrative data entry or employee self-onboarding.
- Change an existing employee selection to a different superannuation fund.
- Update core identity fields including legal name, date of birth, or Tax File Number (TFN).
- Modify any of the core identity fields via an Application Programming Interface (API) request.
- Import employee data records using a Comma-Separated Values (CSV) data template that contains superannuation fund details.
When any of these modifications occur, the affected superannuation fund status resets to a Pending state immediately while the platform processes the automated verification request. Each superannuation fund displays an independent status badge on the employee profile. If an employee maintains allocations across multiple funds, the system verifies and displays each status independently.
The table below lists each super fund verification status badge, its definition and its badge colour.
| Status Badge | Factual Definition | Badge Colour |
| Pending | The verification request has been transmitted and the platform awaits response data from the superannuation fund. | Yellow |
| Verified | The superannuation fund has confirmed that the submitted employee identity details correspond with their internal database records. | Green |
| Failed | The superannuation fund membership verification failed, and we cannot confirm an identity match or process allocations. | Red |
| Incomplete | The superannuation fund did not respond after three communication attempts, resulting in a system timeout. | Red |
| Not Applicable | The designated superannuation fund does not support or require the automated verification process. | Grey |
Helpful Hint
A Failed status displays two specific descriptions within its corresponding user interface tooltip to assist with troubleshooting. A "Details do not match the fund" description requires you or the employee to correct the name, date of birth, or TFN. A "Fund cannot accept contributions" description indicates a structural fund issue, requiring the employee to contact their provider or select an alternative superannuation fund.
Identify issues via dashboard alerts
The platform summarises unresolved verification issues on the main payroll dashboard to ensure visibility before processing payments.
The dashboard notification follows specific operational parameters:
- The alert triggers only when an employee records a fund status of Failed or Incomplete. Employees with fully Verified or Not Applicable records do not generate an alert.
- The system groups alerts by distinct employee records rather than individual fund records. An employee with multiple failing funds still represents a single count within the dashboard notification text string, which displays as "{X} employee(s) have super fund verification issues".
- Clicking the action item expands the data display inline directly on the active dashboard screen to reveal the affected employee names and their exact statuses. This interaction does not redirect you away from the active screen view.
- If all employee superannuation records within the organisation return Verified or Not Applicable statuses, the dashboard notification not display.
Helpful Hint
Dashboard alerts serve an informational purpose to draw attention to data mismatches. They do not introduce operational blocks or restrict your ability to execute other payroll tasks on the platform.
Track pay run verification warnings
When you initialise or compile a pay run that includes any employee with a non-passing status, a contextual notification displays in the warnings section of that specific pay run.
The table below lists the system status for each failed verification and the exact warning text shown on the pay run.
| System Status | Exact Pay Run Warning Text |
| Failed - details do not match | "Super fund verification failed - employee details don't match fund records. Contributions may be rejected." |
| Failed - fund-level issue | "Super fund verification failed - fund cannot accept contributions. Employee may need to change funds." |
| Incomplete | "Super fund verification timed out after 3 attempts. Contributions may be rejected." |
The pay run warning interface follows specific behavioral rules:
- The system generates warnings on a per-fund basis rather than a per-employee basis. If an employee splits allocations across two funds and only one fund records an issue, exactly one warning appears for that employee.
- Funds maintaining a status of Verified, Not Applicable, or those completely lacking a historical verification record never generate a pay run warning message.
Helpful Hint
These warning messages are completely non-blocking. You can finalise the pay run normally even when warnings are active in the system panel. The messages function purely as an informational notice regarding potential downstream contribution rejection by the fund.
Further information
What should you do when a fund remains in a Pending status?
A Pending status means the automated background query is currently awaiting data from the external superannuation fund. No administrative actions or manual follow-up steps are required during this period.
What is the operational cause of an Incomplete status?
An Incomplete status indicates that the superannuation fund did not return a response payload within three successive attempts, causing a communication timeout. This status does not signify an error in the employee core identity data fields.
Does an unresolved or failing status prevent you from completing a pay run or contribution batch?
No. The dashboard notifications and pay run warnings function strictly as informational visibility flags. They do not block the finalisation of active pay runs or prevent the inclusion of contributions within a superannuation batch workflow. Unresolved verifications are handled at the superannuation batch level in a separate operational framework.