Germany
Germany e-invoicing API
Germany uses two EN 16931 formats that developers actually integrate. Public buyers expect XRechnung: XML only, UBL or CII, checked with KoSIT rules and a Leitweg-ID. Businesses that still exchange a readable PDF use ZUGFeRD, a PDF/A-3 with CII embedded.
A German e-invoicing API should create and validate those files from your own invoice data. codecafe24 does that from one JSON model. It does not replace the buyer’s portal or a Peppol access point.
Start with the format that the buyer named on the contract. If they did not, XRechnung is the safe default for government and ZUGFeRD is the usual B2B hybrid.
Related
Questions
Is XRechnung mandatory for every German invoice?
Receipt of structured e-invoices is required in B2B under the Growth Opportunities Act, with XRechnung and ZUGFeRD both able to satisfy EN 16931. B2G buyers specifically require XRechnung.