Intrastat from your own records Complete commodity codes and weights Checked before submission

Custom Intrastat reporting integration

Appfront builds integrations that let companies pull their Intrastat declaration to CBS (Statistics Netherlands) from their own records. Intrastat is the statistic on goods trade with other EU countries, and designated companies submit their arrivals and dispatches every month. We make sure the data comes from your ERP or order system, with commodity code, country, value, weight and transaction type, checked for completeness and ready to submit.

What is an Intrastat submission integration?

Intrastat is the system CBS uses to map goods trade between the Netherlands and other EU countries. Designated companies submit their arrivals from and dispatches to other EU countries every month, with per line, among other things, the commodity code, the country, the value, the weight and the type of transaction. The declaration can be submitted as a file.

In many companies the declaration is compiled by hand every month. An export from the ERP is edited in a spreadsheet, missing commodity codes are looked up, weights are estimated, and returns are settled separately. Items without a commodity code or weight only stand out when the declaration has to be submitted. And a correction to an earlier month is hard to trace.

We build custom because the data is recorded differently in every company: in which system orders, deliveries and invoices are held, whether items already have a commodity code and weight, how returns and triangular trade are booked, and who submits the declaration. Whether and how you are obliged to report, and which rules apply, you can read in CBS's notices and discuss with your adviser; the integration makes sure the data is complete and ready on time.

From your records

Arrivals and dispatches per month from your ERP or order system, without a spreadsheet.

Complete per line

Commodity code, country, value, weight and transaction type per line, with missing data flagged.

Ready to submit

A file in the required format, checked, with history and corrections per month.

How we build your Intrastat submission integration

We start with your flows of goods: which systems you use, what data you hold per item, how returns are handled, and how the declaration is currently made. It often turns out that most items already have everything, and the gap sits with a small group.

1
Mapping flows and data

Your systems, item data, returns, special flows and who files the declaration.

2
Collecting data

Arrivals and dispatches per month, with commodity code, country, value and weight.

3
Checking and completing

Missing or illogical data flagged, and completed at item level.

4
Submission and maintenance

File for the declaration, corrections to earlier months, and ongoing maintenance afterwards.

What an Intrastat submission integration does in practice

The components below feature in almost every Intrastat integration. Which ones you need depends on your flows.

Arrivals and dispatches

Per month, from your ERP, orders or WMS.

Commodity codes

Commodity code per item, with an alert when it is missing.

Value and weight

Value, net weight and supplementary unit.

Validation

Missing and illogical data per line.

File

File in the format required for the declaration.

Corrections

Corrections to earlier months, with history.

Who we build an Intrastat submission integration for

The integration is intended for companies that currently prepare the declaration by hand every month.

Wholesalers

Many items to and from EU countries. The commodity codes are the core.

Manufacturers

Raw materials in, products out. Value and weight matter most.

Online shops

Many small shipments to EU countries. Consolidation is what's needed.

Accountants

Declarations on behalf of clients. An integration per client is the core.

Technology and integrations

This page covers Intrastat reporting from your own records. For customs outside the EU, see our page on customs handling automation; for your own ERP, our page on a custom ERP system; and for excise duty, our page on excise administration. You can read about our approach at building software.

Intrastat Arrivals and dispatches Commodity codes Country of origin and destination Value and weight Nature of transaction Mode of transport Check per line File for the declaration ERP integration

Why Appfront for your Intrastat submission integration?

A declaration compiled by hand every month takes a day and contains estimates. That is what we build on: data from your accounts, missing codes and weights flagged early, and a file that is ready to go.

No monthly chore

The declaration follows from your accounts.

Fewer estimates

Missing codes and weights are completed at item level.

Traceable corrections

Each month shows what was submitted and corrected.

Security and privacy in an Intrastat submission integration

The integration processes data about your trade, such as customers, suppliers, values and quantities: confidential business information. Access is set up per role, and every submission is logged.

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

Frequently asked questions about an Intrastat submission integration

Questions companies ask before getting started.

It pulls the monthly arrivals and dispatches from your accounts, fills in commodity code, country, value, weight and nature of transaction per line, flags what is missing, and produces a file for the declaration. Corrections to earlier months are tracked.

The system Statistics Netherlands (CBS) uses to map goods trade with other EU countries. Companies that have been selected submit their arrivals and dispatches every month.

CBS decides that, and you will be notified. You can read which rules apply to you in that notice and discuss them with your adviser. The integration helps if you are required to file, and can be ready if you become so.

Then the integration flags it, per item. The code is recorded once at the item, and after that it happens automatically. This makes the declaration more complete every month.

Returns are processed according to the rules you set, as a separate line or as a correction. How that should work for your company is something to discuss with your adviser; the integration applies it consistently.

Yes. A correction is recorded with the month it relates to, so you can trace what was originally submitted and what was corrected.

Check that first. Many ERP packages have an Intrastat module, and that is enough if your product data is complete. Custom development makes sense when data sits in several systems, or when you file returns for multiple clients or companies. In that case an integration is often faster than a spreadsheet every month.

Intrastat straight from your own records?

Tell us which system your orders and deliveries come from, how you currently prepare the return and where data is missing. We will show you what the integration looks like.

Edit content