Seven years, sometimes ten Original digital Within a reasonable time

Custom software for the tax retention obligation and auditable record-keeping

The retention obligation sounds like an archiving question, but it isn't one. You may not keep digital files solely in printed form, and the Dutch Tax Authority must be able to access your programs and files during an audit. That makes retention a requirement of the system in which your records are created.

Appfront
Live

What the retention obligation requires of your system

The main rule is set out in the Dutch General Act on State Taxes (Algemene wet inzake rijksbelastingen): anyone required to keep records must retain them for seven years. For data relating to immovable property, the period is ten years. The basic records always fall under this: the accounts receivable and accounts payable records, the purchase and sales records, and the general ledger.

What matters more for software is the form. You keep data in its original form, digital or on paper. Files that were created digitally may not be kept solely in printed form; during an audit, the Tax Authority must be able to access your programs and files. A printout of a general ledger is therefore not a substitute for the general ledger.

Conversely, you are allowed to digitise paper. Scanning is permitted provided it gives an accurate and complete reproduction of the original; if you meet the conditions, you do not need to keep the paper document. That digital record then itself falls under the seven- or ten-year period and must be accessible within a reasonable time.

That is where the practical challenge lies. A system that works perfectly well today must still be able to show data in seven years' time from a version that was replaced long ago, in a form an auditor can follow. Anyone who only thinks about this during a migration or a software change will find that the old data is still there but can no longer be queried.

How we build this

The point is not storing but retrieving. A file that exists but cannot be opened or searched does not meet the requirement that it must be verifiable within a reasonable time.

1
Recording what is created where

For each type of data: where it is created, which retention period applies and in what form it must be kept.

2
Retaining in the original form

Digital documents stay digital, together with the surrounding data needed to be able to read them later.

3
Keeping it searchable

Searching by period, relation, amount or ledger entry, including for years in which the system has since been replaced.

4
Preparing for audit

An export an auditor can work with independently, without anyone having to operate the system.

What the software actually does

The durability of your data underpins everything else. What else you need depends on your size and on the number of systems in which records are created.

Retention period per data type

Seven years for core records and ten for real estate, with the applicable period set for each data type.

Digital stays digital

Files are kept in the form in which they were created, not as printouts, because a printout will not satisfy an inspection.

Scanning with verification

If you digitise paper, you want to be sure the digital version is accurate and complete before the original can go.

Finding records without the system

An export per period or per relation that can also be read by someone who does not know your software.

Readable across versions

An entry from an old system version must still be viewable today, including the context in which it was made.

Immutable records

What has been booked stays as it is; a correction is added alongside it, not over it.

Who we build for

Who has to deal with this differs per organisation. Four situations.

Bookkeepers and controllers

They receive the auditor's request and only then find out whether the system can answer it.

Accountancy firms

They work with the accounts of many clients and do not want a different search process for each one.

Businesses with their own software

If you have had a system built in which invoices or orders originate, the retention obligation applies to that system too.

Organisations switching systems

In a migration the question of what happens to the old data comes up, and that is exactly the difficult moment.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Retention periods are stable, but systems are not. Retention periods, data types and export formats should be configurable rather than hard-coded.

If you are a tax advisory firm and want all returns, the becon extension and the submission schedule in one overview, take a look at software for monitoring tax return deadlines.

Configurable retention period per data type Storage of files in their original form Search by period, relation and journal entry Export in a form an auditor can read Integration with your accounting software Roles for administration, management and accountant Immutable records with corrections alongside Deletion once the period has expired History across system versions Audit trail on every change

Why Appfront

A printout is not a file

What was created digitally must stay digital. We build the storage so that the original is preserved, not just a representation of it.

Retaining is easier than retrieving

The requirement is that data can be verified within a reasonable time. That is a search question, not a storage question.

Seven years will outlast your current system

Expect to migrate at least once in that period. That is a design requirement, not a vision of the distant future.

We do not run your accounts

The tax judgement remains with you and your accountant. We build the system in which the accounts remain sustainable.

Security and privacy

Accounts contain data about your revenue, your margins and your relations, and sometimes personal data of customers and employees. We set access per role, give an accountant access to the period they are working on without the rest, and log every access. Integrations run through secure connections to your existing software.

For this topic, reliability at the moment of recording is the key point. An entry that is changed afterwards without a trace undermines exactly what an audit tests. We record changes immutably with a timestamp and the person responsible, and make a correction a visible correction alongside the original line. How we handle security ourselves is set out in our information security policy.

Frequently asked questions about the tax retention obligation

Seven years, and ten years for data relating to real estate. The core records always fall under this: the accounts receivable and payable ledgers, the purchase and sales records, and the general ledger.

No. You keep data in its original form, and what was created digitally stays digital. In an inspection the Tax Administration must be able to access your programs and files; keeping files only in printed form is not sufficient.

That is allowed, provided the digital copy is an accurate and complete representation of the original. If you meet the conditions, you do not need to keep the paper document. The digital records then fall under the retention period themselves and must be accessible within a reasonable time.

It means an inspector must be able to view and trace your data without it taking weeks. In practice, that is a search question: can you retrieve a period, a relation or an entry, including in years for which the system has since been replaced?

That is the trickiest moment, because the data moves but the way to query it often does not. Before a migration, decide how you will keep the older years accessible; afterwards it often turns out that the files are still there but no longer usable.

No. This is about your own records and the retention obligation that applies to them. Filing VAT on behalf of foreign clients is a different subject; we have a separate page for that on software for fiscal representatives.

Can you still show an entry from six years ago?

Take an invoice number from an old financial year and try to find it in the form in which it was created. If that only works via a printout, you do not meet the requirement. We build this as a standalone application and as part of a broader custom software development project.

Edit content