Important Notices & Breaking Changes V12.15P2 and V12.17

The enhancements described in the related pages below represent significant functional changes that you must be aware of prior to upgrading to this release. Some of these enhancements require specific actions before or immediately after upgrading and are therefore highlighted here for your reference. Please refer to the relevant sections of this What’s New Guide, as identified below, for detailed information about each enhancement and any configuration that is required.

Changes to Interpreted Timesheet Statuses (v12.15p2)

Significant changes have been made in this release to interpreted timesheet statuses whereby instead of two system-defined statuses of Not Reviewed and Reviewed, custom status names can be configured and can be mapped to one of the following status types: Not Reviewed, Reviewed - Pay Only, Reviewed Bill Only, Reviewed - Pay and Bill.

For more information, see Support for Custom Interpreted Timesheet Statuses.

Default Interpreted Timesheet Status for Adjustment Timesheets (v12.15p2)

From this release onward the default interpreted timesheet status for adjustment timesheets cannot be a status with a status type of anything other than Not Reviewed. For more information, see:

Interpreted Adjustment Timesheet Default Status (WIP)

Service Maintenance Moved to Global Maintenance (v12.15p2)

In this release, Services Maintenance has been moved from Recruitment Manager > Maintenance to Maintenance > Global. For more information, see Enabling Automatic Invoicing of Services.

Invoice Terms Moved to General Maintenance (v12.15p2)

Billing terms (also known as invoice terms) were previously maintained under Billing > Maintenance > Invoice Terms and have now been moved to a centralised maintenance area combined with pay terms maintenance.

On upgrade each set of invoice terms that previously existed are assigned a terms type of Bill. For further details, please refer to page Payment and Billing Terms Maintenance.

Breaking Changes to API’s (v12.15p2)

TIS - GET Timesheet API has been modified to included timesheetHeaderId in the response. The path is: {{host}}/timesheet?

Australian Payroll STP v12.17 > Important actions for Payroll Administrators to take prior to first STP submission following upgrade to 12.17

Important actions need to be taken before you submit any STP batches to the ATO after upgrading. See Pay Australia STP Phase 2 - Actions to take prior to your first STP Report in v12.17 for details.

Australian Payroll STP > Important information about payee type for Working Holiday Makers (v12.17)

Payees who are working in Australia under a Working Holiday Maker (WHM) visa must be reported in STP Phase 2 under the WHM income stream. Currently, FastTrack360 allows WHM payees to be configured with a payee type of Labour Hire. Labour Hire is itself a separate income stream under STP Phase 2 and therefore any payee configured with a payee type of Labour Hire will be reported under the Labour Hire income stream.

Therefore, if you employ WHM payees it is important that you check the payee type to ensure it is set to Individual Non Business and not Labour Hire. That will ensure that WHM payees are reported under the correct income stream, which will be derived from a combination of the payee type of Individual Non Business and the tax status of Working Holiday Maker.

For more information about income streams under STP Phase 2 reporting, see Overview of STP Phase 2 | Income stream and tax treatment codes replace payment summary type.

Australia Payroll STP > Mapping of Termination Reasons (v12.17)

Under Single Touch Payroll (STP) Phase 2 reporting it is necessary to report an employment cessation reason when reporting the earnings of a payee whose employment has been terminated. Because of this, configuration has been added to Termination Reason Maintenance in the Payroll Australia module to allow termination reasons to be mapped to ATO-defined employment cessation reasons.

It is important that you map all termination reasons that are configured in your system that are currently used or that have been used in the past, including those that are now flagged as inactive, to the relevant, corresponding cessation reason before you submit any STP batches to the ATO after upgrading.

If you do not map termination reasons to the corresponding cessation reasons prior to continuing STP reporting post upgrade, the ATO will reject submissions for payees who have been terminated with a termination reason that is not mapped to a cessation reason. That includes payees who were terminated in prior periods and have subsequently been paid in an adjustment pay batch.

For more information, see Termination Reasons Mapping.

Australian Payroll STP > Mapping of Allowance Types (v12.17)

Under Single Touch Payroll (STP) Phase 2 reporting all taxable allowances, not just those allowances that receive concessional tax treatment, must be itemised by allowance type for payees with a payee type/income type of Individual Non Business.

Because of this, all existing taxable allowance pay codes will, by default, be flagged to be itemised for the purposes of STP reporting. For those allowance pay codes that were not required to be itemised under STP Phase 1 reporting, it will be necessary to map the allowance pay codes to an allowance type so that allowances can be reported according to the correct type via STP.

It is important that you map all taxable allowances that are to be itemised in STP reporting to their corresponding allowance type before you submit any STP batches to the ATO after upgrading.

If you do not map all taxable allowances that are to itemised to their corresponding allowance types, the ATO may reject submissions for payees who have been paid such allowances.

For more information, see Enhancements to Allowance Pay Codes.

NZ Payroll > IRD Payday Filing Authentication Changes (v12.17)

Due to recent changes to how the New Zealand IRD handle connections between their systems and payroll service provider software, an enhancement has been made to FastTrack360 that affects the process by which a login is initiated and maintained between FastTrack360 and the IRD for the purposes of submitting Payday Filing reports.

The enhancement is a technical change that has no functional impacts but on upgrading to v12.17 it will be necessary to re-authenticate the IRD login credentials for each pay company that submits Payday Filing reports to the IRD. For information on how to do this, please refer to the procedure on the second half of the following page: How to Configure a Pay Company for Payday Filing - FastTrack360 Online Help - Confluence (atlassian.net),