And this is why this needs to be done centrally at https://localizations.manager.io so it flows to all users automatically.
I do not know how to do that. Can that be done by a more experienced person. By going to the United Kingdom localisation what needs doing and then how does it get used by my existing businesses?
At this stage, I could understand why it’s implemented the way it is but once the localization is complete no changes should flow from anywhere until the user requests a newer version. Because otherwise that really sounds scary. Especially with the tax code merging situation.
However, I can live with this method of releasing localizations only if the user has total control on what happens to the tax codes. The categories and transformations on the other hand can flow unimpeded.
Now regarding tax codes, I suggest that the default behavior be something like this more or less:
- New codes should be created by default. (Also the localizations team should
- A utility is provided for the user to merge existing tax codes. Manager can still give suggestions but not go through the merging without user involvement.
That is how it’s already implemented. Localizations are not able to “touch” tax codes. The only way to get tax codes from localization is when creating new business.
For existing businesses, they will need to link their already created tax codes to localization-supplied reporting categories manually (there is going to be guide for that how to do it for specific countries). This is what I mean by updates in localizations not being able to touch tax codes.
Nice. 