GoBD Compliance 2026: BMF Tightens Validation Under § 146 AO

Since the BMF letter of February 23, 2026, GoBD compliance requires stricter validation of accounting data. The Federal Ministry of Finance (BMF) has updated the principles for the proper keeping and storage of books, records, and documents in electronic form, as well as for data access, to align them with legislative changes in §§ 146, 146a, 147, and 158 of the Fiscal Code (AO). For companies, this means that merely archiving receipts is no longer sufficient. The tax administration is increasingly focusing on the substantive and technical validation of data streams to prevent manipulation and ensure traceability from the origin of a metric to the tax return.

What GoBD Compliance Specifically Demands from February 2026

The revised GoBD places the validation of accounting data at the center of audit practice. While the previous amendment of July 14, 2025, primarily regulated the storage of structured data sets in the wake of the B2B e-invoicing mandate, the BMF letter of February 23, 2026, targets the integrity of recording systems. The adjustments affect the regulatory requirements for bookkeeping (§ 146 AO) as well as the retention periods, which remain ten years for tax-relevant documents under § 147 AO. Companies must technically ensure that incoming data is not only stored in an unalterable manner but is also validated for its formal and material correctness before being transferred to the general ledger.

Why § 158 AO Reverses the Burden of Proof in Audits

According to § 158 AO, formally correct bookkeeping establishes the legal presumption that its result is also materially correct. The tax office must first rebut this presumption before it can deviate from the bookkeeping and make estimates. The revised application decree for § 158 AO, which stems from the law implementing the DAC7 directive, strengthens this evidentiary value but ties it to strict conditions. If a system cannot demonstrate the required validation of data according to the new GoBD principles, the bookkeeping loses its formal correctness. Consequently, the protective effect of § 158 AO is lost, giving the tax authority the leeway to make estimates, which generally work to the detriment of the taxpayer.

The Separation of the GoBD Update and KassenSichV Amendment

The GoBD update of February 23, 2026, must be strictly separated from the changes to the application decree (AEAO) for § 146a AO, even though both were published in the spring of 2026. The AEAO for § 146a AO was updated with a BMF letter dated March 17, 2026, and responds specifically to the Second Ordinance Amending the Cash Register Security Ordinance (KassenSichV), which came into force on February 1, 2026. While § 146a AO and the KassenSichV regulate the technical security device (TSE) of electronic recording systems such as cash registers, the GoBD cover the entire upstream and downstream accounting processes. Both sets of rules interlock but require different technical responses in the system architecture.

How Systems Technically Solve Seamless Traceability

A GoBD-compliant documentation and accounting system processes receipts without media discontinuity and ensures traceability up to the DATEV export. To meet the tightened validation obligations, data processing cannot be a black box. In practice, this means: Every metric must be traceable to the source. The path from the source field via the mapping and the tariff to the final formula is hardcoded in the system and remains auditable. When a receipt is read via OCR and AI vision, the system creates a complete booking proposal with accounts, splits, and tax keys. An orchestrator decides in three stages whether the process is booked automatically, submitted for review, or processed manually. Nothing is waved through blindly. Four sources form the safety net for this validation: strictly defined rules, booking history, machine learning, and large language models. Every confirmed or corrected booking trains the system, which measurably increases the proposal quality per creditor.

The Path to Audit-Proof Procedural Documentation

Procedural documentation remains mandatory for all companies required to keep books and must imperatively reflect the new validation steps. A system that merges data from many sources into a continuous P&L, EBITDA, and liquidity calculation requires a precise description of the data flows. If cost modeling is carried out down to the individual invoice line—for example, for shipping, commission, or storage costs, which are allocated by channel and country with version control—the procedural documentation must map this end-to-end process from a single source. Governance is not an afterthought here but is built into every tool. Approvals, logs, and limits ensure that every action remains traceable. System responses to search queries in the archive always include a direct source link to the respective notice or receipt. This architecture ensures that the legal presumption of material correctness under § 158 AO withstands a tax audit.