-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kassensichv DE: Order receipts optional or mandatory ? #142
Comments
@aedler-ft @TSchmiedlechner do you have some input for the posted question ? |
Hi @texTec, suppose orders, delivery notes, invoices and payments are being processed at different times, and the electronic recording system processes the business action not as a whole but in separate processes. In that case, the business activities and other activities must be traceable in their creation and processing, and a unique identification number for the business action must exist. If an external electronic recording system is processing an order, the rule of KassenSichV applies also to the external POS system, no matter if the payment happens at the external system or on a fiskaltrust-powered electronic recording system. In addition to this, the business activity must be traceable across the different electronic recording systems. This can be achieved using 'ftReceiptCaseData' which helps you to bring the data required by DSFinV-K from an external POS system to the fiskaltrust-powered POS system. It is documented more in detail here: https://docs.fiskaltrust.cloud/docs/poscreators/middleware-doc/germany/dsfinv-k#file-bon_referenzen-referencescsv. You can find an example workflow of how to include data of external POS systems and how to merge it with ongoing business actions in fiskaltrust-powered POS systems, including code examples of the requests, in our Postman Collection as well: I hope I could help, |
Thank you for the answer. I was afraid of that, although my research from other hotel software vendors' documentation gave me the impression that they didn't implement it that way. (Only like the Austrian RKSV where the invoice at departure is signed) Since for many things a receipt is not issued to the guest (overnight stay/breakfast etc) it should be allowed to create these OrderReceipts with the daily night run ? I also assume that these receipts should be created incrementally and not like delta updates (new vesion of the folio) to the fiskaltrust middleware ? Also is it allowed to combine order lines and storno of order lines (units/amount negated) in a single order-receipt, or is it better to group them and issue 2 receipts. (Storno receipt marked as reversal and containing all storno order lines) Thanks for your effort |
Hi @texTec, you can find examples of accommodation workflows in the Postman collection as well: https://middleware-samples.docs.fiskaltrust.cloud/#56db38d8-032e-447c-873f-52b143a1256a. They should reflect exactly the use case of info-orders for overnight stays as you described. Storno receipts need to be separate; it is described in detail here: https://docs.fiskaltrust.cloud/docs/faq/germany#how-is-the-cancellation-of-activities-and-items-to-be-represented-in-the-ipos-br-how-are-receipts-reversed. you're welcome! |
Thank you for the help. |
at any time; I am happy if I could help! |
Are order receipts in case of long-lasting business cases (e.g hotel-stay) mandatory, or would it be enough to sign the final invoice on departure.
If mandatory, how to deal with services transfered from third party systems (e.g POS-system in restaurant-sector) ? Is it necessary to create order receipt's for them also ?
The text was updated successfully, but these errors were encountered: