Application detail

What each function does

1. 1Reference number as the title The same reference the agent quotes on the phone and the tracking page. Why: staff should never have to translate between an internal database id and what the customer is saying.
2. 2Status pipeline The full sequence, showing where this job sits. Why visible rather than a dropdown: a new staff member can see what comes next without being trained, and everyone uses the same words for the same state.
3. 3Declared data, marked read only Exactly what the agent submitted, never edited in place. Corrections are recorded separately as an override. Why: if staff can silently edit the original, there is no evidence for a disputed top up and no way to audit a duty change.
4. 4Document vault Files served through the application with an expiring link, never a public URL, with the virus scan result shown. Why: a guessable upload path holding tenancy agreements and identity documents is the single most likely way this platform ends up in the news.
5. 5Personal data marker Flags files containing MyKad or passport scans, and every open is logged. Why: these are exactly the documents a PDPA obligation attaches to, and the retention policy has to apply to them specifically.
6. 6Upload the stamped certificate Where the result from LHDN comes back in. Uploading it is what allows the job to be completed and released. Why it is a required document, not an optional one: it is the thing the agent actually paid for.
7. 7Duty breakdown with the working shown Every component itemised, with the block calculation and the penalty reasoning printed underneath. Why: staff answer "why is it RM241?" several times a day, and the answer needs to be on screen rather than in someone's head.
8. 8Correct the duty Opens the comparison screen where verified figures are entered against declared ones. Why it is a deliberate action: changing the amount owed after payment is a significant event and should never be a casual inline edit. See Screen 03.
9. 9Audit trail including document access Who did what and when, including who opened which identity document. Why access and not just changes: for personal data, knowing who looked is as important as knowing who edited.
10. 10Actions, one obvious next step The primary action is the normal path; the rest are exceptions. Why: nine times in ten the job is fine and the staff member should be one click from done. The exceptions should be available but never compete for attention.