We are moving from the QuickSuper portal to the new Australian Super portal. Currently we load up one file that covers 3 companies. The QuickSuper portal allows this. I spoke with the Australian Super portal help desk and apparently you won't be able to do this anymore and you will have to load up 3 files - is it possible to change the output of the csv file from the EHG process so that each company has its own file or at least its own employer number in the EmployerID column.
Related topics
Where is the Pay Day Super - STO2 Template
Will the ATO accept a QE enabled STP file for this pay period if it is submitted before 1 July?
Can we pay Superchoice via an EFT file.
We are moving from the QuickSuper portal to the new Australian Super portal. Currently we load up one file that covers 3 companies.
The information on Payday Super released so far only mentions flags on PTA to include or exclude an amount from Qualifying Earnings.
Categories
Got a great idea for a product enhancement? Raise it here and let the Community vote!
Thank you for your query regarding separate output files for each Company when using the QuickSuper interface.
QuickSuper was designed some time ago and most organisations have now moved to the SuperStream Alternate File Format (SAFF) for all superannuation contribution reporting, as SAFF offers greater flexibility and is the current industry standard.
Within the current QuickSuper output there is no dedicated setting that will automatically create a separate file for each Company on the database. There may be some limited options worth exploring, such as using pay run number as a parameter on the EHG form, or potentially structuring output based on specific creditors. A Frontier Software Consultant would need to review your configuration and business rules to confirm what is technically and practically feasible in your environment.
If you wished to retain QuickSuper and introduce new functionality, such as separate files per Company, this would need to be delivered as a bespoke enhancement to the EHG process. That would involve a Business Functional Specification, development, testing and release, and would typically be expected to take in the order of 4–6 months end to end.
Given the above, the simplest and most future‑proof option is usually to transition to SAFF. This avoids custom development, aligns you with current SuperStream practices, and provides more flexibility for ongoing super reporting. Frontier Software can assist with planning and implementing a move to SAFF so that it minimises disruption to your payroll cycles.