PLANTS ABROAD · END TO END
How does Plants Abroad run across SAP?
Belgium owns the accounting document while the Netherlands owns the departure-country tax and reporting obligations.
Commercial demand
Sales order identifies BE entity, NL plant and DE ship-to.
Tax determination
SD evaluates departure, destination, classifications and VAT evidence.
Physical fulfilment
NL plant delivers and posts goods issue; the route is NL → DE.
Customer billing
Invoice carries the foreign-country result into the BE company code.
Financial posting
FI records receivable and revenue while preserving NL reporting country.
Country reporting
Dutch VAT, EC Sales List and Intrastat select the relevant evidence.
RESPONSIBILITY MAP
Four teams protect the same country story
Build correct demand
Plant, ship-to, partners, tax classifications and VAT data.
Prove movement
Delivery and PGI establish physical departure and border crossing.
Preserve the result
The company code posts the correct code and reporting country.
File correctly
Returns use the Dutch registration and NL reporting context.
STOCK-TRANSFER VARIANT
When stock moves between the company’s plants
An intracompany NL → ES movement has no customer sale, yet both countries may still require tax and statistical evidence.
Confirm the exact S/4HANA edition, localization and supported Intrastat selection model before assuming a legacy WIA design.
WHEN THE CHAIN BREAKS
Find the last trustworthy event
Wrong tax country
Reconcile plant and ship-to first.
Correct SD, failed FI
Compare mirrored tax definitions.
Missing VAT return
Inspect reporting-country and box mapping.
Missing Intrastat
Inspect movement and selection separately.
Translate the process into configuration dependencies, master data and transactional proof.