At least one damaged transaction has been found in account [Account ID] in the period beginning

This Sage 50 error message notifies you that there are damaged transactions.

  • If the beginning period is within the current 2 open years, Data Verification should fix it.
  • If the period is outside of your open 2 years your data will have to be repaired using our Sage 50 Data Repair Service. This is because Sages 50 Data Verification option only works the 2 open years of data.

You will receive the error message while running a General Ledger report. The error may not appear until you select a range of periods to report.  If you run your report by Date Range it will not show you any errors.

Running Sage 50 Data Verification

  1. From the top menu select File and then Data Verification.
  2. Select Both Tests, and then click Start.
  3. Enter a New Backup File Name. Never overwrite an existing backup file.  Always name your backup file to something that is useful and unique. If you run Data Verification multiple times always give the backup file name a different name. Data Verification will start automatically after the backup has completed.
  4. After the process has finished run a General Ledger report (with a large period range) to see if you still receive the error.

If you still receive the error you will need to submit your data for our Data Recovery Service.

Related Articles

Sage 50 you cannot save these changes

Sage 50 you cannot save these changes

This error may be many different issues. Make sure you are not trying to edit an archived company. You can tell this by looking at the Sage 50 program title bar. Make sure it does not say Archived (company name), you cannot edit an archived company. If you are not...

Unable to determine security privileges Sage 50/Peachtree

Sage 50 and Peachtree Accounting Software - Unable to determine security privileges. Please retry later. This is probably due to another user temporarily blocking access to critical files.This error is caused by damaged .dat files.  It has nothing to do with User...