PayGlobal
Page tree

Versions Compared

Old Version 21

changes.mady.by.user PayGlobal

Saved on

compared with

New Version 22

changes.mady.by.user SamA

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
HTML Wrap
classsection group

Lump Sum E amounts stopped being reported from any pays completed before upgrading to v4.66.

This impacts pays with a Lump sum in arrears payment (aka Lump Sum E) from the Tax Year you started using STP v4 to the last closed pay before upgrading to v4.66.

We expect this to impact PayEvents, Update Events and Finalisations 2022/23 tax year.

If you started using STPv4 in the 2021/22 tax year, then this will also impact any amendments, i.e. re-finalisations of 2021/22.

This issue has been caused by an enhancement introduced in v4.66 to cater for capturing the Lump Sum E Derived Tax Year.

To facilitate the ability to record a Lump Sum E Derived Tax Year, the PayGlobal schema was changed and STP was also changed to stop it from using TransHistoricalMaster.LumpSumE as its data source.

What

have we not advised...

we didn't let you know

  1. Remind you that PayGlobal does not usually back-fill new tables or new fields with historical data records.

  2. Inform you to review all “Lump sum in Arrears” payments that would be reported via STP v4 to confirm whether the amount related on one or more previous tax years, i.e. “Lump sum in Arrears” payments in pays linked to the 2022/23. Payments made in the 2022/21 tax year only need to be checked if you turned STPv4 on during the 2021/22 tax year.

  3. Inform you that you would need to have your HistoricalLumpSumE table manually updated via SQL script.
    This impacts pays from the Tax Year you started using STP v4 to the last closed pay before upgrading to v4.66. We expect this only impacts the 2022/23 tax year.

Checking if you're affected, and fixing the problem

HTML Wrap
classcol span_3_of_5
UI Expand
expandedtrue
titleWhat's the problem?
UI Expand
title
UI Expand
titleHow do I check if I have been impacted by this issue

We recommend running the File Analysis Report (CSV) - PGPRHIST003V.

  • Filters required: Period Type = Y.YTD, Period Range = 2022/23 tax year, Allowances = All allowances with ‘Lump Sum in Arrears’ set to Yes.

  • Sorting by Employee.Employeecode and Virtualhistoricaltransaction.PaySequence.

  • Output = CSV

If no records are returned, you are not impacted by this issue.

If records are returned, you will want to open the CSV output in MSExcel to consolidate the records to a YTD amount and then filter out employees that have a YTD total less than $1200.

If you turned STPv4 on during the 2021/22 tax year, then you will need to run this report again with Period Range = 2021/22 tax year

For online services customers

We are in the process of completing this step for you.

We will provide you with a report outlining the impacted employees and pay sequences.

For on premise customers you can run the report yourself or you can engage with Professional Services for assistance.

UI Expand
titleWhat if no employees received “Lump sum in Arrears” payments in effected tax years?

Then you do not need to do anything.

UI Expand
titleWhat if I have already sent a Finalisation to the ATO for 2022/23?

The ATO’s preference is that you send an Update Event to un-do the Finalisation, i.e. let the ATO know some/all of your data is not tax ready yet.

Once the missing data has been added to your database you can re-finalise (i.e. send a new Finalisation Event).

If not all employees are impacted you may want to complete this step just for those employees that are impacted.

UI Expand
titleWhat if I haven’t sent a Finalisation to the ATO for 2022/23

You will need to get the missing data added to your database before sending the finalisation for 2022/23.

UI Expand
titleWhat data do I need to add to my database

Firstly you will need to review the extracted transaction data to identify whether the “Lump sum in Arrears” payments related to a single tax year or if the transaction needs to be split across multiple tax years. This task can only be completed by you.

Then you need convert the extracted transaction data into a data source that can be used to populate the HistoricalLumpSumE table. Who completes this task is dependant on whether you are an online services customer or an on-premise customer.

The HistoricalLumpSumE table is structured as follows:

 

Field Name

Details

EmployeeCode

Identifies the employee the Lump Sum E payment belongs to

PaySequence

Identifies the pay sequence the payment came from

PayPeriodYTDCode

This is the YTD Code representing the ‘Lump Sum E Derived Tax Year’.
e.g. if the payment was linked to a pay with the Tax Year YTD code 2022/23, then Lump Sum E derived tax year must be 2021/22 or earlier.

Total Amount

This is the consolidated total amount from the ‘Lump sum in arrears’ allowances for the same employee, pay sequence and ‘Lump Sum E Derived Tax Year’.

 

For online services customers

Our professional services team will inject the data for you. After you have completed a review the data we extracted.

This is chargeable work and will be charged at time and materials rates due to the varying transaction volumes per customer database.

For on-premise customers

You can engage with our professional services team to complete this task for you. This is chargeable work and will be charged at time and materials rates due to the varying transaction volumes per customer database.

UI Expand
title

How does Lump Sum E reporting work in STP now?

For STP, PayGlobal now uses the HistoricalLumpSumE table (added in v4.66).
The HistoricalLumpSumE table gets populated when you close a pay. It consolidates Lump Sum E data from the HistoricalAllowance table by: Employee Code, Pay Sequence, PayPeriodYTDCode (aka Lump Sum E Derived Tax Year) and gives a Total amount for this combination.

When the STP submissions are generated, PayGlobal gets the reportable YTD amounts from HistoricalLumpSumE table by selecting all the records for the employee where the Pay Sequence belongs to the Payer/Tax Year being reported, then it groups the records by the Lump Sum E Derived Tax Year. Note: Lump Sum E will only be reported if the total YTD amount for the Payer/Tax year being reported (i.e. irrespective of the derived tax year((s)) is equal to or great than $1200.00.

 

 

 

UI Text Box
sizemedium
typewarningnote

Please contact your account manager or MYOB PayGlobal Support if you wish to book consulting for the above.

 

 

 

 

HTML Wrap
width15%
classcol span_1_of_5

 

HTML Wrap
floatleft
classcol span_1_of_5

 

HTML
<div style="display: none;" data-swiftype-name="country" data-swiftype-type="enum">Australia</div> <div style="display: none;" data-swiftype-name="country" data-swiftype-type="enum">New Zealand</div>

Copyright © 2023 MYOB Technology Pty Ltd. All rights reserved