Invoiceflair Desktop

Invoiceflair Desktop is the workstation tool: the same e-invoicing tools as the portal, but locally on your own machine — without an internet connection, without an account, without signing in. For Windows and macOS, in nine languages. After the one-time activation, the application never asks for a connection again.

Not to be confused

Docuflair Desktop is a different product from the same company: it redacts and pseudonymises documents. Both can be licensed independently on the same machine.

What it is — and what it is not

The desktop is no replacement for the portal but the answer to three sentences: “on the road”, “no network” and “that file must not leave the building”. Technically it uses the same engine and the same tool layer — a ZUGFeRD created here is the same ZUGFeRD as there.

	Desktop	Portal
Authorisation	a licence, activated online once, bound to one workstation	an account (free) or anonymous
Network	only for activation; permanently offline afterwards	for every use
Data	stays on the machine	goes to the service (cloud) or your own server (Enterprise)
Tenants, archive, number ranges	no	yes (with an account)
Tools	seven	ten

What remains reserved to the portal

The desktop deliberately uses only the public surface of the shared tool layer. Everything that knows about a request, a tenant or a database stays in the portal:

Not in the desktop	Why
PDF to e-invoice and invoice data capture	they need the OCR integration, which is not shipped at this stage. PDFs with an embedded invoice can be read by the desktop — see Tools
Your own Word templates	the same reason: DOCX to PDF needs the additional licence. The auto-layout PDF and the Factur-X embedding are licence-free
Batch processing and bulk import	they need a queue, a job store and a tenant. Folder sync is the local answer to “many files”
Archive, finalising, consecutive numbering	the number range belongs to the tenant and needs a database that counts without gaps
Master data, members, mail dispatch	they presuppose an account
API keys and the JSON API	the desktop is the application, not the service
Usage log	there is no log sink; folder sync keeps its own journal

The rule for further development

A new functional capability is built in the shared tool layer, not here. Two implementations of the same ZUGFeRD writer would be two different products within a year — with two sets of defects, two validation reports, and a customer holding both side by side.

How to begin

1. Installation for Windows or macOS
2. Activate the licence — online, once
3. Get to know the seven tools
4. For unattended operation: folder sync