The biggest challenge facing Australian customers for our next financial year is Superstream. The changes being introduced by the government will require employers to communicate with Gateways electronically. This communication is two way; payment details going out to the Gateway, as well as error messages coming back to employers from superannuation funds via the Gateway. All this is being done via XBRL and ebMS3, both of which aren’t historically used by SAP PY.
We’re lucky that the ATO is part of the pilot group, using SAP itself. This will enable the solution, albeit interim, to be fully tested before being rolled out and adopted by Australian customers. But that is where the good news finishes; the whole solution and process hasn’t been through through by the ATO or SILU, and will represent issues for customers.
One example; USI (Unique Superannuation Identifiers). There is not a one to one match for USI to SPIN. One example is MLC Masterkey, as can be seen on this page;
The SPIN MLC0440AU is now mapped to 3 USI. Employers will need to understand which fund they have in SAP maps to which USI. Depending on their employees it could be 1, 2 or all 3.
The ATO and SILU haven’t come up with a plan as to how employers will gather this information, let alone conceptualised what impact it’ll have on their systems. They hope this information will come from the super funds themselves, but there hasn’t been a clear concept as to what would trigger this happening.
What does all this mean? Not only are employers going to have to test, and possibly certify (more on this later) their solution, but the data collection, clean up and testing will also require effort, that needs to be taken into account for these changes.