when doing my annual balance sheet, I had to notice considerable differences between
VAT tax accounts and
VAT tax lines
I can call all positions at the account in question, as well as all tax line entries. Unluckily, at the latter, move numbers are not displayed. I could identify most of wrong moves by comparing amounts. But I would have done better and much easier if move numbers would be displayed at tax lines as well.
Would that be a possible improvement - or do I miss another, better solution for my problem?
But I cannot do everything with invoices (eg import turnover tax), so there are manually created moves, which are prone to mistakes. In my case, I had a mistake in a self-created move template.
Ordinary people make mistakes. I make many of them, permanently. So IMHO there should be good methods to trace them down.
I would suggest to use move template to avoid mistakes.
But I do not see what could be done as we can not deduce the tax line amount out of the move line (this is the reason why there are stored by the way).
The difficulty to fix the issue is probably that it’s a bit difficult to find all the moves generated from the move template but I don’t think it would be wise to put a link from the move to the move template that generated it (the move can changed after the templating, the information is usually irrelevent) but of course if it’s a process that your’re doing frequently then it might be a solution.
That’s what I did, but I had a mistake in one of my move templates.
And other things can happen:
For instance, I create a move from a template and do a change on the move, as the template does not precisely fit the actual case.
I think there is an easy solution, 10’ of work for you super-professionals (no irony):
When at Financial > Reporting > Chart of Tax Codes, I can double-click Tax Codes and thus open Tax lines, looking like this:
I can find move numbers when double-clicking each single line.
If we now had move numbers in this list, it would be easy to copy this list to a spreadsheet, place a list of moves from the VAT account near my list and align both tables by move numbers. Thus, differences in amounts can easily be found.
I did that same with amounts and found most mistakes, but not all, as there can be mistakes in amounts as well.
Thank you very much for this thought, Sir, which indeed solves the problem.
Nevertheless, as the CSV export requires much of knowledge (or - in my case - trial and error), move numbers in tax lines would be a much more convenient and obvious solution.
I think there is some room for improvement if we have some state to the move lines that indicate the tax line status. This is similar to what we do in analytic account where we list all the move lines that should have analytic lines but they do not have. The idea is to be able to list some moves that may be wrong so the user can check them.
For tax lines we should mark as “fuzzy” all move lines that have tax lines but the amount of the tax lines is not a multiple of the amount of the tax lines, then the user can review and either:
Manually Mark the line as valid
Fix the amounts of the tax lines until the state is correctly fixed.
This way we can define a procedure to check all the move lines before tax reporting.
I’m proposing a solution for this problem because I also found some of our users manually modifying values and with the current state of the art is easy to do not be aware of such diferences.
Not a strict check like an error message but a way to easly search the lines that the amount of the taxes lines are not equal to the debit credit move of the linked move.
Even I say a multiple of the amount, because in case that there are two diferent taxes for the same move line the amount must be completly distributed for each tax.
I’m thinking in something similar to “Analytic Lines to Complete” but for account tax. The idea is to let the user know there are some move lines that may have some wrong tax lines and that must be manually checked.
AFAIK the only diferences are when the user has a non deductible tax percentage different from 100%. We can use a fake tax for such cases or even just let the user acknowledge the difference manually or even do it by code in advance when it is already expected.
In any case, i do not think the check should forbbid the user to do anythink in the system (maybe just closing the periods) but it should work in a more informative way to let the user review for correctness.
We would be willing to contribute to the development if there is some proposal/solution for this in the tryton core.
