Your ERP stays. The four things it does not do get done.
If your bookkeeping runs in a system that is not on Erhvervsstyrelsen's register — a foreign ERP, an industry system, something written in-house — the responsibility for the Danish digital bookkeeping requirements is yours, not your supplier's. This closes the four of them a foreign system almost never covers, and leaves your ledger where it is.
What gets done
- A full backup every week, kept with a party that is not related to you, on a server in the EU/EEA — BEK nr 205 af 29/02/2024 § 4. With the exception the rule actually contains: no backup is required for a week in which nothing was booked.
- A SAF-T file as Erhvervsstyrelsen defines it — § 5, stk. 1, nr. 3 — built against their published schema and checked against it in our build.
- E-invoices in OIOUBL via Nemhandel and in Peppol BIS, with the responses each one needs: an application response for OIOUBL, and a message level response AND an invoice response for Peppol.
- The three written descriptions § 6 of the Bookkeeping Act asks for — not seven, which is a product's idea rather than the law's.
What this is not
- Not a bookkeeping system. Nothing is ever written back into your ERP.
- Not an audit, and not a statement that you comply. We show facts and the provision behind them.
- Not a registered bookkeeping system. You stay in the “not registered” category, where the responsibility is yours — you get evidence for four requirements, not a change of status.
You may not need us
Three cases, and the product says so on the first screen rather than after the invoice. If your system IS on the register, its supplier carries this. If you are a financial undertaking, or a subsidiary of one keeping its backup under the parent's rules on a group bookkeeping system, the 2025 amendment to the regulation exempts you from the storage rule entirely. And a breach is punished with a fine — Overtrædelse af §§ 3-5 straffes med bøde. — but the regulation names no amount, so neither do we.