E-invoicing (Factur-X / ZUGFeRD)

import { renderDocument } from '@formepdf/core';
import { standardFonts } from '@formepdf/fonts-standard';

const pdf = await renderDocument(
  <Document pdfa="3b" pdfUa lang="de-DE" fonts={standardFonts()}>
    <Page size="A4" margin={50}>{/* your invoice layout */}</Page>
  </Document>,
  {
    facturX: {
      xml: invoiceXml,        // your EN 16931 CII XML (string or bytes)
      profile: 'EN 16931',    // MINIMUM | BASIC WL | BASIC | EN 16931 | EXTENDED | XRECHNUNG
    },
  },
);

​

What Forme handles

• PDF/A-3 (pdfa: "3b", "3u", or "3a") — identical to PDF/A-2 plus permission for arbitrary embedded files. 3b is sufficient for every Factur-X profile.
• The attachment as a conformant associated file: spec filename (factur-x.xml; xrechnung.xml for the XRECHNUNG profile), MIME type text/xml, /F//UF, /AFRelationship (profile-derived: Data for MINIMUM/BASIC WL, Alternative otherwise; overridable), /Params with a deterministic ModDate, and the catalog /AF association.
• The Factur-X XMP identification (fx: extension schema with DocumentType, DocumentFileName, Version, ConformanceLevel) plus the PDF/A extension-schema description that makes it legal.
• Composition with PDF/UA-1 — an invoice can be archival, accessible, and machine-readable at once (pdfa="3a" pdfUa).
• Validation in CI: every commit renders this exact configuration and gates it on veraPDF (PDF/A-3b + PDF/UA-1) and Mustangproject, the ZUGFeRD/Factur-X reference validator. Evidence: parity.formepdf.com.

​

What Forme does not do

​

Generic attachments

const pdf = await renderDocument(doc, {
  attachments: [
    { name: 'source-data.csv', data: csvBytes, mimeType: 'text/csv', relationship: 'Source' },
  ],
});