Merchants can run the end-of-day process for transactions made through the POS device or POS application by triggering it from the device or the application itself. Banks can also run the end-of-day process centrally on behalf of merchants.
When the end-of-day process is started, the total amounts of the transactions on the POS are sent to the bank's HOST system. If, during this process, there is a mismatch between the amounts and counts on the POS and the amounts and counts on the HOST, this is called the end-of-day falling into batch upload.
Note: In terms of message type, this can be summarized as the amounts and counts sent by the POS in the 500 message not matching the amounts and counts in the HOST's 510 message.
What happens when it falls into batch upload?
When a discrepancy is detected, the POS starts sending transactions to the HOST one by one instead of as a batch total. The HOST compares these records against its own records and processes the missing ones.
Once the process is complete, the amount reflected in the merchant's account matches the POS total. Because this process can take a while, leaving the end-of-day run until late at night can be risky.
If there is a connection problem or the device shuts down, merchants should run the end-of-day process again; if the mismatch recurs, they should contact the support line.