Page Comparison - STP not reporting Lump Sum E amount (v.27 vs v.28) - PayGlobal

HTML Wrap

class	section group

HTML Wrap

class	col span_3_of_5

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 we didn't let you know

Remind you that PayGlobal does not usually back-fill new tables or new fields with historical data records.
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.
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

UI Expand

title	How do I check if I have been impacted by this issue

On-premise customers

To check if you're affected, either contact your MYOB PayGlobal account manager to arrange a consultant to check for you (chargeable), or follow these instructions to check yourself:

Go to the allowances screen, and check which allowance have Tax override type set to Lump sum in arrears.
Run the File Analysis Report (CSV) - PGPRHIST003V.
Set these filters for the 2022-23 tax year:
- Period Type: Y.YTD
- Period Range: 2022/23 tax year
- Allowances: All allowances with Tax override type set to Lump sum in arrears (as above).
On the Sorting tab,sort by Employee.Employeecode and Virtualhistoricaltransaction.PaySequence.
Set the output to CSV.
Check whether you are affected:
- If no records are returned, you are not impacted by this issue.
- If records are returned, check whether any employees are over the threshold.
If you are affected, process the CSV file:
1. Open the file in Microsoft Excel
2. Consolidate the figures to year-to-date amounts.
3. Filter out employees with a year-to-date total less than $1200.
If you turned on STPv4 2021/22 tax year, repeat this process, using the filter Period Range: 2021/22 tax year.

If you have any employees remaining on your report after completing this process then you are affected, and will need to correct your records before finalising.

For online services customers

We will contact you soon with a report showing any impacted employees and pay sequences.

UI Expand

title	What if no employees received “Lump sum in Arrears” payments in effected tax years?

Only employees with Lump Sum in Arrears payments are affected by this issue.

If you don't have any employees in this situation, you are unaffected – you don't need to do anything at all.

UI Expand

title	What 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

title	What 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

title	What data do I need to add to my database

This data can only be updated via the backend (via SQL) and not via the front end (MYOB PayGlobal Application). If you require assistance with this you will require a consultant to be engaged, as mentioned.

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 (s) into an SQL Query 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’.

This excel document will help assist creating the relevant SQL Queries based on the information entered.

Please remove sample data entered and drag the scripts down to populate the relevant rows, then run the update script.

UI Text Box

size	medium
type	note

If you are using excel for this data, leading zero's on numeric fields will be removed.

Please ensure that you test this import via your test database first to ensure there are no errors and it is behaving as expected then backup Live before applying the changes.

For online services customers

An MYOB PayGlobal consultant will contact you to let you know if you are affected by this issue, and how to review the data to see what changes need to be made.

Once you have completed this review, our professional services team will update your database for you. Note that 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.

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

size	medium
type	note

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

HTML Wrap

width	15%
class	col span_1_of_5

HTML Wrap

float	left
class	col span_1_of_5

Panelbox

name	green
title	Related topics

MYOB PayGlobal help centre

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>

Page tree

Versions Compared

Old Version 27

New Version 28

Key

What we didn't let you know

Checking if you're affected, and fixing the problem

On-premise customers

For online services customers

For online services customers

For on-premise customers

How does Lump Sum E reporting work in STP now?