HI HAVE A PERSON LEFFT 3/4/10 HAVE MOVED PAYROLL(WEEKLY) ON WHICH HAS PUT IT INTO NEW YEAR BUT WHEN TRYING TO SUBMIT P45 FOR LEAVER ON INTERNET MOVMENTS GET ERROR

SHOULD I HAVE TRYED TU SUBMIT BEFOR MOVING WEEK ON

THANKS

HAVE UPDATED TO NEW VERSON BUT STILL SAME ERROR

OK, This is our error. HMRC didn't change something on 6 April that we were expecting them to change. The only PC in the world that it still worked from was our in-house test PC, because that has some special settings for dates (mainly to allow us to test stuff for different PAYE years) and that PC was still filing using last-years markers, which still work.

Please can you try this release...

A bit of extra information about this for those who are interested. All UK payroll software developers just got the following email from HRMC:

Dear Developer

Some developers have reported that their customers' in-year submissions are failing with a 5001 error and the message "Your submission contains an unrecognised namespace". This is probably caused by developers updating their software to include the namespace:

<IRenvelope xmlns="http://www.govtalk.gov.uk/taxation/PAYE/MOV/10-11/1">

The in-year movements forms are not year-on-year forms in the same way as End Of Year or Expenses & Benefits, so changes are not made routinely each year. We will only change the namespace if there is a legislative change to the form itself.

There have been changes for the last two years, giving the illusion of routine updates to the namespace. However, there were no such changes this year so the correct namespace remains as:

<IRenvelope xmlns="http://www.govtalk.gov.uk/taxation/PAYE/MOV/09-10/1">

This was published in the December "Notes for payroll software developers" http://www.hmrc.gov.uk/comp/notes-12-3.pdf at section 9.2.

Regards

Evidently we weren't the only software developer to make this mistake. Indeed it is whispered to me that the largest suppliers in the land have been caught by the same error. We're going to make representations to HMRC to ask them to allow the "10-11" namespace as an alternative to the 09-10 namespace (which is only logical, if the "09-10" namespace was intended to last indefinitely it should have been called "09-Onwards") But we don't have any real hope of success. Probably we'll have to make the V1.5.5 release the mainstream release in a day or two.