Messages according to the Dutch Taxonomy To the government via Digipoort Status and errors per message

Building an SBR integration

Appfront builds SBR integrations for accountancy firms, software vendors and organisations that want to submit reports digitally to the government or banks. Standard Business Reporting is the Dutch standard for exchanging financial messages, with XBRL as the format and the Dutch Taxonomy as the dictionary. We build the integration that composes and validates messages, sends them via Digipoort or another channel, and shows the status and any errors. So returns and reports come straight from your own system, without retyping them into a portal.

What is an SBR integration?

SBR, Standard Business Reporting, is the Dutch standard for exchanging financial data digitally in a consistent format. Messages are prepared in XBRL according to the Dutch Taxonomy and submitted via Digipoort to the Tax Administration, the Chamber of Commerce (KvK) and other government bodies. Banks use SBR for credit reporting. An SBR integration lets your software prepare and send those messages itself.

Without an integration, you take a detour. An accountant exports figures, enters them into another package or portal, and submits them there. A software supplier has its customers file via the Tax Administration's website themselves. Errors come back by email or on another screen, separate from the accounting records. And with every new version of the taxonomy, someone has to work out what changes.

We build it custom because the integration has to fit your software and your messages: which message types you submit, which accounting system the data comes from, whether you submit directly via Digipoort or through a service provider, how you handle certificates and authorisations, and how your users want to see the status. The taxonomy and Digipoort are standards; how they fit into your own process is the real work.

Messages from your system

Tax returns and reports prepared from the data in your own accounting system, according to the correct version of the taxonomy.

Validated before sending

Checks against the taxonomy rules before sending, so a message isn't only rejected once it reaches the recipient.

Status per message

Receipt, processing and any errors from the recipient fed back into your software, shown against the message and the client.

How we build your SBR integration

We start with your messages: which types, how many, which accounting system they come from, and how they are currently submitted.

1
Mapping messages and channels

Your message types and recipients, the source of the data, the submission channel, and certificates and authorisations.

2
Preparing and validating

Messages prepared from your data according to the correct taxonomy, with validation before sending.

3
Submission and status

Submission via Digipoort or your service provider, handling of status and error messages, and a log per message.

4
Testing and maintenance

Testing in the test environment, going live per message type, and maintenance when new taxonomy versions are released.

What an SBR integration actually does

The components below appear in almost every SBR integration. Which ones you need depends on your message types.

Taxonomy

Messages prepared according to the Dutch Taxonomy, with the correct version per message type and period.

Data from your system

Amounts and data from your accounting system mapped to the elements of the message.

Validation

Checks against the taxonomy and recipient rules before sending.

Submission

Sending via Digipoort with a PKIoverheid certificate, or via a service provider.

Status and errors

Confirmation of receipt, processing and error messages fed back against the message.

Log

For each message: what was sent, when, by whom and with what result.

Who we build an SBR integration for

The integration is intended for anyone who wants to submit SBR messages from their own software.

Accountants

Tax returns and annual accounts for many clients. The status per message and client is the core.

Software suppliers

Accounting or payroll software that needs to support SBR. The taxonomy and testing matter most.

In-house financial systems

An organisation that wants to submit directly. Submission via Digipoort is what's needed.

Credit reporting

Companies and advisers who report to banks. The messages for banks are the core.

Technology and integrations

This page is about SBR messages. For accountancy firm software, see our page on accountancy software; for a portal for accountants' clients, our page on an accountancy portal; and for accounting integrations, our page on an Exact Online integration. You can read about our approach at building software.

If your education board does not submit messages via Digipoort, but files its annual accounts through DUO's XBRL Education Portal, take a look at our integration with the OCW taxonomy.

If you want to code the general ledger accounts in your administrations consistently first, so that an SBR report follows from them, take a look at our RGS integration.

For XBRL outside Digipoort, such as inline XBRL and reporting to regulators, see our page on an XBRL integration.

XBRL Dutch Taxonomy Digipoort PKIoverheid certificate Validation before submission Status and error messages Messages for the Tax Authority and the KvK Credit reports for banks Log per message Test environment

Why Appfront for your SBR integration?

A filing that doesn't arrive has consequences for your client. That's what we build around: messages generated from your own system, validated before submission, and a status you can always see.

No retyping

Messages come straight from your accounting records. Nobody retypes figures into a portal.

Fewer rejections

Pre-submission validation catches most errors. Anything that is still rejected is visible immediately.

Ready for new versions

The taxonomy changes periodically. Maintenance of the integration keeps your messages up to date.

Security and privacy in an SBR integration

The integration processes financial data and taxpayer data, which is highly confidential. Certificates are stored securely and used only by the integration. Access is set up per role, and every message is logged with a name and timestamp.

The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and two-factor login.

Frequently asked questions about an SBR integration

Questions that accountants and software vendors ask before they get started.

Standard Business Reporting is the Dutch standard for exchanging financial data digitally, with XBRL as the format and the Dutch Taxonomy as the dictionary. It is used for tax returns, filing annual accounts and credit reports to banks, among other things.

Digipoort is the government facility through which messages from businesses reach, among others, the Tax Authority and the Chamber of Commerce (KvK). A direct connection requires a PKIoverheid certificate.

It isn't necessary. You can also submit via a service provider that handles the connection for you. Which route suits you depends on the number of messages and your own preferences; we look at that in the first step.

The message types supported by the Dutch Taxonomy, such as tax returns, annual accounts and credit reports. We build the types you need.

New versions are published periodically. As part of maintenance, we update the integration so your messages are prepared according to the correct version.

The integration processes the acknowledgement of receipt and the status messages from the recipient, and shows them alongside the message. Any error message comes back with the reason.

Check that first. Many accounting packages submit returns via SBR, and that is enough if you work with one. A custom integration makes sense if you have your own software, if you need message types your package doesn't offer, or if you are a vendor who wants SBR in your product.

SBR messages straight from your own software?

Tell us which messages you submit, from which software and through which channel. We'll show you what preparing, validating and submitting look like.

Edit content