Creating invoices
Create a validated draft in the web app, from JSON or with AI.
Choose a form, JSON or an assistant. Every path produces the same validated payload.
The builder
Point and click. Best for your first few and for anything unusual.
From JSON
Paste a payload, get a PDF. Best for testing and scripts.
From an assistant
Describe it in words. Best once your setup is stable.
The builder
Invoices → New.
Pick the issuer and the client, then add lines. Each line has a description, quantity, unit, unit price and VAT rate. Totals recalculate as you type, grouped per rate.
The header fields:
| Field | Default | Notes |
|---|---|---|
| Document type | invoice | Also proforma, advance, credit note |
| Issue date | Today | |
| Due date | Issue date + issuer's terms | Must not precede the issue date |
| DUZP | Issue date | Required on invoices and credit notes. Can be earlier |
| VAT mode | regular | Reverse charge and OSS are the alternatives |
| Variable symbol | Digits of the invoice number | The payment reference your client quotes |
| Constant / specific symbol | — | Rarely needed |
| Notes | — | Free text, max 2000 chars, printed on the PDF |
A credit note additionally requires the number of the invoice it corrects.
Saving produces a draft: no number, fully editable, not a tax document. Drafts follow live edits to the issuer and client until you issue.
From JSON
Invoices → From JSON validates and renders a complete payload. Use it to test the schema, debug automation or handle a scripted one-off.
Validation runs as you type and points to the failing field.
Field reference: invoice schema.
From an assistant
With MCP configured, you can describe the invoice instead of filling a form:
Look up NFCtron by IČO, use my "s.r.o." issuer preset, and invoice them 40 hours of consulting at 1 800 CZK plus 12 000 CZK for the integration work. Due in 14 days.
The assistant looks up the client, loads your issuer preset, builds the payload and corrects any validation errors. Review the result before issuing:
Read what the assistant produced
Validation guarantees an invoice is well-formed, not that it is correct. The schema cannot detect that the model billed 40 hours when you worked 4, or picked 21 % where 12 % applied. Review the draft before issuing — issuing is the irreversible step, not creating.
Templates
Save recurring line items, VAT settings and payment defaults as invoice template presets. An assistant can merge a template with the details for this invoice.
Recurring drafts
Invoices → Recurring, or Repeat on an invoice detail. Invoicey saves the lines as a template and creates a draft on the chosen day (monthly or quarterly, days 1–28). You still issue and send it yourself.
The next run is never the same calendar day. If a previous draft from that schedule is still unissued, Invoicey skips rather than piling drafts. Change lines by saving a new template from a newer invoice — there is no template editor.
Duplicating
Duplicate any invoice to create a fresh draft. Invoicey copies its content but clears the number, issue facts, payment and snapshots.