NEWSLETTER NO. 1

Sovereignty is not friction

Sent to subscribers on . Issues are published here once the next one has gone out. Translated from the Danish original.

You signed up for Struktura's newsletter at strukturacompliance.dk — this is the first issue. The concept is simple: I write when something happens that matters for the compliance requirements facing your business and your ERP — what the change is, when it applies, and what it demands. No fixed schedule, no sales follow-up, unsubscribe at any time.

My perspective: sovereignty is not friction

Scattered fragments assembling into an ordered foundation of horizontal layers
*AI-generated illustration

The common narrative is that EU regulation is friction for European companies — bureaucracy and cost. I helped write some of the requirements at the Danish Business Authority, so my impartiality can be debated. But my honest view, having seen the requirements both from the inside and now from the outside, is the opposite: they are infrastructure.

Structured digital bookkeeping makes your numbers usable — for yourself, before any authority asks. E-invoicing makes your invoices machine-readable across Europe. And the sovereignty agenda forces the question few ask before it is too late: who can actually switch off your systems, change your prices or move your data?

When I started Struktura, I put the entire digital backbone — mail, calendar, servers, CRM, booking — on European infrastructure. It took a few weeks and cost less than expected. Where did it hurt? Two places, honestly: the selection of ready-made integrations is narrower than in the American ecosystems, and a few tools take more manual work to set up. That is the price. In return, I know exactly where my clients' data lives and who can change the terms tomorrow: no one.

Clean compliance is a passport — to public tenders, to larger customers, and to a higher valuation the day the company is sold. That is why I call it a head start, not a burden.

Status on the Danish requirements — in brief

Digital bookkeeping: The requirement already covers virtually all companies subject to bookkeeping obligations — and from 1 January 2026 also personally owned businesses with revenue above DKK 300,000 in two consecutive years.

SAF-T 2.1: The Bookkeeping Act's requirement for the standardised data extract expands from 1 January 2027. The expansion was known as SAF-T 2.0, but the Danish Business Authority has sent a newer version, 2.1, into technical consultation — and that is the one that will apply, before 2.0 has even reached the whole market. If you use a registered bookkeeping system, building this is your vendor's job — but it is your responsibility to know whether your setup keeps up.

E-invoicing: The Danish Business Authority has dropped the planned Danish standard OIOUBL 3.0 (January 2026) and is instead migrating fully to the pan-European Peppol BIS standard. The national side road is closing; the European track is the future — and it points straight at the ViDA requirements in 2030.

In the next issue: what the SAF-T 2.1 consultation concretely means for system vendors and their customers — and why the cancellation of OIOUBL 3.0 is a bigger story than the coverage suggested.