You can use this routine to correct details of selected transactions. The system will highlight missing or incorrect information and then proceed to give display an error message that tells you what to enter or change. You can then verify all of the entries or changes through the system as you do when entering manual transactions.
Note: You cannot add or delete transactions in this routine.
You can correct the error by entering missing information or changing faulty information. However, you may in some cases, i.e., calculation and redistribution, have to make corrections to the postings through the tables and files within the system.
If you have an error that is detected in a transferred journal, it will be suspended and an error report is printed. Errors can be viewed and corrected through the journal maintenance panel and the G/L update cycle recommences. G/L journals that are fed through the external interface are:
- checked that they are complete (if the pre-system is unable to create the full account code, then the system will enable you to use an account completion table to add the missing account parts),
- validated, as are all the account postings, through interface routines ensuring they are correct before the actual G/L update is allowed to commence,
- stored in a temporary file and an error report is printed giving details of the incorrect postings, (if you have any errors),
- accessed through the panel, where you can make the necessary corrections.
When your errors are corrected, the G/L update can be completed.
If errors are still detected, you can “force the G/L update”. This will result in the erroneous journal balances being posted to an error suspense account with an error report. These errors must be corrected by manual journal adjustment.
Transactions that lack important data, such as voucher number, voucher type and currency code, will never be updated to the General Ledger. However, under two circumstances the errors can be corrected afterwards within the General Ledger, through a forced update. These are when the transaction contains a missing or incorrect account string and when a voucher is unbalanced.
Note: A forced update is only allowed for G/L journals and A/R payments since you cannot correct control accounts.