This should be completed when making contributions to a fund for the first time.

The Australian Taxation Office (ATO) requires employers to use the MVR process once the relevant Maintenance Update has been applied.

Using MVR helps reduce contribution errors, minimises rejected payments, and lowers the administrative effort required to resolve issues.

An MVR is required for the following:

To avoid refunds the employers have 20 business days to pay contributions for new employees or when employee changes a fund.

An MVR is NOT required for the following:

An MVR must not be sent under the following circumstances:

If super contributions are delayed, the ATO may request evidence explaining the delay.

The MVR process can be used to demonstrate that verification steps were undertaken before payment.

Funds have a 24 hour turnaround on MVR responses.

After running the Super Fund Report, results will automatically be available in the Valid SuperFunds enquiry.

Users can create customised views by defining column sets. A wide range of filters and search options are available to refine results and minimise data output.

Super funds have until March 2027 to be fully compliant with MVR requirements. From 1 July 2026, MVR submissions can only be sent to super funds that are flagged as MVR-ready (Contributions Version 3) in the FVS.

If a super fund is not flagged as V3-ready, Ozedi will reject the MVR submission. This status is reflected in the Superfund Validation Report under the ‘Certification Details’ field. A value of CONT3.0 indicates that the fund is enabled to accept MVR transactions. Funds are not expected to update their certification status until on or after 1 July 2026.

COINS will only create an MVR record for funds that have the correct Certificate Details on the FVS.

All payroll security groups must be reviewed and updated to ensure that users are granted the appropriate access to support the new MVR process.

In Coins SureStart Payroll (version 12.05), security settings have been enhanced to accommodate this new functionality.

Organizations using SureStart standard security:

A support ticket must be raised to request the required updates to payroll security to enable MVR access.

Organizations with customised security configurations:

Internal updates will be required to align existing security settings with the new MVR functionality.

%WPR761BCOI

%WPR761BCOIL

%WPR762BCOI

%WPRMVR01

%WPRMVR02

%WPRMVR03

%WPRMVR04

This setting controls the database tables used for storing documents. It is mandatory to configure the table specified below to ensure that MVR files can be correctly stored against the employee record.

Document Management > Setup > Setup Maintenance > Document Management Links

Add table co_index

For sending data via MVR there are several fields that are mandatory.

Ensure all employee Home Address Details on employee maintenance are up to date and correct before enabling MVR.

Employee superannuation records on the employee pay calculations, the below rules must be applied.

A new data fix has been developed to update ALL existing employee records by marking them as MVR validated.

Do not send MVR’s for employees who have already had contributions paid.

Execution of this process requires Super Administrator privileges.

This data fix must be executed prior to enabling MVR in the LIVE environment.

This ensures that all existing records are appropriately flagged as MVR-enabled, while only new employee pay calculations will generate new MVR records going forward.

To run the process, navigate to System > System Setup >Data Fix Workbench and apply the filter:

%WSYX9288 – AUS update MVR flag for super for existing employee pay calc.

It is strongly recommended to execute the process in REPORT mode initially to review and validate the affected records prior to running the UPDATE mode.

Once you have verified the output run in Update mode.

This should be run before MVR parameter is set to Yes

This process updates all employee existing super records on employee pay calculations as MVR validated.

The data fix will not update employee pay calculation records that are currently on the MVR Workbench. Prior to executing this process in the LIVE environment, ensure that no MVR records existing on the Workbench.

A new payroll global parameter has been established to enable the MVR process.

By default, the parameter is set to NO, meaning MVR workbench is not enabled. As a result, the MVR workbench will not accept any actions on records and will generate an error.

User must enable the parameter (set to YES) only after the organisation has completed all required MVR configuration and the data fix has been applied to update all existing employee pay calculations. This ensures that only new pay calculations are sent to the MVR workbench.

Employee superannuation records are held on the Employee Maintenance > Pay calculations Tab. A new MVR flag will be displayed to indicate when a record has been successfully validated through the MVR process.

When a new pay calculation is ADDED for a New Employee, this will create an MVR record.

If employee changes funds, recommended to ADD a new record with new effective date and details this will also create an MVR record.

If an employee has requested to include additional contribution types i.e. pre-tax or post tax. The existing SUPG record will already have the MVR flag enabled.

It is recommended to COPY the SUPG record to create new contribution type as the USI and member ID will be the same. This will not create an MVR record.

However, if an employee elects to have the additional contributions sent to a different fund that will hold a different member ID and USI then this will create an MVR record.

When ADDING new Employee Pay Calculation:

When COPYING Employee Pay Calculations:

The new Member Verification Request Workbench can be found under the ATO Workbench Master in Payroll.

Payroll > ATO Workbench > MVR Tab

The MVR is only found on the Master ATO workbench as it is not pay frequency related.

Filters can be applied to reduce the visible data based on create date of a record or status.

A record will be created with PENDING status when a change has been made to the employee pay calculation for a superannuation pay code when adding new super records with new USI and/or member ID.

This process outlines how to submit employee records to superannuation funds for validation.

To successfully receive an MVR, the superannuation fund must be certified to support Contributions Version 3.0 (CONT3.0). The Fund Validation Service (FVS) can be used to confirm whether a fund is eligible to receive MVR submissions.

If an MVR is uploaded for a fund that is not certified, an error will be returned by Ozedi during the upload process.

Select employee records and apply the action ‘Upload MVR’.

Use the filters to reduce the visible data on the workbench.

This Action is available to update the status of SENT to UPLOAD_SEND_SUCCESS or FAILED

Only PENDING transactions can be CANCELLED.

The process is restricted by parameter security. If you try to cancel an MVR record and you do not have correct access an error message will appear.

Once the Cancel request has been applied the employee record is removed altogether from the MVR workbench.

This action is used to retrieve fund responses for records that have already been submitted via MVR.

To perform this process, select employees with a status of UPLOAD_SEND_SUCCESS and apply the ‘Get Fund Response’ action.

The super funds have 24 hours to respond on MVR. These responses from Funds are called ‘Member Verification Outcomes’ (MVOR)

There are two types of responses via the MVOR:

Users must monitor the MVOR for all outstanding MVR transactions.

When an employee pay calculation is added, or when the USI and/or member ID is updated, a PENDING transaction will be created on the MVR Workbench.

This status indicates that the record has been modified and requires validation by the superannuation fund. If required, these records can be cancelled, which will remove them from the Workbench.

This status indicates the record has been sent from Access COINS to Ozedi.

This status indicates the record has been sent from Ozedi to Super Funds.

Once the ‘Upload MVR’ action is applied it may return a status of FAILED.

By drilling into the hyperlink ‘Failed’ it will reveal the error message.

To resolve this error, update the employee’s phone number within Employee Maintenance under the Home Address section. At least one contact number (Home or Mobile) must be provided, as this is a mandatory field for MVR processing.

Once updated, reapply the action ‘Upload MVR’ to the ‘FAILED’ file and records should return status ‘SENT’.

An error indicating that the superannuation fund cannot be found is typically caused by an invalid USI recorded for the employee.

It is recommended to contact the employee to verify and confirm the correct superannuation fund details, including the USI and Member ID, and update the system accordingly.

For records on the MVR Workbench, update the employee’s USI on the Employee Pay Calculation record to reflect the correct USI for the employee’s superannuation fund.

Upon saving the record, the MVR will be updated with the revised details, and the status will be reset to ‘PENDING’. This allows the user to reapply the ‘Upload MVR’ action, after which the record should return a status of ‘SENT’.

Errors relating to the employee address details missing the MVR will return messages as follows.

Update the employee’s address details within Employee Maintenance under the Home Address section. Once updated, reapply the ‘Upload MVR’ action to the ‘failed’ record. The record should then return a status of ‘SENT’.

The super funds have 24 hours to respond on MVR. These responses from Funds are called ‘Member Verification Outcomes’ (MVOR)

There are two types of responses via the MVOR:

For a Failure response the status on the MVR workbench will return ERROR.

Fund MVOR error responses can be one of the following:

To view specific details, drill into the ‘Error’ hyperlink, which will display the error message relevant to the employee.

All MVOR responses that return status of ERROR must be resolved before any super contributions are sent to fund.

When a successful response is received from the fund via the Member Verification Outcomes (MVOR) process, the record will return a status of ‘MVR Verified’.

This status indicates that the fund has validated the employee details provided. It confirms that the employee’s information matches an active superannuation account with the fund and that contributions will be accepted.

The previously named Pull ATO/SuperPay Reponses & Status Report has been rebranded and will also include MVR responses.

During the payroll calculation, system messages are generated based on the MVR status of employees. The behaviour of this process is influenced by the payroll parameter outlined below.

The calculation will generate an error/warning for employees whose MVR status is on one of the following:

Employees with a status of UPLOAD_SEND_SUCCESS will always generate a warning on the calculation report. This will not escalate to an error, regardless of the parameter settings. The warning serves to indicate that the MVR has been sent to the fund but has not yet been verified.

No message or error will be generated where the MVR status is ‘MVR Verified’.

The calculation outcome (error or warning) is determined by the parameter setting, with the default behaviour set to ERROR.

Funds have 24 hours to turn around on MVR responses.

The payroll calculation will return an error if a record exists in the MVR Workbench and its status is not MVR Verified.

If the parameter is set to Warning the report will return only a warning message.

When the MVRCHECK parameter is set to Error, the super payment file validation will return errors if there are any outstanding MVR transactions for an employee included in the file.

If employees have an active MVR record with the following status:

The validation process will flag these as MVR errors in the report. As a result, the super payment file will not progress to the next status, Upload Check Pass.

When the MVRCHECK parameter is set to Warning, the super payment file validation will continue even if MVR transactions are outstanding.

The validation process will include any MVR issues as warnings in the report only, and the file will proceed through to next status, Upload Check Pass allowing submission of the super file to Ozedi.

Configuring the parameter to return a warning may result in employee superannuation contributions being submitted to a fund before the employee’s details have been verified.

This introduces a risk that the fund may not recognise the employee as an active member, which could lead to contributions being rejected.