Void Transaction Support Tool - Void transaction thru Back Office

Status For Deployment - 19-Aug 2025
Objective Allows the Support Team (using Super Admin user access) to Void Transaction on the Back Office so that we can fix "voided but still appears on DSR" issue especially for past POS dates
Pain Point Voided transactions that still appear on Daily Sales Revenue causes incorrect declaration of sales
Audience All Clients
User Access Super Admin only
Old State New State
Dev has to update the transaction status to void unsynced voided transaction

Using the new Support Tool, we can void transactions so that it won't appear on Daily Sales Revenue Report anymore

How to Use
  1. Log in on Back Office using any Super Admin user access
  2. Go to Support Tool
  3. Click "Void Transaction"
  4. Select the Location and POS Date
  5. Encode the Bill Number of the transaction
  6. Click "Filter" button
    1. Expected: The transaction will show up on the table view
  7. Click "Mark as Voided"
  8. Upload an attachment on the pop up - any supporting document that proves the request for tracking purposes
    1. Note: It only accepts images (.jpg, .jpeg, .png) and up to 5mb file size
  9. Once "Proceed" is click, it will upload the file and mark the transaction as voided
    1. Note: Attachments are saved on S3 and can be requested to Engineering team if needed

The image below shows transactions on the Daily Sales Revenue:

The image below shows a sample transaction that we will void (BN 534):

The image below shows that BN 534 is no longer on Daily Sales Revenue:

The image below shows that BN 534 is now on the Void Report:

Validation and Error Messages Solution

Attachment Size Limit of 5mb

Upload image files with less than 5mb file size

Future Development Target Timeline

(Proper Fix) The investigation on the root cause of unsynced Void transactions is still on the roadmap. We need to fix it to avoid this kind of fixing in the first place.



Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us