XRechnung

SoftwareSilo E-Invoice generates XRechnung as CII XML. Store views can select version 2.2, 2.3 or 3.0. The formatter is deliberately XML-only; it does not create a hybrid PDF or upload the document to a portal.

Configure the format

  1. Set Default B2B Format to XRechnung 3.0.x (B2B).
  2. Select the exact version required by the receiver.
  3. Complete seller contact name, phone and email.
  4. Confirm how the buyer reference or Leitweg-ID reaches the generated XML in your project.
  5. Enable the appropriate validation level and generate a manual sample.

The module's internal validator checks structure and its bundled XSD. It does not enforce a Leitweg-ID because the formatter also supports B2B usage. A public-sector receiver may apply additional rules and reject a structurally valid file without its required routing reference.

Output and credit memos

XRechnung produces XML only for invoices and credit memos. Credit memos additionally use document type 381 or 384 from the credit-memo configuration.

If users need a readable invoice, keep Magento's ordinary PDF in the workflow. Selecting PDF only as the e-invoice attachment strategy produces no XRechnung PDF.

Submission is separate

The module does not upload to ZRE, OZG-RE or another receiving portal. Submission, credentials, transport acknowledgements and portal-specific validation belong to the connected delivery process.

Validate a real sample

Check seller contact, buyer reference, purchase-order reference, payment instructions, VAT categories, totals and the selected version. Then validate with the receiver's current rule set. Do this before changing the generation mode from manual to automatic.