Statement PDFs in Node.js

Why statements become PDFs

A statement summarises a period that is now closed. Regenerating it later from live data would produce a different document, which defeats the point. That is the difference between a document and a view of a database, and it is why finance and account management keep asking for this.

What a statement has to carry

Before any of the code below matters, the template has to produce a document that is actually a statement. These are the fields that make it one, and the ones a reader or an auditor will look for first.

• the opening balance and the closing balance
• every transaction in the period with date, description and signed amount
• a running balance column, so a reader can find where a discrepancy starts
• the account identifier, usually masked
• the statement period, which must not overlap the previous one

The Node.js implementation

fetch ships with the runtime, so this adds no dependency. The render happens in a route handler that returns the response body directly, and you pipe the response body straight to res, so the PDF never lands in a Buffer.

app.get("/statement/:id.pdf", async (req, res) => {
  const html = await renderStatement(req.params.id);

  const upstream = await fetch("https://api.pdfpipe.xyz/v1/pdf", {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.PDFPIPE_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      html,
      options: { format: "A4", printBackground: true },
    }),
  });

  if (!upstream.ok) throw new Error(`render failed: ${upstream.status}`);

  res.setHeader("Content-Type", "application/pdf");
  // Streamed, not buffered: a long statement never sits in memory.
  upstream.body.pipe(res);
});

The CSS that makes a statement page correctly

The layout problem specific to this document is that a long transaction table spanning many pages, needing repeated headers and a running balance that stays legible after a break. These rules handle it.

/* Line items run past one page. Repeat the header, keep the
   totals block whole, and never strand a single row. */
thead { display: table-header-group; }
tfoot { display: table-footer-group; }
tr    { break-inside: avoid; }

.totals {
  break-inside: avoid;
  break-before: auto;
}

@page {
  size: A4;
  margin: 18mm 16mm 22mm;
}

What goes wrong in Node.js

Node buffers the whole response if you call res.send(await res.arrayBuffer()). On a 40-page report that is tens of megabytes held per concurrent request, and it is the usual reason a PDF endpoint takes down an otherwise healthy service under load.

What people try first

Most Node.js projects reach for puppeteer, which pulls a 300 MB Chromium download into your image and needs its own memory headroom on every instance. That works until it is running on more than one machine, at which point the browser becomes the thing you operate rather than the thing you use.

Where the statement lives afterwards

Rendering is the short part. Statements are the document most often requested again years later, usually for a loan application or an audit. Regenerating one from current data would produce different figures, so the rendered file is the record and has to be stored as issued.

Getting the document right

• Check the closing balance, which has to reconcile with the transactions listed above it.
• Generation is triggered by the end of a billing or accounting period, so size the timeout for that path rather than for a health check.
• This is a batch shape: render the run through the batch endpoint rather than firing thousands of individual requests.
• Backgrounds are painted by default here, so a design that uses colour needs nothing set. Only an explicit print_background of false turns them off.

Frequently asked

Related

Other Node.js documents, and the same statement in other stacks.