Zum Hauptinhalt springen

Changelog

This page lists relevant changes and updates in fiskaltrust's cloud services, on-premise products, and documentation.

You can subscribe to all changelogs via RSS, follow the GitHub repo, or display categories of changes by tags.

Notification Management Process

· 4 Minuten Lesezeit
Platform Team

This release introduces Notification Management Process

Available since June 2025

Affected markets: DE

Overview

In accordance with Section 146a (4) of the German Fiscal Code (AO), every electronic cash register or recording system must be reported to the responsible tax office within one month after being put into operation or taken out of operation. To support this legal requirement, we have implemented a complete Notification Management Process, including:

  • Notification Management Page
  • POS Operator Data pages
  • Notification Worker (Azure Function)

New Features & Components

  1. Notification Management Page (Dealer Portal) A new management interface is available for dealers, providing the ability to:
  • View and manage all operators under their dealership
  • Enable or disable automatic or manual notifications for each operator
  • Review all sent notifications along with their statuses (successful, failed, pending)
  • Trigger notifications manually for specific operators if needed

  1. Operator Data Page

    A dedicated page where the operator can update all required data. The dealer sends the operator a link to this page. All necessary information for notifications is collected and validated here.

  2. Notification Worker (Azure Function)

    A background worker runs every night at midnight, collecting the operator’s data and sending notifications to ERIC (third-party communication interface for German tax authorities).

Required Data for the Notification

Every notification must include:

  • Operator information
  • Outlet information
  • Electronic recording system information
  • Type of certified TSE
  • Number of electronic recording systems
  • Serial number of the electronic recording system
  • Purchase date
  • Commissioning date
  • TSE information (extracted from the TseInfo JSON)

Common Issues Below is a list of frequently occurring errors and how to resolve them.

  1. Invalid Tax Number Possible Causes a) The tax number does not match the scheme for the Bundesland (state) b) The company must report to another state than where it physically operates c) A regional 10–11 digit tax number is used instead of the required 13-digit number

    alt text alt text alt text

  1. Missing or Invalid Data: Third-Party CashRegister (TSE Serial Number)

    Error: TSE serial number must be at least 64 characters and hexadecimal (0-9, a-f, A-F)

alt text

  1. Invalid TSE BSI Certification Number Required format: YYYY-NNNN

    alt text alt text alt text

  1. Missing Notification Product in the Outlet Problem: The outlet does not have an active notification product or carefree package.

    alt text alt text

  1. ERIC Exception: Duplicate Serial Numbers Error: ERIC reports that the same recording system serial number is used multiple times. Cause: More than one queue shares the same Queue name. Solution: Operator → Configuration → Queues Remove duplicates: • Send “Out of Operation” receipt, or • Hide queue if it does not exist physically Then re-trigger the notification.

    alt text

  1. Missing TSE Information (TseInfoJson) Cause: No TSE data found in the last End-of-Day receipt → possible TSE connection problem. Solution: Check last End-of-Day receipt: • If TSE data exists → re-trigger notification • If not → fix the TSE connection problem or send a zero receipt to restore connection

    alt text

  1. Missing POS System Data (Model, Manufacturer) Cause: No valid POS System ID in the last End-of-Day receipt.

    alt text alt text

  1. Invalid Date Order (PurchaseDate vs CommissioningDate) Error: Purchase date cannot be later than commissioning date.

    alt text alt text alt text

  1. ERIC Exception: Illegal Characters in Fields Error: Some characters in the legal company name or address are invalid.

alt text

Additional Notes

• To check if a POS System is assigned:

Operator → Related Queue → Receipt Journal

Last daily closing must show a correct POS System ID that exists in DE Dynamic

• A notification is only sent when:

✔ Notification state = true in Account Settings

✔ At least one outlet has an active notification subscription. And outlet should have at least one active queue or third party queue

✔ Operator has confirmed all required data

• Postal code and tax number both should be valid while validating the tax number ( The tax number must match the correct state (Bundesland) based on the postal code)

• We have implemented Notification_API and gradually extracting common logic from worker and portal into this API to centralize and simplify the validation and processing steps

• Notification will be send for active queues . Hidden queues or queues that became inactive before July 1st, 2025 will not receive notifications

Useful links: