Enabling the Corrections Audit Trail

Please note that the Corrections feature should only be used if incorrect entries cannot be corrected using standard reversing transactions and the impact of the changes being made is fully understood. Most changes made via Corrections are not reversible.

You will need to be a System Administrator and have all necessary Security Profile permissions to set up the Audit Trail Triggers. Using the Audit Trail may have a significant impact on your system performance.

Please read about using Corrections.

The example used in this document is to set an audit trigger where the Supplier Bank details are changed by a user.

The Corrections Module is primarily used for correcting Records and Transactions. However, it also has the functionality to track any changes made by users in the database legitimately.

Setup

Navigate to: System Control > Data Utilities > Corrections > Audit Trail

In the left-hand pane, highlight the Table on which you want the trigger, and click Insert,

Table Description	Purchase Ledger Accounts
Table Name	PL_Accounts

Complete a Trigger Name; the name cannot contain spaces.
Select the checkboxes that you want to Trigger On.

Trigger Name	SUPP_BANKDETLS
Trigger On	Insert, Update, Delete

In the right-hand Field Description pane, select the checkboxes for the fields that you want to audit with this Trigger.

The Field Description pane contains a Description of each field, which field is the Primary key, which fields the Trigger is executed on, and which fields Show in the table when the trigger is executed. If ticked, the Show checkbox displays the value of the field along with the date and time, and User ID of the person who made the change.

Field Description	Primary	Trigger	Show
BACS bank sort code	n	y	y
BACS bank account no.	n	y	y
Primary Key	y	n	n

Save your Trigger and Close the Audit Trail window.

Making a tracked change

Navigate to: Creditors » Suppliers

Search for and Display a Supplier
Edit the Supplier Record by selecting the Bank tab, and change the Sort Code and the Account No.; Save the record and Close the Supplier record.

Sort Code	11-22-33
Account No.	12341234

Viewing the Corrections Audit Trail

Navigate to Home » [Enquiry] Corrections » Audit Enquiry

You can choose to filter by module and by type of correction (insert, update, delete) and to search for changes made on a specific date or date range and/or by a specific user. When you have selected all relevant filters and entered any search criteria, click Display to view the Corrections changes.

The Corrections Audit Enquiry displays only events defined as a Trigger. These can be events initiated through Corrections and/or Dimensions, however only events in defined Triggers are included. Other Corrections changes can be viewed in the other Enquiries available from this menu: the Record Changes Enquiry displays changes to records made using the Corrections Change Code or Merge Code functionality; the Transaction Changes Enquiry displays changes to transactions including header changes, detail line edits and duplicating and reversing transactions.

A Crystal report is also available that lists the changes made using the Corrections Audit Trail functionality. To access this report, navigate to System » [VAT] ACR

This ACR folder contains all ACR Reports for the System ribbon, not just the VAT reports.

Scroll down and select to Print the Corrections Audit Trail report.

The Corrections Audit Trail prints only events defined as a Trigger. These can be events initiated through Corrections and/or Dimensions, however only events in defined Triggers are printed.

Complete the required parameters and then click OK.

Start of Range	# enter today's date
End of Range	# enter today's date
Select Required Change Type	All Records

Viewing the Corrections Actions Log

Navigate to System » [VAT] ACR

This ACR folder contains all ACR Reports for the System ribbon, not just the VAT reports.

Scroll down and select to Print the Corrections Audit Trail report.

The Corrections Actions Log prints all events made via Corrections, regardless of whether they are defined Triggers or not.

Complete the required parameters and then click OK.

Start of Range	# enter today's date
End of Range	# enter today's date

Using the example we have used in this topic, when you print this report it will be blank because we have not used the Corrections module.

If you had selected Supplier Code as both a Trigger and Show event, and had then used Correct on the Supplier record ribbon, the event would appear on both reports.