EMEBI and VAT summary statement 2026: obligations, deadlines and errors to avoid

For a company shipping or receiving goods in the European Union, the question is no longer just "doing a DEB" as before. In 2026, we must distinguish two obligations which coexist in the customs tool: the monthly statistical survey on intra-EU trade in goods (EMEBI) and the VAT summary statement. Both rely on your flow of goods, but they do not pursue the same purpose, do not obey exactly the same rules and do not tolerate the same approximations.

In practice, many companies still make mistakes on three points: they confuse statistics and taxes, they base their calendar on the invoice instead of the reference month used by the administration, and they let the accounting, ADV and logistics teams work with different nomenclatures. Result: declarations corrected repeatedly, requests for clarification from customs, inconsistencies with VAT and loss of time during closing.

This guide takes stock of the 2026 rules based on official sources from Customs and the CGI, in particular article 289 B for the VAT summary statement. If you have already read our file on [intra-community VAT] (/blog/tva-intracommunautaire-2026-obligations-taux-remboursements), consider this article as its operational extension on the flow of goods side.

The first confusion to clear up is simple: the EMEBI is a statistical obligation, while the VAT summary statement is a tax obligation. Both are fed into the same reporting universe, but the administrations do not look at the same thing.

The VAT summary statement covers intra-EU deliveries of exempt goods. Customs reminds that these deliveries must be declared from the first euro. This is the practical translation of article 289 B of the CGI: when a French company ships goods to a taxable person identified for VAT in another Member State, it must be able to justify the exemption and resume the operation in the summary statement.

EMEBI is used for public statistics. It does not automatically concern all companies. Only companies selected in the statistical sample must respond, by type of flow, according to the instructions notified to them. The same company can therefore be concerned by the VAT summary statement without being required to pay EMEBI, or vice versa for a particular flow.

For the VAT summary statement, the basic rule is broad: as soon as you make intra-EU deliveries of goods, you must declare. This targets classic sales, but also certain transfers assimilated to deliveries, for example a movement of stock from France to another Member State for the needs of the company.

For EMEBI, the logic is different. Customs selects the companies surveyed and specifies whether the obligation relates to introductions, shipments or both. This point is essential because a manager may think he is "not concerned" on the grounds that his accounting team does not see any VAT to declare on a flow, while the statistical survey remains due.

Another point often forgotten: when the company is selected for EMEBI, the response may remain obligatory even in the absence of flows in a given month. The official FAQ explicitly indicates that it is then necessary to submit a "month without statistical response". This is an operational detail, but it is also a highly observed marker of declarative discipline.

The schedule is stricter than you might think. Customs specifies that EMEBI responses must be received no later than the 10th working day following the reference month. They cannot be definitively recorded before the first day of the following month. Concretely, this requires a rapid monthly closing process between logistics, export trade, ADV and accounting.

For the VAT summary statement, the company must also reason by reference month in line with its intra-EU deliveries. The real risk is to wait until the full accounting close of the month to process the declaration. In the most exposed cases, we recommend a logistical pre-cutoff and then a rapid reconciliation with invoicing.

A reliable declaration assumes that several fields are aligned with each other:

• the customer's VAT number in the other Member State;
• the actual country of destination;
• the nature of the flow;
• the declared value;
• the reference date retained;
• the tax qualification of the transaction.

In practice, the most costly error is not always an error in amount. This is often a mischaracterization. A stock transfer, return, misunderstood triangular transaction or consignment shipment can produce a different tax reading than the simple commercial invoice. This is why the link between your customs, accounting and supply chain teams must be documented, not just informal. If you work internationally, our article on the EORI number and our guide on Incoterms 2026 can help lay the foundations of your document flows.

1. Confusing invoice issued and reference month#

The accounting month does not always coincide with the reference month of the EMEBI or the VAT summary statement. When physical delivery, VAT liability and invoicing are out of sync, the declaration must follow administrative logic, not your reporting comfort.

2. Allow stock transfers to go through#

Many businesses mistakenly believe that it takes a sale to report. However, Customs points out that a transfer for business purposes can be assimilated to a delivery. This is a classic blind spot for groups that use several European warehouses.

3. Use an unverified customer VAT number#

A missing, invalid or incorrectly linked intra-community VAT number to the correct customer directly weakens the exemption. Here, business discipline is as important as tax technique.

4. Not correcting erroneous statements#

The official FAQ provides for online correction of answers submitted. Waiting for a check to regularize is almost always a bad strategy. A voluntary and documented correction remains preferable to a persistent inconsistency between VAT, ERP and customs declaration.

5. Isolate the declaration in a single service#

When only accounting manages the subject, logistical errors surface too late. When only logistics is in charge, tax teams lose track of the exemption justification. Best practice is a clear accountability matrix, with a data owner and a fiscal validator.

A robust process is based on five simple building blocks:

1. map the real flows: sale, transfer, return, custom work, deported stock;
2. define the expected VAT and statistical qualification for each flow;
3. lock mandatory fields in the ERP or TMS;
4. reconcile physical shipments, invoicing and declarations each month;
5. maintain a legible audit trail in the event of an audit.

This work is particularly useful before an export expansion, a warehouse opening in another EU country or a change of Incoterm. In many files, the issue is not only declarative: it also affects cash flow, proof of exemption and the ability to respond quickly to the administration.

In 2026, the EMEBI and the VAT summary statement must be treated as a mini data governance project. The VAT summary statement is part of your tax discipline and applies from the first euro for intra-EU deliveries of goods. The EMEBI comes under public statistics and is only due if the company is surveyed, but it can remain obligatory even without a flow over a month.

A company that wants to make its intra-European development more reliable must therefore think beyond the simple "on-time deposit". It must ensure that the qualification of the flow, the documentary proof and the consistency with VAT are aligned. This is exactly the type of subject that should be covered before a test, not during it.