Considerations for using Change Entries in General Ledger

Important information about using Change Entries to correct General Ledger transactions in Sage 300 CRE.

 CAUTION: Sage doesn't recommend using Change Entries in General Ledger to correct transactions. 

Issues potentially caused by using Change Entries

Out of balance issues

• General Ledger out of balance with interfacing applications
• Out of balance Current Ledger, Year-to-date Ledger, Trial Balance, or Balance Sheet

Limited audit trail

General Ledger Change Entries doesn't provide an audit trail of the original transaction and what you changed. This makes any error correction problematic. The only audit trail exists on the Change Entries journal that prints.

Transactions not retained

If you delete a transaction in Change Entries, the transaction no longer exists in the system. You can't report on the original entry or any changes you've made.

Recommended workflow

• Make corrections in the Application of Origin if the transactions didn't originate in General Ledger
• Use Tasks, Record Entries to enter reversing and correcting entries if the transactions originated in General Ledger

 

 

How do I edit transactions created outside of General Ledger?

How do I change, delete or void a General Ledger transaction?