Use the Corrections module to fix incorrect transaction postings or to change or merge records — for example, if a supplier has been created twice. This article covers:
Correcting a transaction
Correcting a record
Merging a record
📌 Note (versions 2.50G and earlier): Click the Plug-ins tab in the Dimensions ribbon, then click Corrections Menu > Correct.
Correcting a transaction
You can change almost any piece of information on a posted transaction, depending on your security profile settings. The process is the same regardless of ledger. The example below uses a Purchase Ledger invoice.
Using the Enquiry window, locate the transaction to correct.
Open Correct from the Corrections menu. The Corrections module opens.
To edit any of the header information, click the Edit button on the ‘Header’ tab.
Fields with a white background can be edited. Greyed-out fields cannot.
Make the required changes.
Click Save.
To change detail lines, click the Detail tab.
Click the line to correct, then click Edit at the bottom of the window. A new window opens.
Fields with a white background can be edited. Greyed-out fields cannot.
Make the required changes and click Save.
Repeat from step 8 for each line that requires correction.
Once all changes are complete, close the Correction window.
Correcting a record
Use this to change a record's code — for example, when a supplier has changed their name and the existing code no longer fits.
In the Supplier Records window, locate the record to change.
Open Correct from the Corrections menu. A new window opens.
Enter the new supplier code in the New Code field.
Merging a record
Use this to merge a duplicate record into the correct one.
In the Supplier Records window, locate the duplicate record.
Open Correct from the Corrections menu. A new window opens.
From the Action drop-down, select Merge. A new window opens.
Enter the target code in the Merge code field, or use the Search window to find it.
Once the code is entered, click the green tick. A confirm merge window appears.
Click Yes to merge.
Several working messages will be displayed until the final one saying ‘Update Complete’ shows
Click OK. The Supplier list refreshes with the change applied.
Enable reason prompts in the Corrections module
You can require users to enter a reason when making corrections. Log in with a user who has access to the Data Utilities menu. Ribbon menu:
On the System tab, click Data Utilities.
Click Corrections > System Settings > Audit Trail.
Tick Prompt for reason when making corrections.
Optionally tick Reason mandatory to require a reason before any correction can be saved.
Click Save.
Classic/module menu:
Click System Control > Data Utilities > Corrections.
Click System Settings.
Tick Prompt for reason when making corrections.
Optionally tick Reason mandatory.
Click Save. Users are now prompted to provide a reason when making corrections.
To include the reason in the Corrections audit trail report: Ribbon menu:
On the System tab, click Data Utilities.
Click Corrections > System Settings > Audit Trail.
Continue from step 3 in the classic/module menu steps below.
Classic/module menu:
Click System Control > Data Utilities > Corrections.
Click System Settings > Audit Trail.
In the audit trail window, tick Show All Tables. Click Yes.
Click the Table Name column heading to sort alphabetically.
Find and click ARM_CM_AUDIT_TRAIL.
Click Insert.
Enter a name for the new audit trigger.
Tick Trigger and Show for Reason for change. Add further triggers as needed.
Click Save. The audit trail report now shows the reason for any corrections made after this trigger was created.