E-Invoicing in SAP

A change in the law makes e-invoicing in the B2G sector mandatory: Why it is important to act now.

Many companies will soon face a new challenge. From 27 November 2020 at the latest, the option of sending paper or PDF invoices to public-sector customers will be completely eliminated. All invoices issued to public clients from this date onwards must be sent electronically via the European communication platform PEPPOL. In order to ensure automatic processing on the part of the federal government and to avoid that every contractor of the federal

government sends its own format, a central XML standard was introduced, XRechnung. This XRechnungs-Standard will initially replace the conventional paper invoices in the German B2G or B2A sector, but can also be used for B2B scenarios. In principle, it is about the exchange of electronically processable invoice data between your SAP system, the central invoice receipt platform of the federal government and the federal government.

Legal foundations

But why is the topic of e-invoicing of such high relevance for your company?

If the business partner to be supplied is a public sector customer, such as public authorities, local authorities, insurers or utility companies, you should start to look into this topic. According to EU Directive 2014/55/EU, "normal" or "conventional" invoicing will no longer be possible from November 2020.

Why choose e-invoicing?

What benefits does your company now have if it uses e-invoicing via XRechnung? Thanks to the cloud-based software architecture, this SAP solution can be integrated into the existing software landscape quickly, easily and without high costs. After successful integration and installation, XRechnung can be sent directly from the SAP system to the central invoice receipt platform of the federal government thanks to PEPPOL conformity.

Our customers:

[Translate to English:] BMW

The solution in detail

An e-invoice is already created in the SAP system in the correct XRechnung format (based on the CEN model) and sent to the central federal invoice receipt platform via the cross-border communication network PEPPOL.

Example scenario:

An SD invoice is created and transferred to the eDocument framework either by job or manually.

From there the invoice is converted into a so-called eDocument, which is sent to the recipient via the SAP Document Compliance Connector and the PEPPOL network.

In this case, this would be the federal government's central invoice platform, but companies can also process these XRechnungen.

Peppol

It is important to know that PEPPOL can only be used if you register there as a sender and receiver access point. Since SAP has already done this, this service can be used against a license. The PEPPOL infrastructure works with a so-called 4-corner model, so that the individual receiver or sender systems never communicate directly

 

with each other, but always via the sender and receiver access points already described. The solution supports the complete document flow of the e-bill. From creation to error handling or status management. See the eDocument Cockpit.

eDocument Cockpit

From there the invoices can be sent, edited and viewed.

Advantages for your company

  • Cloud-based solution and thus calculable costs
  • Quick Installation
  • Ongoing legal compliance
  • The solution is already operational today and the pilot phase is completed

CONSILIO GmbH follows a holistic approach to the realization of your e-invoicing project. We support you from the as-is analysis to go-live support and far beyond.

We maintain close contact with SAP. Our consultants have practical experience in implementing such solutions.

Are you a supplier or company working for public clients?

Do not hesitate any longer, let us advise you with TOP quality!

Contact us now