SAP S/4HANA Localization Guide: Italy, Spain, France, Germany, UK

What it takes to make SAP S/4HANA legally compliant in five European countries: the shared building blocks, the country-specific tax, e-invoicing and reporting requirements, and the configuration activities for each.

Shared building blocks

SAP S/4HANA ships with a common international core, and each country's obligations are covered by a country version activated per company code. Before configuring any single country, a set of foundations has to be in place:

• Company code country key, which drives the default tax procedure, address layout and payment formats.
• An operating chart of accounts plus, where required, a country chart of accounts.
• One tax calculation procedure per country (TAXIT, TAXES, TAXFR, TAXDE, TAXGB).
• Country-specific business partner fields for tax IDs and banking.
• Number ranges that meet legal sequential numbering requirements.
• VAT returns through Advanced Compliance Reporting, e-invoicing through Document and Reporting Compliance, Intrastat and EC Sales Lists, extended withholding tax, and country financial statement versions.
• Country forms, SEPA payment formats and legal archiving.

The five countries at a glance

Italy

Italy is one of the most demanding SAP localizations. All B2B, B2C and B2G invoices must be issued as FatturaPA XML and pass through the Sistema di Interscambio, which DRC handles including SDI status notifications. Configuration covers business places, VAT registers and periodic VAT settlement, withholding tax (ritenuta d'acconto), the SDI channel (PEC or an accredited intermediary), legal numbering and the Bilancio CEE financial statement version. Because SDI specifications change often, the guide recommends a recurring SAP Note review and regression test cycle.

Spain

Spain's SII requires large taxpayers to report invoice data to the tax agency within four business days. Configuration covers the SII activation date, message types and certificates, VAT book mapping, withholding tax, the Modelo 303, 349 and 390 returns, and Facturae for public-sector invoicing through FACe. Monitoring of rejected and partially accepted records belongs in the support model, not just the initial build.

France

France combines VAT compliance with the FEC, a standardised export of all accounting entries produced on request for tax audits, and the phased rollout of B2B e-invoicing and e-reporting through certified platforms (Factur-X, UBL and CII formats). Public-sector invoices already go through Chorus Pro. Because the mandate timeline has shifted several times, the guide recommends treating it as a separate project track with its own go-live date.

Germany

Germany centres on GoBD: accounting records and system changes must be unalterable, traceable and retrievable for the retention period. Configuration covers change logging, archiving, gap-free number ranges, DATEV export for tax advisors, XRechnung and ZUGFeRD e-invoicing as the B2B mandate phases in, the HGB financial statement version and the VAT pre-return and EC Sales List. The guide advises running a mock tax-audit data export during testing.

United Kingdom

After Brexit, the UK's main digital obligation is Making Tax Digital: VAT records kept digitally and the nine-box return submitted through software connected to HMRC's API. Configuration also covers postponed VAT accounting for imports, BACS, Faster Payments and CHAPS formats, and EORI numbers. EU cross-border settings should not be reused unchanged for UK company codes.

Recommendations

• Run localization as a parallel workstream with its own fit-gap, build and test cycle per country.
• Involve local tax experts during design, since thresholds and formats change independently of SAP releases.
• Test every e-invoicing and reporting integration end to end against government sandboxes.
• Enforce country-mandatory business partner fields at entry rather than fixing them later.
• Monitor SAP Notes and legal changes continuously, and build dashboards so finance can react within statutory windows.

The PDF includes a cross-country configuration checklist covering all five jurisdictions. It is a planning aid, not legal or tax advice; always verify current rules with SAP Notes and the local tax authority.