Affinity's approach to super compliance
Areas of Affinity Payroll Admin involved
Employee masterfiles (Allowances/Deductions tab).
ClickSuper interface (if this is the chosen SuperStream clearing house).
Reporting (Crystal Reports and standard payroll reports).
How we utilise each functional area
We use a combination of pay elements (to drive calculations), super fund info masterfiles (to define fund details), and employee masterfiles (to record funds and pay elements). Here's a quick look at how we do it:
Standard pay elements are configured for employer contributions and voluntary employee deductions. An informational code called QEARN is used to track qualifying earnings and also sets the annual maximum contribution base (MCB) at a global level (unless overridden by the employee masterfile).
For each super fund used by employees in an organisation, a super fund info masterfile is created to define things like fund name, ABN, and product name or USI.
The relevant super-related pay elements are added to employee masterfiles and the fund is also recorded against each pay element to tell the system which fund contributions and any voluntary deductions will be paid into.
For super that's calculated based on a percentage of a group of earnings, a code group can be set up to contain the pay elements that this percentage is calculated on. A code group called QEARNINGS is used to contain pay elements considered to be qualifying earnings for STP reporting purposes.
SAFF files which report contributions to super clearing houses are generated from Crystal Reports. This is also where reporting that summarises payments to be made are found (1045) and payments that were made (1046).
The 601 virtual report warns you about employees that have any super-related discrepancies such as missing config or exceeded MCB caps.