Kindly, Start a detailed description for the new updates.
That’s as much detail as I have. ![]()
But don’t worry it’s not as hard as you think, you just need to start with it.
I recommend starting by:
- Copying all your custom fields dropdown items to new
Tax Codereporting categories. - Going back to Settings > Tax Codes and linking the new categories.
We can then pick up from there.
Is this as that I understand?
Do I now need to create separate tax rates for sales and purchases even if they are the same?
Yes, otherwise you will not be able to split the sales vs purchases amounts.
This is basic accounting, the VAT on purchases you make (also called Input VAT) and the VAT on sales (Output VAT) are the same % but not the same amount. It is important to note that Input and Output VAT cancel each other out in your VAT Return. So, your VAT paid to the tax authorities in each country will be the difference between these two. For example, you purchase a table for $100 with VAT 5% inclusive your VAT amount would be $4.76 and therefore assigned to a VAT account under assets. You then sell this table to a customer for $150 with VAT 5% inclusive and the VAT amount is then $7.14 and is assigned to a VAT account under liabilities. The difference of 7.14-4.76 = $2.38 is the value added by you to the original product and is what you must pay the tax authorities. Your supplier will have transferred the $4.76 to the tax authorities and in reality the total of the two is charged to the end customer as it should as this is the principle for VAT. The end consumer pays.
What about the current tax rates and the current taxable transaction recorder before?
I was doing it like that before, then it took some time to get used to Manager’s simple way of collecting taxes. Now I have to go back to the previous method. this is really sad. There is often a great reason for such a change, but it is worrying for me.
What do I do with the old rates and taxable transactions calculated based on these rates? Do I disable it and create new rates according to the new changes? or there is another way?
What change are you referring to? The vat rate in the example is 5%. If you are not bothered or if input VAT is not important then you only record VAT as a liability. Nothing changed as far as I am concerned. Manager does not tamper with existing data so any former recordings you made should still be there.
When tax authorities change VAT rates, which they invariably do over time, then changes are made as well on every new transaction as you would have set a new rate for those. So frankly no clue what your concern is.
The authorities didn’t impose new rates here. As I understand I am required to create new rates because the method of tax collection has changed or is about to change, what I am asking again is, should I stop using the current rates and rely on the new rates? If yes, it appears that the previous transactions will remain unchanged as you explained. But will the reports change? I mean, will the results of tax collection in the reports change for the past periods? These reports will continue to be based on the previous rates, which I will stop using and will not change anything other than deactivating them. Is this the appropriate or correct method?
Another question also, what would happen if I didn’t change anything in my rates and continued to use current rates in the same way without creating any new tax reports categories, what would happen?
Excuse me, sir, I’m a little confused, so many questions are running through my head, that I can’t quite present the question properly, and thank you for help.
No need to apologize. I fail to understand the worries you have. Maybe other forum members will do better with this. You mention there are no new rates meanwhile you state that you are required to create new rates, so that is confusing to me. I tried to answer your question:
@Ealfardan gave a clear answer on what to do, ie create categories and create tax amounts. He rightly separates Sales and Purchase VAT and I explained why that is the case. Some businesses only have Output VAT (sales) as they manufacture from scratch (no VAT purchases made). If you have such business you may have as part of transformations still have all the categories and amounts but you can make those such as Purchase VAT not applicable/inactive if you so wish. Any of your existing data will not be tampered with as far as I know.
- I don’t know what transition scripts Lubos is planning to implement
- I don’t know how final the current approach is.
At some time it is likely the tax codes will be unified. Personally I would use the new codes if you wanted to be involved in their development but would otherwise wait till all my transactions were updated.
That’s my opinion now.
Waiting for the final results of these improvements to decide how I can work with.
Thanks
I hope that doesn’t happen. There’s always a subtler less invasive approaches like for example inactivating previous tax codes and leaving it to the user to decide whether they want to reclassify previous transaction to the new coding system or if they don’t see it’s worth it and just leave things alone.
I say this because many user used unconventional workarounds that yielded correct results under the previous setup but when the change happens, suddenly those useful workaround are now a liability to correct 4,5,6 years of data. ![]()
I assume the solution would be the ability to merge tax codes.
Without some form of unification process reporting comparisons with history periods is likely to be poor.
I disagree. So what if reporting comparison with history periods is poor? Comparison was never a main objective of your tax books and I can’t think of a reason why it should be a secondary objective still.
If we want to make the right decision, first we need to define our objectives and prioritize them and for tax purpose they’d be:
- Compliance
- Accuracy
- Documentation
So people have been using the Tax Summary report before transformation was a thing and it was sufficient.
But if we mess that up to serve tax comparison purpose would spell disaster for many users. We take away their compliance, accuracy and documentation and now what will they have to show to their tax authorities? Same report formatting across periods?
That’s not what the tax authorities look for in proper tax books.
I say we put tax reporting format comparisons in context and look at the big picture, it not at all important.
I had assumed the following would be a manual process done by each user
However if the old structure is no longer supported it may need to be automated
true. this would avoid too much clutter.
but what we would need is merging tax codes based on prior transaction types. we cannot simply merge the newer inward tax code with the existing tax code which was functional for both inward and outward. that would be a disaster.
maybe Manager should first create separate keys for the existing tax codes based on the transaction types and then let the user manually merge them with the new tax codes. it could be 1 to 1 merge or 2 to 1 merge. for some reason i do not want any automatic script doing this. manual is better. we just need the function to do it.
Personally I wouldn’t automate anything that I don’t fully understand. I doubt that anybody here or elsewhere knows what kind of structure each user has and I also doubt anybody can foresee all the problems that may arise.
Automating something that’s not fully understood will only introduce systematic error. Sure I might do that for my HR database but not for my tax records.
That’s exactly why I still think merging is a bad idea.
Unless of course someone could create an exhaustive list of all the things that could go wrong, it’s probably going to create a tax disaster for some user.
Which implies Manager will need to support the old tax code structure well into the future.
Leaving manual merging of tax codes as an individual user choice.
As far as I can tell, the only effect these changes will have is:
- Old tax codes will not appear in dropdowns of sales or purchase transactions since they’re not categorized.
And as a result
- Old tax codes will not appear in localization reports.
Also if I understood correctly, all of the changes made have zero effect on how tax codes works, it’s only how they’re categorized.
This means that there will be no legacy code maintained to keep old tax codes running but they will just be there.
That’s a cost of having perpetual books, you always have to consider what happens to historical data.
This button is gone in Windows Desktop v21.11.37 as well as in Linux Server v21.11.37. ![]()