Replies
No one has replied to this post.
They've fixed one, but are refusing to do the other because they left employer 1 in early February, and didn't start with employer 2 until early March (still less than 30 days). I honestly don't blame them, why should they be liable for the February payment? It's just an unfair system design that employer 1 has to take on responsibility for paying for a month they didn't complete with that employer when the employer gap happens to cross a month end. If it were a full withdrawal, they wouldn't be liable. So, we now have to withdraw in February and restart in March 😕 We'd have had to do this anyway, but it's annoying if they change the stop date late in the year so we're scrabbling around trying to resolve it last minute.
Ruth Canham-James
Employers Changing Stop Dates
Created
Has anyone else had an issue with employers changing stop dates to the wrong date or stopping record inappropriately just before R14?
We processed some change of employers a few months ago, and the dates go in automatically. Old employer approved, all fine. Now, new rows have very recently cropped up on the Apps Data Match report, because employer 1 has moved the stop date back a month. It's because they finished with employer 1 in late March, and started with employer 2 in early April. Employer 1 thought the April stop date made them liable for the April payment, which is doesn't. If we can't persuade them to put it back, we have to withdraw in March and re-enrol in April.
There's nothing we can do to stop this, but them doing it so close before R14 is causing real issues with very little time to persuade them to put it back. We've actually have two employers do this! 🙁 They could do this ten minutes before the R14 deadline, and we wouldn't know until it was too late. That feels like a real flaw in the system.