Save content
Have you found this content useful? Use the button above to save it to your profile.
AIA

Notices of coding - an update

by
15th Feb 2010
Save content
Have you found this content useful? Use the button above to save it to your profile.

The tax authority has provided more information for employers and agents about the current coding run, which has produced incorrect coding notices. Work is under way to correct all of the incorrect codes.

HMRC's latest information for those employers and agents dealing with incorrect code notices provides more reassurance that the department is making progress in identifying the issues giving rise to incorrect codes. The information seeks to provide a little more background, particularly for employers, so that they can understand what has given rise to the mismatch of data triggering incorrect notices. HMRC will be contacting employers again with more precise information about the likely causes but for now are working on re-issuing codes to those who have been affected.

"We are undertaking a review of those cases which include one or more of the issues identified and will issue revised notices of coding to the individuals as soon as possible if they have already been sent a incorrect code. This work is being prioritised so that we deal first with those individuals who are most vulnerable if their code is incorrect. Our plans to review codes will minimise the number of coding notices being sent to your employees or pensioners with these inaccuracies."

"In most of the cases we have reviewed, where we believe the code may be incorrect, we have found a discrepancy between the data we hold and that shown by the employer or pension provider on forms P14. Where we can we will correct the data and send out a correct code to the customer but in some cases we will need to check information with the individual before we can make a change. In other areas we will be asking employers or pension providers to work with us more closely in the future to so that discrepancies do not creep in again."

"As employers and pension providers we recognise that you will have employees and pensioners contacting you for advice on what the revised notice of coding means for them. The numbers of inaccurate codes should be minimised going forward which will help and for any remaining enquiries we are not asking you to respond beyond providing the reassurance that this note gives about the problems being understood and addressed. Where an employee or pensioner does contact you we would be grateful if you could:

  • Reassure them that the revised notice of coding will not take effect until the first payment after 5 April and HMRC will be reviewing and correcting codes in the meantime
  • Ask them to look at the information on our website which explains how a PAYE code is operated
  • Ask them to telephone us on the number of their Coding Notice or 0845 3000 627 if they have any more concerns or wish to talk to us to resolve the problem."

HMRC concludes by warning employers that they will receive more code notifications than normal this year, when the employer notifications start next month.

Tags:

Replies (4)

Please login or register to join the discussion.

avatar
By pauljohnston
15th Feb 2010 11:59

Wrong codes

So this deals with employers and pension providers but what about the other problems.  Such as Married Persons Allowance for widows and widowrs.

I am not sure how the transfer was accomplished from the old system to the new but the number of errors as reported on another post on Accountingweb does raise concerns as to the quality of the HMRC data.

I have only been an accountant for about 15 years but I can remember at least one other occassion when Tax Codes were wrong because of a new computer system.

As I see it no one at HMRC cares enough or is held responsible for these errors which have to be put right by the taxpayer or his agent at the taxpayers expense.

Maybe now is the time for accountability so infuture HMRC should publish the name and direct line number of the person who takes responsibility for implementation.  Hopefully this will mean that more attention is given to the data and its quality than has been so far.  It costs a lot more to put matters right after the event than to do the pre-implentation data checks.

 

 

Thanks (0)
avatar
By User deleted
16th Feb 2010 16:23

Incorrect Tax Codes

I have received codes restricted for "other earnings or pension" of several hundred pounds and then a code for that amount being issued to be used against jobseekers allowance for the year starting 6th April for two clients so far who have previously had a period of unemployment. When you speak to HMRC they try to tell you that they do not know that she will not receive this income again next tax year! I have pointed out to them that if they were made redundent again they would get a P45 to hand in to be used when they claimed taxable benefits but they do not understand.

Also codes received for next year with "we understand you're between jobs" on and then restriced / no allowances because your income is £100k plus when they have little or no investment income.

Also for 2010/11 HMRC are assuming all P11D expenses are taxable in codes although expense claims have been made on the SATR for 2009. They are not allowed to remove them now without a formal claim by letter for 2008/9 I have been informed by two offices. They cannot accept the claim on the tax return for coding purposes?!

I could go on & on.................

Thanks (0)
avatar
By Yonder Dave
17th Feb 2010 18:13

And so could I .........

The best example I have seen is a person with 3 coding notices; one for a job left 18 months ago, one relating to Jobseekers Allowance which ceased last year and a third for a pension which isn't payable for another 5 years!

They even got mine wrong because there is a wrong figure for Employer Benefits, so obviously there has been no check against the SA. Problems with allowable expenses on P11D only started last year and I have resolved them all with Section 336 claims, and now I have obtained Dispensations for all clients (and I get all new clients to complete a P11DX as well as a 64-8).

The biggest annoyance is that if you call the help line the person the other end cannot see how the new code is calculated, and you cannot talk to the local office like you used to. I had to write for an explanation and the reply was that the figures came from the P11D. They don't so I have had to write again with copy of P11D.

Will this be sorted out before the April payroll???

Thanks (0)
avatar
By jonbryce
23rd Feb 2010 22:58

Job seeker's allowance

I too have had problems with Job Seeker's Allowance being coded out where clients have had periods of unemployment in previous years.

This isn't a problem with out of date data, this is a design flaw in the computer software.  If someone is claiming JSA while working, HMRC should be reporting it to the benefit fraud people to get the money back in full, not adjusting the tax code to tax the money.  If they get made redundant, or their temporary contract expires part way through the year, then tax on any benefits they claim will be dealt with via the P45 system, and adjusting it via the tax code will mean they pay tax twice on their benefits.

Thanks (0)