Process description Hypersoft POS

The procedure description enables the auditor to credibly understand the use and methods in the application of your accounting system. The essential point here is your own procedural documentation for the processes within your company. Since we do not know these, we have first set up a few questions for you, which you can use to better create your specific procedural documentation. You will also get an impression from these which topics you document additionally and which questions are inappropriate with them. Afterwards, we write our technical procedure documentation so that you are also well secured in this point. If required, we or some of the specialist trade partners qualified for this can also support you with the overall task.

 

Go through these points for your business and add to them if necessary :

See the entire section under Fiscal Law on the Application Decree on Section 146a AO

Note on procedural documentation Facilitation rule

Hypersoft uses the Facilitation regulation for through service

Note on procedural documentation TSE Error Report

Hypersoft can have multiple electronic recording systems (eAs) signed via one or more TSEs located in the network. This makes it possible that one or more eAs cannot reach a TSE and goes into error status, while other eAs may still be able to address the TSE and have their bookings signed. Thus, TSE failures can also be displayed in the TSE Error Report for some units while other units continue to use the TSE.

Technical means

  • Do they use a TSE or an Austrian Security Device?
  • Integrated cashless payment system?
  • How do you back up your data?
  • Change logs?

operator accounting

  • Change?
  • Change?
  • Tip?
  • Cashless receipts?
  • Vouchers?

Working with fixed price level or loss...

When using fixed price levels or losses to a key or similar, it may not be possible to see later which operator (or manager) actually used it (if it was named as an invitation key, for example). You should be able to describe who has used these opportunities. This can easily be done by, for example, giving each individual manager who uses this technique their own second key with these properties and then naming it accordingly.

fraud

  • Controlling?
  • Use of goods?
  • Are cancellation checks carried out?
  • Booking entry ensured?
  • Separation of goods and money (mobile devices, order voucher etc.)?
  • Customer display (quick service)?
  • Delivery of documents?
  • End of day?

Hypersoft technical procedure documentation

When the first booking is made after a daily closing, the time from the POS system is set in the TSE (notes, therefore the first booking takes slightly longer). This is the standard procedure as it is mandatory and the clock in the TSE is too inaccurate).

TSE use and treatment at Hypersoft

TSE sticks are checked in by Hypersoft to the respective location (client) and displayed in the Hypersoft Portal together with the other devices. When the TSE is activated at the site, the information about the start of the TSE stick's lifetime is traceably transferred to the portal. A conceivable, possibly situation-related recurring use of further TSE sticks is thus prevented. In this way, the Cash Security Ordinance is more secure.

  • Immediate cancellation (obsolete term, see Cancellation before order)
  • Zero positions generate a TSE signature.
  • Cancellations before order generate TSE signatures (like all cancellations and returns).
  • Bill of exchange deposits and withdrawals generate TSE signatures.
  • Modify payment type generate TSE signatures.
  • TSE Online Archive - See the procedure documentation there: Procedure documentation TSE Online Archive

TSE Allocations and multiple use...

With Hypersoft, several TSEs can be operated in parallel. This can result in a transaction being signed by several TSEs, depending on the booking system. For example, the bookings on TSE A and the payment of these on TSE B.

Further documentation: TSE Multiple use

Hypersoft POS

  • Each booking made at the cash desk is signed with a new balance in the TSE (Process Type: Order). It is noted in the transaction that the entries have been signed. If the sales price of the item changes, for example due to loss, change of price level, applied discount, etc., a "minus signature" with the original price and a plus signature with the new price is made on the next new balance. The following data is shown in this signature.

ORDER...

  • quantity
  • Description of the goods or services
  • Price per unit
  • When an invoice is created or a transaction is completed, the transaction is signed in the TSE (Process Type: Cash Receipt). The following data is shown in this signature.

Transaction type - (cash voucher)

Gross turnover per tax rate

Payment amount per payment type (CASH, UNCASH)

  • The signature consists of 2 objects. (QR code) of the signing and (text) of the signing. These can be switched on and off on the invoice via a switch (currently only QR code).

For DIN-A4 invoices there are 5 new variables that can be used in List&Label with the Layouter.

  • DESignature.QRCODE (QR code from the TSE Signature Unit)
  • DESignature.Comment1 (lines are separated with "|" or "NeueZeile")
  • DESignature.Comment2 (lines are separated with "-" (block text in one piece)
  • DESignature.TimeFirstBooking (Date/Time first booking)
  • DESignature.TimeLastBooking (Date/Time last booking)
  • Special case at the checkout:

If a transaction is opened at the cash register that has already been signed with a cash voucher, the signing is cancelled by an offsetting entry and re-signed when the transaction is closed again. This is to catch situations when, for example, processes cannot be processed and are thus identified as errors by the business logic. Businesslogic takes over the executed signature from the cash register and transfers it to the x_ADDON table. For each TransactionID in the x_Trasaction there is also a record in the x_ADDON table with the signature.

Webshop 2.0 connections

See the Procedure documentation for bookings between web shop and POS

BZV connection for card devices

Tip at the payment terminal...

If a tip is given subsequently at a connected payment terminal, the following is carried out when this transaction is completed:

The document signature is re-signed with a counter entry (all times -1).

The subsequently paid tip is signed as type ORDER.

A new voucher signature is created.

Example:

Beleg^38.00_0.00_0.00_0.00_6.00^19.00:Bar_25.00:Unbar

Beleg^-38.00_0.00_0.00_0.00_-6.00^-19.00:Bar_-25.00:Unbar

1; "Tip BZV";6.00

Beleg^38.00_0.00_0.00_0.00_12.00^19.00:Bar_31.00:Unbar

Cashless Top-Up Terminal

Cashless Top-Up Terminal - The charging of the cards is signed with TSE. As usual, the system indicates whether TSE is set up or not.

eCommerce interface

Our eCommerce connection supports compliant working with the TSE.

We cannot make any statements about the security of the bookings on the 3rd party side. Integrate such connections into your procedure description and obtain further assurances from the providers if required. In this context, please also read TSE with eCommerce and 3rd Party Integrations.

BANKETTprofi Connection

See the notes at BANKETTprofi Interface.

zero position

If you are in Germany, the Hypersoft procedure for zeroing must be used. To document the function, an entry is created in the TSE at the zero position (Process Type: "Other process). Zeroing only works on stations that are assigned to a TSE. The selected reason from the list and the typed text under Description are saved.

change

Change is signed when using Wallet-Control. Alternatively, deposits and withdrawals can also be used for change - but not both together in mixed operation for the same wallet.

If a wallet or cash drawer has not yet been closed by Wallet-Control at the time of the cash register closing, the signed change contained in it is signed as change withdrawal via the TSE and the wallet or cash drawer is closed with a separate status (2).

Modify payment type

  • Change payment method:

With the function Modify payment type the original transaction type cash voucher is provided with an offsetting entry and re-signed with the new payment type.

  • Edit operation:

With the function Edit Transaction, the entire transaction in the TSE is provided with an offsetting entry. Both the bookings and the receipt for them. At the new closing, the entries and the voucher are signed again.


Current limit 31.03.2020 with TSE activation:

  • The TSE compatible update cannot make training bookings in Germany with TSE set up.
  • The use of batch jobs to adjust the "Win.ini" is a hack and is not compatible with TSE use. Solve the requirement with the virtual checkout functions (which will be extended shortly). The previous use remains retroactively GoBD compliant, but cannot be used with the TSE.
  • Ward numbers are intended for one-time set-up. In rare cases, customers change station numbers. This is not TSE compliant. Resolve the request with the virtual checkout functions. The previous use remains retroactively GoBD compliant, but cannot be used with the TSE.
  • The cash register function Apply Level Net Price must not be used with the TSE. If you have used this in Germany, remove this function from the POS system.
  • Also no interventions are possible in the booking journal with TSE, this would lead to errors. If you still need functions to correct the payment methods or similar handling errors, please ask the support. Write a note for your procedure description or bookkeeping if someone has caused you to make false entries.
  • No completed support for the Comestero vending system yet.

Back to the parent page: Fiscal law in Germany