VAT / BTW Reconciliation Procedures

Language / Taal: This document is the English version. Lees in het Nederlands

This document describes how Dutch auditors reconcile an entity's recorded VAT (BTW — Belasting over de Toegevoegde Waarde) position against its periodic VAT returns (BTW-aangifte), how corrections through the suppletie process work, and how the RGS (Referentie GrootboekSchema) aids in structuring the reconciliation. It covers the procedural steps, the relevant assertions, and where the process intersects with broader financial statement audit objectives.

1. The Dutch BTW System — Overview

Who is a BTW ondernemer

Any business that supplies goods or services in the Netherlands is, in principle, a BTW-plichtige ondernemer (VAT entrepreneur) and must charge BTW to customers, collect it on behalf of the Belastingdienst, and offset it against BTW paid on business purchases. The legal basis is the Wet op de omzetbelasting 1968 (Wet OB 1968).

BTW is a pass-through tax: the entity is not the economic bearer. The net amount owed to (or receivable from) the Belastingdienst at any point is the difference between verschuldigde BTW (output VAT charged to customers) and voorbelasting (input VAT paid on purchases and costs that are deductible).

Standard BTW rates (as of the source material date, 2026)

• 21% — standard rate (algemeen tarief)
• 9% — reduced rate (verlaagd tarief, for food, medicines, books, public transport, etc.)
• 0% — zero rate (nultarief, for intra-Community supplies, exports, specific domestic supplies)
• Vrijgesteld — exempt supplies (e.g., healthcare, education, financial services) where no BTW is charged and input VAT is generally not deductible

Reporting frequency

The Belastingdienst assigns each VAT entrepreneur a default reporting period:

• Quarterly (kwartaalaangifte) — the standard for most SMEs
• Monthly (maandaangifte) — required for entities with significant BTW turnovers or who have previously been late
• Annual (jaaraangifte) — available for entities with a small net BTW liability or refund

The reporting period assigned by the Belastingdienst determines how frequently the entity's general ledger BTW balances must be settled. For most Dutch SME audits, the relevant period is quarterly.

2. The BTW-Aangifte — Structure

Each BTW-aangifte follows a standardized form (Form OB). The key rubrics are:

| Rubriek | Description | |---|---| | 1a | Domestic supplies at 21% — output VAT base and tax | | 1b | Domestic supplies at 9% — output VAT base and tax | | 1c | Domestic supplies at other rates / zero rate | | 1d | Private use (privégebruik) of business assets | | 1e | Supplies where BTW is reverse-charged to the buyer | | 2a | Supplies from other EU member states (intracommunautaire verwervingen, ICV) | | 3a/3b | Supplies from outside the EU (import) | | 4a | Supplies to other EU member states at 0% (ICS — intracommunautaire levering) | | 5b | Voorbelasting (input VAT deductible) | | 5c | Small-business scheme adjustment (if applicable — KOR, Kleineondernemersregeling) |

The netto BTW (net VAT payable or receivable) is the sum of output VAT (rubrics 1–4) minus the voorbelasting (rubriek 5b). A positive result means the entity owes BTW to the Belastingdienst; a negative result means the entity is entitled to a BTW refund (teruggaaf).

3. BTW in the General Ledger

Dutch bookkeeping systems (Exact Online, AFAS, and others) automatically post BTW to designated BTW-accounts when transactions are entered. The accounts involved typically include:

• Te betalen BTW (BTW payable, a creditor balance): the running total of output VAT charged to customers across the period
• Te vorderen BTW / Voorbelasting (BTW receivable, a debtor balance): the running total of input VAT on purchases
• After settlement: a BTW-afdracht account or direct payment to the Belastingdienst reduces the net payable to zero

In systems aligned with RGS (Referentie GrootboekSchema, see erp-data-and-xaf-standards.md), BTW accounts are mapped to standardized RGS codes. RGS categorizes BTW positions under the W&V (resultaat) and balans sections. For audit purposes, the auditor needs to know the RGS codes used for BTW in the specific entity's bookkeeping to perform the reconciliation.

BTW-codes in the bookkeeping system

ERP systems like Exact Online and AFAS assign a BTW-code to each transaction line. The BTW-code determines:

• Which VAT rate applies
• Whether it is input or output VAT
• Which BTW account (grootboekrekening) the VAT amount posts to
• Which BTW-aangifte rubriek the amount flows into for automatic aangifte preparation

The BTW-code is the lowest-level key that ties a transaction's VAT treatment to both the general ledger account and the aangifte rubriek. Auditing BTW positions therefore requires understanding the entity's BTW-code configuration: are all codes correctly mapped to rubrics? Are there codes that should be zero-rated that are posting to a 21% account, or vice versa?

4. The Reconciliation Procedure

The core purpose of a BTW reconciliation in a financial statement audit is to confirm that the BTW balances shown on the balance sheet (BTW payable or receivable at year-end) are complete and correctly stated, and that any differences between the BTW position per the general ledger and the position per the aangifte have been identified and resolved.

Step 1 — Obtain the BTW-aangiften for the entire audit year

The auditor obtains copies of all BTW-aangiften filed for the financial year (typically four quarterly returns for an SME on quarterly reporting). These are obtained from the entity (usually via the Belastingdienst Mijn Belastingdienst portal printout or the accountant's tax software output).

Step 2 — Sum the aangiften and compare to the general ledger

For each BTW rubriek, the auditor sums the amounts across all four quarters and compares the total to the corresponding BTW account balances in the general ledger over the same period.

Example: the sum of rubriek 1a (21% output VAT) across all four quarterly returns should agree to the total credits posted to the "BTW hoog tarief" output account in the general ledger over the year. Unexplained differences require investigation.

Step 3 — Investigate and classify differences

Differences between aangifte totals and general ledger totals typically arise from:

• Timing differences: a transaction was booked in the general ledger in one quarter but included in an adjacent quarter's aangifte (or vice versa). These are acceptable if they reflect legitimate processing timing, but large or recurring timing differences may indicate control weaknesses.
• Corrections made directly in the aangifte without a corresponding general ledger entry — this is a significant control concern.
• Suppletie adjustments (see section 5 below) — corrections to prior-period aangifte errors are reported via a separate suppletieformulier and will show up as reconciling items.
• Coding errors: transactions posted with the wrong BTW-code, causing amounts to flow to the wrong rubriek in the aangifte.
• Exempt or zero-rated transactions incorrectly treated: for example, an intra-Community supply (ICS) charged at 21% instead of 0%.

Step 4 — Reconcile the balance sheet BTW position at year-end

At year-end, any settled quarterly positions should be zero on the balance sheet (paid or received). Only the Q4 position (if settled after year-end) or any unresolved discrepancies should remain as a balance sheet item. The auditor traces:

• Q4 output VAT balance: agrees to rubriek totals from the Q4 aangifte
• Q4 input VAT balance: agrees to Q4 voorbelasting rubriek
• Net Q4 balance: agrees to the BTW payable or receivable shown on the balance sheet
• Payment or refund after year-end: confirmed via bank statement or Belastingdienst portal record

Step 5 — Assess disclosure

If a material BTW payable is outstanding at year-end, it must be presented as a current liability (kortlopende schulden, crediteuren — belastingen en premies). BTW receivable (refund position) is presented as a current asset. Incorrect netting of BTW payable against BTW receivable from different periods requires correction.

5. BTW Suppletie — Correcting Prior Returns

What a suppletie is

A suppletie (BTW correction) is the mechanism for correcting errors or omissions in previously filed BTW-aangiften. The Belastingdienst's own guidance and the published Toelichting bij de suppletie btw describe it as the process to use when the original aangifte was wrong — either too much BTW was paid (over-declaration) or too little (under-declaration).

The suppletie is filed on a separate form (Suppletie btw / Correctie btw-aangifte, form OB99) and covers the difference between what was filed and what should have been filed. It is not a new aangifte but a standalone correction document.

When a suppletie must be filed

Under Dutch fiscal law, an entrepreneur is required to file a suppletie as soon as they discover a material error in a previous aangifte — without waiting for the Belastingdienst to request a correction. Voluntary and timely suppleties are treated more favorably than corrections made only after tax authority inquiry.

The Belastingdienst imposes a penalty (boete) for late, incomplete, or incorrect aangiften. A voluntary suppletie filed promptly typically results in a lower or nil boete.

Audit implications of suppleties

For the auditor, the existence of suppleties signals:

• Control weakness: if suppleties are frequent or for large amounts, this indicates systematic errors in the BTW-code setup or in the aangifte preparation process.
• Completeness risk: are all required suppleties identified and filed? The auditor should compare the entity's internally identified errors against the suppleties actually filed.
• Balance sheet impact: a suppletie generates either an additional liability (if the entity under-declared and owes more BTW) or a claim for restitution (if over-declared). Both must be reflected on the balance sheet as of year-end.
• Timing risk: a material suppletie filed shortly after year-end may indicate a year-end event requiring consideration under NV COS 560 (events after the reporting period).

The auditor should obtain a complete list of suppleties filed during and shortly after the financial year and trace each to the corresponding ledger entry and to the balance sheet treatment.

6. ICP Listing (Intracommunautaire Prestaties)

Entities that supply goods or services to VAT-registered customers in other EU member states at the 0% ICS rate must file a separate ICP-aangifte (opgaaf intracommunautaire prestaties) listing each such customer by VAT number and the total value supplied. The ICP-aangifte is filed quarterly (or monthly) and is checked by the Belastingdienst against the VIES system (VAT Information Exchange System) of the receiving country.

Audit relevance: the auditor should reconcile the 0% ICS amounts in the BTW-aangifte (rubriek 3b or the export/ICS rubrics) against the ICP-aangifte totals. Discrepancies can indicate that zero-rated supplies are being claimed without valid proof that the goods left the Netherlands or that the customer is a valid EU VAT entrepreneur.

7. RGS Mapping and SBR

The Referentie GrootboekSchema (RGS) is a standardized Dutch chart-of-accounts structure maintained by a steering group including the Belastingdienst, SBR (Standard Business Reporting), and several software vendors. RGS assigns every bookkeeping account a standardized code (RGS-code) and maps it to the XBRL taxonomy used in SBR/jaarrekening filings.

For BTW, RGS defines:

• Codes for output VAT at each tariff level
• Codes for voorbelasting (input VAT)
• Codes for BTW payable (creditor) and BTW receivable (debtor) on the balance sheet

ERP systems (Exact Online, AFAS) that are RGS-aligned will export journal entries with RGS codes embedded in the XAF file. This allows automated reconciliation of BTW positions: the auditor can filter the XAF for all entries under RGS BTW codes and cross-reference the totals against the filed aangiften. This approach is a standard analytical procedure under NV COS 520 (Cijferanalyses).

XAF 4.0 (the current auditfile standard, see erp-data-and-xaf-standards.md) is explicitly RGS-aligned, making the BTW reconciliation through the auditfile more straightforward than in earlier XAF versions.

8. Common BTW Audit Findings and Risk Indicators

| Finding | Possible cause | Audit response | |---|---|---| | Aangifte totals differ from GL totals by more than a small rounding amount | Timing difference, coding error, or unreported correction | Request reconciliation from entity; inspect underlying transactions | | BTW-codes missing from XAF or assigned "blank" | System configuration gap or incomplete migration | Review full BTW-code list in ERP; confirm all are mapped | | Large voorbelasting on costs typically not VAT-deductible (e.g., healthcare, exempt activities) | Incorrect input VAT claim | Review transaction-level BTW codes for specific account types | | Recurring suppleties of similar amounts or on the same rubriek | Systematic coding error or process control failure | Trace the root cause; assess internal control implication | | ICS supplies without corresponding ICP-aangifte entries | Potential non-compliance or omitted zero-rate documentation | Obtain proof of delivery to EU destination; check VIES | | BTW refund outstanding for more than two quarters | May indicate risk of classification (current vs. long-term) or dispute with Belastingdienst | Confirm status with Belastingdienst portal; assess collectability |

Sources

• Wet op de omzetbelasting 1968 (Wet OB 1968) — Dutch VAT law
• Belastingdienst BTW-aangifte guidance (datadump/belastingdienst/btw/btw_aangifte_doen_en_betalen.txt)
• Belastingdienst suppletie toelichting (datadump/belastingdienst/btw/suppletie_btw_toelichting.txt)
• AFAS BTW/ICP inrichten (datadump/afas/vat-btw/01-btw-icp-inrichten.md)
• Exact Online BTW codes (datadump/exact-online/vat-btw/)
• NV COS 500 (reliability of audit evidence)
• NV COS 520 (cijferanalyses — analytical procedures including GL-to-aangifte reconciliation)
• NV COS 560 (events after reporting period — suppletie timing implications)
• BW2 Art. 2:372 (balance sheet presentation)
• docs/erp-integration-exact-afas-research.md (RGS mapping details)

Research gap noted: The primary source for RGS BTW code details is the RGS specification maintained by the Auditfileplatform/SBR steering group. The specific RGS codes for BTW positions were not scraped at code-level detail in the current datadump; the RGS structure described here is based on secondary practitioner sources and ERP documentation. For code-level accuracy, consult the official RGS specification at odb.belastingdienst.nl or rgs.nl.