Single Touch Payroll Phase 2

When to report using STP v4

The mandatory start date for STP Phase 2 was supposed to be 1 January 2022.

However, MYOB received a deferral date of 31 August 2022 for all its products. This deferral date along with PayGlobal’s software release date will influence when you can/should start using STP Phase 2.

PayGlobal will be releasing STP Phase 2 enabled software as soon as we receive ATO approval. The timeframe is anticipated to be between March and mid-June 2022.

Unless your organisation has obtained an independent deferral from the ATO; your organisation must submit its first STP Phase 2 compliant submission on/before 31 August 2022.

If commencing part-way through a financial year, you may need to make historical data corrections to ensure the YTD amounts already submitted to your employees in the year you start using STP Phase 2 are correctly reported under STP Phase 2 reporting requirements. We recommend engaging with our Professional Services team to assist in this process.

For more details about the ATO’s deferral process, see Single Touch Payroll Deferrals on the ATO website.

IMPORTANT: STP Phase 2 preparation work involves changing your allowance/deduction record configurations. Such changes may impact Award and/or Payroll Rules.

We recommend engaging with Professional Services for assistance.

STP exemptions

There are reporting exemptions for a particular financial year or for certain types of employers, employees, and payments.

For more information, see Single Touch Payroll Exemptions on the ATO website.

Reminder: Employees that require exclusion from STP reporting must be linked to a Contract that "include in online tax reporting" = No.

What are the benefits of the change?

STP Phase 2 has been designed to streamline the reporting process and reduce the workload for employers by streamlining data sharing across Services Australia. Once you have implemented Phase 2, there is unlikely to be any further changes as it’s been future proofed as part of the design.

What’s not changing?

While you will need to report additional information in your STP report, there are many things which
aren’t changing, such as:

• The way you submit your pay events using the PayGlobal STP Manager Tool.
• Due dates for pay events is still on or before pay day unless you are eligible for a reporting concession.
• Taxation and superannuation obligations.
• End of year finalisation requirements.

Reporting by IncomeType/Country codes

Employee “Income type”

In STP Phase 2, the terminology previously known as Payment Summary Type has been replaced with a new term and definitions called “Income Type”.

The ATO use Income type codes to define how the employee's income is assessed by worker type.

This change has the most impact on those employee’s currently reported as Payment summary type “Individual Non-Business” (INB). The ATO now require this group to be split-up into 4 new types.

• Salary & Waged employees (SAW)
• Inbound Assignees to Australia (IAA)
• Closely Held Payees (CHP) will be supported in v4.63 (AU Tax Release)
• Seasonal Workers Programme (SWP) will be supported in v4.63 (AU Tax Release)

The following other Income types do not change how you identify them in PayGlobal.

• Working Holiday Makers (WHM)
• Labour Hire (LAB)
• Voluntary Agreement (VOL)
• Other specific payments (OSP)

For more information go to the ATO website - https://www.ato.gov.au/Business/Single-Touch- Payroll/In-detail/Single-Touch-Payroll-Phase-2-employer-reporting-guidelines/?page=4#Income_types

How does PayGlobal support income type?

PayGlobal will automatically derive the income type based on the following settings:

• Employee’s contract Include in online tax reporting
  (Employee.ContractTypeCode | Contract.IncludeOnlineTaxReporting.
  Used to define whether the employee is including in STP submissions or not.
• Employee’s Contract Type
  (Employee.ContractCode | Contract.ContractType)
  Used to define which Payment Summary group the employee belongs to as well as identifying what type of employment contract the employee is on..
• Employee’s Tax Rate
  (Employee.TaxCode)
  Applies to Working Holiday Maker employees only.
• Employee’s Inbound Assignee. NEW field added in v4.59
  (Employee.InboundAssignee)

IMPORTANT: It is recommended that you review all employees who will be reported via STP Phase 2 to ensure they are correctly assigned to their respective categories.

The following table shows the expected setup/mapping of STP Phase 1 (aka v3) vs STP Phase 2 (aka v4):

Viewing the income type

Income type is a field that can be added to Transaction View via the Customise Columns feature. The system derived income type is visible after processing a pay.

Record keeping for inbound assignees

The Tax tab on the Employee record contains two new fields:

• Inbound assignee: If your organisation has employees defined as an Inbound Assignees to Australia (IAA); then you must the Inbound Assignee field to “Yes”.
• Prior tax country: If your organisation has employees defined as an Inbound Assignees to Australia (IAA) or Working Holiday Maker (WHM). You must also set the Prior tax country field – See Countrycodes for more details.

Country codes

Australia has tax treaties with many countries to reduce or eliminate double taxation caused by overlapping tax jurisdictions.

Recording a country code for tax purposes assists Australia to meet its international commitments.

Recording of a country code for tax purposes explicitly impacts employees classed as Inbound Assignees to Australia (IAA) or Working Holiday Makers (WHM):

• IAA employees must report the country they were a tax resident of before coming to Australia.
• WHM employees must report their “home” country.

How does PayGlobal support Country codes for tax purposes?

PayGlobal supports the country code you need capture via a new field called Prior tax country, located on the Tax tab of the Employee record.

Cessation types

The ATO now collects data that was previously reported to Centrelink via an Employment Separation Certificate. One of the data items the ATO required for the Department of Services is a Cessation Reason.

PayGlobal supports the cessation type you need to capture in a new field called Cessation reason; located on the Termination reasons table.

Cessation type code are as follows:

• V (Voluntary Cessation) An employee resignation, retirement, domestic or pressing necessity or abandonment of employment.
• I (Ill Health) An employee resignation due to medical condition that prevents the continuation of employment, such as for illness, ill-health, medical unfitness or total permanent disability.
• D (Deceased) The death of an employee.
• R (Redundancy) An employer-initiated termination of employment due to a genuine bona-fide redundancy or approved early retirement scheme.
• F (Dismissal) An employer-initiated termination of employment due to dismissal, inability to perform the required work, misconduct or inefficiency.
• C (Contract Cessation) The natural conclusion of a limited employment relationship due to contract/engagement duration or task completion, seasonal work completion, or to cease casuals that are no longer required.
• T (Transfer) The administrative arrangements performed to transfer employees across payroll systems, move them temporarily to another employer (machinery of government for public servants), transfer of business, move them to outsourcing arrangements or other such technical activities.

PayGlobal uses the Cessation reason from the Termination Reason record linked to the Employee when you send STP data to the ATO.

The employee record only holds “current” data, if an employee has been rehired or changed employers, PayGlobal will source the correct data from the EmployeeHistory table.

Disaggregation of Gross

The employee “Gross” amount you report to the ATO has been disaggregated into different income assessment groups with each group reported as separate amounts. The social services agencies require these income assessment groups to administer their programmes.
The amount that was reported as “Gross” for Individual Non-business employees in STP Phase 1, will now in STP Phase 2, excludes payments classified as the following:

• Paid leave
• Allowances (extension and rule changes to what was already reported)
• Overtime
• Bonuses and commissions
• Directors’ fees
• Lump sum W (return to work payment)
• Salary sacrifice

There are rules that define what can be included against each income type.

PayGlobal supports these rules with the following changes made to the Allowances table:

• All leave allowances will require the “Subtype” field to be populated.
• “ATO reporting category” options
• “ATO reporting subcategory” options
• Validation on allowance setting combinations
• Automated mapping of your allowance records to the new Subtype, ATO reporting category and ATO reporting subcategories on upgrade and/or saving the Allowances record.

Not every allowance can be automatically mapped to a valid SUBTYPE, ATO REPORTING CATEGORY and ATO REPORTING SUBCATEGORIES. The reason being, the PayGlobal schema does not hold enough information about your Allowance records to make business operational decisions that may be unique to your organisation. After upgrading, you are strongly advised to review the settings of all your allowances and adjust as necessary.

Paid Leave

Paid Leave is required to be reported into the following groups:

• Other paid leave
• Paid parental leave
• Workers’ compensation
• Ancillary and defence leave
• Cash out of leave in service
• Unused leave on termination (paid leave type U)

Why is paid leave now being reported distinctly instead of remaining as part of Gross Income?

• Services Australia will be using this information as part of the 'income tested payments affected by leave payments.
• ATO will be using this information to analysis minimum legal obligations for ordinary time earnings (OTE).

What is not included in “Paid leave”:

• Lump sum A – this is already separately reported and does not change.
• Lump sum B – this is already separately reported and does not change.
• Casual loading paid to compensate the employee for the lack of paid personal or annual leave
• Other ETP Leave payments i.e. RDO, TOIL and Personal leave.
• Overtime related leave payments.
• Return-to-work payments made the employers Worker’s Comp. Insurer.
• Unpaid leave i.e. any absence from work transacted as non-paying)

What are the Paid Leave changes in PayGlobal?

• Leave allowances can no longer be used for more than one purpose,
  e.g. An allowance used for leave is taken CANNOT be the same allowance used to pay-out unused leave on termination.

• “Time off in Lieu” (TOIL) allowances that relate to overtime, must be reported as “Overtime” not “Paid leave”.

  

  If you currently use only one allowance for this purpose you will now require two, one in relation OTE hours (this is deemed “Paid leave”) and the other in relation to overtime hours.
• All leave allowances will require the “Subtype” field to be populated.
• Leave allowances that have balances tracked through PayGlobal, i.e. those with Allowance types:
  L. Annual leave, O. Long Service Leave, S. Sick/Special leave and V. Leave Credit paid, will be automatically mapped to the required Allowance Subtype on upgrade to v4.59 or newer. For new allowances created, extra validation has been included to help the decision making process.
• Leave allowances that do not have leave balances tracked through PayGlobal, i.e. those with Allowance types A.Allowance or H.Hourly will require the Subtype and the ATO Reporting
• Category/Subcategory to be manually set. This is because it is not automatically possible to determine what the leave is for. And depending on what the leave is for, the ATO may require it to be reported as something other than paid leave.
• 6. You will need to review how your database is configured to manage leave loading.
  • a) Leave loading allowances must be assigned the Subtype prefixed with “Leave loading”
  • b) All three of the following fields must populated or must all be left blank
    • “Loading cash-out allowance” on the Details (ii) tab of Allowance records that represent leave cashed-out during service.
    • “or Loading allowance” on the Values tab of Annual Leave Table records
    • “or Loading allowance on termination” on the Values tab of Annual Leave Table records Loading for leave taken, cashed-out and termination must be distinct allowance records This is necessary to ensure leave loading monetary values are correctly reported to the ATO.

Allowance Payments

In STP Phase 1 reporting, some allowances are reported separately, and some were reported as part of gross income.

In STP Phase 2, you now need to report all allowances separately. This impacts most income types, not just expense allowances that may have been deductible on your employee’s individual income tax return.

The allowance payment types you will separately report in STP Phase 2 are:

• cents per km (allowance type CD)
• award transport payments (allowance type AD)
• laundry (allowance type LD)
• overtime meal allowance (allowance type MD)
• domestic or overseas travel (allowance type RD)
• tool allowances (allowance type TD) (new)
• qualification and certification allowances (allowance type QN) (new)
• task allowances (allowance type KN) (new)
• 7x new other allowance type categories (allowance type OD)
  • Non-deductible (ND)
  • Uniform (U1)
  • Private Vehicle (V1)
  • Home Office (H1)
  • Transport/Fares (T1)
  • General (G1)
  • Job Keeper (see allowance change details)

Allowance change details

• Allowances Types: CD, AD, LD, MD and RD have some new ATO guidelines. If you are unaffected by the new guidelines, the only change is how the data displays in the STP payload.

• Allowances Types: TD, QN and KN must now be reported in STP Phase 2 as distinct allowance type payments. In STP Phase 1, it is likely these montary amounts reported where either included in Gross Income or reported as an “other” allowance.

  

  In PayGlobal these allowances will require the ATO Reporting Category and/or ATO Reporting Subcategory to be manually set.
• Your existing ‘Other’ allowances will be automatically remapped on upgrade to the ATO Reporting Subcategory of “Other – general”. However, as it is unlikely that all of them belong in the general category, you must review post-upgrade and manually set to the correct “Other - …..” option
• Job Keeper allowances do not change. The codes that are to be reported continue to be sourced from the PayGlobal Allowance Code field. You will need to ensure all your Job Keeper allowances are correctly linked to the ATO Reporting Category “Allowance Type” and ATO reporting subcategory “Other – Job Keeper”.

Don't report:

• Reimbursements – These are an amount that reimburses an expense which was (or will be) incurred by the employee in the course of their duties and can be verified by receipts some reimbursements may be subject to FBT.
• Fringe benefits – These are not amounts that you are paying to your employee. These amounts (if reportable) will continue to be identified using the ATO Reporting Category “Reportable fringe benefit”

What do I need to do?

You must review your allowance settings post upgrade. Please refer the hyperlinks on the Allowance Types list above for more details to help you determine whether you need to remap your existing allowances and/or create new allowance record to support the new rules. Or go to the ATO’s Single Touch Payroll Phase 2 employer guidelines. The direct link to the Allowances details are here: https://www.ato.gov.au/Business/Single-Touch-Payroll/In-detail/Single-Touch-Payroll-Phase-2-employer-reporting-guidelines/?page=4#Allowances

Changing your allowance configuration may impact Award and/or Payroll Rules.

If you are unsure, please contact Professional Services for assistance.

The allowance payment types are supported in PayGlobal via the ATO Reporting Category and ATO Reporting subcategory fields on the Allowances entity.

PayGlobal Setup > ATO Reporting

The following table shows how your PayGlobal Allowance configurations will be reported in STP.

Overtime

You will need to review how your organisation has been recording/transacting payments relating to Overtime, i.e. work done:

• Beyond their ordinary hours of work
• Outside the agreed number of hours
• Outside the spread of ordinary hours (the times of the day ordinary hours can be worked)

This means you will need to check the Include in Super OTE flag is correctly set to “Yes” and the ATO reporting category has been set to “Overtime”.

Special cases to be reported as overtime:

• TOIL (time off in lieu) allowances; only cashed-out amounts are to be reported as overtime. If you have been using one allowance to manage TOIL, you will now require a minimum of 3:
  • TOIL taken
  • TOIL cashed-out
  • TOIL unused leave on termination
• Call back/recall allowances; are overtime when an employee has left the workplace or completed their ordinary time without any prearranged agreement to work overtime but is called back to work overtime.
• On-call/Stand-by or Availability allowances; may or may not be classed as overtime. Please check the employee’s Award. For example, if paid as per:
  • clause 31.2 of the MA000036: Plumbing and Fire Sprinklers Award 2010. These types of payments are not ordinary time earnings and should be reported as Payment Type – Overtime
  • clause 20.3 of the MA000031: Medical Practitioners Award 2020. These payments are ordinary time earnings and should be reported as Allowance Type-KN (Task Allowances).
• Leave loading that is demonstrably referable to a notional loss of opportunity to work overtime is not ordinary time earnings and should be reported as Payment Type – Overtime.
• Commissions & Bonuses
  • Commissions & Bonuses that are wholly referable to overtime hours worked are not ordinary time earnings and should be reported as Payment Type – Overtime.
  • Commission referable to ordinary hours worked must be reported as Payment Type – Bonuses and Commissions.
• Identifiable Overtime component of Annualised Salary – If not already setup as separate allowance, it will now need to be so.
• Part time additional hours that are paid at a penalty or overtime rate that do not accrue leave entitlements. If not already setup as separate allowance, it will now need to be so.
• Travelling time, travelling time outside of ordinary span of hours. If not already setup as separate allowance, it will now need to be so.
• Driving rates/kms the excess of the total ordinary hours per period, if no regard to the terms of the award, or the stipulated overtime rate for piece-rate awards that include hourly driving rates and rates per kilometre are not ordinary time earnings. If not already setup as separate allowance, it will now need to be so.

Bonuses and Commissions Amount

Only bonus and commission payments that relate to OTE hours are to be reported as Payment Type
– Bonuses and Commissions.
In PayGlobal your;

• OTE Bonus allowances will need to be mapped to ATO reporting category “Bonus”.
• OTE Commissions will need to be mapped to ATO reporting category “Commission”.

Important: If you have not previously had separated bonus or commission amounts into OTE and non-OTE payments you will now need to have these as separate allowances.

Directors Fees

Directors’ fees include payments to a director of a company, or to a person who performs the duties of a director of the company.

In PayGlobal your allowances will need to be mapped to ATO reporting category “Director fee”

CDEP Amount

CDEP values are no longer reportable, but the STP schema still includes a space for it. The monetary value will be zero or blank.

Salary Sacrifice Amount

In STP Phase 1, there was no requirement to report Salary Sacrificed amounts. As a result employee’s that sacrificed 100% of their salary were not included because their “Gross” was $0.00.

In STP Phase 2, the value of all salary sacrifice amounts, except those relating to Reportable Fringe Benefits or Exempt Foreign Employment Income are required to be reported as follows:

• Superannuation (S) – an effective salary sacrifice arrangement, entered into before the work is performed, where contributions are paid to a complying fund, where the sacrificed salary or wages are permanently foregone.
• O (Other Employee Benefits) – an effective salary sacrifice arrangement, entered into before the work is performed, for benefits other than for superannuation, where the sacrificed salary or wages are permanently foregone.

Salary Sacrifice – Other Employee Benefits

The following configurations will be reported as Salary Sacrifice “Other Employee Benefits”:

• Deductions
  • Taxable = Yes
  • Superannuation Deduction = No
• Allowances
  • Salary Sacrifice = Yes
  • Superannuation Allowance = No

Salary Sacrifice - Superannuation

The following configurations will be reported as Salary Sacrifice “Superannuation”:

• Deductions
  • Taxable = Yes
  • Superannuation Deduction = Yes
• Allowances
  • Salary Sacrifice = Yes
  • Superannuation Allowance = Yes

IMPORTANT: On the 1st January 2020, the Treasury Laws Amendment (2019 Tax Integrity and Other Measures No. 1) Bill 2019 changed the law to ensure that an individual’s superannuation salary sacrifice contributions cannot be used to reduce OTE or count towards a payer’s minimum superannuation guarantee contributions, if the pre-sacrifice payment was salary or wages for superannuation guarantee purposes.

In other words, no Superannuation Fund records should be using these fields anymore.

Lumps Sums

Lump Sum E

Now requires the associated financial year(s) to be reported too.

Limitation: PayGlobal does not currently provided the ability to record which financial years a back payment relates to. It will report all Lump sum E amounts as the financial year before that which the rest of the submission relates to.

Lump Sum W (return to work)

Lump Sum W is a new payment amount for STP Phase 2.

A “Return to Work” amount is paid to induce a person to resume work, for example, to end industrial action or to leave another employer. It does not matter how the payments are described or paid, or by whom they are paid.

These types of payments, to induce workers to return to the workplace, cannot be classified as Payment Type – Bonuses or Commissions or Lump Sum Type-E but must be taxed as “Return to Work” payments (as per NAT3347 Return to Work Payments) and reported as Lump Sum Type-W YTD amounts.

PayGlobal will support this as follows.

You will need two separate allowances records:

1. Return to work for non-working holiday makers
   1. Set ATO reporting category to “Return to work”
   2. Set Tax override type to “Return to work” (in existing allowances this will be blank. This ensures the employee is correctly taxed as per the NAT3347).
2. Return to work for Working Holiday Makers
   1. Set ATO reporting category to “Return to work”
   2. Set Tax override type to “blank” (this ensures the employee is correctly taxed as per the NAT3347).

Backpays

Some ATO documention has the following statements:

• If there are several different payment types to be paid in arrears, they cannot be bundled into one single “back pay” code and processed through payroll.
• ….STP Phase 2 require the components of the back payment to be separately itemised
  This could be interpreted as all back payments needing to be reported against respective ATO Reporting categories; e.g. backpay on leave taken due to a pay rise.

The ATO have clarified to PayGlobal that amounts for back payment of remuneration that accrued, or was payable,

• less than 12 months before the date of payment are to be reported separately
• more than 12 months before the date of payment continue to be reported only as Lump sum E

Important: You will need to review the setup of your backpay Allowance record settings. Given that components of the back payment are expected to be separately itemised, this may involve the need to create a new set of back pay allowance records. Refer to the STP Phase 2 Transition Manual for Recommended Allowance Setup

Child support garnishees and Child support deductions

The ATO are now collecting Child Support payment data on behalf of Services Australian. This must be reported as either:

• Child support – This reflects deductions made under a notice as per section 45 of the Child Support (Registration and Collection) Act 1988.
  These are your standard child support repayments.
• Child support garnishee - This reflects deduction made under a garnishee notice as per section 72A of the Child Support (Registration and Collection) Act 1988.

PayGlobal supports this via options L. Child support standard and R. Child support garnishee within the Deduction Class field on the Deductions table.

If not, it is recommended that you engage with Professional Services, to assist with cleansing historical pay data for the 2021/22 tax year.

Removal of the Onboarding section (aka TFN Declaration data)

This data has been replaced with “Employment Basis Codes”, “Tax Treatment Codes” and “Tax offset Amount”. Other fields have just moved to new locations within the payload.

Employment Basis Codes

PayGlobal will automatically handle the codes to be assigned to each employee. Reporting of this value is based off the following settings:

• Whether the record is for an ETP death beneficiary
• Employee’s income stream
• Employee’s “Employment Status” at time of submission (i.e. Employee.EmploymentStatus Code | EmploymentStatus.StatusType)

Tax Treatment Codes

Tax Treatment codes help the ATO identify how the employee’s monetary tax values have been calculated.

PayGlobal automatically calculates the codes to be assigned to each employee. A full mapping of these codes is located in the MYOB PayGlobal STP Phase 2 Transition Manual.

Tax Offset Amount

Reporting of Tax offset amounts a new for STP Phase 2. This value will come from the employee’s Total rebates field, located on the Tax tab.

The employee record only holds “current” data, if an employee has been rehired or changed employers, PayGlobal will source the correct data from the EmployeeHistory table.

Transferring Payee YTD amounts

The ATO uses the BMS ID and Payroll IDs reported with each STP submission like a serial number. It identifies the relationship between employers, employees and the software product/software product instance the data has come from.

When employees change payers within the PayGlobal database or the environment that the payroll data is stored in, this impacts the BMS ID and in some cases the Payroll ID too.

In STP phase 1, changes to BMS IDs and/or Payroll IDs resulted in employee(s) having multiple payment summary records with MyGov and YTD values being incorrect due to some DSPs not catering for the zeroing out method for reporting changes.

In STP phase 2, the ATO has added two new fields to STP which can be used to report replacement of BMS ID and/or payroll IDs as an alternative option for transferrring YTD amounts.

• Previous BMS ID
• Previous payroll ID(s)

PayGlobal supports reporting of previous BMS IDs and Payroll IDs via the Updates tab in the STP Manager Tool. The Updates tab has new button called Update Payee(s).

Migrating to PayGlobal

If you choose not to transfer employee YTD amounts from your previous payroll system to PayGlobal, you do not need to tell the ATO about any changes.

If you do choose to transfer employee YTD amounts from your previous payroll system to PayGlobal, you will need to import the YTD amounts into PayGlobal using an opening balance pay. Once the Opening balance pay is closed, you can then create an Update Event to inform the ATO of the transfer.

Migrating from PayGlobal

If you choose not to transfer employee YTD amounts from PayGlobal to your new provider, the only task you need to do is send the ATO a new Finalisation submission after closing the last pay to be generated by PayGlobal.

If you do choose to transfer employee YTD amounts from PayGlobal, you will need to engage with Professional Services to assist in the data export. But as far as STP goes, you will not need to any other submissions once the Pay Event from the last pay to be generated by PayGlobal.

Previous BMS ID

Each change of BMS IDs must only be reported once.

It will allow the ATO to identify that the payer has transferred the YTD amounts that had been reported for the financial year under an old BMS Id and to not display these previously reported YTD amounts as an Income Statement or pre-fill into the IITR.

When to report a preview BMS ID

• Your organisation has recently migrated to PayGlobal from another software provider AND you have imported your YTD values.
• Your organisation has consolidated data spread across multiple databases.

How to report a previous BMS ID

To report a change of BMS ID, you must create a new Update submission.

Previous Payroll ID

Reporting a previous Payroll ID allows the ATO to identify that this is a continuation of an existing employment relationship. It signals to the ATO that the payer has transferred the YTD amounts that had been reported for the financial year under an old Payroll Id and to not display these previously reported YTD amounts as an Income Statement or pre-fill into the IITR.

When to report a preview BMS ID

• Your organisation has recently migrated to PayGlobal from another software provider AND you have imported your YTD values AND your employee has a different employee code in PayGlobal compared to your legacy system.
• Your organisation has consolidated data spread across multiple databases AND as part of that exercise the employee's employee codes were changed.
• Your organisation has outgrown the employee code character set and the employee codes have been replaced with a new character set

How to report a previous BMS ID

To report a change of employee Payroll ID, you must first create a CSV file that contains both the old and new payroll IDs for each applicable employee. The following conditions apply:

• The file name must begin with "STPEmployeePreviousIDs" and end with ".csv".
• The file only needs two fields: PreviousEmployeeCode, EmployeeCode
• Each field on every row must be populated.
• The file must be stored in the data directory’s Import folder.

Once the file is ready complete the following steps in PayGlobal:

Undoing a Finalisation

Prior to STP Phase 2 PayGlobal did not support the ability undo Finalisation submissions for previous tax years. Meaning, it was not possible to use PayGlobal to advise the ATO that a finalisation had been sent too early/by mistake if the tax year had only just rolled over.

In v4.61 and beyond, it is now possible to send an Update submission for ANY tax year/payer/payee combination and set the Finalisation flag to false.