The seven tools

Seven tools in the sidebar. All of them accept files by drag and drop and through a button — the button is the route for keyboard operation.

Every selection produces a fresh page

With a tool that passes judgement on a file, a finding left standing next to a new file would be the most dangerous display imaginable. Nothing is therefore carried over.

The seven in detail

Tool	What it does	What matters
Validate	an XML invoice or a hybrid PDF in, a validation report out	With a PDF, the embedded invoice is extracted first — what is validated is always the data record, never the printed image. A PDF without an embedded invoice therefore gets no validation error but the statement that there is nothing here to validate
View	makes an invoice legible: header data, seller and buyer side by side, line items, tax breakdown, totals, payment	Amounts and dates follow the operating system’s settings, not the language of the interface. Empty fields are not shown at all, and the amount payable is emphasised
Convert	reads an invoice and writes it in another format	The result is validated before anyone saves it. Saving happens only on explicit request; the proposed name comes from the result. Changing either the source or the target discards the previous result
Create	builds an invoice in one of the nine formats from the data entered	What is captured is what an ordinary invoice needs — deliberately not the entire standard model; anything further can be processed afterwards in Convert. The row total is calculated as you type
Extract	retrieves the embedded invoice from a hybrid PDF	Accepts PDFs only. Saving happens without a byte-order mark — the file leaves exactly as it sat inside the PDF; an added mark would be a change to a possibly signed document
Combine	visual PDF + invoice XML → hybrid PDF	The file extension decides the assignment, not the button — whoever drops both files at once should not have to work out which goes where. If the XML is not CII it is converted; if the PDF is not PDF/A-3 it is lifted. Both are reported, because they are interventions in your files
Folder sync	watches inbound folders and converts every incoming invoice	The only tool that works without intervention — see Folder sync

Two things about the messages

The engine’s validation findings are in German

The interface is translated into all nine languages, the finding texts themselves are not yet; the portal translates them, here the normative wording stands. Rule IDs and BT references are language-neutral. An open point.

An undetected format is not a validation verdict. It is issued as information, with the engine’s message — which usually names the way out, for a SAP IDoc for instance the route via Convert.

A repaired file is likewise reported and not silently accepted: the sender’s export is broken and will fail elsewhere just the same.

What is missing here

PDF to e-invoice, invoice data capture, your own Word templates, batch processing, bulk import, the archive and finalising are reserved to the portal — with a reason given for each under Invoiceflair Desktop.