This document will outline the configuration requirements within Access COINS ERP+ to enable Super Payday. There are many changes required to be undertaken by Payroll clients to ensure you meet your obligation in reporting to super funds.

ATO announced in 2024 a reform to align employers’ payment of Superannuation Guarantee (SG) contributions with salary and wages, instead of the current quarterly requirement. This will take effect from 1st July 2026.

Payday is the date that an employer makes an ordinary time earnings (OTE) payment to an employee. Each time OTE is paid, there will be a new 7-day ‘due date’ for contributions, with some limited exceptions.

Employers

Super Funds

Key changes for Employers:

Knowledge of Access Coins ERP+ is necessary

Refer to ATO website for full details

Prior to registration it is important to read the ‘Ozedi Dashboard User Guide’ and understand the methods of payments prior to registration.

All COINS payroll clients must register for Super PayDay with Ozedi using the COINS URL

Once registered, an email will be sent to activate your user account.

Using the login below you can log in and start creating the organisation account as per the ‘Ozedi Getting Started Instructions.

Ensure you select SuperStream as the Service, when creating your account in organisation account, fill in all details as required and add account.

You will need to take note of you 15-digit Account Number at this time for COINS PR parameters

For machine-to-machine access between Ozedi and COINS you will be required to setup and configure the External App Access (API) user account.

The API Username and Password credentials are required to be able to connect to COINS and will be part of the COINS PR parameters. This user will not be able to login to the dashboard.

Ozedi has introduced New Payment Platform (NPP). Where payments are made in real time (instant) and can confirm that money was received by super funds. This new method of payment is available 24/7.

Unlike the traditional methods of payment (EFT file) where file is uploaded to bank with collection points throughout the day. This process is being phased out and replaced by NPP, real time instant payments. Other methods of payments like BPay and Direct Debits will also be phased out by 2030.

During the registration process you must select payment method for making the superannuation contributions to funds.

The options for processing Super are ZEPTO payments, RewardPay and Manual Payments. This step must be made prior to configuration back in COINS as parameters must be set prior to processing.

Please refer to the Ozedi Dashboard User Guide for further information on this step, as bank details needs to be maintained here.

This is a 10-digit number that is unique for each Ozedi Client ID (ABN). Each Client ID or each active ABN currently submitting will require a SSID.

This will be applied to all STP files submitted from Ozedi to the ATO linking the SSID to ABN to Ozedi and ensuring it has been authorised by the end user for the Product ID (COINS ERP+).

Ozedi will provide the SSID to all clients in March 2026. Once you have received the SSID users must complete authorization with the ATO (via phone or online using MyID) and link their ABN to the product with the SSID. (process steps will be provided closer to date when you receive your SSID)

Failure to complete the authorization with ATO will result in ATO rejecting the STP files.

The SSID must be stored in COINS and will require users to update once received and registered. This is company specific and a new field has been made available on the ATO workbench.

Please find a checklist for configuration of Ozedi SuperPay dashboard and SuperPay in COINS.

Please note that this is only a guide.

With the introduction of Super Pay there are several new payroll parameters that will be required to be configured prior to enabling the new process. These can only be populated once full registration with Ozedi is completed.

New filter to display all SuperPay parameters. To ensure nothing is missed.

Additional PR Global parameters that may affect SuperPay

A Supplier must be configured in Accounts payable. All Super funds must be configured in a lookup table to be available for allocation to employee on Pay Calculations.

Payroll > Global Parameter > Lookup Codes

Filter on lookup type = Superannuation Funds

This search will present a list of superfunds as setup in the system.

Under Super Payday there is a requirement to hold the ABN for all super funds.

Prior to the introduction of Super Payday, the lookup table field ABN was previously only required for SMSF.

A requirement will be to update this table to ensure all super funds have their corresponding ABN.

Whereby a fund has several policies linked to the same ABN you will only need to enter the fund code once as the USI is held against the employee ID which identifies the policy within the fund.

For example, below AMP Savings Trust has one ABN and within that ABN there are 5 policies.

Therefore, the lookup code for AMP would be one single entry holding the single ABN.

To update a selection of funds within the lookup use the BULK functionality to update the table. Otherwise, Open and manually update records.

If you are updating the code and description, you will need to look at mapping previous codes to the new code and/or description.

You may have an existing super code that holds different ABNs for a Superfund.

Example:

The lookup table may hold one code for Local Government Super Fund; however, this Fund has multiple ABNs for the multiple policies under the Fund.

Therefore, new Super codes must be added to the lookup table for each unique ABN. This can be completed by either:

Employee Maintenance > Pay Calculations Tab

Pay Calculations is for recording of employee superannuation information along with deductions. These may be a flat amount or percentage based.

To identify the specific policy within a fund the employee is contributing to, the USI is recorded against the fund id on the employee record.

COINS superannuation Pay Calculations codes have not changed with Super Payday:

All employees must be linked to a super fund from the lookup table and must also contain a USI (if linked to APRA fund) on employee pay calc record along with membership ID.

Payroll > Company Setup > Employee Administration > Load Employee Pay Calculations

You will need to use the filters to minimise the data in the open table. There is no requirement to extract terminated employees or dormant records.

For example:

Filter on individual frequency; Not terminated; Last Effective date; not dormant and pay calc code starting with SUP*

Apply the filter

To export all the data in it's original form, it is recommended to use the PRINT button vs Excel button on the tool bar Depending on the range of data on the open table it may time out, or the selection may be too excessive

Select the PRINT button

This will print to the report server all data in the current workbench for all fields

From the report output use the excel button to open in excel file

All employees must be linked to a super fund from the lookup table and must also contain a USI on employee pay calc record along with membership ID.

Working in combination with the Lookup table you will need to review all employee pay calculations to ensure they are correct and meet the following criteria:

Payroll > Company Setup > Employee Administration > Load Employee Pay Calculations

Data to be reviewed and/or updated are columns:

8. Once the necessary data has been reviewed / updated with new effective date in the excel file, unhide all columns and remove filters.

9. Copy ALL and paste back into the open window – you must still have the original DATE/TIME and ROWID in the reloaded data.

10. Save.

11. Go to employee Pay Calculations to verify data has been updated on the employee record correctly.

For employees that require a new Fund Code allocated to a pay calculation it is not recommended that you update the current record with new Fund Code.

This will not be a true indication of history if you use BULK update as it will override data.

Best practice is to ADD a new record with new Effective Date for new Fund ID for individuals.

You can either:

Super fund validation refers to the process of verifying that the details provided for a superannuation fund (APRA and Retirement Savings Account Providers) are correct and compliant before processing contributions or payments. This is critical for payroll and ensuring funds go to the right account.

Self-Managed Super funds are not included in the FVS.

Key Validation checks:

COINS ERP+ has introduced a new process and enquiry for users to verify employee super fund details prior to populating information on employee pay calculations.

COINS ERP+ has implemented a process to download Superannuation Funds information for users to validate employee superannuation fund details prior to adding to the employee pay calculation record.

If you are adding a super record to the employee pay calculation record and you have not downloaded the SuperFund Report you will get an error message. This error will only occur on initial implementation.

However, it is recommended daily scheduled runs are setup to support the updating of employee records.

To download the data, go to ‘Download SuperFund Report’ and click NEXT.

This will populate the data in the ‘Valid SuperFunds’ enquiry.

Once the download has been completed it will automatically populate the data in the ‘Valid Super Funds’ enquiry.

Users have the option to create different views using column sets. There are a diverse number of filters and search options available to minimise the data output.

The standard information provided is as follows:

Entering data on the employee pay calculations will now be validated against the data in this enquiry.

SuperPay parameter PR/SuperFundValError will impact whether you get a warning on saving the employee pay calculation if the download has not been run for the day. This is to ensure that you are entering a valid USI onto employee record.

If set to be warning, you will receive the below message on saving.

If set to error, you will receive the below message on saving and you will need to run the download to verify employee USI before saving the employee record.

If entering a USI on the employee record and it is not valid, you will receive the following message. You must obtain a valid USI from the employee before they can be paid.

Two new fields have been developed to enable correct reporting of employee details to super funds.

Employment Category - Employee work classification as per SAFF requirements

Total Salary Package - Employee Total $ salary package

Payroll > Employee Maintenance > Profile Tab > Work information

This field is to be used to describe the employment category of the employee, these are as per the SAFF definition. Select from the ‘Employment Categories’ table.

Payroll > Global Setup > Employment Categories

New table to be populated to describe the employment arranged between employee and employer. These must be populated as follows as follows.

Super Funds may require salary package amounts for insurance purposes. This is an optional field in SAFF File. COINS offers two values that can be used.

HR > Personnel Workbench > PR Details Tab

This will display the annual salary based on employee’s base rate multiplied by hours per pay period multiplied by pay frequency in payroll.

This is not updateable and is calculated by COINS.

Payroll > Employee Maintenance > Profile Tab

New Field to enter Total Salary Package of employment for employee. This field is a free text numeric field.

Employee maintenance records may require to be updated with new values for new fields. These can be completed with a bulk load for employees.

Create a new column set so that the new fields are easily visible on employee maintenance workbench.

Below is an example of a column set that holds new data.

Create a csv load file that contains the new fields. Column A must be employee ID (kno), and the new fields can be populated in the following columns

Save the CSV file as CSV UTF-8 (comma delimited csv)

Payroll > Company Setup > Employee Administration > Load Employee Data

A report will be generated which will display how many records were included in the file (Row 1, which contains the field names, counts as a record) and how many could be read successfully.

Immediately following the number of records will be a list that contains Records in Error followed by Warnings.

Once the CHECK is successfully completed and no errors, run the function again in LOAD mode

In Employee Maintenance verify data has been loaded successfully.

Payroll > Company Setup > Oncost % configuration

Select Federal ‘FED’ record and open

Enter ‘Employer ID’ which equates to column AE in SAFF file for Location ID.

This is used to identify a specific employer under the client facility. IT is company specific.

A new shared folder must be created to ensure users have access to all SuperPay files. This will reduce the risk of a single user having access to files. The log files will be placed in this shared folder and may be requested by Support.

System > System Setup > Shared Folders

Directory is the name of the shared folder. Once saved the record creates a directory and this is used in the full file string on the parameters for where the file is to be stored.

Recommend directory name is pr_suppay

Once the folder has been created Payroll Users and/or Payroll Groups must have access to the shared folder.

If shared folders have already been implemented for Payroll, use the same Read/Write Function as other payroll folders as this should already be assigned to users/groups.

Once access has been granted the user navigates to ‘Report Status > My Files’ a Folder drop down will appear on the user to select the shared folder.

Before making any changes to parameters, verify if they are required to be Company Specific by selecting the parameter and using the ‘Choose Action > Create Company Specific.’

Add new Transaction type for PPAY to identify the PR prepaid invoices. Once created add to above parameters.

There has been a change made to the EFT Output and Print process.

When generating the ABA file for wages, it will not only create the PAYEVNT file for Single Touch Payroll (STP) but also the SUPERPAY file for employees. These files will be in the ATO Workbench.

Unlike currently once the EFT is generated an Employee Status cannot be updated from PAID to any other status via the ‘Change employee Status’ if a SUPERPAY file exist. An error will be generated if employee status is changed.

The SuperPay file must be CANCELLED from the ATO Workbench and can be recreated via the EFT process if it has not been submitted to Ozedi.

The previously named STP Workbench has been rebranded to ATO Workbench and will now include SUPERPAY workbench.

All STP PAYEVNT files and SUPERPAY files generated from the EFT Output are in the new ATO Workbench found in each pay frequency.

Payroll > [Pay Frequency] > ATO Workbench

A Master ATO Workbench is also located within the Main Payroll Menu, which stores ALL files generated from all frequencies, including company control information.

Payroll > ATO Workbench

Once the EFT Output and Print is processed, the SuperPay csv is located on the

SUPERPAY Tab on the ATO Workbench.

Several Actions are used to submit the file to Ozedi and return responses.

The paperclip will automatically store all files generated by the process against the file for SuperPay. E.G. SAFF csv and EFT file.

Details of what is in a file can be found by drilling into the Period hyperlink.

This will display employees within the file, the type of contributions, including USI, amounts and the payment reference.

Payment reference is linked to the fund payment ID used in ABA file or NPP transaction.

Column sets can be used to change the layout of information.

Several filters have been defined to assist in reconciliation and extracting necessary data.

When drilling into the status hyperlink, the user will be redirected to Submission History.

This will display all stages of file processing including log file reference.

The number from the submission history will reflect what log file to download

A new tab on the employee maintenance record has been added to display all super transactions processed via SuperPay for an individual.

Payroll > Employee Maintenance > SuperPay Transactions

This will provide users with the ability to review/reconcile and extract data from the individual employee record for all super payments once paid via SuperPay workbench.

New Company report allowing organisations to report what has been submitted to super funds for a period of time.

Use the arrows to select a specific fund or all funds to be report on. Moving Funds from Available to Selected section of the report

Report output is broken up by Fund – it will outline each payroll period payment made for individuals.

Use for reconciling to Standard superannuation report.

On posting the Payroll Costing Workbench the batch transactions have been updated to now include ‘AP Prepaid Invoice Batch’.

The PL Analysis report when run for the payroll batch will include payroll suppliers in both AP batches, Posted and Non-Posted AP batches.

Superannuation payments are now managed at the time of processing each pay run via the ATO Workbench.

Whether payment options with Ozedi are Zepto or Manual payments the funds must be paid prior to posting the payroll costing workbench.

Both invoices will show in Accounts Payable > enter Invoices. The Transaction Type PPAY is used to Identify payroll auto posted invoices. Eg Superannuation

When you drill into the POSTED batch this will automatically have created corresponding GL and CB batches.

On Invoices Tab, the supplier linked to the funds on the Superannuation Lookup table will be automatically posted.

When you drill into the Internal Reference for the super transaction the Costing Distribution will show the invoice as PAID

For the posted invoices the corresponding GL batch will show GL transactions for the auto posted invoices.

The GL account will show Debit from Payroll Clearing Account.

Credit to the Supplier Purchase Control account stored against the super supplier.

Cashbook will create a Batch from the auto posted invoice which will need to be manually reconciled against the bank statements.

Your COINS payroll process prior to the EFT Output and Print remains unchanged.

Below are processes that should be used as guidelines when SUPERPAY is LIVE in COINS.

Please refer to the Section for SuperPay Testing Pre-Go Live for testing

On the ATO workbench for SuperPay are several actions, each action must be applied using the arrow.

Prior to VALIDATE the costing workbench must be validated. If you fail to validate the costing workbench it will return an error on VALIDATE.

If you UPLOAD without validation an error will be populated.

First process is to VALIDATE the file to ensure there are no errors prior to submission to funds. This is for both Manual and Zepto contribution payment methods.

This process will validate the following:

Once the action is applied a new window is opened, click NEXT.

Status of the file if VALIDATION passes, swill be UPLOAD_CHECK_PASS.

Depending on size of file status may change to UPLOAD_PRE_PROCESSING. This is the initial status when file upload initiated, and file is accepted.

The user must wait for the status to return either PASS or FAILED. If a user tries to apply the next action an error will appear

If the status returns UPLOAD_PRE_PROCESSING _FAILED that means the file has validation errors.

Refer to the section on Reviewing Error Messages to troubleshoot error messages and regenerate/reprocess the file or entire payroll process.

Whilst the information in Ozedi is limited, the data returned to COINS has further information therefore recommendation is to review the SuperPay Submission Messages/Errors for specifics, like below:

This may be due to invalid APRA USI for employees; other errors will appear if a USI is invalid as there are no payment details for an invalid USI. Fix the USI on the employee Pay Calculation record and the other errors will be auto corrected on next validation.

You should update the employee pay calc to have the correct USI for the fund. Then REGENERATE The file this will pick up the new USI from employee pay calc.

Once errors are resolved the file must be REGENERATED to create a new unsubmitted file ready to VALIDATE again.

To verify, once you have the new UNSUBMITTED file drill into the period and find the employee to check the new USI has been updated.

You must then VALIDATE file for resubmission.

Once file is validated with no errors and the status of UPLOAD_CHECK_PASS only then can you apply the action UPLOAD. This uploads the file to Ozedi for processing. This step is also for both Manual and Zepto contribution payment methods.

Once the action is applied a new window is opened, click NEXT.

Status of the file changes to UPLOADING

If user clicks on refresh the status may change to UPLOAD_SEND_IN_PROGRESS UPLOAD_PRE_PROCESSING. This is the initial status when file upload initiated, and file is accepted.

If user tries to apply the next action an error will appear.

Status must return UPLOAD_READY before you can continue to process the file, run the action ‘Check Upload Status.’

Once the action is applied a new window is opened, click NEXT.

Once the file has been uploaded successfully to Ozedi the file status will be marked as UPLOAD READY if processing manually.

The Ozedi Dashboard now contains the file for submission to funds.

The upload process will again run through various Validation at Ozedi:

If Errors are found the file will return UPLOAD_PRE_PROCESSING_FAILED user should refer to troubleshoot error messages and regenerate / reprocess the file or entire payroll process.

Once errors are resolved the file can be REGENERATED to create a new unsubmitted file ready to UPLOAD again. At this point you should start again at Validate process.

If processing via Zepto should complete full process automatically and return UPLOAD_SEND_SUCCESS. This will indicate the super has been sent, paid and remittances emailed to funds.

This Action is available to update the status of each stage throughout the process.

For example, once the file has been uploaded depending on the size of the file, the status may return UPLOAD_PRE_PROCESSING

Once the action is applied a new window is opened, click NEXT.

The report output will return if the status has been completed and update the workbench.

This action may need to be run several times to ensure Status is updated to current valid status before moving onto the next stage.

Refer to the upload status values table in the section on Upload Status Values.

This action allows a user to cancel a SuperPay file that has already been uploaded to Ozedi dashboard but not processed. Status must be UPLOAD_READY before you can use action ‘Cancel Ozedi Upload.’

Once the action is applied a new window is opened, click NEXT.

Status updates as the files are being cancelled, it is also being removed from the Ozedi Dashboard.

Once completed the status will be UPLOAD_CANCELLED

If STP has been submitted to ATO (status is Submitted or Completed) and SuperPay can be Cancelled however, the file must be regenerated from the original Cancelled file. This will create a new Unsubmitted file.

If STP has not been submitted to the ATO and SuperPay has been Cancelled, then you must also Cancel the STP file.

To recreate both files the ‘EFT Output and Print’ must be run again.

This action is used if the organisation is opting for processing Manual Payments with Ozedi. File must have status of UPLOAD_READY before manual payment can be processed.

Once the action is applied a new window is opened, click NEXT.

Status updates as ABA file are being processed.

Once the EFT file has been created status must return PAYMENTSABAFILE_SUCCESS

The report output will generate report of what payments will be made and contained in the ABA file.

User must extract the ABA and upload to bank for payment to the super funds.

This action is used if the organisation is opting for processing Manual Payments with Ozedi. File must have status of PAYMENTSABABAFILE_SUCCESS.

Only once payment is sent to funds, can remittances be sent.

Once the action is applied a new window is opened, click NEXT.

Status updates as remittances are being sent out to funds.

Check upload required to run to update Status. Once remittances have been successfully sent to super funds the status must be UPLOAD_SEND_SUCCESS

File has been sent, and payment has been made to funds.

This action should only be run if the SuperPay file returns an error and needs to be regenerated for erred employees or in some cases all employees.

A file will return with a FAILED status for the requirement to regenerate.

Select the file to be regenerated and apply the action. In the case of a UPLOAD_PRE_PROCESSING_FAILED the regenerate will be created for all employees as errors exist in the load file that need to be resolved before submission to Ozedi.

Once the action is applied a new window is opened, click NEXT.

The original file changes status to ‘REGENERATED’ and a new file has been created as ‘UNSUBMITTED.’

Process the new SuperPay file as per business requirements.

The Cancel action can only be applied to SuperPay file that does not have a status of UPLOAD_SEND_SUCCESS or PAYMENTSABAFILE_SUCCESS

Cancel is permitted on a file with UPLOAD_PRE_PROCESSING_FAILED. However, caution should be considered as file has returned error on upload so these must be resolved and REGENERATED and UPLOADED – should not be CANCELLED.

If a SuperPay file is Cancelled, it can be re-created by running the process EFT output and Print or Regenerated from Cancel file.

This action is used by COINS consultants and support only, to investigate/resolve file issues on behalf of a client.

Funds infrequently send responses electronically and there is no regulatory requirement for funds to send responses at the time 12.05 was released.

Once the action is applied a new window is opened, click NEXT.

Coins is checking upload status

As funds are not mandated to send response the status will return BLANK

During the registration of your organisation with Ozedi if selection of Contribution payment method is set to ‘Zepto’ then the process is automated.

User must complete necessary steps.

Ozedi new instant payment service using Zepto is focused on using NPP. This manages the processing of the file directly to the funds and the handling of payments instantly to the super funds.

Users are required to continue to run the action ‘Check Upload Status’ regularly.

If at any stage a process FAILS user is to review Error messages and resolve.

If processing via Zepto contribution payment method the complete full process will run automatically and return UPLOAD_SEND_SUCCESS. This will indicate the super has been sent, paid and remittances emailed to funds.

During the registration of your organisation with Ozedi if selection of Contribution payment method is set to ‘MANUAL PAYMENTS’ then the process is 100% driven by user.

User must complete necessary steps

This action is used if the organisation is opting for processing Manual Payments with Ozedi. File must have status of UPLOAD_READY before manual payment can be processed.

Once the action is applied a new window is opened, click NEXT.

Status updates as ABA file are being processed.

Once the EFT file has been created status must return PAYMENTSABAFILE_SUCCESS

The report output will generate report of what payments will be made and contained in the ABA file.

User must extract the ABA and upload to bank for payment to the super funds.

If payment method is set at Ozedi to ‘Manual Payments,’ then users must extract the EFT file from COINS to upload to the Bank.

File must have Status of PAYMENTSABAFILE_SUCCESS

For ABA file it can be found in the following areas to download.

Click on paper clip to view all SuperPay files include the EFT file.

It will open a new window to ‘Browse Documents’

Click on hyperlink for SuperPay BACS file. This will open new window, ‘View Document’ where you can click on Option button to Check Out Document.

This will allow you to download the ABA file.

From users PC Downloads directory, user can pick the file up for submission to bank.

Like the regular payroll ABA file for wages, users can download the SuperPay File from ‘My Files.’

It is highly recommended that the file reside in a shared folder so that all Payroll users can access the SuperPay EFT file if required. If not sent to a shared folder, then the user who created the ‘SuperPay Manual Payment’ will only be able to access the ABA file in ‘My Files.’

This action is used if the organisation is opting for processing Manual Payments with Ozedi. File must have status of PAYMENTSABABAFILE_SUCCESS.

Only once payment is sent to funds can remittances be sent.

Once the action is applied a new window is opened, click NEXT.

Status updates as remittances are being sent out to funds.

Check upload required to run to update Status. Once remittances have been successfully sent to super funds the status must be UPLOAD_SEND_SUCCESS

File has been sent, and payment has been made to funds.

The VALIDATE and UPLOAD processes both runs through various Validations at Ozedi:

All error messages for all stages of processing can be found stored on the FAILED record. There may be instances where the uploads return UPLOAD_PRE_PROCESSING_FAILED or UPLOAD_PAYMENT_FAILED

To view all error messages, drill into the STATUS of the file.

A new window will open and redirect user to ‘SuperPay Submission History.’ Click on the FAILED state.

This again will open another window whereby all messages and errors can be viewed.

You must review all error messages and resolve. Only once errors are resolved can the file be REGENERATED, VALIDATED and UPLOADED.

In the above example the SMSF has invalid BSB which is held on the lookup table ‘Superannuation.’ The BSB must be updated, file regenerated then uploaded for resubmission to Ozedi.

The previously named Pull ATO Submission Report has been rebranded and will also include SuperPay responses.

For STP the report type has been updated to Pull ATO / SuperPay Responses

For STP this must be run until a COMPLETED message is returned. This is the only way to update the STP workbench Status.

Funds infrequently send responses electronically at the time of release this report type is a work in progress – future enhancement.

This process should be scheduled to run if payment option is Zepto with Ozedi. This will ensure that the process is being checked regularly to ensure the file status returns UPLOAD_SEND_SUCCESS.

If you do not schedule to run and verify workbench has been updated to final status, then user must run ‘check upload status’ from workbench.

Table below displays the various status settings for upload file as it is processed.

Files must be at yellow status before applying the next action if using Manual payment options.

Green status is the final stage for file and that SuperPay process has been completed.

Once all configuration is completed and employee pay calculations are updated a pay run will be required to be processed.

Once you have uploaded the file for validation the below message will appear.

If the file has errored, the status will have PRE PROCESSING FAILED.

Click on the Actions button and select ‘View Upload Errors.’

A new window will open with error messages.

The error message regarding invalid APRA fund is a result of an invalid USI. Therefore, find the employee in the file with incorrect USI 123, update employee record for next validation. You can download the Errors and review in excel.

The other four errors are related to invalid APRA fund as Ozedi is looking at population of Fund Banking Details if not provided using the ATO’s Fund Validation Service (FVS). If provided, they are validated against the ATO’s Fund Validation Service (FVS). If the Fund banking details are not correct, an error will be reported.

To continue the file on the Dashboard must be cancelled.

The employee record must be updated with correct USI before creating new SuperPay file.

On the ATO workbench both SuperPay and STP file must be ‘Cancelled.’

Payroll > [Frequency] Payroll > Maintenance > change employee status.

Change all employee back to CALC status.

You must RESET the payroll.

Rerun the CALC process and this should bring in the new employee USI into the pay run.

Complete the standard payroll process and rerun the EFT process which will create a new SuperPay file.

Follow the steps again for extracting the file from COINS and uploading file into the Ozedi Dashboard.

Qualifying earnings (QE) refers to the earnings on which employers are required to make superannuation contributions under the Payday Super reforms. Essentially, it's the amount paid to employees that includes OTE, salary sacrifice super contributions, all commissions and other earnings currently included in employee’s salary and wages for SG purposes.

Qualifying earnings will be reported to the ATO in the Pay Event as a new code ‘Q’ as at the first pay day after the 1st of July 2026. STP will continue to report Total Super Liability there is no change to this. The ATO will calculate the SGC based on qualifying earnings to ensure employers have met their obligation.

To ensure your database is ready for reporting the new Qualifying Earnings will report YTD values. Users must review and prepare to correctly map the Earning Categories and Pay Calculations to ensure readiness for when COINS releases the new STP PAYENT via a MU package first thing in new financial year 2026/2027.

New parameter STPMAXQE will hold the maximum contribution base limit as Qualified Earnings and so only the capped YTD amount will be reported once limit is reached.

When an employee has a salary sacrifice arrangement, you need to consider if the sacrificed amounts will be taken into account when working out their qualifying earnings (QE).

Salary sacrifice amounts that would have been QE if they weren’t sacrificed to superannuation are included in QE for an employee. This means the pre-sacrificed amount is counted as QE for super guaranteed purposes.

However, amounts salary sacrificed to other employee benefits – including benefits that are fringe benefits and exempt benefits (other than those sacrificed to superannuation) aren’t QE. This includes:

A new field ‘Qualifying Earnings’ tick box is found under the Single Touch Payroll Info.

You must select the Qualifying Earnings if the earning category is currently treated as OTE for purposes of Super Guarantee.

You must select the Qualifying Earnings if the pay calculations that are ‘Fringe Included in Pay’ are currently treated as OTE for purposes of Super Guarantee.

The maximum contribution base (MCB) is the upper cap of earnings on which an employer must pay the minimum amount of super guarantee (SG).

Currently, employers pay SG on an employee’s ordinary times earnings up to this cap for a quarter, but not on amounts above it. Under Payday Super, the MCB will shift from a quarterly cap to an annual cap. Instead of applying per quarter, the cap will apply to the total qualifying earnings (QE) for an employee for the financial year.

Employee Maintenance > pay calculations

Drill into the SUPG hyperlink and you will need to update the ‘Per Quarter’ to 999,999,999.99 and set the ‘Per year’ value to be that of the current SG capping amount.

To extract and update bulk employee records you can use the ‘Load Employee Pay Calculations’ to update these figures on employee record. Updating current record only is required.

Once you have updated the employee record it should look like below.

Users can enable the capping on the master pay calc SUPG code under

Payroll > Global setup > AUS Specifics > Pay Calculations.

Filter for SUPG code and open the record.

Update the ‘Per Year’ amount to be capped value and reset ‘Per Quarter’ to be 9’s.

The SuperStream Alternative File Format (SAFF) has been specified by the Australian Tax Office (ATO) as a standard file format that employers and payroll software providers can produce from their systems. The SAFF will be generated by COINS when the EFT process is run and will be used in COINS SuperPay workbench to submit to superfunds via Ozedi.

All fields are to be separated by a comma (,) value. There are four distinct types of records with the SAFF:

Header Values - the first line of your file must contain the label/value pairs as defined in the “Header Values” section below.

Section Headings – the second line of the file must contain the section headings as defined in the “Section Headings” section below.

Column Headings – the third line of the file must contain the column headings as defined in the “Column Headings” There are 133 column headings.

Repeating Line Values – the remaining lines of the file are populated with your contribution and member registration information as defined in the “Repeating Line Values” section below. Each of your employees for whom you are providing contribution and member registration information should have only one row of data per USI.

The Sending Service Provider (Ozedi) is validating the first three lines to confirm that the file uploaded is a SAFF file.

This line contains no values that you are required to populate, but it must be in your file.

Must appear in 3rd Row of the file.

After the header lines in the SAFF, there are several repeating lines which are used to provide the details of a superannuation fund, an employer, an employee and either contribution or member registration information.

This action is used by COINS to investigate file issues on behalf of a client. Will only be used by Support or COINS consultant when required.