E-Invoicing for Tax Firms: Turning the Mandate into an Opportunity

Updated: 2026-08-02

For tax advisory firms the e-invoicing mandate initially means extra work: clients ask questions, processes change, software has to catch up. At the same time it is the first occasion in years where every client has to take a digitalisation step at the same time.

What actually changes in day-to-day practice

The real shift is not the file format but data quality at intake. Until now a document arrived as an image and was keyed in or read by OCR — with an error rate and rework. An e-invoice instead delivers a structured record: invoice number, amounts, tax rates, line items and payment terms sit in clearly defined fields under EN 16931.

That moves the effort around:

• less manual capture and checking of OCR output
• more weight on clean master data — a wrong VAT ID or a missing Leitweg-ID now fails hard
• new: a validation step — is the incoming file standard-compliant at all?

The error case becomes the normal case

In practice the most common question is not “how do I create an e-invoice?” but “why is this one being rejected?”. Typical causes are incorrectly rounded tax amounts, disallowed code-list values, or a missing reference on a credit note.

For the firm that means you need an answer to which rule was violated and what specifically to change — not just an error number. A validator that names the violated rule in plain language saves more time here than any training session.

Batch validation instead of one file at a time

Across several clients, the command line pays off. A whole folder of outgoing invoices can be validated in one run:

npx -y @beleggo/cli validate ./client-4711/*.xml --explain

The exit code is 0 when everything is valid and 1 as soon as one file has errors — so the check can be wired into existing scripts or a nightly run. --format json returns a machine-readable result for further processing.

Prioritise clients instead of blanket mailings

A circular to every client mostly generates callbacks. Segmenting along what the law actually requires works better:

The underlying dates are set out in full in E-Invoice Deadlines, the legal basis in the Wachstumschancengesetz.

The firm as digitalisation adviser

The advisory occasion reaches further than the format. Talking to a client about invoice intake inevitably means talking about approval routes, payment runs, archiving and master-data hygiene — topics clients rarely raise on their own.

Three approaches that work in practice:

1. Walk the process, don’t send a questionnaire. Trace one real incoming invoice together, from inbox to posting. The gaps show up by themselves.
2. Settle on one format, not several. One outgoing format per client — see Which format?.
3. Resolve archiving early. What must be retained is the structured original, not the printout — see Archiving e-invoices.

Data protection with client data

A practical point when choosing tools: many online validators upload the invoice to a third-party server. With client data that needs explaining. Validation in the browser tool runs entirely locally — the file never leaves the machine. The same holds for @beleggo/cli and @beleggo/mcp, which run the same engine on your own hardware.

Next step

Take one real outgoing invoice from a client and validate it against EN 16931. The result is usually the most concrete basis for discussion you can bring to the next client meeting.