Zypp
ENNL

ZendBase Tax

More control over VAT. Less manual work.

Bring financial data, VAT controls and assessments together. With ZendBase Tax you make deviations visible, investigate differences and record your conclusions.

Request a demoSee how it works
ZendBase Tax control dashboard showing how controls are distributed by risk level and control group.

The control dashboard: where signals gather and how review work progresses.

The day to day

The work is familiar. The overview is not.

Exports, manual checks and scattered spreadsheets make it hard to keep oversight across periods and entities. Each period the pattern starts again: export, check, explain.

  • Data from different administrations

    Figures come from more than one financial administration. Before you can set them side by side, there is export, conversion and matching.

  • Recurring checks and investigation

    The same questions return every period. Does the VAT code hold, does the amount agree, and which item needs a closer look.

  • Findings spread across tools

    A signal lives in one file, the explanation in another. The conclusion is then hard to find again.

How it works

One connected control process

Source data is standardised for analysis. VAT reconciliation, sampling and dashboards support the same process. Which connection is possible depends on the source system and on your organisation.

  1. 01

    Collect data

    Financial data from the source administration, brought onto one structure so controls can run on the same population.

  2. 02

    Check

    Automated VAT controls on the imported population, according to the rules that have been configured.

  3. 03

    Assess

    Investigate a signal, assign responsibility and record a judgement.

  4. 04

    Document

    Explanation, history and sampling results stay with the finding.

Supported byVAT reconciliationSamplingDashboards

Controls

Automated VAT controls

Controls run on the imported population, in line with the configured rules. Standard controls can be supplemented with rules that belong to your organisation.

  • Missing or unexpected VAT codes
  • Differences between base amount, VAT rate and VAT amount
  • Inconsistencies between master data and transactions

The dashboard shows where signals concentrate, what needs attention and how review work progresses. A flagged transaction is a signal. Assessment comes after that.

Overview of all controls in ZendBase Tax, grouped by risk, showing flagged records and review progress per control.
Per control: group, number of signals, share of invoices and how much has been reviewed.

Assessment

Assessment and follow-up

From a finding you inspect the transaction context. You assign responsibility and record priority, status, judgement and explanation. The change history stays available.

Automation supports the tax specialist and the controller. A signal is not a confirmed error. They decide what it means.

  1. 01

    Signal

    A control flags a transaction that needs attention.

  2. 02

    Investigate

    You review the finding together with the transaction context.

  3. 03

    Assign

    You record who takes it on and what priority it has.

  4. 04

    Judge

    Status, judgement and explanation are stored with the finding.

  5. 05

    History

    Changes stay available to consult.

Reconciliation

VAT reconciliation

You compare Dutch VAT return figures with amounts calculated from the transaction data, per return category. Differences and the explanation of the mapping guide the investigation.

Not every category drills through to invoice level. The reconciliation shows the difference and where the explanation comes from.

Dutch VAT return categories in the ZendBase Tax reconciliation view.
The reconciliation follows the categories of the Dutch VAT return.

Sampling

Sampling

You define a population, choose a method and suitable parameters, keep the selection, assess the selected records and document evidence and results.

The recorded population, settings and selection make the sample reproducible. ZendBase Tax does not impose a fixed confidence level and does not promise acceptance by a regulator.

Setting up a sample in ZendBase Tax: population, document type and date basis.
A sample starts with the population: name, document type and date basis.

Geography

Make international transaction flows visible

ZendBase Tax gives geographic insight into purchase and sales transactions. You see where flows come from and where they go.

This is insight into your transactions. It is not coverage of tax rules worldwide.

World map in ZendBase Tax showing purchase and sales flows from the Netherlands.
Purchases and sales on the map. Click a flow or country for the underlying transactions.

Start

Start with a concrete question

A first conversation is about one entity, one period and one control question. From there it becomes clear what the data will support.

How long that takes depends on the source, the data quality and the question. We do not commit to a fixed implementation time.

  1. 01

    Choose the question

    One entity, one period and one control question.

  2. 02

    Inspect the data

    Which data is available, and what the data quality looks like.

  3. 03

    Configure

    The controls and mappings that belong to that question.

  4. 04

    Validate

    Walk through the findings with finance and tax.

  5. 05

    Repeat and extend

    A process you can run again, and extend where that is useful.

Demonstration

What shows up in your data?

Discuss a demonstration, or a scoped exploration with one entity and one period.

Request a demoAll Zypp products
  • One entityA scoped starting point
  • One periodA period you know well
  • One control questionWhat you want to make visible