Automate close

Automating day-end closing as supported by Hypersoft can solve several problems. It should be the standard for almost every business.

Best practice: Automate daily closing - control instead of headaches

What happens if nobody locks the door?

A forgotten daily closing is no small matter, but a frequent practical problem with real consequences:

  • The early shift accidentally books to the previous day

  • Reports are not sent or are sent incorrectly

  • Stock and loss analyses do not fit

  • Sales reports and invoices missing

  • Owners or senior employees have to wait to "finalise quickly"

  • In the worst case scenario, an important document is missing for further processing or revision - or there is unnecessary stress the following day.

✅ The solution: Automatic daily closing with intelligent transaction handling

The automated closing logic supported by Hypersoft ensures security and flexibility - even if no one on site performs the closing manually.

The process consists of two components:

  • A timer that controls the time of automatic completion

  • Intelligent automatisms that handle open processes based on rules

What is done automatically?

Hypersoft makes it possible to individually define what happens during automatic completion for each transaction type:

Process / special case

Automatic behaviour possible
Open table processes

E.g. automatic conclusion as cash payment
Unbilled personnel transactions Blocking of further personnel bookings until clarification
Unpaid online orders (eSolutions) Transfer to customer account or special reason for loss
Transactions without a contract, but with a receipt Finalisation with internal note or printout
Empty day (no booking) Z-termination number remains, no meter loss*

*This mechanism also allows re-securing in the event that manual locking is forgotten.

Advantages at a glance

  • No more waiting for responsible persons

  • No risk due to incorrect subsequent bookings

  • Smooth report delivery (e.g. for franchise or controlling)

  • Correct loss and cost of goods sold reports

  • Reassuring relapse protection during stressful shift changes

⚙️ Technical note: What happens with "zero booking"

If the daily closing is carried out automatically - e.g. in the morning because it was closed manually the previous evening - a report with €0 turnover is generated, but the Z-closing number remains untouched.

➡️ Only the next daily closing with actual bookings receives a new Z number. In this way, the counter remains fiscally correct and seamless.

Conclusion

Manual completion is important - automatic completion saves the day if it has been forgotten.

Automate your daily closing with Hypersoft - and gain security, time and an overview. Your data is correct, even if nobody thinks about locking up.

Use automatic transaction completion for eSolutions...

  • For open Online Order procedures, the line Customers / Online Order is available.
  • Unpaid SOT operations are to be set up like table operations.

Further topics:

Best practice: Automatic report export and dispatch

Orphaned Webshop Operations

Orphaned SOT operations

Operation settings for completion

From the program group POS Settings start the program Automate daily closing. The dialogue Automatic terminationappears, if no station is switched to Active, you can call up the program Procedure settings for termination with the button Settings . The settings stored here are automatically executed at the end of the day:

These settings are only used for open transactions to which a payment type has been assigned here. As long as the payment type Leave open is entered, the open transactions in question are not processed.

Element / Switch Function / Description
Transaction type column The Operation type column contains a line so that you can set the behavior of the program individually for each operation type (for which operations are open).
Form column Forward If you want to print a form for the process that is still open, select it here.
Column Level / Loss An open transaction can be automatically transferred to another price level or to a loss reason.
Form column By This column enables you to create another document after reposting to a different price level or a reason for loss. For example, to document the current value of the transaction after the reposting.
Payment type column

The Payment Type column determines whether the transaction is to be completed or not.

For example: Accidentally uncompleted transactions can be concluded in the main currency, open payments from hotel guests to rooms.
Block customer account

If customer transactions are open at day-end closing and are rebooked via a payment method, you can hereby determine that these accounts are additionally blocked.

Locked customer accounts can be unlocked by the manager by opening them or you can remove the lock in the customer master.
Block card

This function blocks cards that were previously entered in the whitelist.

This function blocks cards in systems that use cards that have been approved in the whitelist. Without the whitelist check being activated, this lock is of no use.

To unlock the card, a manager must read the card or re-initialize (reassign) the card.
Locking employees

Locks employees for posting to their own personnel transactions if their transactions are still open at day-end closing and their transactions are transferred using an automatic payment type.

Locked employee accounts can be unlocked by opening them from the manager or by removing the information from Employee is locked Employee Master.
Exit button Press Exit to save your settings.

Further topics:

Multi-Object transaction

Automatic daily closing with open group operations

Back to the overarching topic: Daily closing procedures and options