If you are referring to posting adjustments against AP transactions, or journal entries in AL, then both of these types of changes are written to a posting journal file which can be kept for the audit trail. Neither of these functions attach a 'user name' along with the entries.

If you are referring to editing Account History in Ledger, then there is no audit trail.

All Adagio applications (versions 6.8A and later) have security by user group and function, so if your concern is to prevent certain users from performing functions that will adversely affect the data, then you can set up security to do just that.

Regards,

It appears that you are seeking some kind of "database change" log for the Adagio accounting database. Adagio does not keep such a log, but there is a reason for this.

Accounting databases are subject to such continuous change and update, that simply recording every single change made to the data results in enormous log files. These files consume large amount of disk and computer resources to maintain, and are often of limited use in actually tracking down a problem, because they are so mindlessly recorded. For example, ACCPAC for Windows keep track of the last user to change a record. However, when Dayend is run in Order Entry, every Order that is affected by the dayend is marked as having been changed by the individual that performed the dayend function. Thus, you cannot actually tell who was the last operator to change a specfic order or invoice.