Four months ago, I completed deployment for EMEA region and during this deployment we worked on multiple new designs with respective to the current design used in NA region. Enabling country specific tax account is one of them where we had requirement to add separate GL account for certain tax codes used only for specific countries.
While analyzing this requirement, we came across SAP’s proposed solution in Note 2361093 (Enabling country dependent tax accounts) and 2397146 (Country specific tax accounts prep (In background 2469831 and 2488015). Our system was already compliant to accept this solution as notes were already implemented/part of some deployment, so we decided to go-ahead and implement this solution.
In current system design, we were able to assign only one GL account per tax code, however with solution deployment in new countries brought requirement to have separate GL account for same tax codes used in multiple countries, which was not possible with our current below settings.
E.g. Country Belgium & Mexico are willing to use same tax code A1 with different GL accounts, now possibility could be anything like both countries wants to compliant with their existing system with certain parameters while using same tax code.
In OB40 we see no country field available for selection
- System should be compliant with SAP Notes 2361093 (Enabling country dependent tax accounts) and 2397146 (Country specific tax accounts prep (In background 2469831 and 2488015) other we won’t be able to use cluster table VC_T030K.
- Enable country field for tax if client is using Native SAP and not external tax engine line Sabrix (Sabrix or OneSource’s next version, Global Next has already brought possibility to use Native SAP functionality, but this is altogether different topic to write 😊)
This requirement can be addressed by adopting new tax code for any one country however if we consider of enabling country field for tax code GL assignment would be good solution for long term if we are expecting multiple country deployment of our solution.
If we consider to go-ahead with enabling country, then as per above SAP notes we should follow below quick steps.
- Instead of using direct transaction code OB40 use path Financial Accounting (New) > Financial Accounting Global Settings (New) > Tax on Sales/Purchases > Posting > Define Tax Accounts or transaction code SM34 > VC_T030K
- On next screen select transaction key in which you want this change
- Double click on left pane rules and select country check box for your chart of account.
- Now update your tax code with field country and country specific account, with this we can use same tax code in both countries with their own assign GL accounts.
- Once we enable country file in chart of account for specific transaction key, we won’t be able to use this same key from transaction code OB40, it will generate below message.
So, going forward change will only be allowed by using above path or VC_T030K cluster table from SM34.
- Difference in unique combination: T030K table use to store only Chart of account, transaction key, tax code and GL account, however with this change same tax codes will be repeated multiple time for above combinations. Now table will not have unique combination for above 4 fields only which could impact in reporting if report is using these 4 combinations, instead now we would need to consider country field as well.
- Impact on global GL assignment process: If we did this config, we could see requests to use project/country specific GL accounts for tax codes which could be difficult to manage & global GL assignment process could be lost. This could be a big issue for long run, but this still can be controlled with better design management.
Hope you found this post helpful for your requirement or for future reference. I would be grateful to hear your comments or suggestions.