v1.5 · judged by the official validators
A pure SDK — no native dependencies, edge and serverless friendly — to generate, validate, embed and read Factur-X invoices at the EN 16931 profile, with the French rules built in. Every promise here is judged by an official validator, not by us.
npm add facturx-sdk
Factur-X is ZUGFeRD — same standard, two names. A file produced here is a valid ZUGFeRD 2.x EN 16931 file, and the reader is exercised against the German KoSIT corpus on every commit.
Judged by the reference tools, on every commit
Online validator · free
The three schematrons — EN 16931, Factur-X and BR-FR — run in your browser. The file is never uploaded anywhere, and each finding comes with its rule code and the exact place in the document.
Factur-X PDF or CII XML · no account, your file stays put
Integer amounts, totals computed then verified, typed errors carrying the exact field path. The SDK never quietly fixes anything.
import { cents, computeTotals, percent, quantity, unitPrice, assertValidInvoice } from 'facturx-sdk';
const draft = {
id: 'F-2026-0001', issueDate: '2026-09-11', typeCode: '380', currency: 'EUR',
operationCategory: 'services', // goods / services / mixed (French reform)
seller: { name: 'Atelier Exemple SAS', siren: '443061841', vatId: 'FR64443061841',
address: { postCode: '75011', city: 'Paris', countryCode: 'FR' } },
buyer: { name: 'Client Démo SARL', siren: '732829320',
electronicAddress: { value: '732829320', scheme: '0225' }, // platform routing
address: { postCode: '69002', city: 'Lyon', countryCode: 'FR' } },
delivery: { date: '2026-09-10' },
lines: [{ id: '1', name: 'Consulting', quantity: quantity(20000), unitCode: 'DAY',
unitPrice: unitPrice(8000000), netAmount: cents(160000),
tax: { category: 'S', rate: percent('20') } }],
paymentTerms: { dueDate: '2026-10-11', latePenaltyRate: percent('10'),
recoveryIndemnity: cents(4000), earlyPaymentDiscount: 'none' },
};
const invoice = assertValidInvoice({ ...draft, ...computeTotals(draft) });
// otherwise: FacturXValidationError { issues: [{ code: 'BR-CO-15', path: 'totals.taxInclusiveAmount', … }] }import { renderInvoicePdf, embedFacturX } from 'facturx-sdk/pdf';
// The human-readable page, drawn from the model — no need to bring your own PDF
const page = await renderInvoicePdf(invoice, {
fonts: { regular: ttf, bold: ttfBold }, // a static font, embedded
labels: 'en',
});
// The page + the XML → PDF/A-3 Factur-X, checked by veraPDF on every commit
const pdfA3 = await embedFacturX(page, { invoice }, {
outputIntent: { iccProfile: srgb },
});import { fromCiiXml, fromUblXml } from 'facturx-sdk';
import { extractInvoice } from 'facturx-sdk/pdf';
// Received PDF → typed, validated invoice (or undefined if it carries no Factur-X)
const received = await extractInvoice(pdfBytes);
// The three syntaxes of the French socle, one model
const fromCii = fromCiiXml(xmlString);
const fromUbl = fromUblXml(xmlString); // same invoice ⇒ same object
// FacturXParseError { code, path } when a document cannot be readCents, quantities and prices as integers, products in bigint, a single commercial rounding. The totals you supply are checked — a VAT-inclusive total that does not add up is a named error, not a value quietly corrected behind your back.
BR-CO-15 @ totals.taxInclusiveAmount. Official EN 16931 and AFNOR codes, ready to wire into your form.
22 BR-FR rules from the XP Z12-012 standard: SIREN, invoicing framework, legal statements, 0225 addresses, VAT on debits.
Factur-X, plain CII and UBL: any profile, any prefix, attachments, prepayments, credit notes. The same invoice read from CII and from UBL yields the same object. Exercised on 30 invoices from other tools, re-emitted conformant.
The four statuses a platform reports to the French public portal — the official annex knows no others for an invoice — the 40 normalised refusal reasons, and the CDV message written and read back, validated against the UN/CEFACT CDAR schema.
Since 1.5 the SDK also produces the readable page — header, lines, totals, VAT, legal statements, pagination. Those statements come from the same source as the XML: the page and the structured data cannot drift apart.
npx facturx-sdk validate invoice.pdf — the syntax is detected on its own, every finding carries its field path, and the exit code lets a pipeline block a non-conformant invoice.
No DTD, no external entities, bounded depth and size, no content ever executed. SECURITY.md
No Node API in the main entry point; pdf-lib only inside facturx-sdk/pdf. A Request → Response handler is enough for Next.js, Hono or Cloudflare Workers — the example is in the repository.
Receiving structured invoices is mandatory for every business, then issuing them according to company size, through an accredited platform. The SDK is the format and compliance brick; the platform is the transport one.
facturx command line: validate, summarise, extractSpelled out in the English documentation; the in-depth reform guide stays in French, because it comments on French regulation.
Four runnable examples, all executed in continuous integration: issuing from a JSON model, receiving a folder of PDFs, an HTTP handler, and prepayments leading to a final invoice.
npm add facturx-sdk