Skip to main content

Troubleshooting and Tips

Practical solutions and advice for avoiding common issues when integrating the DSFinV‑K.

Allocation Groups

In restaurant scenarios, it is expected to use both receipt and order transactions. To connect the individual processes, use e.g. table number and, where appropriate, other additional criteria in the transactions[].head[].allocation_groups array as outlined in the DSFinV‑K documentation provided by the Bundeszentralamt für Steuern (BZSt).

AVBelegstorno Process Type

The DSFinV‑K documentation provided by the Bundeszentralamt für Steuern (BZSt) refers to the process type (receipt type) AVBelegstorno (other processes – cancel receipt), which is also available in the SIGN DE as transaction_type 'ANNULATION' (= AVBelegstorno). However, this process type should not be used for systems connected to a TSS.

BON_ID vs. BON_NR

In the DSFinV‑K, transactions[].head.transaction_export_id, corresponding to 'BON_ID' of the DSFinV‑K official documentation provided by the Bundeszentralamt für Steuern (BZSt), and transactions[].head.number, corresponding to 'BON_NR' of the official DSFinV‑K documentation, are used. Neither the tx_id nor the number from SIGN DE should be used for these fields as they do not match the requirements described in the documentation.

Business Date and Export Creation Date

When creating a Cash Point Closing, you need to specify the export_creation_date - the day on which the closing is created. The business_date is not mandatory: it should be used if the day on which you are creating the Cash Point Closing and the day for which it is meant for are not the same. An example would be creating a Cash Point Closing on a Tuesday, but with transactions that happened on the previous day, Monday. In that case, you should put Monday as the business_day, while Tuesday would be the export_creation_date.

Empty Exports

Some Windows users may encounter an issue where export files appear empty after unpacking. To resolve this, we recommend using a ZIP file extractor such as 7-Zip, WinRAR, or PeaZip.

Handhelds/Terminals

When using handhelds/terminals/slaves (see Master-Terminal Relationship in Cash Registers), it must be recorded from which specific device every line was sent to the master Cash Register. This information should be indicated using the field transactions[].data[].lines[].source_cash_register.

Retroactive Cancellations

When dealing with retroactive cancellations, you need to add a reference to the initial transaction in the Cash Point Closing, see transactions[].head.references. In order to do so, different schemas can be used. If the initial transaction was signed with the fiskaly SIGN DE the type "InterneTransaktion", ReferenceInternalTransaction, can be used.

Computer monitors with fiskaly newsletter subscription page on them

Stay up to date

Subscribe to our dev newsletter and be the first to learn about new updates, features, products and news!

*By submitting the form, I consent to fiskaly processing my information in accordance with the fiskaly Privacy Policy.Privacy Policy