Feature - Prompt ACH Deposit Effective Date to Avoid Non-Business Day

Feature - Prompt ACH Deposit Effective Date to Avoid Non-Business Day

Release Date - 3/14/16
Version: 8.2 & Up

The purpose of this feature is to give the user the option to enter the ACH Effective Entry Date. This date defaults to the system date plus one day when you create the NACHA file. As a result, this day may fall into a weekend or holiday. Some banks reject ACH effective dates on non-business dates. For this reason, we added a new ACH Global Setup option  that will allow the user to choose whether he/she wants the system to prompt the user for the ACH Effective Entry date when creating the NACHA file. See sample screen below:



10. Prompt Effective Entry Date When Create NACHA File? The default value for this field is N.

If this option is set to Y, a window will pop up that will allow the user to enter the Deposit Effective Entry Date. This field will default to the system date plus one day. 


The date entered cannot be less than the system date. Also, it cannot be greater than 7 days past the system date as a safety measure to avoid typo errors.

If users wish to defer this process, then they should use the F1 key, which means System Date plus one day. Entry of a fixed Deposit Effective Entry Date will not work for deferred report processing. If the F1 key is pressed, the text "System Date Plus One" will be displayed next to the entry date.  Currently, if you create a NACHA file through defer processing, the system does not have the ability to avoid making the Deposit Effective Entry Date on a non-business day.  If your bank has an issue with this, then we suggest that you not use defer processing to automate this task.


One other common issue is that you may make a mistake on a Deposit Effective Entry Date when creating the NACHA file. Then what do you do?  The NACHA file is actually a common ASCII file that you can edit iwith a common editor like NOTEPAD.  All you have to do is to find that NACHA file and bring it up with NOTEPAD, and search for your Deposit Effective Entry Date in the YYMMDD format.  For example, if you enter the effective date as 04/13/2019 (which is a Saturday), search for 190413 in your NACHA file using your editor.  Replace the value to the following business day (Monday,190415 in this case) and save it.  Then you can follow the normal procedure to upload this NACHA file to your bank's portal to complete the rest.

Modified Programs: NSCTLFIL.FD, NSCTLFIL.W30, NSCTLMNV, NSCTLINI, ARACHJNL, ARACHPRC, ARACHQRV, ARHISDTL

CLS


    • Related Articles

    • Feature - ACH Warning When Changing Order Terms

      Release Date 4/29/16 When using the ACH Processing add-on and changing the terms on an order in order entry or order billing from an ACH term to a non-ACH term, the application will check whether there are any ACH payment records defined in the order ...

    • Feature - Elliott AR ACH Processing

      Article Transfer Tracker Article Transfer Tracker 100% C86 Release Date: 1/27/2015 Introduction Elliott AR ACH Processing is designed to debit a customer's bank account through ACH debit transaction by using NACHA (National Automatic Clearing House ...

    • Feature - ACH Add and Change Event

      Date Released - 12/16/16 We have added two new events that are triggered from the ACH Detail Screen. These events can be accessed from Accounts Receivable-> Maintenance-> Customer File Maintenance. ADDACHCU is triggered when an ACH account is added. ...

    • Feature - Add Acct Name to ACH Account Detail Screen

      Release Date: 08/17/2016 The Elliott ACH feature allows users to make direct debits to their customers' bank accounts through ACH transactions. To know more about this feature, please see the following Knowledge Base article: ...

    • Feature - Add "F2 = System Date - 1" to Release Held Orders

      Release Date - 11/15/18 This feature is related to the following KB article: https://support.netcellent.com/portal/en/kb/articles/feature-auto-release-held-order-utility In this change, we added a new option to the Customer Last Payment Date >= field ...