VAT in Germany is a consumption tax that almost every business trading there will encounter. The standard VAT rate Germany applies is 19%, with a reduced rate of 7% for essentials. Foreign companies, freelancers and established GmbHs all fall within scope. The rules apply from the first taxable transaction, and the penalties for getting things wrong are genuine, not symbolic.Key TakeawaysThe VAT standard rate in Germany is 19%. Reduced VAT rates of 7% apply for basic necessities and cultural items.No minimum threshold for registration exists for foreign companies.

If you use Oracle ERP for your business, Spanish compliance isn't a single configuration switch. You need to establish which entity and transaction is in scope, how an invoice moves from Oracle to its recipient, and which separate tax-reporting or invoicing-system obligations apply. An e-invoicing service provider can help scope that workflow and assess the integration needed for your Oracle environment; confirm specific connector capabilities against your deployment before promising them.Key TakeawaysThe right sequence to integrate e-invoicing for Oracle is: scope the entity → map the invoice journey → identify B2B exchange requirements → assess SII and RRSIF separately → verify the actual Oracle and service-provider integration → test responses and reconciliation.VeriFactu is not natively built into Oracle, so most businesses use a certified connector.Businesses should first check whether SII applies, as taxpayers covered by SII are generally excluded from RRSIF for the same operations.First, Understand Which Spanish Compliance Rules Apply to Your Business1. SII: Electronic VAT ledger reportingThe Immediate Supply of Information system, or Suministro Inmediato de Información, requires in-scope businesses to electronically submit specified VAT ledger information to the Spanish Tax Agency (AEAT).It applies to large businesses, VAT groups and businesses registered under the monthly VAT refund scheme (REDEME).SII is a VAT reporting obligation. For businesses using Oracle, relevant functionality may already be available.

Creating e-invoices in Germany means generating EN 16931-compliant invoice data in XRechnung or ZUGFeRD format so invoices can be validated, exchanged, and archived correctly. Businesses must choose the right format, capture mandatory fields, and use compliant tools or integrated systems.Key takeawaysGermany requires businesses to receive structured e-invoices from 2025, with phased issuance obligations starting in 2027 and expanding in 2028.XRechnung is XML-only and mainly used for public authorities, while ZUGFeRD combines PDF/A-3 with embedded XML for broader business use.A plain PDF is not a compliant e-invoice; mandatory seller, buyer, tax, item, and total data must be structured properly.Validation is essential before sending, because missing fields, wrong formats, or incorrect tax calculations can trigger invoice rejection.Low invoice volumes are usually handled with web tools or accounting software, while high volumes need ERP integration, automation, and batch workflows.What Is an E-Invoice?An e-invoice is a structured, machine-readable XML invoice in XRechnung or ZUGFeRD format that complies with the European EN 16931 standard. It contains all mandatory information as defined data elements and enables automatic validation, posting, and archiving.E-Invoicing Germany: Mandate and FormatsGermany’s e-invoicing mandate is reshaping how businesses issue and receive invoices. Since 1 January 2025, all businesses established in Germany must be able to receive structured electronic invoices. The obligation to issue e-invoices will apply in phases, starting in 2027 for businesses with annual turnover above EUR 800,000 and extending to all businesses from 2028. An e-invoice in Germany is not just a PDF sent by email.

The description of the Peppol 4 corner model Germany sets the specifics of the modern functioning of e-invoicing in a regulated digital-first world. It substitutes disjointed invoicing systems with a uniform structure that guarantees a secure and compliant and automated exchange of documents. The Peppol 4 corner model is the bridging force of scalable and interoperable business-to-business financial communication as Germany becomes the first to implement mandatory e-invoicing.Key TakeawaysThe Peppol 4 corner model enables invoice exchange through certified Access Points instead of direct integrations.A single connection allows businesses to transact with multiple partners across the Peppol network.The model supports Germany’s shift toward mandatory e-invoicing compliance.Built-in validation and standardized formats reduce errors and improve processing accuracy.The 4-corner e-invoicing framework drives efficiency, cost savings, and operational scalability.What Is the Peppol 4 Corner Model in Germany?The Peppol 4 corner model Germany is a decentralized 4-corner e-invoicing framework that facilitates the exchange of structured invoices between suppliers and buyers through certified intermediaries known as Access Points. It standardizes communication protocols and data formats, allowing businesses to interact seamlessly without maintaining multiple direct integrations.How Does the Peppol 4 Corner Model Work? The Peppol 4 corner model provides a systematic procedure that eliminates straight system reliance and provides secure and precise delivery of invoices. The participants communicate with each other via an Access Point, which conducts validation, routing, and compliance.Step-By-Step Workflow:1.

Germany’s e-invoicing obligations makes an invoice valid only when mandatory VAT data is delivered as structured, machine-readable content aligned to EN 16931. Reception capability for structured e-invoices applies from January 1, 2025; domestic B2B issuance becomes mandatory from January 1, 2027 (larger enterprises) and January 1, 2028 (all).Key takeawaysMandatory content follows §14 UStG: seller/buyer IDs and addresses, invoice number, issue and supply dates, line description, quantity/unit, net amounts, VAT rate/category, VAT totals, and amount due.Encode these values using EN 16931 Business Terms (BT codes) for consistent validation and processing across systems.Use a compliant format such as XRechnung (XML) or ZUGFeRD 2.0.1+, and include currency plus payment terms.XRechnung adds mandatory process and endpoint fields (e.g., ProfileID, EndpointIDs) and, for B2G, the Leitweg ID; missing fields commonly trigger rejection and payment delays.Germany’s E-Invoicing MandateGermany is moving B2B invoicing from “documents” to structured, machine readable data. An invoice qualifies as an e-invoice only when it is issued in a structured format that can be automatically processed by the recipient’s systems, typically using EN 16931 compliant standards such as XRechnung or ZUGFeRD.The mandate requires businesses to be able to receive structured e-invoices first, then to issue them for domestic B2B transactions in phases. The timeline below shows how the implementation is staged.MilestoneWhat It Means in PracticeFrom Jan 1, 2025Businesses must be able to receive structured e-invoices.From Jan 1, 2027Issuance becomes mandatory for domestic B2B for larger enterprises (based on turnover threshold rules).From Jan 1, 2028Issuance becomes mandatory for all domestic B2B transactions.What Are the Mandatory Fields of an e-Invoice in Germany?Every e-Invoice in Germany should be issued with Mandatory data fields - the minimum legal and technical dataset, which makes an e-invoice valid, processable, and auditable, like seller and buyer identifiers, invoice number, issue and supply dates, item level quantities, etc. In Germany, mandatory e-invoice fields are the legally required VAT invoice details under §14 UStG, carried in structured EN 16931 Business Terms, plus any additional mandatory fields imposed by the chosen German format, such as XRechnung.§14 UStG defines what information must appear on an invoice for VAT purposes in Germany. This includes the parties’ identification, a unique invoice number, issue and supply or service dates, a clear description of goods or services, quantities, net amounts, VAT rate and VAT amount, and the total amount payable.EN 16931 defines how that same legally required information must be expressed as structured, standardized data so the invoice can be validated and processed automatically.

Validating an e-invoice in Germany means checking the structured invoice for format, business rules, and VAT content compliance so it can be received, processed, and deducted correctly under the country’s mandatory B2B e-invoicing obligations. Key TakeawaysValidation must cover syntax, EN 16931 and XRechnung business rules, and the factual VAT content. XRechnung is the core XML route for public invoicing, while ZUGFeRD adds XML to a PDF/A-3 file. Missing mandatory fields can cause rejection, payment delays, and blocked input VAT deduction until correction. Germany’s E-Invoicing MandateStarting January 1, 2025, Germany has treated a domestic B2B e-invoice as valid only when it is issued, sent, and received in a structured electronic format that supports automated processing.Transition Period: Paper and non-structured invoices remain permitted through 2026 (or 2027 for businesses under €800K turnover and EDI users), after which structured e-invoicing becomes mandatory for domestic B2B transactions.E-Invoice Formats: Germany supports two structured formats, XRechnung (XML-based, common in public sector) and ZUGFeRD (a hybrid PDF/A-3 with embedded XML, where the XML takes precedence in case of conflict).Transmission Channel: No specific delivery channel is mandated; businesses can use email, portals, or interfaces, as long as the invoice is structured and supports accurate VAT data processing.What Is E-Invoice Validation?E-invoice validation is the control process that tests whether a structured invoice is technically correct, semantically consistent, and complete enough for German VAT purposes. It is not just opening a file successfully. It is confirming that the invoice can be processed electronically and relied on for tax and accounting purposes. In practice, validation means checking three separate layers before the invoice is trusted.1. Format ValidationThis is the technical gate. The XML must conform to the expected syntax and schema, use valid structure, and contain the required machine-readable elements.

Oracle Fusion Cloud Financials holds the transactions, customer records and accounting data behind an invoice. But it alone doesn't remove the complexity of e-invoicing. E-Rechnung rules in Germany test what happens after that transaction is created: whether the required information reaches the buyer in a permissible structured format and whether the business can receive and retain incoming invoices.For CFOs, the decision is not simply whether Oracle can produce an e-invoice. It is “who owns German format rules, invoice exceptions, and changes to the integration over time?” and “How do we connect Oracle to the e-invoicing requirements without rebuilding our ERP?” An e-invoicing solution provider such as ClearTax can sit between Oracle and country-specific requirements, handling supported formats, compliance validation, transmission and network connectivity.Key TakeawaysGenerating a UBL invoice in Oracle does not make it compliant with XRechnung or Peppol BIS.Oracle, an integration layer, an e-invoicing provider, and a Peppol Access Point each do different jobs. Assign ownership before choosing the technical route.For large enterprises, a central e-invoicing layer can help keep country-specific compliance logic outside the core ERP.What does Oracle e-invoicing integration involve?Oracle e-invoicing integration connects invoice transactions to the structured formats, validation rules, delivery channels, and status processes required by a recipient or jurisdiction.

Spain e-invoicing mandate introduces domestic B2B e-invoicing in phases with a hybrid model. The Royal Decree 238/2026 defines Crea y Crece, mandatory exchange of B2B e-invoices. The businesses must use structured e-invoices, interoperable platforms and new data-sharing requirements for domestic B2B transactions..The new Ministerial Order HAC/1028/2026 entered into force on 6 Oct 2026 starts the countdown to mandatory B2B e-invoicing. It provides the technical and functional specifications for Crea y Crece Law and Royal Decree 238/2026.Key TakeawaysPhase 1 of the Spain B2B e-invoicing mandate starts in October 2027 for businesses with annual turnover exceeding €8 million. The remaining businesses follow phase 2 in Oct.

Spain introduced several digital tax and invoicing regimes side by side. Three matter most for most businesses: SII, Verifactu and Crea y Crece. TicketBAI and NaTicket (regional) and B2G e-invoicing through FACe sit alongside them. These FAQs show which ones apply to you and when.Frequently Asked Questions for Spain E-InvoicingWhat is e-invoicing in Spain?It means issuing and receiving invoices as structured, machine-readable data, instead of manual or PDFs. It’s been phasing in through several rules, each with a different date and compliance rules.

Spain’s e-invoicing framework requires businesses to exchange structured e-invoices as per the formats specified in the EN 16931. The semantic data model of EN 16931 covers multiple syntaxes including Fracturae, UBL, CII, and EDIFACT. The complexity of e-invoicing model is that your ERP may generate one format, the compliance layer may exchange another, and a trading merchant may issue a different syntax. That’s where interoperability and format conversion between platforms comes in the picture. It’s important for the businesses to understand what Spain e-invoicing formats look like and how they are used.Key TakeawaysThe four formats used in Spain are Facturae, UBL, CII and EDIFACT.EN 16931 specify all the formats. It's a content standard, not a format you generate.Under the new B2B framework, every invoice not issued through the AEAT's public e-invoicing solution (SPFE) must also go to the SPFE as a certified copy (copia fiel) in UBL, at the same moment it is issued.Facturae is already required for invoicing public administrations under Ley 25/2013.