STP not reporting Lump Sum E amount

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.

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

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

For online services customers

We are in the process of completing this check for you. We will provide you with a report outlining the impacted employees and pay sequences.

For on-premise customers

• If you haven’t rolled your accumulators for 2022/23 yet, then you can use the Employee’s main browse grid to create a basic employee grid report to show Lump Sum E.

• If you have rolled your accumulators for 2022/23 - you can 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'

Note: The ‘YTD Code’ will be unique to each customer database.

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. However you are more than welcome to also run the File Analysis Report (CSV) - PGPRHIST003V, report as described for on-premise customers

For on-premise customers

You can either:

1. Run 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.
   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.

2. Run a SQL script <insert script here>

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:

For online services customers

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

For on-premise customers

You can do this step yourself using this SQL Update script <insert script>.
Or 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.