How To Setup Sage 50 ACH NACHA Payments

How to setup Sage 50 – NACHA/ACH Payment to the bank

Sage 50 ACH NACHA Accounts Payable Payments How to set up Sage 50 - NACHA/ACH Payment to the bank Sage 50 vendor direct deposit payments using ACH NACHA

Support for Integrated vendor accounts payable ACH payments from Sage 50 to the bank. The following notes outline the general process when you want to setup NACHA / ACH payments. You can optionally have your bank complete an automated deposit or print vendor checks when sending Sage 50 ACH payment information.


Step 1: Considerations

Because the requirements for each bank may vary. The purpose of this document is to summarize the key requirements/service specifications for Integrated vendor accounts Payable processing. Extracting the payment information from Sage 50 will be performed by a Sage 50 user at your company and sent to the bank.


Step 2: Research

Start by calling your bank to request contact information for their technical support department. Then reach out to the technical support department at your bank so you can ask a few questions. Request written documentation outlining the requirements along with instructions for testing the ACH payment transfer. Finally ask about costs from the bank for this service.


Step 3: Planning

The next step is to setup an online meeting with you bank. This meeting is to help you understand all the steps that will need to be completed and the information for files to be provided to the bank. Questions should include how long the process will take once the test file has been sent to and tested by the bank. From beginning to end to have a live system is in place to process Sage 50 NACHA/ACH payments may take several weeks.


Banks may require multiple files such as:

  • Control file
  • Sender Identification number
  • Check register
  • ACH register
  • Control Total File


Each bank will have a technical support department who can help understand the details of the file(s) that need to be created. The files will be extracted from Sage 50 and then handed off to the bank. The bank will then process ACH payments for accounts payable payments. Request the following “file specification formats” from this department as well as the file delivery method so you can get started.


Sage 50 ACH Definitions:

A control file – counts of transactions and / or control total – sum of all total payment records may also be required.

The sender identification number is the number used to identify your bank account the payments will be deducted from.

File acknowledgement – some banks will provide a file acknowledgement options which are automated email confirmations.

File format – The payment file required may be a text file, CSV or XLS file format. It will need to be organized in the exact manner by field, by line item and by record. The value in each field will be defined in the requirements documents. Some fields may specify the number of characters expected and size of the field. Other fields may specify if it is numeric, alp or alphanumeric and/or padded with leading 0’s, blanks or other characters because of the system they use.



Normally included as a part of the testing and ongoing process may be a pre-note transaction which validates the bank routing, account number and may include the account holders name prior to an actual ACH transaction being completed. Pre-notes may not be required but are recommended.


Once the test export from Sage 50 has been completed for ACH payments and provided to the bank normally a testing process is completed to confirm the data is delivered in a format the bank required. A sample run or two may be required to complete and finalize the Sage 50 Ach testing process.  Both transmission and format testing may be required.


Each bank may have one or many ACH payment types that can be used as a part of the ACH file(S) provided to the bank. Study the requirements from each bank to determine how the information will be defined and delivered to the bank. Each bank may have one or many codes used to define the account type of the receiving account such as checking or savings or other types of banking accounts the ACH payment will be deposited into.


After testing the bank should notify you of rejected files and/or transactions. Updates may be necessary to the output files and retesting should then be completed until multiple successful test transmissions have been completed. You may need to have more than one meeting with the bank to complete the testing process when using Sage 50 ACH NACHA payments.


Questions on Sage 50 ACH payments from Sage 50 to the bank.


We would like to transition from physical checks to ACH payments to our vendors. We are currently using Sage 50. Are you able to create an add-on for us to issue NACHA reports/upload files for our bank? Possibly using Sage Intelligence Reporting? If so, could you please send me a quote for doing this?


Yes, we can have a meeting and provide support for creating the ACH file for the bank from Sage 50.


Is there a report in Sage 50 that can be used for electronic check payments in NACHA format requirements?


No it will need to be created.


What are the options for creating an ACH file?


Available tools that may be used to complete the data extraction from Sage 50 for AP automation to create an ACH file for the bank.

  • Access from Multi-ware
  • Crystal Reports
  • Sage Intelligence
  • Sage 50 SDK


Support for Integrated accounts payables ACH payments from Sage 50 to the bank.

Sage 50 training and / or Sage Timeslips Support

Fix Sage 50 pervasive database

Fix Sage 50 pervasive database

2013, 2014, 2015, 2016, 2017, 2018, 2019


Sage 50 Pervasive Data Base Engine Update. Are you receiving errors installing pervasive? Due to a recent update with the Pervasive Database engine the below notification was sent to Sage 50 customers on version 2017 through 2019 by Sage. Connect for technical support for Sage 50 and promotional upgrade offers reach out now!


Sage 50 Pervasive Error On Start Sage 50 installation, actian zen, database, failed, pervavive, Error installing Pervasive, Unable to install pervasive Fix Sage 50 pervasive database 2013, 2014, 2015, 2016, 2017, 2018, 2019



What is pervasive for Sage 50?



Pervasive is the data base engine that runs Sage 50


Sage 50 Pervasive Database Notice – This article refers to an update just released for the following Sage 50 versions. Fix Sage 50 Pervasive database notice for the following versions:

  • 2013 – Sage 50 2013
  • 2014 – Sage 50 2014
  • 2015 – Sage 50 2015
  • 2016 – Sage 50 2016
  • 2017 – Sage 50 2017
  • 2018 – Sage 50 2018
  • 2019 – Sage 50 2019



Sage 50 pervasive database engine summary of issue being addressed: Pervasive is no longer providing keys to activate older versions of their product. This impacts Sage 50 US versions 2013 thru 2019. But, customers are able to use the product so long as they do not update their hardware, operating system (to major version), or add new installs. Because, Sage 50 US 2019 and older are unsupported versions from Sage Software and they will not be releasing an update for these products. However, support for Sage 50 is still available at 800-475-1047.



Due to a third-party database component that is no longer supported, you will be unable to reinstall or reactivate Sage 50 US versions 2013 through 2019. For example, should you upgrade hardware and then attempt to reinstall Sage 50 US versions 2013 through 2019, the re-installation will be unsuccessful.



How do you stop pervasive in Sage 50?



 If you are using Sage 50 2020 or newer, the name of the service has been changed. The name change from Pervasive to Actian, as noted below has been completed.

  1. Press Windows+R keys.
  2. Type SERVICES.MSC, and then click OK.
  3. (Quantum users only) Right-click Sage 50 SmartPosting 20xx, and then select Stop.
  4. Right-click Actian PSQL Workgroup Engine, and then select Stop.


What are the top Errors Sage 50 users running version 2013 to 2019 may receive?

  • Error installing Pervasive
  • Unable to install pervasive
  • Error: “The installation of the Actian Zen [or Pervasive] database has failed. Please contact Sage 50 Technical Support for assistance.” Note: Sage 50 Accounting 2020 uses Actian Zen for the database engine, while 2019 and earlier use Pervasive.
  • Error 22665.
  • Unable to install Pervasive.
  • Error: “Error installing Pervasive.”
  • Unable to install Sage 50—U.S. Edition.
  • Error: “Aborting Install: Error installing Pervasive.”
  • Top Error: “Database Service Manager has stopped working.”
  • Error: “The Pervasive PSQL v11 Workgroup (32-bit) SP3 Setup cannot be run when the Pervasive PSQL Server Engine (64-bit) is installed. Please uninstall the 64-bit Server Engine and restart setup.”


Discover help to correct pervasive database errors and promotional upgrade offers. Sage technical support for Sage 50 phone number 800-475-1047

Sage 50 training

Sage Timeslips Support



installation, actian zen, database, failed, pervasaive, Error installing Pervasive, Unable to install pervasive

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


  • 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 Sage Intelligence Replaced With Logicim

Sage 50 Sage Intelligence Retired – Replaced With Logicim XLGL

Sage 50 Sage Intelligence vs Logicim – Reach out now for promotional pricing on upgrades for Sage 50 and Sage Peachtree training Call today for help with migration to Logicim for Sage 50.


Question Sage 50 Sage Intelligence vs Logicim: Sage 50 Sage intelligence replace with Logicim for Sage 50 BI Sage Intelligence use Logicim


I haven’t seen any updates about this announcement last October. What exactly does this mean for my clients that are using Sage 50 Sage Intelligence reports? I also have several clients that need external reporting now. Clients are asking if their current installation of Sage Intelligence for Sage 50 will continue to work in future released versions of Sage 50?


Answer from Sage:


Sage no longer offers the Sage 50 Sage Intelligence BI license with any new purchases of Sage 50. Any clients on active service plans that have it will be supported through Sep 2021. As of this article you may test drive a free 30 day trial for Logicim which will replace Sage 50 Sage Intelligence. Please reach out to speak with a Sage 50 specialist about Logicim 800-475-1047.


Announcement Sage 50 Sage BI is being retired and replaced with Logicim XLGL:


Sage has announced that Sage Intelligence for the Sage 50 US Edition is being retired effective September 2022. The decision was made due to the limited number of Sage 50 customers that adapted BI as a reporting tool. Sage Intelligence will continue to be available as a part of Sage 100. This information was released by the Sage Product Marketing Director Mike Edgett on October 6, 2021.


Why use Logicim?

Use Your Excel Spread Sheet Skills To Build Powerful Reports for Sage 50:

Easily create reports from your Sage 50 company data, extract information from the Sage 50 data tables using this new tool and present it in detail or summary formats. The replacement tool works very similar to Sage BI, and is also a Microsoft Excel add-in. Report on a single Sage 50 company data file or multiple Sage 50 companies and leverage the knowledge you currently have when working with spreadsheets.


How is the data accessed?

Access all data from any Sage 50 company file, all version, all editions. Connect to a single company at a time or report for multiple companies and works very similar to Sage BI.


What reports are included?

Includes 35 ready-to-use reports. A user can start with an existing report and modify them or create your own using Excel and XLGL specialized tools. Keep data up-to-date with the click of a button. Drill down on figures for extended information. Easily hide rows or columns with zero values from your Sage 50 company data files.


Can I use one report for multiple Sage 50 companies?

Freeze a copy of your dynamic report and send it to anyone.


What are the requirements for Logicim XLGL?

  • Microsoft Windows 10, Windows 11 or Windows Terminal Server (2012+)
  • Microsoft Excel 2010 or higher
  • Sage 50 Canadian Edition (2012 and above) or Sage 50 US Edition (2021 and above)

Call to speak with a Sage 50 expert regarding Logicim 800-475-1047


Sage 50 Support Plans

Accounting Business Solutions by JCS provides a complete set of tools and services to help you with anything related to Sage 50 USA Edition. Choose from one of our support plans below to get started.

  • Phone Support
  • Remote Control Support
  • Need Analysis
  • Form or Report Creation
  • Data Import/Export Solution
  • Training
  • Data Repair
  • Software Installation and Configuration

Call to speak with a Sage 50 expert consultant 800-475-1047 to down load a free 30 day trial for Sage 50. We have not been able to determine if any Sage 50 Sage Intelligence reports will convert if you are considering replacing Sage BI for Sage 50 with Logicim.