PDFs and e-invoices in pure TypeScript.

E-invoices that pass the official checks.

One typed object in, a conformant e-invoice out: the PDF a person reads and the EN 16931 data a machine reads. Java has Mustangproject, PHP has horstoeko/zugferd, Python has factur-x - this is the TypeScript answer.

import { renderZugferd, type Invoice } from "@jasy/e-invoice";

const invoice: Invoice = {
  number: "INV-2027-001",
  issueDate: "2027-01-15",
  currency: "EUR",
  dueDate: "2027-01-29",
  seller: {
    name: "Northwind GmbH",
    vatId: "DE265013614",
    address: { line1: "Hauptstrasse 1", city: "Berlin", postCode: "10115", country: "DE" },
    contact: { name: "A. Schmidt", email: "billing@northwind.de", phone: "+49 30 123456" },
  },
  buyer: {
    name: "Globex AG",
    address: { line1: "Marktplatz 5", city: "Munich", postCode: "80331", country: "DE" },
  },
  lines: [{ name: "Consulting", quantity: 8, unit: "HUR", netUnitPrice: 120,
            vat: { category: "S", ratePercent: 19 } }],
  payment: { iban: "DE89370400440532013000", terms: "Payable within 14 days." },
};

const { bytes, xml } = await renderZugferd(invoice, { locale: "en" });

why trust it

Every claim on this page links to its proof.

• An engine of its own

  Layout, text shaping and the PDF writer are ours, in TypeScript. No Chromium, no Java, no pdf-lib underneath.

  How it works
• Measured against react-pdf

  Faster, AES-256 encryption by default, accessible to PDF/UA - each measurement with the code to check it.

  See the comparison
• Checked, not claimed

  E-invoices pass the KoSIT EN 16931 rules and veraPDF. Check any file yourself - ours or anyone's.

  Open the validator
• Accessible PDFs

  One flag emits a tagged PDF/UA-1 document that passes veraPDF's machine checks.

  Accessibility
• Byte-stable output

  The same document renders to the same bytes, every time - an archived invoice stays reproducible.

  Output options
• Anywhere JavaScript runs

  Node or the browser, plain TypeScript, Vue, React, Angular or Nuxt - the same engine underneath.

  All guides

one engine · two runtimes · same code

Runs on your server. And in the browser.

Pure TypeScript, no Node-only crutches. The same component tree produces the same byte-exact PDF whether it runs on a server or entirely in the browser - your call, not the library's.

Your PDF is a Vue component.

Author a document the way you build an app - components, props, slots and your reactive data - then render it to a real PDF, right in the browser. Real layout and pagination underneath, fully typed props, and a familiar feel if you have reached for @react-pdf/renderer on the React side.

<Document>
  <Page :gap="12">
    <Text :size="30" bold>{{ invoice.title }}</Text>

    <Row
      v-for="line in invoice.lines"
      :key="line.id"
      :justify="'between'"
    >
      <Text>{{ line.name }}</Text>
      <Text bold>{{ line.total }} €</Text>
    </Row>
  </Page>
</Document>

Drop it into Nuxt.

One install, zero config. Author PDFs as components and render them right in the browser, or stream them from a server route - your choice, the same components and helpers on both sides.

<script setup>
const { open, download } = usePdf(Invoice)
</script>

<template>
  <button @click="open">View PDF</button>
</template>

// server/api/invoice/[id].get.ts
export default definePdfHandler((e) =>
  Document([
    Page([
      Text(`Invoice #${getRouterParam(e, "id")}`),
    ]),
  ]),
)

• Zero config

  Add it to modules. Components and the render helpers are auto-imported - no wiring, no imports.

• Client or server

  Render in the browser with usePdf, or stream from a Nitro route with definePdfHandler. Same vocabulary.

• Nitro caching, lean bundle

  Cache a route per path + query in one option. jimp stays server-side - the browser bundle stays small.

Your PDF is a React component.

Author a document in JSX - components, props, hooks and context - then render it to a real PDF, right in the browser. Real layout and pagination underneath: tables that carry their header across pages, newspaper columns, headers and footers that keep their space.

<Document>
  <Page gap={12}>
    <Text size={30} bold>{invoice.title}</Text>

    {invoice.lines.map((line) => (
      <Row key={line.id} justify="between">
        <Text>{line.name}</Text>
        <Text bold>{line.total} €</Text>
      </Row>
    ))}
  </Page>
</Document>

PDFs that follow your signals.

A document is a function of its data. inject(JasyPdf) turns it into a real PDF, and pdfResource() renders it again whenever your signals change - right in the browser, with real layout and pagination underneath.

export const invoicePdf: PdfDocumentFn<Invoice> = (invoice) =>
  Document([
    Page({ gap: 12 }, [
      Text(invoice.title, { size: 30, bold: true }),
      ...invoice.lines.map((line) =>
        Row({ justify: "between" }, [
          Text(line.name),
          Text(`${line.total} €`, { bold: true }),
        ]),
      ),
    ]),
  ]);

// in a component: renders again whenever the invoice changes
readonly preview = pdfResource(invoicePdf, () => this.invoice());

roadmap · MIT · built in the open

1.0 is built. Here's what's next.

Built in the open, MIT-licensed. Everything the 1.0 set out to do is done and shipping; this is what comes after it - in order, no dates promised.

• Read and edit any PDF

  Open a file, change what is on the page, and merge, split or extract. Reading a form and filling it already ships.

• Digital signatures

  Sign a document so a receiver can prove nobody touched it afterwards - the piece an e-invoice still misses.

• The last few percent of layout

  A public measure() helper, a heading across all columns, and a border that stays open where a box is split across pages.

• Templates you can start from

  An invoice, a report and a letter that work as they are, and come apart when you want your own.

• More e-invoice profiles

  Peppol and further country formats, on top of the Factur-X, ZUGFeRD and XRechnung profiles already supported.

• Our own bidi

  Hebrew and Arabic already order correctly. The UAX #9 library behind that seam has not been touched since 2023 and ships no types, so it is going to be ours.