FastTrack360 Version 12 Online Help

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In preparation for EOFY there are some checks you can do to check the configuration of your system to ensure you avoid some common issues. These checks are listed in the table below along with suggested corrective actions if your configuration is not correct.

Check

Corrective Actions

Have payees been setup with the correct payee type/employment type (Individual Non Business vs. Labour Hire)?

Where necessary, change the option in the Payee Type field on the relevant payee records from Labour Hire to Individual Non Business or vice versa.

 For more information, see Frequently Asked Questions.

Have allowances been configured to report correctly through Single Touch Payroll based on the allowance type?

Where necessary, tick or untick the Show on Individual Non Business Payment Summary/ Show on Individual Non Business Payment Summary (Above Threshold)/Include in Gross Earnings options depending on whether the allowance is to be itemised or included in gross earnings for the purposes of STP reporting depending on the allowance type.

For more information about ATO requirements for reporting allowances for Individual Non Business payees (including Working Holiday Makers) see Withholding for Allowances.

For more information, see also Configuration of Allowances.

Have superannuation contribution rate rules and salary sacrifice superannuation deductions been flagged as RESC (Reportable Superannuation Contribution) if and only if the contributions or deductions facilitate contribution amounts that exceed the mandatory amount required to be paid under the superannuation guarantee (SG) scheme or under an applicable industrial award or agreement?

If transactions have already been processed against a superannuation contribution rate rule or a deduction header and the status of the RESC option was configured incorrectly, a custom script may need to be run to fix the historical transactions. If you require this, please FastTrack Customer Service.

  • No labels