Description
Cause
- Editing a transaction multiple times can cause the transaction to post incorrectly
- Damaged transactions
- Changing an account on a paid or partially paid vendor invoice
- Changing an account on a paid or partially paid customer invoice
Resolution

- Section 1: Run Data Verification
- Change the accounting period to Period 1; see How do I change the accounting period?.
- Select File, and then Data Verification.
- Select Both Tests, and then Start.
- Save the backup. When the backup completes, the data tests will begin automatically.
- If you get the same error during the Data Verification test, skip to Section II.
- If you do not receive any errors during the Data Verification test, change the accounting period back to the current period.
- Run the General Ledger report. If you still receive the error, proceed to Section II.
Section 2: Run Integrity Check
- Select File, then Backup and make a backup of your company. Put before test in front of the backup name.
- Change accounting period to Period 1.
- Open the Integrity Check by going to Help, Support Utilities, Integrity Check
- Select Continue.
- Check Reindex Files.
- On the Reindex Files List, select Chart and click OK.
- Repeat Steps 2-5 reindexing the following items:
- Customer
- Employee
- Vendor
- Jrnl Header
- Jrnl Rows
- For each test indicated below, repeat Steps 2-3, then select the indicated item and click OK:
- Customer / Journal
- Vendor / Journal
- Employee / Journal
- Chart of Accounts / Journal
Note: During the Data Synchronization tests, it may flag customers, vendors and employees as being corrected; click OK to each message to continue on.
During the Data Synchronization test for Chart of Accounts if it flags bad transactions:- Either write down the Reference number for each indicated entry, or take a screen shot to note which entries are referenced
- Delete each of the indicated problem transactions and re-enter them
- Once the transactions listed have been recreated, re-run all the tests again to verify that the transactions are not flagged again and no further synchronization errors occur
- If the error no longer occurs, it is advisable to create a new backup of the company; see How do I create or make a backup?
- If the error still occurs, restore a backup made prior to the error occurring; refer to How to restore a backup.
Note: If the damaged transaction is in an Inventory account, step 7 should include Line Item, and step 8 should consist of the Inventory/Journal test.
Section 3: Converted data from Intuit QuickBooks
- If you receive the error after converting from QuickBooks, it indicates the data did not convert correctly.
- View the IntuitConversion.log file to see what went wrong. Repair the data in QuickBooks, and then convert the data again.
- See the guide Sage 50 Accounting U.S. Edition Converting from QuickBooks.
Section 4: Consolidated company displays error
- Run Data Verification as outlined in Section I in all subsidiary companies. If the error continues in any subsidiary company, refer to Section II.
- Afterwards, reconsolidate the consolidated company.
- If the problem persists, create a new consolidated company and add one company at a time to see which one is causing the problem.