How To Repair Sage 50 GL Account Type

Steps in Sage 50 – Repairing an inappropriately changed GL Account type

Backup prior to beginning any repair process for Sage 50. Reach out for promotional pricing on upgrades and support!

 

Repairing Sage 50 – This is to repair Sage 50 problems caused by changing a GL account type from an account the rolls into retained earnings to on the doesn’t or vice-versa, when the account has historical data in closed years.

 

If there is not a lot of historical transaction data, an attempt can be made to re-calculate the accumulators that are used in reporting for the GL and financial statements.

 

Steps when Repairing an inappropriately changed GL Account type in Sage 50

 

Step 1. Print samples of the incorrect reports.

Step 2. Backup your Sage 50 company data files

Step 3. Change to fiscal period 1 (FP1) this provides special properties to utility we will run to change things in prior periods.

Step 4. Go to Help-Support Utilities->Integrity Check.

 

Repairing Sage 50 general ledger Sage 50 Data Base Repair Utility sage 50 database maintenance

 

Step 5. In the Data Synchronization Section run the Chart of Accounts / Journal test

 

Sage 50 Data Integrity Check Repairing Sage 50 general ledger Sage 50 Error Messages Sage error messages sage error codes sage support sage database utility peachtree data recovery

 

Sage 50 multiple Accounts

Note the if multiple accounts have issue’s this test may need to be run multiple times. It should pop up to say that a footing error was corrected in such&such account in period # whatever. Keep running the test until no message displays.

 

Before running Synchronization tests, re-indexing the tables that are being corrected is often appropriate. In this case the files would be; Chart; Jrnl Header & Jrnl Rows. Re-indexing should always be done on File at a time.

Step 6. Reprint the same list of reports created in Step 1

Step 7. Next audit the results against the before reports printed.

If things are not fixed or actually worse, restore immediately before doing anything else.

 

Sage 50 Repair is complete

 

Once you have completed your audit of Sage 50 and confirm the data has been corrected and your issue and the gl trial balance is in balance you are good to go. (meaning debits and credits at the end of the current period Sage 50 general ledger trial balance are the same exact balance)

Step 8. Make a backup if you have reviewed the reports in detail and they are error free and you are not receiving any errors in Sage 50 when recording transactions.

 

Sage 50 repair last steps

Step 9. Then change the account type for the affected gl account(s) back to their original settings and run the chart/journal sync test again in FP1 until no messages are displayed. Confirm that the GL trial balance is in balance for all open periods and that the ending balance for retained earnings in the last closed period modified by the net earnings for that year matches the beginning balance in the first open period on the general ledger report.

 

Step 10. Set up a new account with the correct account type. Either edit all transactions in all open periods to the new account or make a journal entry to move the entire balance of the bad account to the new one at the end of each open year. It must have a zero balance at the end of each open accounting year. Next set the bad account to inactive. You can also rename the id for the old/bad account and then rename the ID for the new account to be the same as the old one using the changeID button.

 

Sage Support

 

Make frequent backups and be sure to capture a screen shot should you receive any additional errors in Sage 50. For Sage 50 technical assistance give us a shout 800-475-1047

Services:

  • Sage 50 Data Integrity Check
  • Repairing Sage 50 general ledger
  • Sage 50 Error Messages
  • Sage error messages
  • Sage error codes
  • Sage support
  • Sage database utility
  • Peachtree data recovery
  • Sage 50 Training
  • Sage Timeslips Support

Sage 50 Errors

Sage 50 Errors

Are you getting a Sage 50 error message?

What do you do when you receive Sage 50 Errors Messages especially if you are on an unsupported version of Sage 50? You may need some instruction and assistance getting thru this and we are here to help.

Due to a required upgrade to Actian Zen v13 (formerly Pervasive) in the Sage 50—U.S. Edition 2020.0 release scheduled in July 2019, SAN members and Certified Consultants/Partners supporting clients on older versions of Sage 50 or Sage 50cloud will no longer be able to maintain versions prior to 2019, along with 2020 on the same computer.

What does a Sage 50 Error Mean?

If your Sage 50 Accounts or Sage 50cloud Accounts data has errors or corruption, and you need assistance fixing the Sage 50 issue so you can get back to work give us a call. For 30 years we have supported small businesses using Sage 50 Accounting products.

The Pervasive License Check for Sage 50 US versions 2018.2 and earlier specifically look for a Pervasive version 11 license key. When you install Sage 50 US 2020.0, Pervasive will upgrade to version 13 Actian Zen on the machine. As part of this upgrade, Pervasive/Actian makes the v11 keys inactive, leaving the new v13 keys. This will cause the earlier version of Sage 50 to no longer work as it will not have the proper key. For assistance with sage 50 exception management software

It is also important to note that Sage 50 2018.2 and earlier versions are no longer customer-supported releases, so if you need help please call to discuss your upgrade options.

For Sage 50 Errors or to Upgrade your old Sage 50 accounting product to latest Sage 50 software version call for the best software pricing toll free.

For more information on how to resolve Sage 50 data base errors messages visit www.jcscomputer.com

 

sage 50 error, sage 50 error code 30, sage 50 error messages, sage 50 errors, sage 50 exception management software

Sage Timeslips Training

X