German TSE & Cash-Register Security Act: What Wholesalers Need to Know in 2026

**TSE applies to wholesalers too — contrary to common belief, with unannounced inspections since 2025.** At Luniops we often see food wholesalers believe Germany's KassenSichV is only for restaurants and retail. Wrong. The TSE requirement applies to any electronic recording system that handles cash transactions — including cash-and-carry markets, direct sales to customers, factory outlets, and mobile sales units. A wholesaler who only sells via invoice and bank transfer is indeed out. A wholesaler with a counter, a self-serve area, or truck sales is in. 2026 penalties: up to 25,000 EUR per case, more on repeat violations. On top: tax authorities have been auditing more aggressively since 2025, often with unannounced cash inspections (§ 146b AO). Fail to show TSE data and you immediately face an estimation — typically with a 10–20% safety surcharge on known revenues. Practical experience: these inspections cluster particularly in industries with high cash share — and food wholesale with cash-and-carry sits at the top of that list.

**KassenSichV requires certified TSE plus a receipt obligation — transition periods have expired, BSI certificate is mandatory.** The regulation has required since 2020 a certified Technical Security Element on every register that handles cash transactions. As of 2026 transition periods have long expired — even retrofitted legacy registers must be TSE-certified. The TSE logs every transaction with timestamp, signature, and sequential transaction number tamper-proof. Plus the receipt obligation: every cash transaction needs a receipt, even if the customer does not want one. The receipt may be electronic (QR code, email) — paper is not mandatory, but provision is. Practically: a printer or QR display at the register is required. Violations carry significant fines, often five-figure per audit. Important: only BSI-certified TSEs are allowed — homebrew or non-certified security modules trigger immediate estimation. The list of certified vendors is published by BSI on its website and updated continuously.

**DSFinV-K: the export format the tax audit wants — otherwise estimation with safety surcharge.** At any audit the authority can demand a DSFinV-K export — defined CSV format with all register movements, TSE signatures, voids, tips, and payment types. Cannot deliver it and you face estimations. For a cash-and-carry with 50,000 EUR daily turnover, easily a six-figure damage. Important: DSFinV-K demands structured void reasons — "void" without a reason is suspicious and typically triggers a deeper audit. In practice DSFinV-K is the most common stumbling block because many cash systems store the data but cannot export it in the required format — the audit then ends with an estimate instead of proof. Concretely: when the auditor requests a test export and the vendor does not deliver standard-button DSFinV-K, the burden of proof flips. Instead of the auditor having to find gaps, you have to prove everything was documented — a position you never want to be in.

**Six wholesale scenarios — four clearly in scope, two disputed or out, when in doubt deploy TSE.** In KassenSichV scope: cash-and-carry markets (Metro-style), direct warehouse sale with self-pickup and cash, factory outlet and canteen as soon as cash is received, mobile sales units like truck sales or market stalls with cash transactions. NOT in scope: pure B2B delivery paid by invoice or SEPA. Disputed: card-only operations — KassenSichV technically defines "cash transaction" as cash, but in practice we recommend TSE for self-serve concepts anyway because of receipt and recording obligations. When in doubt clarify with the tax advisor — penalties exceed deployment cost by far. Rule of thumb: better one TSE too many than one too few. A cloud TSE at 200 EUR investment per register is in any scenario below the threshold of a single fine, which is why the risk-return calculation almost always favors TSE deployment.

**Worked example: 1,200 EUR TSE investment versus 192,000 EUR real damage — and reputational fallout.** TSE hardware (cloud or USB) costs 200–400 EUR per register, plus 30–50 EUR/year maintenance and certificate renewal. Four registers = one-time 1,200 EUR, ongoing 200 EUR/year — negligible versus the risk. Versus: fines up to 25,000 EUR per case, estimations potentially six figures, plus extra tax-advisor cost. We had a 2025 onboarding case where a cash-and-carry market had to pay 180,000 EUR estimation plus 12,000 EUR fine after a tax audit — the TSE investment would have been ~2,000 EUR. On top: reputation damage. Estimations are noted in the tax record and can become problematic in bank financing, because banks want a clean tax history in their credit checks. Also: in case of a future company sale, a tax estimation in the due diligence is a red flag that can noticeably reduce the purchase price — a delayed but very real cost.

**Standard wholesale software typically cannot do cash-and-carry — two systems mean double error sources and broken stock sync.** Most wholesale software does not natively support cash-and-carry or self-pickup workflows. They are built for ordering, delivery, and invoicing — not point-of-sale at a counter. Operating cash-and-carry requires either a dedicated POS with an interface to the wholesale software (stock sync, customer master data) or a platform that handles cash-and-carry natively with TSE. The latter is significantly simpler — two systems mean double data maintenance and double error sources. Common practical mistake: customer is created in wholesale software and again in POS — maintenance breaks down after 6 months, mailings go to old addresses, credit limits are mis-managed. On top: the inventory sync problem. If the cash-and-carry register does not sync stock against the wholesale software in real time, you sell goods twice — once cash-and-carry, once via delivery. Complaints and refunds become the norm, not the exception.

**Cloud TSE versus USB TSE: 2026 clearly toward cloud — backup and lifetime decide, USB risks are real.** TSE data must be retained 10 years, readable at any time, ready for DSFinV-K export. USB TSE has physical lifetime risk — lose the stick or it fails, you have a compliance problem. Cloud TSE (Deutsche Fiskal, Epson, Cherry) solves this with automatic backup but charges ongoing fees, typically 8–15 EUR/month per register. As of 2026 the market clearly moves to cloud TSE — ongoing cost justified by lower failure risk and simpler maintenance. Common retention mistakes: USB TSE in a desk without backup (lose it and bookkeeping is formally unusable), TSE certificate expires without renewal (all transactions from expiry not certified), old TSE thrown out at register replacement (violating the 10-year retention). These three mistakes appear in practically every second USB-TSE installation — cloud solves them structurally and is therefore the more economical choice even at higher recurring cost.

**Clean KassenSichV compliance also means DATEV integration with TSE reference per journal entry — voids need mandatory reason.** End-of-day closes must flow into DATEV with correct account mapping per payment type (cash, debit, credit) and tax key. Voids need a separate posting run with reason. Tips are rare in B2B but must be VAT-correct when present. A modern platform delivers all this preconfigured — manual is an error source. Important: the DATEV booking must carry the TSE transaction reference, otherwise the bridge between cash audit trail and accounting cannot be drawn. Without it you lose audit time and trust — even when the data itself exists. In practice the account mapping per payment type is the most common error source: if card payments are booked to the same account as cash, the cash-difference analysis is nearly impossible and the auditor immediately finds inconsistencies.

**Common practical questions — answered concisely, focused on migration and retention topics.** Do we need TSE for card-only payment? Disputed — deploy TSE to be safe because of receipt and recording obligations. What about register migration? Old TSE data must be retained 10 years, exported as ZIP — old hardware TSE may only be discarded after the export is verified. Can we run TSE-required transactions through our wholesale software? Only if it has certified TSE integration — most standard wholesale software does not. What about foreign self-pickup customers like Polish restaurateurs paying cash? KassenSichV applies regardless — buyer location is irrelevant, what counts is execution at the German register. How often test-export TSE data? At least quarterly. How do we handle counterfeit-money incidents? Separate booking position with documentation and police report — otherwise it looks suspicious to the tax authority.

**Luniops bundles cash-and-carry, TSE, and DATEV in one platform — no Excel bridges, with BSI-certified cloud TSE.** Concretely: Luniops offers an integrated cash-and-carry mode with certified cloud-TSE integration (Deutsche Fiskal), DSFinV-K export on click, automatic DATEV integration with end-of-day closes per site, and 10-year audit-proof archiving. Orders, deliveries, cash-and-carry sales, and invoices live in one platform — no Excel bridges between POS and wholesale software. Voids captured with mandatory reason, tips booked VAT-correctly where relevant, TSE transaction reference in every DATEV journal entry. To run your cash-and-carry site KassenSichV-compliant in 2026, talk to us about setup and pilot — we also bundle the BSI-certified TSE setup so you do not have to deal with three different vendors. In the pilot we show you a complete DSFinV-K test export of your first pilot days before any contract is signed — so you know concretely what would be presented in an audit.