Skip to content
Audit Defense

Why Should Tax Defensibility Deteriorate Over Time?

By Marc van RijbroekNovember 2026

The real question is not how to reconstruct a tax decision years later. It is why we allow the evidence to disappear in the first place.

Recent research from an indirect tax technology provider describes a growing challenge for multinational businesses: as time passes between a transaction and a tax audit, the ability to explain and defend the original tax treatment erodes - what the research calls “defensibility drift.” Fragmented systems, changing tax rules, incomplete transaction records and manual reconciliation all contribute. The findings are striking: 80% of enterprises reportedly require significant manual effort to achieve audit readiness, and 58% face highly complex indirect tax audits.

These findings raise a more fundamental question.

Why should the defensibility of a tax decision deteriorate over time at all?

At Taxmarc, we believe the underlying problem is not the passage of time. It is how indirect tax technology has traditionally been designed.

The missing link: preserving the tax decision where it belongs

Most tax solutions focus on determining the correct tax treatment at the moment of a transaction. The engine returns a result to the ERP system, the transaction is posted, and that is where the story usually ends.

But what happens to the information behind that decision? Which VAT registrations were considered? Which countries and jurisdictions were involved? What was the business scenario? Which tax classifications, exemptions, transaction characteristics and determination rules shaped the outcome?

If that information is not preserved, the business may need to reconstruct the original tax decision years later - using systems, master data and tax rules that have since changed. That is not an inevitable consequence of time. It is an architectural choice.

Taxmarc takes a different approach

Taxmarc was designed around a simple principle: every tax decision should carry its own evidence.

When Taxmarc determines the indirect tax treatment of a transaction, it does not simply return a tax code. The solution captures and stores more than 50 tax-relevant parameters directly in the source SAP system, alongside the transaction itself. Before posting, the determination is checked against the Taxmarc Tax Control Framework (TCF), which evaluates the transaction against configured tax control requirements.

The result is not merely a booked tax code. It is a transaction supported by the determination parameters and control information that produced it.

This changes the starting point of the audit discussion. Instead of asking, years later, “can we reconstruct why this tax code was used?”, the organisation retrieves the tax-relevant information that was captured when the transaction was originally processed.

From reactive audit preparation to continuous tax control

Preserving the tax decision is the foundation, and it enables more. With Taxmarc Radar, organisations monitor booked transactions, identify exceptions, and apply additional controls to the transactional information Taxmarc has already captured. Combined with Taxmarc Insight, that same information can be analysed across countries, entities, business scenarios and periods.

The objective is to move from retrospective investigation to continuous tax transparency:

  • Traceability - the tax-relevant parameters supporting the original determination are preserved at source
  • Preventive control - transactions are validated through the embedded Tax Control Framework before posting
  • Continuous monitoring - Taxmarc Radar™ identifies exceptions in booked transactions
  • Transparency - Taxmarc Insight™ analyses transactional tax information across the organisation
  • Audit readiness - dependence on reconstructing historical tax decisions from fragmented information is reduced

Audit readiness begins at transaction creation, not when the auditor arrives

The indirect tax technology industry increasingly recognises that determining the correct tax amount is no longer enough. Businesses need to explain, substantiate and monitor their tax decisions throughout the transaction lifecycle. We agree - and we would take the argument one step further.

If the relevant evidence is captured, validated and preserved within the original ERP transaction, there is no reason to accept that the ability to defend that decision erodes with time. Deterioration is a property of the architecture, not of the calendar.

The challenge is not to build better tools for reconstructing the past. It is to design tax technology that preserves the evidence from the beginning.

Don’t reconstruct the tax decision. Preserve it when it happens.

Frequently Asked Questions

What does “tax defensibility” mean in indirect tax?

Tax defensibility is an organisation’s ability to explain and substantiate the indirect tax treatment of its transactions when challenged - typically in a tax audit. It depends on whether the evidence behind each determination (jurisdictions, registrations, business scenario, applied rules) is still available and intelligible when the question arises.

How does Taxmarc preserve tax determination evidence?

Taxmarc stores the tax-relevant parameters behind each determination directly in the source SAP system, alongside the transaction, and validates the determination against a configurable Tax Control Framework before posting. The evidence is created at transaction time rather than reconstructed afterwards.

What is a Tax Control Framework in SAP?

A Tax Control Framework (TCF) is a structured set of controls that validates whether transactions meet defined tax requirements. In Taxmarc, the TCF operates before a transaction is posted in SAP, so exceptions are identified preventively rather than discovered in later review.

Why Should Tax Defensibility Deteriorate Over Time? · Taxmarc