User Audit Trail? - AR82.1 - Returned Payment

In evaluating the results of AR82.1 - Returned Payment - I am not seeing anything relating to a user/login audit trail on the resulting Debit Memo??

It would appear that Lawson is ignoring/breaking some of it's own data architecture rules in creating these results:
- does not enforce/write a Debit Memo Reason Code (even though this is a required value for any debit memos being entered into AR)
- does not write a corresponding TX Batch occurrence (BLINVHDR) - even though the Debit Memo is given a batch number (some incremental "dummy" value)

It is the TX Batch occurrence (BLINVHDR) that has an OPR-CODE (Operator Code) attribute - which would be the appropriate audit trail attribute - but since no TX batch occurrence is physically being written in the returned payment scenarios.......

Has anyone else tripped over this in thier travels - or perhaps has some words of wisdom I.E. am I missing something? Any feedback would be appreciated.