Microsoft Dynamics 365 maintains a log of every change that is made to a record in the application, be it a contact, a sales and purchase transaction, an invoice or bill, a journal, or even a functional setting. In addition, depending on the nature of the change, the solution records the time when the change happened along with the details of the user who performed that change.
In short, the audit trail in Microsoft Dynamics 365 provides details on the 4Ws:
When – The date and time an action/change was performed.
Where – The module/table under which the action was performed. This could be across invoices, bills, bank feeds, expenses, or any other module/table field under the Microsoft Dynamics 365 database.
What – A description of the action/change that was performed, such as creating an invoice, editing line items on the invoice, or updating the contents of a bill.
Who – The user who performed the action/change.
The audit trail in Microsoft Dynamics 365 is essentially a system generated number that cannot be tampered with for any posted transaction. Once posted, a transaction cannot be deleted either. Further, any reversal of previously posted transactions generates a new audit trail for change tracking.
If a record is changed multiple times, the audit trail shows every version that has been created, and not just the most recent one. This allows a user to compare multiple versions and track specific data that has been added, removed, or modified.