SAP “Plants Abroad” Functionality
A practical guide to managing cross-border VAT and Intrastat reporting in SAP.
SAP “Plants Abroad” is a standard SAP function that lets a single company code manage VAT registrations and tax reporting across several EU countries. It ensures the correct VAT registration number is applied to every sales invoice, treats VAT correctly on cross-border stock transfers and consignment transactions, and streamlines VAT and Intrastat reporting. The function automates the VAT and Intrastat postings that arise when a company moves its own stock across borders, and it supports the extra reporting obligations that come with holding VAT registrations in more than one country.
One point is worth stressing, because it is a common misconception: while “Plants Abroad” significantly improves VAT reporting and exchange-rate handling, it does not remove the underlying complexity of tax determination. That determination still has to be configured and managed with care.
When should you use “Plants Abroad”?
The “Plants Abroad” functionality becomes relevant in three closely related situations. The most common is where a company maintains plants, storage sites or warehouses in several EU countries and is VAT registered in each of them. It applies equally where goods move between those locations as intra-company transfers, or where consignment stock is held across EU borders. A further trigger is currency: when the countries in which the company is VAT registered operate with different tax currencies, the functionality provides the mechanism needed to convert and report amounts correctly.
Once “Plants Abroad” is activated, a dedicated tax-reporting-country field becomes available for VAT reporting, alongside the currency-conversion capability. This removes the need to create separate company codes for European plants or to rely on manual workarounds for VAT and Intrastat reporting — both of which are error-prone and challenging to sustain at scale.
Why standard SAP VAT determination is not enough
Standard SAP VAT determination does not cover every VAT requirement, because not all process flows fit within its default framework. Organisations that want to take full advantage of the available functions therefore need to activate the “Plants Abroad” setting deliberately, rather than assuming the standard configuration will accommodate every cross-border scenario.
How tax determination works in Sales and Distribution (SD)
Within the Sales and Distribution (SD) module, tax determination is driven primarily by two factors: the country of the supplying plant, which represents the country of departure, and the country of the ship-to party, which represents the destination. Tax classification is derived from the customer master and the material master in the context of the country of departure, while tax condition records are maintained with reference to both the country of departure and the destination country. Together these elements let SAP apply the appropriate VAT treatment to each transaction.
Cross-border stock transfers and the WIA invoice
With “Plants Abroad” in place, a dedicated plant-abroad invoice (document type WIA) can be generated for a cross-border, intra-company stock transfer between a foreign plant and a domestic plant — for example, between a warehouse in France and a warehouse in Germany. From a VAT perspective, such a movement is treated as a notional (fictitious) intra-community transaction, even though no third-party sale takes place.
To illustrate, a transfer of this kind requires an intra-community acquisition of goods, accounted for through the reverse-charge mechanism, to be reported in the German VAT return, and a corresponding intra-community dispatch to be reported in the French VAT return. Both sides of the movement must also be captured in the Intrastat report, keeping the statistical and fiscal records consistent across the two jurisdictions.
What activating “Plants Abroad” changes in SAP
The “Plants Abroad” functionality is embedded across the Sales and Distribution (SD), Materials Management (MM) and Financial Accounting (FI) modules. Activating it introduces new fields at transaction level, and because these are standard database fields they are present in every SAP environment by default.
The most visible change is a new “Tax Reporting Country” field added to the tax-code properties, which also appears on the VAT return reports and the EC Sales List. A further currency field converts VAT-relevant amounts into the currency of the relevant tax-reporting country. Beyond these reporting fields, the functionality supports new stock-transfer processes — including intra-company replenishment and consignment business — by enabling self-invoices through the WIA process.
Although “Plants Abroad” operates as a global, cross-functional setting in SAP, it can also be applied selectively to specific company codes where that better suits the business. From a VAT standpoint, the risk associated with activating the functionality is generally minimal, which makes it an attractive way to bring cross-border reporting under proper control.
How to activate “Plants Abroad”: a roadmap
Activation is best approached as a structured sequence rather than a single switch. The summary below shows each stage and its purpose.
| Stage | What it involves |
|---|---|
| 1. Review tax codes | Assess all existing tax codes to establish which require changes. |
| 2. Update tax codes | Add the “Tax Reporting Country” field so each transaction maps to the correct jurisdiction. |
| 3. Set up alternative currencies | Configure alternative currency fields to support multi-currency transactions. |
| 4. Update exchange-rate types | Adjust exchange-rate types to match each country's requirements. |
| 5. Configure stock transport orders | Define new pricing procedures so cross-border flows are priced and posted correctly. |
| 6. Review AP/AR tax-code selection | Check tax-code selection for Accounts Payable and Accounts Receivable, which the changes can affect. |
Working through these stages methodically helps ensure nothing is overlooked once the functionality goes live.
Conclusion
Successfully integrating and managing “Plants Abroad” within SAP calls for careful planning, deliberate configuration and appropriate training for the teams who rely on it. Handled this way, the function lets an organisation make full use of SAP's capabilities while continuing to meet local requirements — delivering greater operational efficiency and clearer visibility across international operations.
Frequently asked questions
- What is SAP “Plants Abroad”?
- It is a standard SAP function that lets a single company code manage VAT registrations and tax reporting in more than one EU country, automating VAT and Intrastat postings for cross-border movements of a company's own stock.
- When should you use “Plants Abroad” in SAP?
- Use it when a company holds plants, storage sites or warehouses in several EU countries and is VAT registered in each, when goods move between those locations as intra-company transfers or consignment stock, or when the registration countries use different tax currencies.
- Does “Plants Abroad” remove the need for separate company codes?
- Yes. Once activated it removes the need for separate company codes for European plants and eliminates manual VAT and Intrastat workarounds, because tax-reporting country and currency conversion are handled within one company code.
- What is a WIA invoice (document type WIA)?
- A WIA invoice is a plant-abroad self-invoice created for a cross-border, intra-company stock transfer between a foreign plant and a domestic plant. From a VAT perspective the movement is treated as a notional intra-community transaction.
- Which SAP modules does “Plants Abroad” affect?
- It is embedded across Sales and Distribution (SD), Materials Management (MM) and Financial Accounting (FI), adding standard fields such as the “Tax Reporting Country” field in every SAP environment.
- Is there VAT risk in activating “Plants Abroad”?
- The VAT risk on activation is generally minimal. It can be applied globally or selectively to specific company codes, but it does not remove the underlying complexity of tax determination, which still needs careful configuration.
Author
Richard is the founder and CEO of KGT and a former EY Indirect Tax Partner with over 30 years of experience. He studied tax law at the University of Leiden, where he earned a master's degree in law.
Early in his career at Andersen, Richard established one of the first business units at a Big Four firm dedicated to the intersection of indirect tax, ERP, and SAP.
An expert in tax control frameworks and tax function effectiveness, he publishes exclusively on the Global Indirect Tax Management website, where he shares best practices in the field.
Big Four firms operate under audit independence requirements that confine them to an advisory role and prevent them from developing products that affect financial reporting.
Richard founded KGT to close that gap, providing end-to-end solutions spanning SAP VAT advisory, optimization of tax determination logic, SAP configuration, and development of custom SAP add-ons that extend SAP's functionality.