Skip to main content

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.

Documentation – New Landing Page, Architecture Guide, and Platforms

· 8 min read
Documentation Team
Documentation Team
The team working on the Documentation

This release introduces a redesigned documentation landing page with a new search, adds guidance for planning a fiskaltrust.Middleware setup, new cash register integration pages for all markets, and market-specific updates for Austria, Germany, Greece, Italy, Poland and Portugal.

Added: Redesigned documentation landing page​

The documentation landing page has a new design that matches fiskaltrust.eu, in light and dark mode:

  • Search: a search field in the header of the landing page shows up results directly below the field as you type. Each result shows its area (Developer, Partner or Release Notes) and market first, and results are sorted Developer, Partner, Release Notes. The Search button opens the full search results page, which uses the same order.
  • Search on every page: the same search field is in the navigation bar on every other page. On narrow screens, a search icon opens the search results page.
  • Developer and Partner cards: direct links to the Developer and Partner main sections.
  • Select Your Market: the nine markets side by side, each linking to that market's guide.
  • Recommended Resources: the POS System API 2.1, PosDealer API and Receipt API references, the Development Kit on GitHub and the Development Platform.
  • What's new: the latest release notes, at most one per product (Middleware, Portal, InStore App and Documentation), with a link to all release notes.
  • Footer: A new footer links to GitHub, LinkedIn, YouTube, the fiskaltrust.Portal, fiskaltrust.eu and the blog.

Why it matters: Readers find the right page from the landing page in one step, whether they search, start from their role or start from their market, and see the latest releases at a glance.

Added: Choosing a Middleware Architecture​

The new Choosing a Middleware Architecture guide compares the local, hybrid and cloud models of the fiskaltrust.Middleware, explains the SCU models (local or managed, dedicated or shared), and walks through the decision factors: operating system, whether an additional signature device is needed, hardware or cloud signature device, and local or cloud Middleware. It includes availability by market, a decision diagram and a checklist.

Why it matters: Developers can choose the setup that fits their POS system and markets before they start the integration.

Added: Platforms​

The new Platforms page gives an overview of the platforms the fiskaltrust.Middleware runs on: Windows, Linux and macOS, Android, Docker and Kubernetes, and the hosted fiskaltrust.Middleware for Cloud. It compares Launcher 1.3 and Launcher 2.0 and covers the download from the fiskaltrust.Portal, install, test and uninstall scripts per platform, and the Android Launcher 2.0, which provides the POS System API over Android IPC.

Why it matters: Developers find the supported platforms, launchers and download links on one page.

Added: fiskaltrust.Middleware, Terminals and Locations​

The new fiskaltrust.Middleware, Terminals and Locations page explains why the fiskaltrust.Middleware is the cash register in the regulatory sense, how POS terminals connect to it, how many fiskaltrust.Middleware instances a location needs, and what to do when the fiskaltrust.Middleware is not reachable.

The market pages add the local rules:

Why it matters: Developers can plan their rollout per location and know how terminals, receipt chains and closings relate to each fiskaltrust.Middleware instance.

Added: Cash Drawer Movements​

  • Cash Drawer Movements: how to record cash that goes into or out of the cash drawer without a sale, for example transfers to the bank or safe, owner deposits and withdrawals, or the opening float, and how change is recorded in a sale.
  • Germany: Cash Drawer Movements (Kassenlade) covers the local flags for Geldtransit, Privateinlage, Privatentnahme, Lohnzahlung, Anfangsbestand, DifferenzSollIst, Einzahlung and Auszahlung, and their DSFinV-K GV_TYP mapping.

Why it matters: Developers record cash movements the same way in every market, and German integrations find all cash transfer types and their DSFinV-K mapping in one place.

Added: Downpayments, tips and proforma invoices​

Why it matters: Developers know how to handle downpayments from the first payment to the final invoice, including the cases where the downpayment covers or exceeds the final amount.

Added: Additional Lines on the Receipt​

The new Additional Lines on the Receipt page describes how a POS system adds text lines to a receipt rendered or printed by fiskaltrust: sublines below a charge item with cbChargeItemLines, receipt-level lines with cbReceiptLines, and payment receipts with cbPayItemLines or Receipt.

The market pages add what the local printers support:

Why it matters: Developers know which additional lines they can send and how they appear on the printed and digital receipt in each market.

Added: Portugal Middleware Not Reachable​

The new Middleware Not Reachable page explains why late signing is not possible in Portugal, how documents are issued on pre-printed forms during an outage, and how they are recovered afterwards with the Handwritten flag, including refunds and voids of recovered documents.

Why it matters: Developers in Portugal know how to prepare for an outage and how to recover the documents issued during it.

Improved: Android IPC Transport​

The Android IPC Transport page now explains how to choose between the Bound Service IPC and the Activity Intent transport, and recommends the Bound Service IPC for new integrations. The Bound Service IPC section adds the prerequisites, the architecture, step-by-step instructions, a minimal example and a full reference implementation.

Why it matters: Developers integrating on Android can pick the right transport and implement it from a working example.

Updated: QR code on receipts in Germany and Austria​

  • Germany: the new section Content of the QR code describes the signature item that carries the QR code, how to encode it, the DSFinV-K print recommendation and the 12 fields of the QR code.
  • Austria: the Machine-readable code (QR code) section describes the signature item that carries the code and the case when the signature creation device has failed.

Why it matters: Developers know which signature item to print as the QR code and how to print it.

Updated: Market rules for discounts and agency business​

  • Greece: the data structures page describes how discounts are transmitted to myDATA as deductionsAmount and how to set discountOption.
  • Poland: the data structures page describes how discounts and extras are assigned to sale lines on the POSNET printer.
  • Agency business: Portugal rejects charge items for agency business, as described in its type of service table; in Greece a receipt or invoice with only agency business items is transmitted as myDATA type 11.5 or 1.4, as described in its type of service table.

Why it matters: Developers know how the general rules for discounts and agency business apply in their market.