customer request for a flag which executes zero-receipt to recover from late/failed signing mode while executing daily-closing

[steininger]

Initial message from customer:

_

Wir haben bei der Cloud TSE in D oft das Problem das diese außer Betrieb ist. Eine Neuintialisierung kann ich nur mit einem Nullbeleg veranlassen, ist natürlich aufwendig weil momentan bei uns nur manuell machbar. Nun meine Frage: Wäre es möglich das Ihr beim Daily Closing automatisch eine Initialisierung macht? In Österreich haben wir in der Nacht (Tagesende) einen autom. Nullbeleg implementiert um das zu umgehen. In D wäre dafür aber aus meiner Sicht das Daily Closing ideal.

_

pro's

• simplification of recovering from late-signing or failed mode while daily closing
• easy integration, no manual action required to recover from late-signing or failed mode

con's

• longer runtime of call may cause additional timeouts
• concatenated response in happy path will include multiple signatures and multiple similar signature-items
• response in unhappy path will be unclear, is zero-receipt to recover failed or is daily-closing failed is unclear to caller. daily-closing may not execute it's purpose what will lead to multiple concatenated days in DSFinV-K export.

[TSchmiedlechner]

Hi @steininger, thanks a lot for forwarding this, and sorry for the late response. It took some time to carefully consider this suggestion. Also, thanks for listing the pros and cons already 🙂

At this point with several, we'd rather not change the existing behavior of the daily-closing receipt because of the following reasons:

1. The possible duration of daily-closings could become very long in some cases (up to 140 seconds). Many PosCreators have implemented the Middleware in a way where the daily-closing is a manual operation - waiting that long for this receipt is not an option in these cases.
2. If we'd change the daily-closing receipt, we would also have to logically alter at least the other closing receipts as well, which would further complicate the situation.

Summarized, we basically consider this a major change that we'd rather not implement at this point in time. We consider to change this behavior in an upcoming major version though, as it logically would make sense to have each zero receipt behave the same way.

One possible alternative we could offer is to enable the zero-receipt behavior on daily closings only when a specific, to-be-added flag is set. As this would still require a change in your implementation, I'm not sure how helpful this is though - automatically sending a zero receipt before a daily-closing from your POS software might be roughly the same effort, right?