Evidence that survives a Malaysian payment cycle
A screenshot of a settings page rarely helps. The evidence that holds up is tied to a named run, a named user, and a named freeze.
Files we inherit are often full of policy excerpts and a screenshot of a “dual control enabled” toggle. That material shows intent. It does not show that the control operated on the Thursday the settlement file was released.
For a Malaysian acquiring or e-money cycle, useful evidence usually looks like this: the change ticket that promoted a fee rule, the access listing as at freeze, the job log for the batch, the hash or control total of the file the acquirer consumed, the approval record for any refund above threshold, and the lock timestamp on the released file. If any of those artefacts rotate out after thirty days, the engagement letter should say so before fieldwork starts.
Retention rules sometimes limit how long logs are kept. That is a practical constraint, not a reason to skip the test. We document the gap and test what remains. Pretending a missing log was “not applicable” is how findings reappear in the next review.
If you are preparing for us, export the run artefacts while the cycle is still open. Waiting until the examiner arrives is how evidence disappears.