activities, Arjan Hassing, automated, basic, best format, block, Business, calculate, chain transactions, compliance, cost reduction, cross-border A-B-C transactions, cross-border transactions, customer master data, decision tree, department, determine, double payment, effective, effective communication, efficient, electronic interface documents, ERP, European Union, exchange rate, financial, framework, HM Revenue & Customs, iDoc, indirect tax, indirect tax functionality, instructions, Invoice, IT consultant, KEY Group, logistic, malfunctions, manual processes, mismatch.VAT treatment, OBCD, objectives, Plug and Play, processes, procurement, purchase, reluctance, report, reverse charge, richard cornelisse, robbert hoogeveen, sales, SAP, SAP configuration, SAP consultant, SAP implementation, Shared Service Centers, shortcoming, solution, system, tax code structure, test environment, test phase, value added tax, VAT, VAT configuration, VAT filing, VAT registration, VAT rule, VAT-relevant, work stream
Operational malfunctions in a system that is used to manage VAT compliance can lead to substantial financial risks.
There are countless examples of the mismatching of VAT treatment of purchases and sales in chain transactions, double payments of VAT and “forgotten” manual adjustments to the VAT filing, all attributable to shortcomings in SAP’s automated VAT solution.
Errors in the basic VAT configuration of ERP systems can also carry consequences for an organization.
Without the proper VAT rules, many systems are incapable of processing transaction information correctly, so that transactions may become blocked.
This has a great impact on logistics processes, invoicing processes and financial processes.
Tax and financial departments are under increasing pressure to reduce the costs of compliance processes. One result of this is the increasing transfer of VAT-relevant processes from national tax supervision to Shared Service Centers.
These Shared Service Centers are not generally manned by tax specialists.
They trust the functionality of the group’s ERP system to determine, calculate and report local VAT.
Our added value is that we help clients free up resources, reduce manual activities and manage risks.
The KEY Group possesses considerable practical experience and understands SAP’s possibilities, but also its limitations.
With respect to the possibilities, we can express the wishes to the external SAP consultant in his own language and we can demonstrate how these can actually be achieved in SAP.
In practice, we note that certain functionality intended for the support of indirect tax objectives does not get used – due either to reluctance (not within budget) or to a lack of knowledge in this area.
From an indirect tax standpoint, the realization that you are part of a larger team in which each of the participants has other priorities is key.
This means that effective communication and agreements are essential.
Instructions must be understandable and so short and compact that they can also be used as a reference framework and material for the tests.
In practice, Excel is often used to record all transactions and to indicate what the VAT treatment, etc., should be for each transaction individually.
This cannot be imported and is difficult to evaluate for this reason. Moreover, the use of Excel carries the risk of making copy/paste errors.
The question is: what is the best format for providing instructions to other work streams and for making the test phase efficient and effective?
It turns out in practice that decision trees are a particularly effective communication resource with the IT consultant. In addition, an SAP implementation is not “Plug and Play.”
SAP has its limitations and not all transactions can be implemented in the systems in an automated fashion.
Examples of possible errors in SAP
- Not making use of the proper partner functions in SAP for a supplier who provides services in multiple countries and invoices VAT locally. Result: the standard VAT calculation generates incorrect results.
- Missing/improper VAT registration numbers in customer master data, such that invoicing requirements are not satisfied for cross-border transactions.
- Master data is adjusted and tested in the test environment, but the changes are not included in the final upload to the production system.
- The logic of the tax code structure is disrupted by VAT rate changes, something that could have been prevented using the SAP configuration.
- When performing reverse charge bookings, VAT rate changes do not get changed.
- For cross-border A-B-C transactions, a VAT mismatch between the VAT on procurement and the VAT on sales arises for party B.
- Blocked so-called iDoc (electronic interface documents) because of errors in the OBCD design.
- Suppliers with invoices in other currencies and the VAT amount in Euro, so that the booked VAT amount is incorrect due to an incorrect exchange rate.
- Incorrect derivation of VAT registration numbers for cross-border transactions caused by incorrect SAP configuration.