TopicsTax engine or SAP standard?
Tax engine or SAP standard? The guide to your selection.
For tax departments on SAP ECC® or SAP S/4HANA®: when the standard is enough, how to compare vendors neutrally and which costs are often underestimated.
- Vendor-neutral
- 12 chapters
- Straight to your inbox
Get the guide
You will receive the link to the guide by email. Required fields are marked with *.
We use your details to send you the guide. You will receive the guide even without the optional consent. kallman GmbH is responsible. Details, including your rights, in our privacy policy.
What the guide covers
For decision-makers working in tax and IT.
-
The basic decision
SAP standard, tax engine or hybrid: how to tell which option suits your company.
-
The selection criteria
What matters functionally and technically: from country coverage and the rule set to integration with SAP.
-
The selection process
Four phases with results and the questions to ask vendors.
-
Costs and risks
The cost blocks that are often missing, and how to avoid depending too much on one vendor.
What is a tax engine?
A tax engine (also tax determination solution or indirect tax engine) is a specialised software component that determines the correct tax code as an add-on to SAP or outside it. The tax code stands for the taxable event and the tax rate and drives the accounting of a transaction. The tax engine replaces the SAP condition technique, which quickly reaches its limits in international companies with demanding transactions.
- Determining the transactionAutomatically, based on the country of departure and destination, product classification and the status of buyer and seller.
- Rule updatesWith some vendors, rate changes, exceptions and new legal requirements are maintained automatically.
- Audit trail and reportingEvery tax decision can be traced, including the rule version applied.
- Vendors with SAP integrationFor example Avalara, Meridian, Sovos, Taxmarc, Thomson Reuters ONESOURCE and Vertex.
A tax engine does not replace a competent tax department. It automates how the rules are applied. The rules themselves must be agreed, checked and owned beforehand.
The selection process at a glance
Four structured phases that lead to a sound decision. In the guide we describe each phase with checking questions and results.
-
Needs analysis
Selection
Requirements catalogue
-
Market screening and solution review
Selection
Shortlist, demos and proof of concept
-
Evaluation and decision
Selection
Evaluation, total cost of ownership and contract
-
Implementation and go-live
Implementation
Live operation
Is SAP standard still enough?
SAP tax determination with the condition technique, tax procedure and tax codes is a solid basis. It is typically enough if all five points apply:
- Your company has no foreign VAT registrations.
- You are not involved in VAT chain transactions.
- Your range of products and services is simple in VAT terms.
- Exceptions are rare and easy to manage.
- The tax department understands the condition technique and shares responsibility for tax determination.
If one point does not apply, the standard quickly reaches its limits.
Rule of thumb from practice: from around EUR 100 million in revenue with international business and a varied mix of products and services, you should seriously consider using a tax engine.
What vendor-neutral means to us
The starting point is not a vendor’s solution but the requirements of your company.
- Requirements, criteria and weighting are fixed before the first vendor presents.
- All vendors answer the same set of questions and are assessed by the same criteria.
- Demos and proof of concept run on your own cases, not on standard examples.
- The option of staying with SAP standard is also seriously examined.
Frequently asked questions
-
What is a tax engine, and what is it not?
A tax engine is specialised software that takes over tax determination, that is, it determines the correct tax code for every transaction. It runs as an add-on in the SAP system or as an external solution. However, a tax engine does not replace a tax department: the tax department still has to agree on the rules and master data and take responsibility for them. -
Which costs of a tax engine are often underestimated?
The licence is what you see first. Often underestimated are internal resources in tax and IT, tests per country, data migration, training, ongoing maintenance of the rule set, and adjustments for SAP upgrades and for adding new countries. -
What are the most common mistakes in the selection?
The decision is made after a convincing demo instead of a proof of concept with your own data. IT decides without the tax department, or only standard cases are tested, although the differences in quality only show in chain and triangular transactions or other complex exceptions. -
Who should be involved in the selection?
Tax and IT together, from the start. The tax department defines the requirements and test cases, IT assesses integration and operations. This needs a clear mandate with budget approval at CFO level: tax engine projects fail less often because of technology than because of organisation.
Your contact
Adam Dubielecki is a partner at kallman GmbH and co-author of the book “Umsatzsteuer in SAP S/4HANA”. He has supported various projects to implement tax determination solutions in S/4HANA and, as co-founder of kallman, was responsible for developing tax determination solutions.
