Re-issue any supplier invoice on your letterhead.

Documents in, structured data out, your document back — one tool call.

extract_and_generateinspect_documentcreate_template

The problem

Every business that rebills costs — agencies, bookkeepers, property managers, freight forwarders — receives supplier invoices in a hundred different layouts and has to send them back out in exactly one: their own. Today that gap is closed by hand. Someone opens the supplier PDF, retypes the vendor name, the line items, the totals into the company template, and hopes they didn't transpose a digit.

Even teams with an AI agent end up stitching it together themselves: one call to extract the data, hand-rolled templating in between, another call to render a PDF. Two round trips, two things that can half-fail, and an agent inventing its own ad-hoc glue.

How Inkrun solves it

1
Send the supplier invoice plus your template
A Markdown template with {{field}} placeholders — {{vendor_name}}, {{invoice_number}}, {{total}}, the line-item table.
2
Inkrun extracts the invoice
The invoice preset returns schema-shaped data with per-field confidence — deterministic tier first, model tier only when needed.
3
Inkrun renders your template with the extracted values
On your theme: your logo, your fonts, your accent color, your cover page.
4
You get back a link
A themed PDF that looks like you issued it.

one tool callMCP

agent → extract_and_generate(supplier-invoice.pdf,
          template: letterhead_invoice_md,
          theme: "letterhead")
      ← { url: "https://…/renders/inv_8f2.pdf", warnings: [] }

Why it holds up

Never half-billed

Extraction credits and the render credit reserve together and release together. If the render fails, the extraction is refunded too — no orphaned charges.

Never fabricated

A field the document doesn't contain renders as a visible blank plus a warning — Inkrun will not invent an invoice number.

Never off-brand, never injected

Extracted values enter the template as data, not markup. A hostile PDF whose "vendor name" contains HTML comes out as literal text. Content never carries styling, so output can't drift.

One meter

Deterministic extract (1 credit) + render (1 credit) — a typical re-issued invoice costs 2 credits, settled to the cheapest tier that actually did the work.

Where it fits

Agencies and consultancies rebilling pass-through costs on branded invoices
Bookkeeping and outsourced-AP firms normalizing supplier documents for clients
Property managers turning contractor invoices into owner statements
Any AP workflow where “make it look like ours” is a manual step today

One MCP connector, both directions of the document layer.

Get API key