What usually goes wrong
The problems we get called about.
- A rate is wrong and the trail goes cold.Tax says the engine is wrong, IT says the data is wrong, and the transaction has already posted.
- Nobody owns the integration.The tax team does not read ABAP. The SAP team does not read tax logic. The gap between them is where these issues live.
- Configuration drifted from the business.New entities, new jurisdictions, new product codes — set up correctly three years ago and never revisited.
- An audit asked a question you cannot answer.Explaining why a specific transaction was taxed as it was turns out to be much harder than expected.
- Performance at volume.Determination calls that are fine in test and slow to a crawl on a real invoice run.
What's included
Scope, in plain terms.
- Integration support.SAP to ONESOURCE connectivity, mapping, and custom logic in the determination path.
- Determination troubleshooting.Tracing specific transactions end to end and explaining the result in writing.
- Configuration review.Checking the engine still reflects how the business actually operates.
- Audit support.Written explanations of determination logic for internal and external audit.
- Performance tuning.Call volume, batching and response time at scale.
- Change support.New entities, jurisdictions and product categories reflected properly.
These issues live in the seam between SAP and ONESOURCE, which is exactly the seam most support arrangements leave unowned.
We are technologists, not tax advisers. We make the system do what your tax function has determined it should do, and we can explain exactly what it is currently doing. What the correct treatment ought to be is a question for your tax advisers.
Free, no obligation
Let's look at one problem properly.
One problem area, examined by an engineer. You get a written findings note and a fixed-price proposal. No charge, no obligation.
Book a 45-minute technical review →