Edit: RESOLVED. What does "ChRIS 1606 Accounts Information within the accounts does not match that on the CT600 " mean?

Edit: RESOLVED. What does "ChRIS 1606 Accounts...

Didn't find your answer?

Edit: worked it out. Company reg number was lacking leading zero. Filed OK now.

Original post:

Just tried to submit a CT600 and it got rejected with the message "ChRIS 1606 Accounts Information within the accounts does not match that on the CT600 "

Any idea what it means?

Replies (6)

Please login or register to join the discussion.

avatar
By GaryMc
26th May 2011 08:28

Just to add some further info
That particular error message is a cross check between the Co reg number on the CT600 and the tagged Co reg number on the accounts.

They have to match for the submission to go through. Chatman added the leading zero but he could have removed the leading zero in the other document and it would have filed. It has to be a minimum of 2 and a maximum of 8 characters.

Thanks (0)
avatar
By Peter Cane
26th May 2011 09:38

Just for further info

There can also be a problem if the company name on the CT600 differs from the accounts. I have heard of one instance where one said Limited and the other Ltd, which caused a failure.

Thanks (0)
avatar
By GaryMc
26th May 2011 09:52

That will be a software not HMRC issue
The only check that the Government gateway makes relates to the registration number.

Company name in the accounts and CT600 do not have to exactly match but Phil Hodgson of VT has reported on his website that some software is making this unnecessary check.

See here for details - http://www.vtsoftware.co.uk/support/ixbrltaxpackages.htm

Thanks (0)
avatar
By Peter Cane
26th May 2011 10:03

HMRC software

Gary

The only time I've heard of a failure where the company name was different was somebody using the HMRC software.

I've not come across it using our software, Alphatax.

 

Thanks (0)
avatar
By DMGbus
26th May 2011 12:25

Leading zero missing (Sage software)

Using Sage Accounts Production, Sage Practice Solution and Sage Corporation Tax we encountered this issue.

The accounts had a 7-digit company number (no leading zero), the CT600 had an 8 digit company number (with leading zero).

The "difference" of the leading zero was the cause of rejection.  The core 7 digits number was correct.   Looks like Sage software itself is incapable of pre-submission data validation in this respect.

So, in this instance we have the hassle of an "integrated" software package and it doesn't do what you'd expect it do - it does NOT co-ordinate / integrate important data.

 

 

Thanks (0)
avatar
By carnmores
28th May 2011 15:46

a space before the leading zero also throws it out

 the tiniest infraction

Thanks (0)