One topic, one guide.
Long-form guides with decision frameworks and checklists. Pick the topic that concerns you right now.
The e-invoicing mandate, step by step.
Receiving has been mandatory since 2025, issuing follows in 2027 and 2028, and why rebuilding the whole invoicing pipeline beats a minimal converter.
Who must issue from 2027, who only from 2028 and what the 800,000-euro prior-year threshold means, verified against the VAT Act, the ordinance and the ministry.
What has been mandatory at the inbox since 2025 and how an XRechnung or ZUGFeRD file is validated, assigned and archived for eight years.
The eleven most frequent rejection reasons, each verified against the official validation rules, and the pattern behind them.
Five questions per client, ten minutes, one traffic-light outcome: where configuration is enough and where nothing works without a real interface.
The mandate in your industry.
Multi-part freight invoices, self-billing under the mandate (BMF para 17), TMS format limits and the GoBD archive gap.
Which entity is the recipient of third-party invoices, what the structured data set never carries and what the route to the property ledger looks like.
What the mandate means for a craft business and what common craft software does and does not do, by the vendors' own accounts.
Honest math, real operation.
Three to four hours of operation a month times your hourly rate, against operation from 900 €, including the cases where building it yourself wins.
All states re-verified against the official funding banks on 13 September 2026: which grants for externally built automation actually still run.
What the system does, where German tax-advice law draws a hard line and when the whole idea is a bad one.
An anonymised field report from a law firm: 19 proposals approved and published from May to August 2026, and why the continuous operation is the real value.
Workflows in firms and service teams.
What “digital law firm” really means: DATEV criteria and a roadmap to process automation.
Use-case selection, starter model, operations and metrics, without breaking operational discipline.
Status model, follow-ups, routing logic and SLAs: an intake that does not depend on one person's memory.
Approval, guardrails, topic rotation, publishing: AI drafts, humans approve, and the quality stays yours.
Handoffs, status and reporting: how service teams keep quality while raising throughput.
Rather apply this to your organisation directly?
Describe your bottleneck in two sentences. You get a concrete assessment within 24 hours.