Part A - Items to address ***

1. What happens to the YTD figures when a Pay Period flows into the next year, e.g. Weekly paid employee Week Start: 28/12/2020 and Week Finish is: 03/01/2021.
2. Sitla sent a message on skype saying fields have changed. Can you send us details on the change sith supporting documents?
3. We need all 4 files outlined in this case tested as well as the 5th format code-named "EMD2020"
4. Can you also test scenarios such as
   1. Lumpsum payments
   2. Directors remuneration
   3. Bonus Overtime
   4. Redundancy
   5. LumpSum Payment Approval Number
   6. One-Off payment
   7. FNPF Deduction

Part B -  Reply from FRCS on Pay Day Reporting ---

Please refer attached specification and their usage below :

Your questions are answered in red.

1. Does the output file needs to excel instead of CSV? This will be in excel 
   1. This is in LinkSOFT -Rashna
2. Do we need the option to generate the EMS files by pay? That is a separate file for each pay team? It will be payday you can file weekly, fortnightly, monthly and bi-monthly and submit at the end of the month
3. Should there be any empty/ null columns in the file, the default value should be 0? Put 0 if no value
4. Rajesh has earlier confirmed that our file has passed the test and only date format was an issue and requested for excel. I have asked for the new format but received no response as usual.The new format is attached .
   1. The date format is different for the ECAL Pre and Post files, field sizes had been added to the specification - Rashna
   2. No evident change in the PayDay file specification, attached to the case for UAT.

Items 2, 3, and 4 above need to be designed in LinkSOFT

HI Rashna, we have addressed items 3 and 4 as they are small changes. THis change will be on Monday's build, however, we still do not have clarity on item 2. Here is what we need:

1. Using the demo environment, create two pay teams, WEEKLY and MONTHLY
2. Create 5 employees and assign 2 employees to Team WEEKLY and 3 employees to team MONTHLY
3. Process one WEEKLY PAY on the 10 of JANUARY and another payment on the 25th of JANUARY
4. Process team MONTHLY for the month of JANUARY
5. Give us a sample of the OUTPUT file for Pay Day Reporting for January 2020

TPOS Templates provided by FRCS

Hi Alvis,

Attached are the 2 templates we downloaded from TPOS this morning. I will obtain the other 2 file templates from FRCS directly from the portal.

Regards,
Sitla.

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0217

2. The following changes were made(Include Database object names, Program classes and any other relevant information):

1. Add a VIEW option at the end of the Integration to alow user to View Data and export to Excel as required
2. Added custom name to identify the file
3. Ensured the 4 files are in the specifications attached in this case.

3. Affected Areas:

1. Tax File Integration

4. The issue was caused by:

1. Legislative Requirement changes

5. Notes: 
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N): No. FRCS is constantly changing requirements which is causing the delay of V12.30 release

2. Variations to the approved design:

Use the following steps to upload the file to the FRCS portal:

1. Download the Excel (xlsx) file from Tax Submission -> View grid
2. Open the downloaded file in excel then save the file.
3. Submit the file to FRCS portal.

The following tests have been completed in version 12.30.0218

TEST - Pay Day Manual

1. Sitla created Jan Monthly pay in LinkSOFT Internal system, exported the file, and successfully imported it into TPOS
2. The same was done for Feb 2021

FRCS has not provided us with a test environment so there is no way to test the other scenarios.

We have verified the file format as best we can and will release this in V12.30

Next Step:

1. Test all 4 files and give us the go-ahead to proceed with release.

Hi Sanjay.

Response from FRCS as per below as per Email Log:

Can someone help answer this query? Given the following use case where the business has a paid employee under the following Pay Period Dates, what would be the expected Employment Start Date & Employment End Date in Payday Report files?

• The first pay of 2021 had start dates from Dec/30/2021 – does this need to be forwarded to Jan/01/201 in Payday File > Employment Start Date?
• Period# 3 has overlapping dates Jan / Feb, does this mean for Payday File #3 – Employment Start Date will be Feb/01/2021?
• When uploading Period#3 file to the TPOS system, will the Start Date need to be pushed to Feb/01/2021 as well?

• The first pay of 2021 had start dates from Dec/30/2021 – does this need to be forwarded to Jan/01/201 in Payday File > Employment Start Date? 1/1/2021
• Period# 3 has overlapping dates Jan / Feb, does this mean for Payday File #3 – Employment Start Date will be Feb/01/2021? Use February 1/2/2021 to 9.2.2021
• When uploading the Period#3 file to TPOS system, will the Start Date need to be pushed to Feb/01/2021 as well? Okay.

This is just for the first few months. We are making changes now and will advise as soon as it is done meaning it will accept dates as below.

Hi Sitla,

Comment 10 is not clear.

Can you fill in table 1 below:

Hi Sanjay,

See Below: Only the overlapping dates get pushed to the next month as the actual process and payment dates fall in the next month. Therefore gross is added accordingly in Year to Date Figures. Pays that fall within the month are fine, and date remains as is.

Updated as per below Email Log

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0219

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Changed "Employment Start Date" to align with the same month and year as the "Employment Finish Date"

3. Affected Areas:

1. PayDay Reporting Integration

4. The issue was caused by:

1. Change Request 

5. Notes: We have has to go back and forth many times. The standard of documentation is poor and incomplete. The changes in this request are not clear and may result in inaccurate information being sent to TPOS.
6. Next Step: UAT. Test the following scenarios on top of your standard test

1. Pay scenarios covering Table 1 of Comment 12
2. Special Pay - then output the file and verify numbers
3. Normal Pay after SPecial Pay - verify numbers
4. Back pay processing - verify numbers

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N): No - FRCS is constantly changing requirements. Requirements document is incomplete and does not cover required scenarios

2. Variations to the approved design:

PART A - Development work for this case has been completed.

1. The change will be available in version:12.30.0222

2. The following changes were made(Include Database object names, Program classes, and any other relevant information):

1. Changed Date format for POS ECAL and all other files to DD/MM/YYYY and uploads to TPOS was failing
2. Removed Detail View Grid Formatting to resolve "time" portion in Payroll dates
3. Added validation for "Classification" as this affects the Employee "Gross Pay Amount" export in PayDay files. All "Pay codes" used in Payday require Classifications. Where classification is not required, we have added the option to select "Not Applicable"

3. Affected Areas:

1. Payroll Processing ~> Tax Integration - for Pay Day Reporting

4. The issue was caused by:

1. CHange in FRCA Specification

5. Notes: Sitla tested these files and they have passed. SO we will need to build the changes and test this before releasing GA.
6. Next Step: UAT

----------------------

PART B - Development Reference:

1. Changes implemented was according to the approved design (Y/N):

2. Other relevant notes:

Tested Results in TPOS as per below tables

Note:

1. Failed fields were corrected by entering the date range instead of keeping the same date in both Start and Finish Feilds. TPOS will refuse to upload a file with the same date in both Employment Start & Employment Finish field.
2. For Post ECAL File - Date fields need to be reformatted in excel to DD/MM/YYY before upload.
3. All field data was verified against data from LinkPAY using the Tax Reconciliation report.
4. All ems Files were uploaded in TPOS for confirmation.