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.

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.

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.

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.

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.

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.

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.

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.