AccountingWEB.co.uk 7-Apr-2005
Categories: Software, IT News, Internet/E-commerce, Any Answers, Direct tax
Times read: 1432
I then opened another company file and tried to file on line. I received the same error message as above. I opened several more company files and I was unable to even view P14's, P35 etc let alone file on line.
This morning I spoke to Intuit who after one hour told me that there is no resolution to this problem at the moment, they are working on it.
Is anyone else experiencing this problem.
I have no such punctuation included in my own data entries, BUT....Quickbooks itself is 'gathering up' the last two lines of every address (employee as well as the employer!), so that when you enter, say, 'Brighton' in the city box, and 'BN1 1BN' in the postcode box, these two lines are in fact shown on the P60, etc., as: 'Brighton, BN1 1BN'. This, as I understand is not allowed by the IR gateway, and the returns will be rejected.
I have asked Quickbooks about this, but they have yet to come back to me. I asked them last Tuesday (5th), and you might have thought they could have responded quicker, in view of the urgency - and, presumably, since it affects ALL their customers!
Perhaps this 'gathering up' of the last two lines doesn't, in fact, matter? Perhaps I have been told incorrectly? I see that others have apparently filed using their Quickbooks - did they notice how the last two lines were showing?
Help!
Tim Heaton
Problem with Wk1 sorted, and I've managed to file two P35s this morning via Quickbooks.
Excellent service - gives confidence in Quickbooks for the future.
Andrew
There is a p35.xsl file available on the QuickBooks website if you don't want to wait. http://exceed.quickbooks.co.uk/Support/
Phillip, the P60 issus has been fixed and that too will be available for download in the morning.
BUT
I would warn other users to be careful about the P60s for employees with a Wk1 tax code - QB seems to think they are involved in a trade dispute and doesn't show the right tax deduction on the P60. They did a patch for it yesterday, before which the problem was that it showed no tax, but the update still doesn't work properly - it fixed it for some employees, but left others showing the wrong tax deducted.
If you have any employees with a Wk1 tax code, check them very carefully.