This is urgent as I need to have the VAT return in by the 7th of Jan.
I have tonight just tried to create a VAT return. I got to the screen where
the Liability report is shown and you click Next - it then tells me the usual
message about having unapplied payments (which there are none) and credit notes (which there are a few of but these are from last year and VAT returns have been created after they existed) marking entries with VAT and any corrections will be submitted in the next return etc. When I click OK, it waits a while and then the
following error appears:
"Net VAT payable does not equal net VAT amount posted to VAT liability"
Now I've been over the entries from the last three months for the VAT return
period and there are no problems. I've looked at the detailed VAT liability
report and all of the entries tally with what is shown so I'm entirely in the
dark here. I am convinced this is NOT a problem with the accounts but a
problem with MOA.
I have restarted the SQL instance (just in case), restart MOA etc. Nothing
works.
I did have a problem with limited space in TEMPDB but that has been resolved now. I also repaired the database file and it did find one error. However a second 'repair' came up error free.
Is there any way to tell what MOA is doing and therefore where it is getting
it's info about the figures not matching up?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks for your comment.
The period for the VAT return is from September to November though - VAT change came in on 1 December :-) I was actually about update the ticket with that info.
The problem seems to be nobody (including MS) seem to know much about this! When you come to rely on something as important as your accounts software and it breaks (especially when doing your VAT) it is a complete nightmare!
Any help AT ALL is very gratefully received!
How have you dealt with the VAT rate change? I'm not familiar with MOA (should that be MWAH lol?), but Sage (for instance), have recommended changing an existing tax code to suit - now if that were done in MOA, is it possible that the program is doing some kind of validation on the figures and discovering a big discrepancy in what the Standard Rate tax that has actually been charged in the period Sep to Nov and the amount that is supposed to be assigned to that code (which has subsequently been changed in the Tax Parameters). If this is a possibility, try changing the Standard Rate tax rate back to 17.5% purely to run the VAT Return, then change it back to 15% immediately after.
Another possibility - do you get Updates "tthrough the pipe" from MS? If so, have they delivered an update which was supposed to deal with any VAT bugs (due to the rate change) and -er- they got it wrong. Microsoft wouldn't do that, surely?? ;-)) Have a look in your System Restore Points to see if this might be the case, and, after doing a backup, roll it back - if that is possible.
Thanks for all the help. I had a look into all of this but it turned out to be far more difficult to track down and far more mundane!
It wasnt anything to do with VAT, end of company financial years (as mine was September when the problem VAT period started) or anything else. The accounts were correct, the numbers were fine, everything with them that I could see with my limited accounting knowledge was fine. The problem, it appears, was a corrupt invoice.
The invoice itself looked fine. There were no fancy lines on it, just straightforward support charges like most other invoices. When I voided it, the VAT return worked fine. I recreated it and applied the payment and it was still working fine so the original invoice must have had a problem somewhere in the database that caused the problem. The invoice was dated in August and paid in September so it wasnt the VAT change. The new one is identical.
As I have the MOA database and app installed on the server and the server runs under ESXi, I took a copy of the VM and isolated it and restored old backups until I got a VAT return that worked and then worked my way forward from there. It was luck more than anything else that the very first invoice I voided was the right one.
The Microsoft Discussion group was useless in helping with this. MS support for MOA is dreadful. Im off to look at the Mamut Office apps to see if that can provide the same functionality with better support.
Thanks for everybodys help!
Business Accounts
Answer for Membership
by: moorhouselondonPosted on 2009-01-06 at 23:39:16ID: 23312640
If this is a well-established routine for you then I suspect this might be something to do with the rate change from 17.5% to 15%. As a workaround: have you tried splitting the VAT period down into two sections (1) the portion of the quarter where 17.5% was applicable (2) ditto 15%. You just then need to splice the two sets of figures together.