In POS applications and on the merchant side, we use the term "Batch" in a similar way to end of day. Every transaction made via POS is kept under a batch number (end-of-day number).
Transactions made via POS are reported to the HOST with the relevant batch number when the end of day is taken on the POS.
In other words, the POS reports the transactions it holds to the HOST and generates a new batch number internally, starting newly created transactions under this new batch number.
So, what does batch delete mean?
Batch delete refers to the situation where the transactions on a POS device cannot be reported to the HOST due to a POS malfunction or other reasons, and the batch found in the application is deleted.
If a batch has been deleted for any reason, this situation must definitely be reported to the merchant's bank, with a request to manually close the end of day. Otherwise, customer complaints will arise over amounts that do not get credited to the merchant's accounts because of the batch that could not be closed on the HOST side.
The other important point is that your offline transactions have been reported to the HOST. If offline transactions were not reported to the HOST due to a malfunction or other reasons, it will be very difficult for you to retrieve that transaction.
(There are of course certain processes available for recreating the record of these transactions. However, an extra process and effort will need to be expended.)
You can refer to this article for information on how offline transactions are reported to the HOST: What are offline transaction parameters? Can examples be given of how offline transactions are reported to the HOST? - Arif UNAL (arifunal.com).
