A clean invoice template you can fill in below and download as a PDF, or generate from your own data with one API call. Line items, tax, payment terms and your own branding.
An invoice is the document that gets you paid, so it has to do two jobs at once: satisfy whoever reviews it inside your client's accounts payable team, and stand up if a tax inspector asks for it three years from now. This template covers both. Fill it in below and download the PDF, or send the same fields to the API and generate one for every order your app processes.
Nothing is stored: the document is rendered when you press the button and streamed straight back to your browser.
Issuer and client blocks, invoice number, issue and due dates, line items with quantity and unit price, subtotal, a tax line you can relabel to VAT, GST or sales tax, the total due, and free-text payment terms. Amounts are computed for you as you fill the form in.
Through the API you can pass your own HTML instead of the stock layout, or override the header with your logo and colours. Paid plans render without a watermark, so the PDF that reaches your client carries only your brand.
Invoice numbers must be unique and, in most of Europe, sequential with no gaps. Generate the number in your own database — a sequence or an ordered counter per year — and pass it in. Never derive it from a timestamp or a random string.
Which fields are mandatory depends on where you invoice from. The checklist below covers the common core across the UK, the EU and the US; add your VAT or company registration number where your jurisdiction requires it.
Post the order data to /api/v1/render with the template id and get the PDF back in about 0.6 seconds. For nightly billing runs, send up to 100 invoices in a single batch call and collect the results from the webhook.
Attach the bytes to your outgoing email, push them to object storage, or let PDFGeny keep the document and hand your client a download link. Stored documents expire on a schedule you choose.
Most teams meet this document twice. The first time, someone needs a single invoice today and fills in a form like the one above. The second time, the same company is sending four hundred invoices on the first of every month and nobody wants to touch a form at all. The template on this page is the same document in both cases — the only thing that changes is whether you type the fields or post them.
The layout is deliberately conservative. Accounts payable software and the humans who operate it are not looking for a design statement; they are looking for the invoice number, the total and the due date, and every second they spend hunting for one of those is a second your payment is delayed. So the number sits top right where it is scanned first, the total sits alone in a tinted block, and the line items are ruled rather than boxed so that a long description does not break the grid.
If you are automating, the field names in the API example match the form exactly, which makes the migration from “we fill this in by hand” to “our app does it” mechanical. Map your order model onto those keys once and the same call serves both a one-off invoice and a monthly billing run.
Yes. You can fill in the form on this page and download the PDF without an account, up to a few documents a day. A free API key raises that to 50 documents a month for automated use.
Through the API, yes — pass your own HTML for the document, or override the header block with your logo and brand colours. The form on this page uses the stock layout so that it works without an account.
The layout carries every field commonly required in the UK, the EU and the US, but the mandatory set depends on your jurisdiction and on whether you are registered for VAT or GST. Check the checklist above against your local rules, and speak to your accountant if you invoice across borders.
Keep the sequence in your own database and pass the number in. A per-year counter such as INV-2026-014 is easy to audit. Do not use timestamps, random ids or the customer's order number on its own — none of them guarantee a gap-free sequence.
Yes. The batch endpoint takes up to 100 documents per call and returns them together, or notifies your webhook when the run finishes. That is the usual shape of a monthly billing job.
No. Documents rendered from this page are streamed back to your browser and dropped. Through the API you can opt in to storage and get a download link with an expiry you set.
Issue a separate credit note that references the original invoice number rather than editing or deleting the invoice. An issued invoice should never change — that is the whole point of the sequential numbering.
One POST request returns the finished PDF. Free plan: 50 documents a month, no card required.