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

**TSE can matter for wholesalers — the real question is the cash-register function.** Germany's § 146a AO and KassenSichV apply to defined electronic recording systems used for reportable business transactions. For wholesalers, the risk area is not ordinary B2B invoicing, but a counter, cash-and-carry, factory outlet, self-pickup desk, or mobile sales setup that uses an electronic cash-register system. Pure delivery business paid by invoice or bank transfer is a different fact pattern. The BMF FAQ itself is guidance and says the individual decision remains with the competent tax office, so scope should be checked per setup instead of treated as automatic.

**For in-scope electronic recording systems: certified TSE, receipt issuance, and reviewable records.** Since 2020, in-scope electronic recording systems need a certified technical security element that protects the digital records; receipts must be made available in close temporal connection with the transaction and may be paper or electronic. The TSE records transactions with technical evidence such as transaction number, time information, and signature-related data. Only certified TSE components should be used; non-certified or incomplete cash-register setups weaken review evidence and can create fine or estimation risk.

**DSFinV-K: the export format for cash-register review.** In a cash-register audit or Kassen-Nachschau, the practical question is whether the business can provide complete, structured data from the cash-register system, including TSE evidence, voids, and payment types where the setup is in scope. If the data exists somewhere but cannot be exported in the expected structure, the proof position can become weak. The financial effect of a finding depends on turnover, record quality, and the authority's assessment, so test exports and vendor documentation matter before rollout, not only when a reviewer is already on site.

**Wholesale scenarios need a scope check, not slogans.** Likely review candidates include cash-and-carry markets, direct warehouse sale with self-pickup and cash-register processing, factory outlets, canteens, mobile sales units, and market stalls. Usually different: pure B2B delivery paid by invoice, SEPA, or bank transfer without a cash-register function. Card-only or self-service concepts can be fact-specific because recording, receipt, and local setup matter. Clarify the concrete scenario with a tax advisor and, where needed, the competent Finanzamt before choosing a POS/TSE design.

**The risk calculation is about evidence, not scare numbers.** TSE hardware, cloud services, vendor setup, remediation, and advisory effort should be modeled together rather than treated as a generic benchmark. The exact risk depends on turnover, records, and the authority's findings. Missing or inconsistent cash-register evidence can lead to remediation, extra tax-advisor work, estimation discussions, and due-diligence questions. The calmer approach is to document the scope decision, keep the POS/TSE vendor evidence, and run periodic test exports.

**Wholesale software and POS software solve different jobs.** Most wholesale systems are built for orders, delivery, invoicing, inventory, and accounting handoff; a cash-and-carry counter also needs POS behavior, payment handling, receipt issuance, and, if in scope, a certified TSE path. Operating two systems creates master-data and stock-sync work, but trying to process TSE-relevant counter sales through software that is not a POS/TSE system is also risky. A clean architecture defines which system owns the cash-register process and how stock, customers, and accounting summaries move back to the wholesale platform.

**Cloud TSE versus hardware TSE: backup, certificate lifecycle, and export readiness decide.** TSE evidence must remain readable and available for tax review for the applicable retention period. Hardware devices need physical custody, backup/export routines, and certificate monitoring; cloud TSE products reduce some operational risks but add provider dependency and recurring fees. The decision should be made with the POS vendor and tax advisor, then documented with certificate, serial number, export, and migration evidence.

**Accounting handoff still matters after the POS decision.** End-of-day closes should map cash, debit card, credit card, vouchers, refunds, and voids to the correct accounts and tax keys. Where cash-register/TSE data is relevant, the accounting handoff should preserve enough reference information to reconcile POS totals back to the cash-register evidence. Manual account mapping and unexplained voids are common sources of month-end errors; structured exports help the accountant review the bridge from POS to bookkeeping.

**Common practical questions — answered conservatively.** Card-only payment: clarify the exact setup, because recording and receipt obligations can still matter. Register migration: export and retain old POS/TSE evidence before retiring hardware or contracts. Foreign self-pickup customers: buyer location is usually less important than whether the sale is executed through a German cash-register setup. Test exports: run them regularly enough that problems surface before a tax review. Counterfeit-money incidents: document separately with evidence and, where appropriate, a police report.

**Where LuniOps fits — and where you still need POS/TSE expertise.** LuniOps covers the wholesale side: orders, deliveries, invoicing, e-invoicing (ZUGFeRD/XRechnung), GoBD-oriented audit trails, and structured exports for the accountant's DATEV handoff. LuniOps does not provide TSE, KassenSichV cash-register fiscalization, DSFinV-K, or point-of-sale handling. If you operate a cash-and-carry counter or another in-scope cash-register setup, that part should be handled by an appropriate POS/TSE provider while LuniOps remains the operational wholesale system. Clarify the TSE scope with your tax advisor and POS provider before a pilot.