CIT filing software

Corporate income tax filing software in the Netherlands: what firms check in 2026.

Corporate income tax filing software (aangiftesoftware vennootschapsbelasting) must submit the return in SBR/XBRL via Digipoort, carry the annual figures from the bookkeeping into the return (the RGS bridge), and support one combined return for a fiscal unity. Below are the process and deadline points a firm or controller checks, plus where Lowkey's deterministic VPB layer fits: the reliable preparation before the return, not the filing package itself.

Create account What to check RGS bridge file: first file free

What to check in CIT filing software

Since the 2012 tax year the Dutch CIT return is a digital SBR message. The software you pick must do three things: submit in SBR format via Digipoort, carry the annual figures from the bookkeeping into the return reliably, and handle the tax adjustments and any fiscal unity correctly. The points below are what a firm or controller actually checks in 2026.

Does the return go via SBR and Digipoort?

Yes. Standard Business Reporting (SBR) is the method for compiling and submitting the return, in the open XBRL standard. All SBR reports to government run through one digital channel: Digipoort. CIT filing software must therefore submit in SBR format; the submitting system needs a PKIoverheid services certificate to send through Digipoort. Check that your package supports the current Belastingdienst taxonomy for the tax year you are filing.

What is the filing deadline in 2026?

In principle the return must be in within five months after the end of the financial year. If the financial year matches the calendar year, the 2025 return is due before 1 June 2026. Extensions are possible: the Belastingdienst usually grants five extra months. If your firm works under the Becon extension scheme (the extension scheme for tax consultants), a longer filing schedule applies under which you file a set percentage of your returns spread across the year. Verify the exact dates and schedule per case; broken financial years and extensions move the deadline.

In practice this means your software has to keep the deadline and extension status visible per client. A missed or misjudged deadline triggers a default penalty, separate from the contents of the return.

What is the role of RGS and the bridge file?

RGS (Referentie Grootboekschema, the Dutch reference chart of accounts) is the standard that links the general ledger accounts in the bookkeeping to the SBR codes you file with. It is the bridge between your own account numbers and the codes you report in to the Belastingdienst, the Chamber of Commerce and the statistics office. A bridge file (brugstaat) is the import file that records that mapping per item, so the annual figures reach the filing software without retyping.

What usually goes wrong is not the technology but the mapping: a mislinked account moves an amount to the wrong line in the return. Good preparation records that mapping deterministically and flags the items the adviser has to review.

What about tax adjustments and the C/F reconciliation?

The return starts from the commercial annual figures, but taxable profit differs from them. Think of an adjustment for fiscal depreciation on a building (capped at the floor value), the deduction limit for mixed costs, the earnings-stripping rule that caps the deduction of net interest, and loss relief. Software has to make that commercial-to-fiscal reconciliation (the C/F reconciliation) traceable, not just show the end figure. In an audit you want to show the bridge from trial balance to taxable profit.

How does the fiscal unity work?

In a corporate income tax fiscal unity the parent company files one combined return for the whole group; the results of the included subsidiaries are taxed at the parent. The requirements are in article 15 of the Dutch Corporate Income Tax Act 1969 (Wet Vpb), including legal and economic ownership of at least 95% of the shares, with at least 95% of the voting rights, the profit and the net assets. Your software must be able to consolidate the group bookkeeping into a single return, including eliminating intercompany positions. The run-up, the formation request itself (Part A and Part B), is separate from the return. Read more about the fiscal unity request.

Where does the client data sit?

For a firm under a duty of confidentiality this is not a detail. A CIT return holds the client's full figures. For every component that touches data (OCR of uploads, storage, processing) check the region and the retention policy. Under the GDPR the firm stays the data controller; a vendor is a processor and should record that in a data processing agreement. Read how we handle data and why everything runs in the EU.

Sources: Belastingdienst on SBR, Belastingdienst on the CIT return and deadline, Belastingdienst on the Reference Chart of Accounts (RGS) and article 15 Dutch CIT Act 1969 (wetten.overheid.nl). Last updated: 30 June 2026.

Existing filing package or Lowkey?

Important and honest: Lowkey is not a replacement for your filing package. The SBR submission to Digipoort still runs through your existing software. Lowkey is the deterministic layer before it: the working papers, the reconciliation and the bridge file that set the figures up reliably for import. The table shows who does what.

  Existing filing package Lowkey CIT layer (before it)
Role in the chain Compiling and submitting the return Working papers, reconciliation and bridge file that prepare the figures
End product Filed CIT return in XBRL AMFO reconciliation and RGS bridge file, ready to import
SBR submission via Digipoort Yes, that is the core task No, it does not submit; it feeds your package
Output Structured per provider Deterministic: same input gives the same bridge file
Client data and GDPR Differs per provider EU only; processed in memory and discarded
Fiscal unity Consolidates the group in the return Fills the formation request, Part A and Part B
Pricing model Licence or subscription Per finished document; bridge file from EUR 5

How the Lowkey CIT layer works

01

Annual accounts or trial balance in

Upload the annual accounts (PDF) or a trial balance (Excel or CSV). A model reads the upload only to take over the figures and accounts. It never decides the tax outcome.

02

Reconciliation and RGS bridge file, deterministic

Lowkey builds the AMFO reconciliation and the RGS mapping on fixed rules. Every general ledger account is mapped to RGS 3.5, with explicit check points for the items the adviser has to review. The same input gives the same bridge file every time.

03

You check and import into your package

You get the bridge file back, ready to read into your existing filing software. The tax assessment, the adjustments and the SBR submission stay with your firm and your own package.

What the tool does and does not do

Does
Build an AMFO reconciliation and an RGS bridge file, deterministic and repeatable, ready to import.
Does
Fill the fiscal unity formation request (Part A and Part B), consistent across both parts.
Does not
Submit the return for you via SBR/Digipoort, or take over the tax assessment. That stays with you and your filing package.

Weighing up which package fits your firm more broadly? Read the guide on choosing tax filing software, the honest comparison of suites, general AI and narrow tools, and where we keep your data in the EU.

Pricing

EUR 5 / bridge file, excl. VAT

The RGS bridge file is EUR 5 per file, the first file is free per firm. The fiscal unity formation request is EUR 49 per document. You are billed per finished document, collected monthly through Stripe. No seats, no minimum, no setup fee. You only pay when a file is produced.

Frequently asked questions

Must the Dutch CIT return be filed via SBR?

Yes. The corporate income tax return is filed electronically via Standard Business Reporting (SBR) in XBRL format, over the government channel Digipoort. CIT filing software must therefore submit in SBR format; a PKIoverheid services certificate is required to send through Digipoort.

What is the CIT filing deadline in 2026?

In principle within five months after the end of the financial year; for a calendar year that is before 1 June of the following year. Extensions are possible, usually five extra months via the Belastingdienst, and under the Becon scheme an adviser works to a longer filing schedule. Verify the exact dates per case.

Does Lowkey replace my existing filing package?

No. Lowkey is the reliable preparation layer before the return: reconciliation, working papers and an RGS bridge file for import, plus the fiscal unity formation request. The SBR submission to Digipoort still runs through your existing package.

Does Lowkey store the client data?

No. Uploads and data are processed in the EU to produce your working paper or bridge file and then discarded. We keep a billing line, never the contents. Read how we handle data.

General information, not personalized tax advice. Process and deadline details can vary by case and tax year; check them with the Belastingdienst. Last updated: 30 June 2026.

Related topics

Further reading on the CIT chain and software:

Lowkey tools Portal for firms Fiscal unity (CIT) ATAD2 hybrid mismatch