Public bodies are the federal, regional, and municipal administrations and energy companies, schools, and hospitals. Starting 27 November 2020, all public contractors that issue invoices to the federal administration must submit an electronic invoice.

No deadlines are yet set for issuing e-invoices by contractors to state governments, and local authorities. Every state defines its own rules.

The federal government's E-Invoice Regulation specifies that a supplier issues an e-invoice in "XRechnung," a format developed by the German Coordination Office for IT Standards (KoSIT). XRechnung is an XML-based invoice format.

The existing XRechnung standard only allows two XML formats, either UBL or UNCEFACT/CII, to transmit electronic invoices. It is also possible to use other data formats such as Zentraler User Guide des Forums elektronische Rechnung Deutschland.


What do we offer?


Take aways 

Formal support and active involvement of senior management

Optimum process improvement or business transformations will not likely be realized by the sum of individual independent efforts.The risk is that individually everybody knows what needs to be done within his or her own area of expertise, but what is lacking is overall direction and thus progress.

Anticipate what users would want

We combine technical knowledge with industry understanding and knowhow of technologically advanced tools and methodologies available in the market or developed by ourselves.

What do we like to achieve

  • Focus on tax processes that could be improved
    • Manual process: same data requests are made by different stakeholders
  • As Is assessment
  • Anticipate future changes and the data needed
    • What are tax trends?
    • What is happening locally and what should be considered across jurisdictions where you operate?
    • Anticipate new stakeholders and their data needs or requests (internal and external)
  • Define scope and actions for short, mid and long term
  • Write business case for change
  • Realize sponsorship for implementation

‘As is’ assessment, actions and business case

  • What tax data is requested and by whom?
  • What tax process can be improved and what can be automated?
    • CIT, VAT, tax data warehouse
  • What is the Return on Investment?
    • Hard saving: process improvement
    • Meeting (new) tax requirement
  • What systems are in use: SAP, Oracle, etc
    • By which entities?
  • How many end-use computing tools (e.g. excel spreadsheet) do we have?
  • How do we avoid an ad-hoc solution?
    • Understand the bigger picture
    • Real problem and not the symptom

Risk and reward

Technology-related tax risk: understand and address the potential harms and benefits of (new) technology.

Technology tools & systems integration

Ascertaining proper IT support for ensuring efficient, timely and reliable reporting.

Change and project management

VAT should be considered in every aspect of the process, from concept through completion and beyond. Managing by design — looking at any process or transaction from end to end and factoring in all the requirements and controls essential to designing and optimizing a compliant VAT process.

Effective communication and teaming

We speak the language of the business and IT and no translation is needed.

Set up a project plan

  • Set up a project charter that will take effect preferable during feasibility but ultimately during design
  • Write a business case and problem statement
  • Define scope of the project
  • Define objectives and goals of the project
  • Involve stakeholders and define priorities
  • Set measurable milestones
  • Ensure that the right sponsors provide buy-in.
  • Identify (project) risks and how to manage them
  • Jointly validate and refine the project plan and develop a roadmap to success
  • Hold regular meeting to track progress of the various work streams