Hypersoft process with eSolutions
Foundations for architecture and fiscal security
From Hypersoft's point of view, POS systems are connected to eSolutions systems if they process business transactions together. For example, if a customer orders online and you comply with their change requests at the POS system without sending them back to the online shop, you also confirm this POS link in the practice. Hypersoft therefore treats all eSolutions connections as cash register postings from a fiscal point of view, so that they are also signed in Germany, for example.
Common master data in the POS and eSolutions area
In Hypersoft systems, the master data, and in particular the item master data, is generated and updated centrally. There is no provision for programming a self-order kiosk directly or making price changes, for example, because these are maintained in the central multifunctional item master. We even offer the 3rd Party eSolution API systems so that these can also be integrated correctly from a fiscal point of view3rd Party eSolution fiscal requirements).
One source of master data serves all your distribution channels.
Gaps in the numbering of eSolutions orders
Orders that are cancelled by the user during the payment process are assigned an order number in the eSolutions system. If, for example, you notice that you have gaps in your order numbers when exporting your order, this is due to the payments cancelled by your users for these orders. Cancelled orders are currently not displayed in the order overview in the portal or transferred to the POS. Once orders have been transmitted to the POS system, they can no longer be cancelled and there are no gaps. (Orders that have already been transmitted to the POS system, such as in-house orders or pick-ups without a payment obligation, are reliably saved in the POS system, even if they have not been paid for by the user).
Gaps in the numbering of eSolution orders Further documentation:
The signing of a web voucher sale or sold item takes place at the POS system and therefore the sale of a voucher or item is only signed after collection by the Online Order Connector via the POS system assigned to it. If you are working with manual releases by operators, signing takes place with the release. Communication between the webshop and the POS system usually takes place within 5 minutes.
If an order has not been collected by the POS system after 5 minutes (this also applies to web voucher orders), a notification is sent by e-mail (see also emergency operation), indicating that an order has not been collected by the POS system within 5 minutes. This does not change the status of the order. This means that as soon as the checkout is (subsequently) available, the order is collected, processed and signed.
Connections between eSolutions and emergency operation...
If you decide to use the emergency mode in this context, you have the option of viewing the orders in the portal in order to enter them again manually at the POS. The manual capture is (of course) signed by the TSE. If you now also manually check the box Order transmitted to Pos for these orders in the portal, these bookings will no longer be transmitted to the POS when the connection is possible again. Otherwise, you would have to cancel the subsequent double transmission (not recommended). Decide on the desired procedure and file this in your procedure documentation.
Emergency operation without server fiscal issues Further documentation:
Consolidation and joint evaluations of the transaction data
When the commerce orders from the webshop, the self-order kiosk, from in-house provision or from 3rd parties reach the POS system at the respective location, these are immediately processed fiscally depending on the country: in Germany, for example, the bookings are signed via TSE (the location of the business or the POS system applies, the webshop can also operate outside the location and all bookings are then treated as generated by the location).
A target of the booking data serves the fiscal treatment at the location and furthermore you can have the data merged in a central office.
Hypersoft procedure with SOT Further documentation:
Back to the parent page: Fiscal Law on the Application Decree on Section 146a AO