The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Building an e-invoicing process in Salesforce across german, belgian and french Rules (opens in a new tab)

You will learn how national e-invoicing rules in Germany, Belgium and France differ and what each means for Salesforce invoice data, configuration and exchange channels.

Why read this

The article also outlines a readiness checklist for a multi-entity org.

ZUGFeRD

  • XML embedded in the PDF
  • Human-readable PDF included

XRechnung

  • Structured XML file
  • No PDF included as part of format
Germany's ZUGFeRD and XRechnung formats differ in how they carry structured data

The article argues that a Salesforce team cannot treat European e-invoicing as one rule set. Each legal entity and transaction must first be checked against the applicable country’s deadlines, structured format and exchange method. Germany’s ZUGFeRD and XRechnung, which have transition periods running through 2026 and 2027, are contrasted with Belgium’s mandatory Peppol-based structured invoicing from January 2026 and France’s phased platform-based model starting in September 2026.

For the Salesforce implementation, the author recommends mapping the regulatory scope, defining the required output and exchange method, auditing that the needed seller, customer, tax, line-item and reference data exists at generation time, and adding controls with Validation Rules, Flow or Apex. The lifecycle should also cover receiving incoming e-invoices and handling corrections.

The piece then shows how the Finblick application on AgentExchange supports these needs with Legal Entity records, Matching Rules tied to Tax Rules, ZUGFeRD and XRechnung generation from the Invoice record, and Credit Notes for corrections. It closes by recommending testing across entity, country, VAT and correction combinations, and ongoing review as national rules change.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?