Skip to main content

fiskaltrust.Middleware 1.3.34 (Germany)

June 02, 2022

In this version of the Middleware, we've updated the Fiskal Cloud Connector to 4.0.2 and made the Middleware compatible with the DSFINV-K 2.3. Additionally, we fixed an issue that occurred when switching from one Swissbit Cloud or Deutsche Fiskal TSE to another, and removed unnecessary additional data that was sent to the CryptoVision TSE.

caution

Version 1.3 of the Middleware is meant for the German market only, customers in Austria and France should continue to use version 1.2. We will unify these experiences in an upcoming version.

Updated third party dependencies: Swissbit Cloud & Deutsche Fiskal

We've updated our dependency to the Fiskal Cloud Connector (used by the Deutsche Fiskal and the Swissbit Cloud SCUs) to version 4.0.2. The Middleware's behavior was not changed by this update. Users can update to the latest FCC version by updating to version 1.3.34 of the respective SCU - the FCC update will be automatically installed.

Feature: Update DSFINV-K export to version 2.3

We've implemented some minor changes to make our DSFinV-K export compatible with the recently released version 2.3 of the standard. Like the previous versions of the export, we've again obtained a certification from Audicon. The export is fully backwards-compatible to existing data, and no further changes than updating to the latest version of the Queue are required to use it.

Bug fix: Don't send 'additionalData' to CryptoVision TSEs

We noticed that QR codes generated by our Middleware could not be correctly validated with AmadeusVerify when using a CryptoVision TSE. Our investigations showed that this was caused by the fact that we were sending additional data when signing receipts with the TSE, which is not supported by the verification software, and should be generally avoided. We've removed this parameter to make the QR codes verify correctly.

In addition, we've also prepared an appendix that PosCreators and PosDealers can add to their process documentation (Verfahrensdokumentation) to deal with cases in which auditors raise questions about this behavior.

Bug fix: Switch from one SwissbitCloud SCU to another caused errors in some cases

We implemented a functionality that enables to deregister an ERS (i.e. a client) from Swissbit Cloud and Deutsche Fiskal TSEs, to be able to re-register it when performing a SCU switch from one of these TSEs to another. This error only occurred in scenarios where both TSEs (the source and the target) where created in the same account, as the Fiskal Cloud ensures that ERS names are unique.

Affected packages

Packages not listed here were not updated, as we decided to not increase the version of unchanged packages. All packages with versions greater or equal to 1.3.1 are compatible with each other (it is e.g. possible to use fiskaltrust.Middleware.SCU.Swissbit.1.3.1 with the new queue packages).

  • fiskaltrust.Middleware.Queue.EF v1.3.34
  • fiskaltrust.Middleware.Queue.SQLite v1.3.34
  • fiskaltrust.Middleware.Queue.MySQL v1.3.34
  • fiskaltrust.Middleware.SCU.DE.DeutscheFiskal v1.3.34
  • fiskaltrust.Middleware.SCU.DE.SwissbitCloud v1.3.34
  • fiskaltrust.Middleware.SCU.DE.Cryptovision v1.3.34

Next steps in the Middleware

We will focus on developing of the next version of the fiskaltrust.Launcher in the next sprints. This version will be developed open-source, and our first public prototype can be found in the public repository https://github.com/fiskaltrust/middleware-launcher.

As always, we're happy to hear feedback and suggestions via feedback+middleware@fiskaltrust.cloud or directly via issues in our GitHub repositories.