Brutos EU Intrastat

Published: 02/24/2026/4:10 pm

Overview

This document explains the setup required and what is provided by the query reports provided by Vision33 for Intrastat reporting and the submission of Intrastat returns. A single query is available in the SAP Query Manager in the Intrastat category. For customers on HANA platforms there will be four separate queries. See below for further information on how this works.

Data will be returned on any sales or purchases, invoices or credit notes, for any EU country except for the home country.

If you are unsure about any definitions, rules or values referred to within this document please always refer to EU guidelines. A link to guidelines provided by UK HMRC is below:

https://www.uktradeinfo.com/intrastat/aboutintrastat/pages/supplementarydeclarations.aspx

The setup and reporting described in this document wholly replaces the SAP IS Reporting functionality and the reasons for this are explained in a later section.

Limitations

This document is valid for report version 2.3.

Nature of Transaction (NoTC) is defined as 10 for all transactions with a value and 30 for all transactions with a zero value. There are exceptions for DK & IE, see later.

Liquid mass calculations should be checked by the user to ensure that they are suitable for the business, see later section.

Further detail on these limitations is included in the relevant sections.

This document is for guidance only and no liability will be accepted for any errors or inaccuracies that may be contained within or the reports described.

Period

The reporting period date range is entered by the user at runtime and is based on the document posting date. This is the same as VAT reporting.

Commodity Codes

Commodity codes are defined by the EU and the correct codes must be identified and assigned by the user.

The default location for defining commodity codes is in the SAP Item Group.

This is a UDF, which will display if you click View/User Defined Fields in the SAP menu while in the item group form.

If defining commodity codes by the item group is not sufficient (e.g. merchandise is one item group but may span several commodity codes) then the user can select ‘N’ in the option “UseGroupCommodity” as illustrated above.

In this case the user must enter commodity codes in the item master, for all items in the group, and an 8 char UDF has been created for this purpose.

If SAP Intrastat has been activated and the item has been ticked as IS Relevant (see above) then the user will see an Intrastat tab in the item master but this is not used for V33 Intrastat reporting. See illustration below.

Value

An exact value calculation is displayed in the detailed reports and rounded up to whole currency units (GBP, EUR etc) in the summary reports. It uses document line total values in the local currency.

Any additional charges on the invoice are included. Free of charge items are also included and assigned an appropriate NoTC, see relevant section below.

Net Mass

Net Mass is the weight including immediate packaging and is expressed in kg. The detailed reports will show the exact calculated weight and the summary report rounds up to the nearest whole kg.

The calculation is hierarchical depending on the type of item and the data available.

So it will calculate net mass in kg, in several different ways depending on the data available, taking the first successful calculation from the list below:

Item Master weight field, sales or purchase

Pack type weight field

Quantity calculation if the unit of measure is kg, g or mg

Supplementary Units

This only applies to actual alcoholic beverages and the unit is defined on the item group.

If LPA is selected (for spirits) then the ABV must exist on the brand master.

Country

For Arrivals (purchases) this is always the supplier billing address country from the Business Partner record.

For Despatches (sales) this is from the customer document delivery address if one exists, otherwise it will take the customer document billing address country.

Delivery terms

An Incoterms UDF has been added to the marketing document header – U_IncoTerms, linked to a UDT – V33_INCOTERMS, as below:

This defaults to EXW in the query if no other value is defined in the UDF.

NoTC (Nature of Transaction)

This defaults to 10 for document lines with a value and 30 for document lines with a zero value. There are some country exceptions e.g. IE lines with value 1, DK 11.

Invoices and credit notes are treated identically except that credit notes are a negative adjustment to the calculated values.

A 20/21 (depending on country) code is intended for FOC returns and replacements, but they have been ignored because they are difficult to identify. If a credit was for a zero value it may not raised at all and how do we identify a replacement as opposed to an FOC sale? In the UK we also have a 16 code for credits where goods are not returned but it also notes that this cannot be used for correcting value errors. This is not easy to identify either.

If “without quantity” is ticked on a document row is it because goods are not being returned or because it is a value adjustment?

In both cases we would need an NoTC code to be manually selected on every order/invoice line and the whole idea of the V33 solution is to keep maintenance to a minimum.

So, in V33 Intrastat reports, credits/returns are recorded in the same manner as negative invoices.

Reports Provided

Reports are provided for Arrivals and Despatches. In both cases a summary report provides the rounded, summarised data required for the Intrastat Return and a detailed report provides a breakdown of the same data for audit purposes.

Always check your detailed reports to validate the reported data. Checking these reports is an effective method of checking that your setup is correct e.g. 0 weights or blank commodity codes will be displayed next to the offending item/document lines.

Some countries use variants of the default NoTC codes e.g. Denmark uses 11 instead of 10 for a straight sale or purchase. So, if the standard report values do not match your requirement then please let us know and we will add exceptions as necessary.

All reports are run from a single parameterised query from Query Manager, Intrastat category: (now separated on HANA installations)

Summary Report Illustration:

Detailed Report Illustration:

Setup Requirements

SAP and Brutos Setup

The Brutos pack types table must include the litres volume for pack types used.

The Brutos pack types table can also be used to define net mass in the “Weight” column.

Item Groups should define the commodity codes or else set the UseGroupCommodity=N and define on the item master.

Buying and selling units e.g. kg, g, mg, must be maintained in the item master for items not assigned to pack types. Otherwise set buying and selling weights e.g. for items purchased in boxes define the buying weight in kg, g or mg.

UDF’s

OITB.U_UseGroupCommodity     Use group commodity code Y/N
OITB.U_Commodity                       Group commodity code
OITM.U_Commodity                      Item commodity code if item group not being used

SAP Intrastat

SAP provides an Intrastat option in standard setup but this has been reviewed and the decision made that a simpler, more reliable alternative is required. The Vision33 Intrastat reports completely replace all SAP IS functionality. An overview of SAP IS is included below and the user is free to use this instead of the Vision33 option if required. SAP provide their own IS documentation and a V33 review document can also be made available on request.

SAP B1 Intrastat is a comprehensive utility and covers all possible requirements for Intrastat setup and reporting. Because of this the user needs to take care with the setup to obtain correct results. When the Intrastat Wizard is run, any mistakes or omissions may result in incorrect calculations and/or exclusions and these are not visible to the user. Error reporting is limited.

For example, the default settings in item master setup will multiple your supplementary unit of litres by the weight, which we do not want. Certain field values are mandatory in Intrastat reporting and SAP ensures that all these are present in a generated output file. If they are not, then those records will be excluded and unfortunately there is nothing in the wizard that informs the user about these exclusions. Note that it is mandatory to set values by item and there is no option to define by item group.

So, it is possible to process an Intrastat Wizard run with missing values but then an output file is not generated. There are also no standard reports to provide an audit trail of reported transactions and although this is not difficult to set up it will only include successful transactions.

Because certain fields are mandatory in the report they must be set up correctly in SAP to ensure accurate reporting. This means that the item master must include definition for Country of Origin, Commodity Code, Supplementary Units and the BP must include delivery address EU country, Incoterms, Nature of Transaction, Transport Mode. If any of these is missing, then the Intrastat run will fail.

There is obvious scope for error within the process and little visibility of errors. It also requires substantial maintenance.

Revision History