From VAT Requirements to SAP Processes: The Knowledge Behind Tax Technology

Throughout my work on VAT and SAP implementations, I have come to realise that understanding the technology is only one part of the challenge. What often makes the real difference is the ability to connect VAT requirements with the way a business operates and how its transactions are processed in SAP.

A tax technology implementation is not simply about configuring tax codes or setting up rules in a system. It requires an understanding of the VAT treatment, the underlying business processes and the SAP environment in which transactions take place. When these elements are not properly connected, even seemingly straightforward requirements can become difficult to implement.

Understanding the VAT requirement is only the starting point

The first step is to understand the VAT requirements applicable to the business. This includes identifying the relevant legal entities, VAT registrations, countries involved, contractual arrangements and the movement of goods or provision of services.

However, understanding the VAT treatment from a tax perspective does not automatically explain how it should be reflected in SAP. For example, the VAT treatment of a cross-border transaction may depend on which legal entity sells the goods, where they are dispatched from, who arranges the transport and which entity is responsible for the delivery.

Other factors, such as the incorrect use or interpretation of Incoterms, can also lead to misunderstandings about the actual transaction flow and, consequently, its VAT treatment.

Understanding how the business operates in SAP

An important part of an implementation is understanding how the business actually processes its transactions in SAP.

A good example is a drop shipment scenario. The supplier may deliver goods directly to the customer, without the selling company physically handling them. However, the SAP process may involve a purchase order, sales order, third-party delivery process and customer billing.

Each document represents a different part of the transaction, and the information available at each stage may differ. It is therefore important to understand where the relevant VAT information originates and whether it is available when tax determination takes place.

Without this understanding, there is a risk of designing a tax solution based on the expected business flow rather than the process that is actually executed in the system.

Understanding the existing SAP configuration and technology

Before introducing changes, it is necessary to understand how tax determination currently works and which configuration elements influence the result. This includes tax procedures, tax codes, condition types, access sequences and condition records, as well as country-specific settings and custom developments.

In my experience, changes to one configuration element can have consequences elsewhere. A solution that works for one transaction type or country may affect other scenarios if existing dependencies are not considered.

Even Meridian’s tax determination solutions, which are designed to use standard SAP fields and functionality, deliver the best results when the underlying VAT requirements, business processes and SAP configuration are properly understood. This understanding is essential to ensure that the available SAP parameters are used correctly and that VAT determination reflects the actual business scenarios.

For example, in a cross-border sales transaction, SAP may use standard fields such as the delivering plant, departure country, destination country, customer tax classification and material tax classification as part of the tax determination process. If the plant is incorrectly assigned or the material tax classification is missing, the system may determine an unexpected tax code. In such cases, changing the tax configuration may not be the right solution. The issue may instead be related to master data or the way the business process is set up. Understanding how these standard SAP fields are used is therefore essential to achieving the expected VAT result.

Master data is equally important

Even when the VAT requirements and configuration are correctly understood, tax determination can still fail if the relevant master data is incomplete or inaccurate.

Customer and supplier VAT registrations, material tax classifications, plant assignments, company codes and country-specific information can all influence the tax result.

For example, an incorrect material tax classification or missing plant assignment may lead to an unexpected tax code determination, even when the configuration itself is correct.

This is why master data should not be treated as a separate technical activity. It is an essential part of translating the VAT requirement into a working SAP process.

The importance of having the right knowledge available

A successful implementation requires input from different areas of expertise. VAT specialists need to understand the tax treatment, SAP consultants need to understand the system functionality, and business representatives need to explain how transactions are processed in practice.

These perspectives need to come together when designing the solution. If one is missing, requirements may be misunderstood, important questions may remain unanswered and decisions may need to be revisited later.

The business does not necessarily need to have all this expertise internally. However, it is important to ensure that the right knowledge is available throughout the implementation, particularly when analysing business flows and defining the expected tax determination.

Testing against real business scenarios

Testing should confirm that the complete business process produces the expected VAT result. Testing only whether a particular tax code is determined correctly is not sufficient.

Tests should cover the relevant business documents, master data and configuration, from the initial transaction through to billing or accounting, depending on the process.

When an unexpected result occurs, the issue may not necessarily be related to tax configuration. It could originate from the business process or the data used in tax determination. Understanding all these elements makes it easier to identify the actual cause.

Bringing everything together

Tax technology can automate VAT determination and support more accurate and efficient tax processes. However, the quality of the outcome depends on how well the underlying requirements are understood and translated into SAP.

In my view, the most important capability in a tax technology implementation is the ability to connect three areas: VAT knowledge, business process understanding and SAP expertise. When these come together, technology can provide the right support for consistent VAT determination and a solution that reflects the real needs of the business.