The context here was, an Employer actioning a change “any correction, can only be done by the employee, due to GDPR etc” Revenue will not take information from an employer, only an employee, due to GDPR. Revenue will not provide any data to an employer other than the RPN details, Employers have no access, to individual circumstances which can impact Tax Credits, & have no access to the reasons for reductions in SRCO & USC cut off thresholds, they also have no access to 2nd employment information, and other sources of PAYE income, such as Pension income, no access to adjustments to credits from previous years, so an employee’s detailed revenue data is private to the employee, an employer can only see the totals applied to the employment, and not any breakdowns, so it has everything to do with GDPR.What has GDPR got to do with any of this?
If an employer believes the tax credits on the Revenue system are incorrect they are completely permitted to advise the employee.
This has been the case forever and is nothing to do with GDPR. It is to give employees a degree of privacy from their employer about other employments and personal circumstances. It is nothing to do with GDPR.Employers have no access, to individual circumstances which can impact Tax Credits, & have no access to the reasons for reductions in SRCO & USC cut off thresholds,
and it is not the Employers place, to highlight a tax issue,
An employer has literally no business prying into an employee's PAYE or USC data and attempting to deduce why a particular rate has been applied.It is not the employer’s obligation, but neither GDPR nor anything else does not stop an employer advising an employee that their Revenue data looks implausible and that the employee may wish to take action.
Employer didn't mess it up
They applied the Rpn provided
Sounds like reduced rate usc for having a medical card (instructed by revenue)
A person can't earn more than 60k and get reducted rates
If they do by the end of the year , standard rates will apply and a liability will arise according to revenue
Employers have no control of your personal situation by having reduced rates
In summary, if you earn more than 60k and have reduced rates usc it's your responsibility to tell revenue you will exceed the earnings limited and switch you to standard rates to prevent a liability
Regarding the liability , you might do a phased payment plan approach
Hope it works out for you , not ideal having a liability
This is correct but so is the above post, the amended Rpn for these situations is always a week1/month1 basis so the damage was already done and any payrolls after the amended cert only corrects thoseEmployers should download the RPN before every payroll run to ensure that they have the latest information
For most payroll software, this is included as a feature, to be used or not at the employers' discretion
It's not a matter of discretion though.For most payroll software, this is included as a feature, to be used or not at the employers' discretion
This is correct but the software providers "prompt" the users by 'download now" buttons for example when they go to create a wage , this happens in sage and Collsoft anyway , the user is presented with a window to download the latest RPN before proceeding to create a wage, it's no excuse to be avoided but you are correct, it isn't FORCED , the payroll user needs to do it otherwise they can X/close tht window and proceed which will use thr previous rpn BUT an error warning message is returned ffom revenue that an 'out of date Rpn used' and this messsge is also on the payroll report on ROS so employers and revenue can see a payroll didn't sue thr latest RPNWhat I meant is that it probably isn't an automatic download of RPNs but a user managed download
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?