- Created by PayGlobal, last modified by SamA on Jul 04, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 14 Next »
https://help.myob.com/wiki/x/tIsCBg
How satisfied are you with our online help?*
Just these help pages, not phone support or the product itself
Why did you give this rating?
Anything else you want to tell us about the help?
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, including Pay Events, 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.
The issue was 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 failed to do
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
HistoricalLumpSumEtable 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.
What you need to do to fix the problem
If no employees received “Lump sum in Arrears” payments in affected tax years, then you do not need to do anything.
If one or more of your employees did receive one of these payments, then you will need to correct the incorrect data. If you have already finalised this with the ATO, then you will also need to send an update event to re-do the finalisaiton. This process is different for on-premise and online services customers.
For on-premise customers, 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
Online services customers We are currently checking this for you. Soon, we will provide you with a report outlining the impacted employees and pay sequences.
If you're affected, we'll send you a report soon.
Once you have the report, follow these instructions to identify which and fix the issue:
To fix the issue, call your account manager to arrange an MYOB PayGlobal consultant to correct your data. This is chargeable work and will be charged at time and materials rates due to the varying transaction volumes per customer database.
If you have already sent a finalisation to the ATO, you also need to send an update event to undo the finalisation, then re-finalise once the data is fixed. If not all employees are impacted you may want to complete this step just for those employees that are impacted.
To correct your data, either:
- call your account manager to arrange an MYOB PayGlobal consultant to fix it (this is chargeable work and will be charged at time and materials rates due to the varying transaction volumes per customer database), or
- run an SQL script to correct your data.
Running a script:
- 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
HistoricalLumpSumEtable. 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’. |
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’. |
If you have already sent a finalisation to the ATO, you also need to send an update event to undo the finalisation, then re-finalise once the data is fixed.
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’. |
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.
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.