Electronic Invoicing in Germany and Switzerland

Integrating e-invoices into an ERP system requires several steps. First, the ERP system should support the required standards for e-invoices, such as XRechnung or ZUGFeRD. Then, it is necessary to configure the interfaces of the ERP system to enable the receipt and processing of e-invoices. Additionally, training for employees should be planned to facilitate their use of the new system.

To ensure that all employees use e-invoices correctly, it is important to offer training sessions that explain legal requirements and internal processes. Clear guidelines and templates should also be provided to maintain consistency. Regular reviews and feedback rounds can help identify potential error sources and address them. Close cooperation between departments can also contribute to improving the practice of e-invoicing.

E-invoices are not mandatory for all types of invoices. For example, invoices issued to private individuals are exempt from the e-invoice requirement. Additionally, invoices with a total amount under 1,000 euros can be issued in paper form. There are also specific exceptions for certain industries and services that are not subject to the e-invoice obligation.

Automating the receipt of e-invoices involves several steps. First, it is important to select an appropriate e-invoice system or software solution that supports the receipt and processing of e-invoices. Next, relevant interfaces and formats, such as XRechnung or ZUGFeRD, should be configured. Additionally, it is advisable to check the integration into existing accounting or ERP systems to ensure a smooth workflow.

The selection of the best software for supporting e-invoices depends on various factors, including specific company requirements, integration with existing systems, and user-friendliness. Common software solutions include ERP systems, accounting software, and specialized e-invoice platforms. These software solutions typically offer features such as automated invoice creation, digital archiving, and interfaces to tax authorities. A thorough analysis of individual needs is crucial.

To prevent forgery in e-invoices, several measures are necessary. The use of digital signatures and certificates can ensure the authenticity of invoices. Additionally, a secure transmission method should be chosen to avoid manipulations. Regular training for employees on handling e-invoices also contributes to security.

The process for approving electronic invoices involves several steps to ensure that they meet legal requirements. First, the invoice is created in an electronic format and then sent to the recipient. The recipient checks the invoice for accuracy and completeness before approving it. After approval, the invoice is typically stored in a digital archive to comply with legal retention obligations.

The number of attempts allowed to confirm an e-invoice is not specified. However, it is important that the confirmation occurs promptly to meet legal requirements. The deadlines for confirmation can vary depending on specific regulations and context. Therefore, compliance with relevant legal provisions should be ensured.

The import of e-invoices into an ERP system usually occurs via standardized interfaces or import formats. First, the e-invoices must be in the correct format, such as XRechnung or ZUGFeRD. Subsequently, the ERP system can process the data via an import function. It is important to observe the specific requirements of the software being used to ensure a smooth import.

E-invoices must be adjusted according to legal requirements when returns or refunds occur. A credit note is required to correct the original invoice. This correction must include all relevant information to meet legal demands. It's important to clearly document the return or refund to avoid misunderstandings.

The transition to e-invoices is particularly required for public tenders. Starting from January 1, 2025, companies are obligated to send electronic invoices to public authorities. This applies to both service and goods invoices. The shift to e-invoices aims to increase efficiency and transparency in the invoicing process.

The value-added tax identifier (VAT ID) must be correctly specified in e-invoices according to legal requirements. It should be placed in the header of the invoice, ideally near the billing address of the recipient. Additionally, it is important that both the issuer and the recipient have the VAT ID listed to ensure traceability. Compliance with these requirements is crucial for the legal validity of the e-invoice.

The automation of verifying e-invoices for accuracy can be achieved through software solutions that implement specific validation rules. These software tools can compare invoice data with legal requirements and highlight any errors. Additionally, integration with existing ERP systems can optimize the process. Regular updates to the validation rules are necessary to account for changes in legislation.

The e-invoice offers numerous advantages for cashbook reconciliation, including increased efficiency through automated processes and reduced error sources. It also enables faster processing and archiving of invoices, enhancing transparency. Compliance with legal requirements is facilitated by standardized formats, leading to better traceability.

The automation of transferring e-invoices to an inventory account can be achieved through the use of software solutions that process e-invoices and integrate them into the inventory accounting system. Key factors include the existence of interfaces between systems to ensure smooth data exchange. Additionally, e-invoices should be in a standardized format to facilitate automation. Careful planning and implementation are necessary to avoid errors and enhance efficiency.

E-invoices require specific security measures to ensure the integrity and confidentiality of the data. This includes using digital signatures to verify the authenticity of invoices, as well as implementing encryption technologies to protect the data during transmission. Additionally, a secure archiving system should be established to safeguard invoices against unauthorized access. Regular security audits and employee training are also recommended.

Yes, e-invoices can also be used for complex deliveries. The electronic invoicing system is designed to cover various delivery types and conditions. However, specific requirements for invoicing and the information included must be considered. Correct implementation of the e-invoice is crucial to meet legal requirements and ensure a smooth process.

The automation of transferring e-invoices into the accounting system can be achieved through software solutions specifically designed for this purpose. These programs allow e-invoices to be imported directly from email or other digital storage locations. Subsequently, invoice data is automatically extracted and transferred into the accounting system. Careful selection of the software and integration with existing systems are crucial for successful automation.

An electronic invoice in the sense of the law is an invoice in a structured electronic format that can be machine-read and further processed and complies with the European standard EN 16931. A scanned invoice or a regular PDF does not meet this requirement – even if it is sent by email.

As of January 1, 2025, every domestic company must be able to receive e-invoices – this applies without a transition period. For sending, transition rules apply: from January 1, 2027, for companies with more than 800,000 euros in revenue from the previous year, and from January 1, 2028, for all domestic B2B sales.

XRechnung is a pure XML file without a visual format – it is designed for software. ZUGFeRD is a hybrid format: a PDF/A-3 file with the same structured data embedded as XML. Both meet legal requirements if they comply with the EN 16931 standard. For sending to authorities, XRechnung is the usual method.

As of 2025, the retention period for invoices and other accounting documents is eight years instead of the previous ten (§ 147 Abs. 3 AO, § 14b UStG). The crucial point for e-invoices: the structured data part must be retained in its original form, unaltered, and machine-readable. A printout or a PDF copy is not sufficient.

A faulty e-invoice is not overwritten but corrected: either via a reversal invoice followed by a new issuance or through a correction document that clearly refers to the original invoice. Important for input tax deduction: Until an effective correction is made, the basis for it is usually missing.

In four steps: first ensure reception, which is already mandatory. Then clarify archiving, then set up sending, and finally automate checks and booking. Whoever starts with sending works around the obligation that is already in effect.

Peppol is an international network for the exchange of electronic business documents. Instead of establishing a separate connection with each business partner, both parties connect to their own access point – similar to email, where not every provider negotiates individually with everyone.

No, there is no general e-invoice obligation for business transactions between companies in Switzerland. The electronic invoice is only mandatory for suppliers to the federal administration for contracts valued at over 5,000 Swiss francs. The QR invoice is different: it is a means of payment, not an e-invoice in the technical sense.

The Leitweg-ID is the address of a public authority in electronic invoicing. It tells the receiving system which authority and department the invoice should be sent to. Without a correct Leitweg-ID, an invoice is typically rejected by the authority, regardless of whether it is content-wise correct.

By validating against the EN 16931 standard and the respective specific implementation. Structure, mandatory fields and calculation rules are checked – for example whether the sum of the items matches the total amount. This validation should run automatically upon receipt, not only in accounting.

In structured format, not as free text. The standard provides a dedicated field for payment conditions that must be machine-readable. A sentence like "2% discount for payment within 14 days" in free text will not be recognized by any system – and the discount will not be automatically applied.

As a separate document with a document type that identifies it as a correction, and with a clear reference to the original invoice number. The original invoice remains intact and is not altered – it is subject to retention requirements, even if it has been canceled.

Via DATEV interfaces, which take over structured invoice data along with the document image. The crucial point is that not only a PDF is transferred, but the structured data – otherwise the office would still have to re-enter the data, and the advantage of the e-invoice would be lost exactly where it is greatest.

Exceptions include, among others, small-value invoices up to 250 Euro, travel tickets, invoices to private individuals, and certain tax-exempt transactions. Small businesses under § 19 UStG are permanently exempt from the issuance obligation – they must still be able to receive e-invoices.

In recurring obligations such as rent or maintenance, the contract often serves as the invoice. According to the tax administration's view, it is sufficient in many cases to issue an e-invoice once for the first period, provided the details do not change. If anything changes, a new one must be issued.

The German obligation applies to domestic transactions between domestic companies – invoices to foreign countries are not subject to it. However, other member states have their own, sometimes stricter rules, and some require reporting to the tax authorities. Before conducting business in a country, the local situation should be checked.

Via the appropriate tax category code in the structured fields, supplemented by the legally required note on the recipient's tax liability. The note alone in the free text is insufficient – the category must also be machine-readable, otherwise validation at the recipient's end will fail.

A procedure documentation describes how documents are created, checked, recorded, and stored in your company. The GoBD require it from every company that is required to keep accounting records. If it is missing, an audit can question the regularity of the accounting - regardless of whether the documents are present.

Three things: Are the documents complete and unchanged? Is the process documented? Are the data machine-readable and readable within a reasonable time? If any of these is missing, the properkeeping of the books may be called into question – with significant consequences.

Via an interface that takes the order data and generates the e-invoice format from it. The actual effort does not lie in the format generation, but in the master data: Complete addresses, correct tax identification numbers and unique item descriptions are prerequisites.

The invoice number must be unique and sequential (§ 14 Abs. 4 UStG). Multiple number ranges are permissible as long as no number is duplicated within each range and no unexplained gaps occur. When switching to e-invoicing, special attention must be paid to duplicate assignments by two parallel systems.

With fixed stages and deadlines, but requiring approval before dispatch. Fully automated reminders can damage customer relationships if a payment has only been booked late or if a complaint is ongoing. The system should generate the proposal, and a human should confirm it.

Audit-proof means: Documents are complete, unchangeable, always findable and readable for the entire retention period. A folder on the network drive does not fulfill this, because files there can be changed or deleted without anyone noticing.

For invoices to private customers, nothing changes – the obligation applies only between companies. However, those who invoice developers, property management companies or public clients are affected. All companies must be able to receive e-invoices, including those that only invoice private customers.

As an invoice with multiple line items, each referring to a delivery note and service date. The standard provides fields at the line item level for this purpose. The service period is crucial: when deliveries span multiple months, it must be clear which line item was provided when.

Down payment invoices are standalone invoices with VAT disclosure. The final invoice shows the total performance and deducts the already calculated down payments along with their tax. The standard provides specific fields for this – a deduction only in the text is insufficient.

In four steps: technical validation upon receipt, automatic matching with order and goods receipt, digital approval by the responsible person, then booking. The paper circulation with printout, signature and scan is eliminated – this is the biggest time saving in many companies.

Price and pricing model of Ouhud e-invoice: upon request. However, before the pricing question arises, there is another: What do you need to be able to do by when? The receipt of e-invoices has been mandatory since January 1, 2025, while there are transition periods for sending until the end of 2027.

E-invoices can be received and sent through various channels, with electronic transmission occurring via standardized formats and protocols. Common channels include email, web portals, and specialized e-invoice platforms. The use of XRechnung or ZUGFeRD as formats is also widespread. The choice of channel should comply with legal requirements and the technical capabilities of the parties involved.

Yes, the receipt of an e-invoice must be technically confirmed. This is necessary to prove the proper delivery and receipt of the invoice. The confirmation can be done through an automated system that registers the receipt of the e-invoice. This requirement is part of the legal regulations for e-invoices that will take effect from January 1, 2025.

If a business partner cannot accept e-invoices, the first step should be to initiate a conversation to clarify the reasons. There may be technical or organizational hurdles that can be overcome. Alternatively, the possibility of a transitional arrangement or another form of invoicing can be considered. It is important to observe the legal requirements for e-invoices and seek legal advice if necessary.

An e-invoice must contain certain mandatory information to comply with legal requirements. This includes, among other things, the invoice number, the invoice date, the complete addresses of the supplier and recipient, as well as the tax number or VAT identification number. The quantity and type of goods or services provided, as well as the net amount and the applicable tax rate, are also required.

The transfer of the VAT ID and tax number usually occurs through specific fields in electronic invoices or tax returns. It is important that the VAT ID is provided in the format 'DE' followed by nine digits, while the tax number may have different formats depending on the federal state. Error-free transfer is crucial to avoid delays or issues with tax recognition.

E-invoices from foreign suppliers must meet the same legal requirements as domestic invoices. This includes compliance with invoicing regulations according to the Value Added Tax Act. It is important that the e-invoice contains all necessary information, such as the supplier's tax number and the correct VAT treatment. Additionally, invoices should be transmitted in an accepted format to meet legal requirements.

The credit note procedure allows the recipient to create a credit note instead of an invoice. In e-invoicing, the credit note is transmitted electronically, adhering to the legal requirements for invoicing. The recipient must ensure that the credit note contains all necessary information to guarantee input tax deduction. Additionally, an agreement between the parties regarding the credit note is necessary.

Travel expense receipts and expenses must be clearly and transparently documented in e-invoice processes. This includes recording travel costs, providing receipt numbers, and assigning them to the corresponding cost types. Receipts should be digitized and provided in a uniform format to facilitate processing. Additionally, it is important to observe the legal requirements for e-invoices.

An electronic invoice does not require an electronic signature to be legally valid. However, it is important that the invoice meets legal requirements and ensures the authenticity of the origin as well as the integrity of the content. This can be achieved through various methods, such as the use of qualified electronic signatures or other security measures. The exact requirements may vary depending on the country and specific regulations.

Whether a readable view needs to be stored alongside an XML file depends on specific requirements and legal regulations. In many cases, it is advisable to archive a readable version to ensure the traceability and accessibility of the information. This can be particularly important for audits or internal controls. It is recommended to consult the relevant regulations to ensure that all requirements are met.

In ZUGFeRD, the PDF/A file is the tax-relevant original. This file contains the invoice in PDF format as well as the structured invoice data in XML format. The PDF/A file ensures long-term archiving and the immutability of the invoice. The XML data format allows for automated processing of the invoice contents.

To prevent the duplicate booking of e-invoices, companies should implement an effective invoice management system. This system can be supplemented by unique identification features, such as an invoice number or a QR code. Additionally, regular training of employees in handling the system is important to minimize errors. An automated check for already booked invoices can also help avoid duplicate bookings.

The actual receipt time of an e-invoice can be proven through various methods. A common practice is to use receipt confirmations that document the time of electronic transmission. Additionally, logs from the e-invoice system or the email servers that confirm the receipt of the invoice can be utilized. The digital signature of the invoice can also serve as proof, as it records the time of creation and transmission.

The verification of bank details and supplier data before a payment is carried out in several steps. First, the data should be compared with the information stored in the system. A phone confirmation of the bank details with the supplier can provide additional security. It is also advisable to pay attention to any warnings or indications that may suggest fraud. Regularly reviewing supplier data helps minimize risks.

The separation of test and production operations for e-invoice interfaces is achieved by implementing separate environments. In the test environment, all new features and changes are tested before being transferred to the production environment. This minimizes the risk of errors in live operations. Additionally, clear processes for switching between environments should be defined to ensure data integrity.

The gradual integration of suppliers into the e-invoicing process occurs in several phases. First, an inventory of existing processes and systems should be conducted. Next, suitable e-invoicing solutions are selected, and suppliers are trained. In the implementation phase, test runs are conducted before full integration takes place. Continuous support and feedback loops are important to optimize the process.

The transmission of cost centers, order numbers, and project references typically occurs via standardized interfaces or through manual entry into corresponding systems. In many companies, this data is managed in ERP systems that allow integration with other software solutions. The exact method of transmission may vary depending on the system used and the specific requirements of the company.