InvoiceyDocs
Everyday workflows

Import history

Preserve previously issued PDF and ISDOC files in bulk.

Switching to Invoicey mid-year leaves your history behind. The import flow at Invoices → Import bulk-loads previously issued invoices so your list, dashboard and totals cover the whole year rather than starting from zero.

You can also start this from first-run onboarding (Bring your invoice history?) or skip it and come back later. Pick the tool you used — Fakturoid, FakturaOnline, iDoklad, and the rest. Upload files is ready today. Direct Connect stays locked until we ship a hosted integration.

Web only. There is deliberately no import tool over MCP or Slack — a bulk write of historical tax documents wants a human looking at a review grid, not an assistant looping over a folder.

How it works

Pick the issuer

Choose the business that issued these invoices. One batch belongs to one issuer.

Set batch defaults

Select the source provider and whether invoices should arrive marked as paid.

Upload PDFs

Add up to 40 files per batch, 16 MB each.

Let Invoicey classify

Each PDF is inspected for embedded or sidecar ISDOC data.

Review

Confirm every row. Archive imports expose editable header fields and paid state.

Import

Rows keep their historical dates and numbers. Invoicey's counter then advances past the imported sequence so the next native invoice cannot collide.

Full versus archive

This is the distinction that determines what you get.

The PDF carried an ISDOC. Invoicey parses it into a complete, validated payload — line items, VAT breakdown, both parties, dates.

These behave like natively issued invoices: filterable, searchable, correctly counted in VAT and revenue totals. Both the original PDF and the extracted ISDOC are stored.

Most Czech invoicing tools embed ISDOC, so this is the preferred path.

Duplicates

Every imported row gets an idempotency key:

  • isdoc:{uuid} when the ISDOC carries a UUID.
  • num:{provider}:{number}:{issueDate} otherwise.

Re-importing the same batch skips rows whose key already exists, or that collide on (issuer, number). Skips are reported in the summary. Nothing is overwritten — there is no replace mode, so recovering from a bad import means deleting the rows, not re-running it on top.

Imported artifacts are immutable

Imported invoices are flagged so Invoicey never regenerates their PDF. Downloads always serve the original file your previous tool produced.

That is the honest behaviour: re-rendering someone else's invoice in Invoicey's layout would produce a document that never existed, differing from the one your client actually holds. Archive rows without an ISDOC simply have no ISDOC download.

Provenance

Each imported invoice records where it came from — provider, label, version, batch ID, import timestamp — so a year later you can still tell which invoices Invoicey issued and which it inherited.

Not supported

  • OCR or AI extraction from non-ISDOC PDFs
  • Received (purchase) invoices — this is outbound only
  • Import over MCP or Slack
  • Automatic replace on number collision