Relocating Electronic Bookkeeping Abroad: Rules and How to Avoid Penalties

German rules on the relocation of electronic book keeping (elektronische Rechnungsstellung) have become more flexible in recent years.

Businesses can now keep and manage electronic books and records not only in the EU/EEA, but also in other countries if legal tests are met. That includes places like the US, Switzerland or the UK, which are common outsourcing sites.

The draft bill of the German Ministry of Finance from August 5, 2026 adds a new relocation penalty (“Verlagerungsgeld”) for companies that do not follow the rules in cross-border bookkeeping.

This guide explains what is changing, when penalties can apply, and how tax and finance teams can prepare. It focuses on cloud setups and outsourced services.

Framework for Relocating Electronic Bookkeeping

Under the general rule, books and records must be kept in Germany. The German Tax Code (“Abgabenordnung” or “AO”) allows exceptions for electronic bookkeeping under defined conditions:

Relocation within the EU/EEA Electronic books and records may be kept in one or more EU Member States. A formal application is not required, but:

• taxation must not be harmed; and
• the German tax authorities must keep full access to tax-relevant data.

Relocation to third countries Electronic books and records may also be kept in one or more non-EU states. This is only allowed if the taxpayer applies to the competent German tax office, and certain conditions are met, including:

• disclosure of data processing sites and service providers,
• compliance with procedural duties under the AO,
• unrestricted electronic access for the tax authorities,
• no harm to taxation.

Paper records must continue to be kept in Germany. Only electronic books and records, or parts of them, may be moved.

These rules have helped many groups centralize bookkeeping and use global outsourcing. At the same time, tax authorities can revoke approvals and demand a move-back of the electronic bookkeeping.

What Is New: The Relocation Penalty

The draft bill introduces a specific penalty linked to the Verlagerung der elektronischen Buchführung. It does not really change whether relocation is allowed, but it raises the stakes for procedural failure.

Under the planned rule in Section 146(2c) AO, the relocation penalty:

• ranges between EUR 2,500 and EUR 100,000, and
• targets breaches of duties directly tied to relocation.

In practice, this gives tax authorities a focused tool. Instead of relying only on general penalties and formal steps, they can sanction relocation-related failures directly.

Triggers and Amount: When Can the Penalty Apply?

The relocation penalty can be imposed if a taxpayer:

Ignores a move-back request If the tax authority orders a move-back of the electronic bookkeeping, for example after revoking a third-country approval, and the taxpayer does not comply, a penalty becomes possible. Relevant cases include:

• no relocation within the set period,
• incomplete relocation, with key data still abroad,
• failure to show that the move-back was done properly.

Breaches duties tied to an approved relocation Approval for third-country relocation or allowed relocation within the EU/EEA comes with ongoing duties. These usually require that:

• full data access for the German tax authorities is kept,
• procedural duties under the AO remain met,
• the relocation setup does not harm taxation.

If these duties are not met, for example because IT architecture or service providers change, the penalty can apply even though an approval exists on paper.

Moves electronic bookkeeping to third countries without approval If electronic bookkeeping is moved to one or more third countries without the required approval from the competent tax authority, this is a direct trigger for the penalty. This includes:

• moving core systems without an application,
• later adding third-country parts that effectively move parts of the bookkeeping.

The range of EUR 2,500 to EUR 100,000 lets tax authorities match the penalty to the size and length of the breach.

Why Unapproved Third-Country Relocation Is Especially Risky

Modern bookkeeping setups are complex. They often include:

• ERP and general ledger systems,
• invoice and workflow tools,
• document archiving platforms,
• interfaces and middleware,
• cloud hosting, storage, and backup services.

In such setups, relocation is not limited to one main server moving abroad. Risk also arises where:

• production data is hosted in third-country data centers,
• backups or disaster recovery sites are located in third countries,
• data is copied to third-country regions for speed or backup,
• administrators or support staff access systems from third countries,
• certain bookkeeping parts, such as sub-ledgers or invoice processing, are run from third-country service centers.

Because third-country relocation needs approval, any relevant third-country footprint of electronic bookkeeping must be reviewed carefully. The draft bill itself does not spell out technical rules for multi-region cloud setups or distributed services.

A practical compliance approach is therefore to:

• treat any third-country role in core bookkeeping data or operations as possibly covered by the relocation regime; and
• check carefully whether that role:
  • is clearly outside the relocation scope, for example a purely support service, or
  • is covered by an existing approval and documented as such.

Where doubt remains, taxpayers should ask the tax office for clarification or change the setup to avoid unapproved third-country relocation.

Practical Checklist: How to Reduce Relocation-Penalty Exposure

To manage relocation risk well, tax and finance teams need a clear view of their technical and organizational setup. The following steps help build that view and prepare for the new penalty:

Map the electronic bookkeeping landscape List all systems that form part of electronic bookkeeping, including:

• ERP, general ledger, and sub-ledgers,
• invoice receipt and processing tools,
• document management and archiving solutions,
• e-invoicing, book keeping software (digitale Buchhaltung, Buchhaltung Software), and digital book keeping tools.

Include outsourced services and cloud platforms, not just in-house applications.

Document data processing and storage locations Record where data is:

• stored and processed in production,
• copied or mirrored,
• backed up and archived,
• held for disaster recovery.

Capture where administrators and support teams access systems from, including remote access from abroad.

Identify and flag third-country elements For each part, note whether it involves:

• hosting or storage in a third country,
• day-to-day control or administration from a third country.

Distinguish clearly between:

• third-country elements covered by explicit approvals, and
• unapproved third-country exposure.

Centralize relocation approvals and correspondence Keep a file of:

• applications for third-country relocation of electronic bookkeeping,
• approvals granted by the tax authorities, including conditions,
• correspondence about changes to systems or locations.

Make sure the file is up to date and easy to reach for audits or inquiries.

Develop and test a move-back plan Define internal roles and responsibilities:

• tax and finance for regulatory coordination,
• IT for technical moves.

Establish processes for:

• exporting and moving data back to Germany, or another allowed location,
• resetting systems and shutting down third-country environments,
• showing the tax authority that the move-back was completed.

Where possible, run test migrations or at least dry-run planning exercises.

This checklist turns abstract relocation duties into concrete operational steps and can lower the risk of penalties.

Typical High-Risk Scenarios Under the New Regime

Based on the draft bill and existing rules, several scenarios stand out as possible triggers for relocation penalties:

Hidden third-country cloud use A group moves its ERP to a major cloud provider. Due to default settings or later tuning, data ends up copied to non-EU regions, for example for speed or resilience. No relocation approval has been requested, and tax teams do not know about the third-country footprint.

Backup and disaster recovery in third countries Primary systems stay in the EU, but backups or disaster recovery sites are placed in third-country data centers. From a tax view, this may count as partial relocation of electronic bookkeeping, and without approval it can trigger penalties.

Failure to comply after approval is revoked A third-country relocation was approved at first. Over time, conditions are no longer met, for example because access procedures change or new providers are added without disclosure. The tax authority revokes the approval and orders a move-back. The taxpayer does not move back in time or cannot prove that the move-back was complete.

Weak procedural documentation During a tax audit, the taxpayer cannot show:

• • where bookkeeping data is stored and processed in detail,
  • how access for the tax authority is kept,
  • which approvals cover which parts.

This may lead the authority to decide that relocation duties were breached and to impose a penalty.

These scenarios show that relocation risk often comes from technical changes and configuration details, not just from a strategic choice to move bookkeeping abroad.

What to Monitor as the Draft Evolves

As the legislative process continues, several points will be important:

Definition of relocation in complex IT setups How authorities will treat:

• multi-region cloud deployments,
• hybrid on-premise/cloud models,
• distributed services such as separate invoicing, archiving, and analytics in several jurisdictions.

Scope of electronic bookkeeping Clarity on which systems and data count as part of electronic bookkeeping for relocation purposes, especially where tax-relevant and non-tax-relevant data are mixed.

Treatment of third countries Any special handling of countries with certain data rules or adequacy decisions, and how this fits with relocation approvals.

Evidence requirements for approvals and duties Practical expectations on:

• documentation of approval and its scope,
• ongoing proof of data access and procedural compliance,
• acceptable formats and steps for showing a completed move-back.

Tax and finance teams should follow guidance, admin practice, and case law so their internal standards stay aligned with new expectations.

Conclusion: Build Operational Readiness Around Relocation

The draft bill introduces a relocation penalty between EUR 2,500 and EUR 100,000, aimed at three situations:

• failure to comply with a move-back request,
• breaches of relocation-related duties under an approved or allowed setup,
• unapproved relocation of electronic bookkeeping to third countries.

For businesses that rely on global cloud and outsourcing solutions, the core response should be operational, not just formal:

• map the full system and data footprint of electronic bookkeeping,
• identify all third-country parts and verify their approval status,
• organize approvals and correspondence in a strong file system,
• design and test a practical plan to move electronic bookkeeping back if needed.

This proactive approach turns relocation rules from a penalty trap into a manageable compliance area. It also helps businesses handle future audits and rule changes with more confidence.

Q&A

Question: Does the draft bill ban relocating electronic bookkeeping outside Germany?

Short answer: No. The draft bill does not really change the ability to relocate electronic books and records. Relocation within the EU/EEA remains possible without a formal application if taxation is not harmed and German tax authorities keep full access. Relocation to third countries also remains possible, but it needs approval from the competent German tax office and ongoing compliance with the conditions.

Question: What are the main situations that can trigger the new relocation penalty?

Short answer: The penalty can apply in three main cases: failure to comply with a tax authority move-back request, breaches of duties linked to an approved or allowed relocation, and moving electronic bookkeeping to third countries without the required approval. The planned penalty range is EUR 2,500 to EUR 100,000.

Question: Why can cloud and outsourcing setups create relocation risk even if the main system seems to be in the EU?

Short answer: Modern bookkeeping systems often include backups, disaster recovery, copied data, middleware, archiving tools, and remote administration. If any tax-relevant bookkeeping data or activity touches third-country locations, this may count as a relevant relocation or partial relocation. The risk is highest when tax teams do not know that cloud settings, support access, or backup settings create a third-country footprint.

Question: What should tax and finance teams do first to reduce exposure?

Short answer: They should first map the full electronic bookkeeping landscape, including ERP systems, sub-ledgers, invoice tools, archives, cloud platforms, backups, and outsourced services. They should then document where data is stored, processed, copied, backed up, and accessed from, and compare all third-country elements with existing approvals.

Question: Why is a move-back plan important?

Short answer: Tax authorities can revoke approvals and require electronic bookkeeping to be brought back. A move-back plan helps the business respond within the set period, move data and systems to Germany or another allowed location, shut down non-compliant third-country environments, and prove to the tax authority that the move-back was completed properly.

Photos / Illustrations: AI-generated (created with Semrush Content Toolkit)

Source: Haufe, Bundesfinanzministerium, KPMG, NWB

Disclaimer: We assume no liability for the accuracy and completeness of the information. The information provided here does not constitute recommendations for action.