Edit Transactions

Process correction with log copy

Once a transaction has been completed (e.g. with the creation of an invoice), it can be reprocessed as required using authorised cash register functions. The original process is never changed, but copied for editing. All changes (cancellations, additional bookings) are logged in full, and a cancellation document with reference to the original is automatically generated for invoices.

Further topics: Authorised transaction correction with log copy

Two cash register functions with different interfaces but comparable authorisation control are available for processing completed transactions:

Both variants use the same user authorisations.

For the new version, there are also individually labelled cash register functions whose documentation can be found directly on the respective function pages:

Note: In all cases, the original process is not changed, but copied for editing. Changes are fully logged and a cancellation document is automatically generated for invoices with a reference to the original.

Use of the dialogue

A list of all completed processes is displayed with Edit processes (conventional).

From here, authorised users can:

  • reopen an operation for operation correction,

  • change or modify the payment method,

  • create a copy of the receipt.

The scope of access can be individually controlled via the user authorisations.

The original process always remains archived unchanged. Changes are only made to a copy, which is logged with all relevant time stamps, user IDs and change types.

Further functions for the subsequent processing of transactions

In addition to the main Edit transactions function, the Hypersoft system also offers other cash register functions for specific post-processing. Some of these may be located in other programme areas:

cash function details Documentation of handling
Modify payment type Targeted correction of payment types, also possible after daily closing (with separate authorisation). Modify payment type

Tipping retrospectively

Editing within the scope of the standard functions. Edit Transactions
Edit operations new Modernised version with reduced interface. Edit operations new

Tipping retrospectively

Entry or adjustment of tip amounts after transaction completion Book a tip

All of the above functions are audit-proof: the original process remains unchanged, changes are only made to a created copy with complete logging.

(Another option is to only provisionally finalise processes in order to clarify certain points - such as the final payment method when guests ask for the invoice - before finalising them)

In the standard setting, transactions can only be processed up to the end of the day.

The newer cash register function Modify payment methods is available for specific adjustments. This allows only the payment type of a transaction to be changed without affecting the rest of the transaction. This is necessary, for example, if it transpires after completion that a different payment method was used than originally booked.

Impact of the changes on Activities Campaigns and Check...

In the Hypersoft system, there are services that are billed on a time-dependent basis, such as digital invoices with NoCOO or web vouchers.

When a transaction is corrected, existing invoices - and any voucher sales they contain - are automatically cancelled and recreated and posted when the transaction is closed again.

This ensures that the billing remains complete and correct even after a correction.

As part of this process, new campaign and check sales are generated, including those for cancellations and new bookings. This ensures that all processes are stored in the system in a verifiable and traceable manner.

Further topics:

Old Campaigns & Activities in the UX licence model

Hypersoft procedure for vouchers

Hypersoft procedure for cancellations

Differences Between the Change Payment Type and Modify Payment Type Functions

Modify payment type is another cash register function.

Differences between change payment method and modify payment method.

The cash register function Change payment type allows you to change the payment type of a transaction within the current business day.

If a cashless payment method is selected, the system automatically triggers the payment process at a connected payment terminal.

This function is only available until the end of the day.

The cash register function Modify payment type is intended for subsequent corrections, e.g. in the case of incorrect payment type postings.

Even if a cashless payment method is selected, no terminal contact is triggered here, as a pure booking correction is assumed.

With the appropriate system settings and authorisations, this function can also be used after the end of the day.

Restrictions: Multi-payments and foreign currencies cannot be modified.

Note the setting: Transfer item to cashier operator

Process" transactions after the end of the day

Completed transactions can be subsequently corrected within one opening day.

In order to process transactions from previous business days, the global setting "Process transactions after daily closing" must be activated and the corresponding user authorisation must be available.

It is called up via the cash register function Edit transactions, which also includes other functions such as changing payment types or printing receipts.

In the case of a correction from a previous billing period, the following occurs:

Copy of the original process is transferred to the current opening day - the original process remains archived unchanged.

Negative postings from the original transaction are automatically written to the journal in order to neutralise the original posting in the current day's context.

When the process is completed again, the updated postings are written to the journal with a positive number.

Without changes, the transaction copy remains revenue-neutral. Any changes - whether cancellations or additional bookings - only affect the current opening day.

This procedure ensures that the original data remains unchanged, that all corrections are fully logged and that transaction processing is GoBD and DSFinV-K compliant.

Notes on using the process correction

The process correction is a controlled procedure with complete logging.

If used properly, the inventory and turnover remain neutral, provided that no changes (e.g. cancellations or additional bookings) are made.

Changes only affect the current opening day and can be tracked at any time.

Recommendation:

Only correct transactions that you or authorised colleagues have booked.

Make sure that all generated receipts (especially cancellation receipts for invoices) are filed together with the original receipts.

These notes serve to avoid misunderstandings and ensure transparent accounting.

Note on additional information that cannot be restored

When a transaction is corrected, all billing-relevant data is transferred in full and logged.

Certain additional information that is not saved permanently when the original contract is concluded - e.g. seat numbers or the allocation of several guests/rooms at one table - cannot be automatically restored when the contract is reopened.

Recommendation: If such additional information is relevant for your company, record or document it separately before correcting the process.

Further topics:

Authorised transaction correction with log copy

Process" transactions after the end of the day

Edit Transactions

Change operations with client name and address

Please refer to the separate chapter Edit addresses subsequently.

Further topics:

Edit addresses subsequently

Edit Transactions

Back to the overarching topic: Hypersoft POS Cashier Mode