EU VAT, OSS & Intrastat Reporting

The problem

EU VAT reporting is not one return. A seller with cross-border activity is producing a domestic VAT return per registration, a One-Stop-Shop return covering B2C distance sales into other member states, an EC Sales List for B2B intra-community supplies, and Intrastat declarations for dispatches and arrivals once the value thresholds are passed. Each has its own period, its own filing body, its own definition of what counts, and its own format.

NetSuite holds every fact you need to produce all of them — the customer's country and VAT number, the ship-from and ship-to, the item's commodity classification, the transaction value, the currency, the date. What it does not do is assemble those facts into the four different shapes the four different returns require. So the shapes get assembled in Excel: an export of invoices, a VLOOKUP against a country table, a manual split of B2B from B2C, a hand-typed Intrastat file, and a quarterly ritual that one person understands and nobody can audit.

That process breaks quietly. A credit memo issued after period close never makes it into the OSS correction. A customer VAT number that was valid at order time was deregistered before invoice date, so a zero-rated supply should have been charged domestic VAT. An item added last month has no commodity code, so it silently drops out of Intrastat. None of these produce an error anywhere — they just produce a wrong return.

What ECOSIRE builds

We build the reporting layer NetSuite is missing: a set of scripts and records that classify each transaction once, at source, and then derive every EU return from that classification.

Transaction classification at source

A User Event script on Invoice, Credit Memo, Cash Sale and Vendor Bill classifies each line the moment it is saved. It determines the supply type — domestic, intra-community B2B supply, intra-community acquisition, OSS-eligible distance sale, export outside the EU — from the ship-from country, the ship-to country, the customer type and whether a valid VAT number is on file. The classification, the member state of consumption and the rate applied are written to fields on the line, so every downstream report reads a decided value rather than re-deriving it and possibly deriving it differently.

OSS return preparation

A Map/Reduce script aggregates OSS-eligible supplies by member state of consumption and by VAT rate for the reporting quarter, nets off credit memos, and handles corrections to prior periods as separate correction lines the way the OSS return expects. Output is a review screen built as a Suitelet, with drill-down from each aggregated figure to the underlying transactions, plus a structured export in the layout your filing portal or agent requires.

EC Sales List

Intra-community B2B supplies are grouped by customer VAT number and supply type (goods, services, triangular) for the ESL period. The engine flags any transaction classified as an intra-community supply where the customer VAT number is missing, malformed for its country, or was not verified — those are exactly the lines that later become assessments, and they surface before you file, not after.

Intrastat dispatches and arrivals

A custom segment on the item record carries the commodity code, net mass and supplementary unit. A Map/Reduce job builds dispatch and arrival lines by partner member state, commodity code, nature of transaction, delivery terms and mode of transport, converting values to the declaration currency at the rates your policy specifies. Items missing a commodity code or mass are reported as exceptions with a direct link to the item record, so the gap is fixed once rather than patched every month. Threshold tracking tells you when a member state's arrivals or dispatches threshold is being approached.

VAT number validation

A Scheduled script revalidates customer VAT numbers on a cadence you set and stores the result and the date on the customer record, so the zero-rating decision is backed by a dated check. Where you have access to an official verification service, the script calls it; where you do not, it applies per-country format and checksum validation. Which of these applies is agreed in scoping, not assumed.

Period control and audit

A reporting-period custom record locks a filed period so late transactions are routed into the next period's corrections rather than silently changing a return you have already submitted. Every generated return is stored as a record with its figures, its generation timestamp and the transaction set it was built from — which is what an auditor asks for.

Who this is for

EU-established sellers using OSS for B2C distance sales; businesses with multiple EU VAT registrations running under OneWorld subsidiaries; distributors and manufacturers moving goods across member state borders and therefore in scope for Intrastat; and any finance team whose current EU VAT process depends on one spreadsheet and one person.

How delivery works

1. Scoping call. We review your registrations, which member states you file in, whether you use OSS or IOSS or both, your Intrastat obligations by member state, your item data quality and your current filing route (direct portal, agent, or software).

2. Fixed quote. A written scope and a fixed price, issued before any development starts.

3. Build. Development as an SDF project — SuiteScript 2.1 User Event, Map/Reduce and Scheduled scripts, custom records, the item custom segment, saved searches and the Suitelet review screens. Typical lead time is one working week.

4. Install in your sandbox. We deploy to your sandbox, run the reports against a historical period you have already filed, and reconcile our output to your submitted figures line by line. Differences are investigated until each one is explained — that reconciliation is the real acceptance test.

5. Production deployment. The same bundle goes to production with script deployments, role permissions and period configuration. We run one live period alongside your existing process before you rely on it alone.

6. Support window. A defined post-go-live period for defect resolution and configuration support, plus the full source and documentation.

This is built to order for your account. There is no ready-made download and no free trial — we scope it, quote it, build it, and you own the resulting SDF project.

What you should know upfront

We build the derivation, the review screens, the exception reporting and the export files. We are not tax advisers and we do not sign or submit your returns. Where a member state requires a specific electronic format or a licensed intermediary, we build to that format and integrate with the route you already use; the filing relationship stays yours.