cancel
Showing results for 
Search instead for 
Did you mean: 

GOSI is being deducted after employee termination

former_member714542
Discoverer
0 Kudos

Dear Experts

I am using country grouping 24 for Saudi Payroll and currently facing the issue during the scenario of employee termination.

I hired one employee on 1st of November, updated the Infotype 3252 (Social Insurance SA) so system could calculate and deduct GOSI from his salary, processed November payroll and then closed the payroll.

Then I terminated employee on 1st of December next month with separation reason 'Contract Termination', and when I processed Dec payroll the system still calculates and deducts the GOSI amount which in result coming under 'Claim' amount as salary allowances are not being calculated (which is right as per standard). I already defined 'Contract Termination' reason as dismissal under feature 24EOS for country grouping 24.

Also, the system does not process the EOSB standard wage type /670 which is payout for EOS. However, the system calculated the provision amount for EOS wage type under /650 previous month in November. Also, when I run simulation for previous month November (which I already executed and closed), the system brings /670 wage type for EOS payout, which infact should have been processed for Dec period.

I have attached the screenshot for December simulation as the reference.

dec-salary.jpg

Please your suggestion.

Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

VivekPalanivel
Product and Topic Expert
Product and Topic Expert
0 Kudos

This is the standard technical limitation if employee is terminated on the last day of the month. Ideally this employee's November payroll should have been his last payroll but we have run November payroll month as active and now running December. In December its checking if the employee was terminated and the answer comes No, so it calculates GOSI.

former_member714542
Discoverer
0 Kudos

Hi

Well, I have attached the screenshot of termination action then perhaps you can guide where it goes wrong. Also, I have attached the screenshot of GOSI Schema SADA so kindly advice where it might be going wrong in case of termination of an employee on 1st of the month.

Thanks,

VivekPalanivel
Product and Topic Expert
Product and Topic Expert
0 Kudos

a) Chances of error in program is very remote. So it should be mostly master data issue.

b) In SAEN schema, added SA91 after ELSE too (around line number 90 or 100)

VivekPalanivel
Product and Topic Expert
Product and Topic Expert
0 Kudos

This is normal behaviour.

a) You are running payroll post employee left the company so better delimit IT3252 as per last working date. Post last working date let him/her be not eligible.

b) Standard retro doesn't calculate /670 , only the current payroll calculates. We did a workaround but adding that calculation pcr even in Retro check of the schema. It worked fine.

former_member714542
Discoverer
0 Kudos

Hi

Thank you for your prompt response. However...

a) It's not about delimiting IT3252, as I changed the termination date to 6th December instead of 1st Dec without delimiting IT3252, and now system calculates 5 days salary without GOSI deduction which is fine now. Only when I terminate the employee on 1st or 2nd of the month then system deducts GOSI from salary, so I think there would be some bug in the program....

b) There is no Retro in Dec salary, only the current payroll for Dec period. So If you could elaborate about your workaround (where you added PCR in subschema) that worked fine then it would be much helpful for me to understand.

Thanks.