Unlike credit cards, ACH transactions act more like checks and are not authorized in real-time, which means transactions can be rejected (similar to a bounced check).

The network provides status codes when an ACH transaction is rejected. An ACH reject can occur for a number of reasons. For example, the bank account may be frozen or lack sufficient funds to cover the transaction.

If payments are unsuccessful, you are usually notified within two to four business days of the transaction (much quicker than the five to 10 days it takes with paper checks).

CardPointe does not send the information of ACH Rejection to the Hauler Hero system. We recommend regularly checking for failed ACH payments and or requesting email notifications.

To locate rejected ACH payments in CardPointe:

Report > Transactions > Method = ACH Reject

(the date range is defaulted to the last 7 days. Select the Date dropdown to the left to extend the view if needed)

If the ACH has been rejected we recommend marking the payment as ACH FAILED within Hauler Hero. This will log the failed payment in the payment history and also set the invoice back as Unpaid.

Sign up for email notifications for your failed ACH payments

From your Card Pointe account, select Administration > Email Notifications

Under Transaction & Event Notifications, select your Bluechex account in the drop down.

Select notifications for PER REJECTED TRANSACTION, Per DECLINED TRANSACTION

If those options above are not available, you can also configure your email notifications this way -

Email Notification Set-up:
​

To create a smoother process and experience for handling rejected Fiserv ACH (Automated Clearing House) sales transactions, an upcoming update to CardPointe will include a change to ensure that ACH Rejects are displayed properly within the CardPointe web application and API.

Previously, when a Fiserv ACH sales transaction was rejected, it resulted in the creation of an ACH return transaction line item that was included in a funding batch regardless of whether the transaction was successfully funded or not. ACH Rejects were displayed as negative entries within a funding batch and, in the case where the transaction was not successfully funded, the reporting was missing the positive entry for the transaction.
​

With this update, when a transaction is rejected and has not been funded, a new ACH Reject transaction record will not be created. Instead, the status of the original sales transaction will be marked as Rejected. The ACH return code linked to this transaction will be visible in the transaction table within the Transactions tab under Reporting, as well as on the Transaction Details page under Transaction History and History Data.

The offsetting ACH reject transaction will no longer be featured on the Funding tab within the Reporting section. Instead, the original transaction will be assigned a funding batch and marked as "Rejected."

Below is an illustration of the previous reporting view, showcasing the creation of a new transaction record with a negative entry due to a rejected transaction.

Below is a snapshot of the current reporting view. This indicates that the Status of this transaction record has been updated to Rejected, instead of generating a negative entry in the reporting.
​

This shift aims to enhance clarity and precision in conveying the rejection status of the transaction record within the reporting framework.

As a result of the modification in ACH Reject reporting, you might need to make some adjustments in your financial records and accounting procedures. These changes in ACH Reject reporting could potentially impact how you maintain your books, which may require you to review and adapt your existing financial processes to ensure accuracy and consistency.