STP ERROR - Lumps sum E values not reported post 4.66 upgrade

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 to confirm whether the amount related on one or more previous tax years.
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.

Then you do not need to do anything.

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 you have added the missing data 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.

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

If you haven’t rolled your accumulators for 2022/23 yet, then a basic employee grid report to show Lump Sum E.

If you have rolled your accumulators for 2022/23 - run the File Analysis Report (CSV) - PGPRHIST003V report described in the next FAQ or run a the following SQL query

select thm.paysequence,thm.employeecode,thm.LumpE
from transhistoricalmaster as thm
inner join TransPerPaySequence tpps on tpps.PaySequence = thm.PaySequence
Where tpps.YTDCode = ‘TY2223'

The YTD Code will be unique the customers database.

Run the File Analysis Report (CSV) - PGPRHIST003V, with filters for 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.

With the File Analysis Report (CSV) - PGPRHIST003V report , you will need convert this into a data source that can be used to populate the HistoricalLumpSumE table.

The CSV file will give you a total per employee per pay sequence per allowance code setup with Tax override type ‘Lump sum in arrears’
The HistoricalLumpSumE table requires one record per employee per pay sequence, per PayPeriodYTDCode (aka Lump Sum E Derived Tax Year) i.e. the allowance total is consolidated. In other words if the tax year you are trying to finalise is 2022/23, then the Lump Sum E derived tax year must be 2021/22 or earlier.

or 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.

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

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