| Document # | Title | Effective Date | Version |
| FHC-ERR-01 | Resolving Error Processing Transaction Statuses | July 06, 2026 | 0.1 |
This article describes common causes and the steps to follow for transactions experiencing errors while processing within the FORTH system. It is for CRM Administrators, Account Managers, and Billing Specialists with standard or elevated access to transaction and billing logs within the FORTH CRM.
This article is organized into the following sections:
Overview
When a transaction fails to process through your payment gateway, the FORTH CRM marks it with an Error Processing status. This status prevents failed payments from stalling without your knowledge. By understanding the specific error codes returned by Forth Pay and CFT Pay gateways, you can quickly correct data entry errors, fix account mismatches, and resubmit the payments. This process ensures accurate ledger management and reduces the time spent diagnosing failed transactions.
Prerequisites
- Standard CRM Administrator, Account Manager, or Billing Specialist permissions in the FORTH CRM.
- Permissions to view the Transactions ledger or billing tabs.
How to Access
- Log in to the FORTH CRM.
- Navigate to Contacts or Enrollments > Transactions.
How it Works
When a transaction fails, the system appends a specific error message to the transaction details log. Review the steps below to identify and fix the issue.
- Navigate to the Transactions ledger.
- Locate the transaction displaying the Error Processing status.
- Click on the transaction or view its Notes/Logs tab to read the error string.
- Match the error message against the gateway tables in the Troubleshooting section below.
- Update the missing or incorrect information in the user profile, bank details, or enrollment settings.
- Re-schedule or re-submit the transaction.
Troubleshooting / FAQ
Review the tables below to identify the cause of the Error Processing status based on your active gateway.
Forth Pay Gateway Errors
| Error Message | Cause | Suggested Resolution |
|---|---|---|
| Invalid Routing Number; | The routing number entered is incorrect or invalid. | Verify the 9-digit ABA routing number with the client and update the bank details. |
| Bank routing number is too short or has too many leading zeros; | ||
| Bank routing number validation negative (ABA/district). | ||
| State should be 2 characters. | The state field in the contact billing address is formatted incorrectly. | Change it to the standard 2-letter abbreviation (e.g., "CA"). |
| ZIP code must be 5 or 9 digits. | The ZIP code formatting is invalid. | Ensure it contains exactly 5 digits, or 9 digits formatted with a hyphen. |
| No Splits Found; | The transaction does not have a designated recipient or payee profile assigned in the system configuration. | Assign a payee. |
| Payee Not Set; | ||
| Missing Payee; | ||
| Missing Account Number; | The bank account details are missing. | Update the billing profile with the correct account number. |
| Bank routing number and account number are required. | ||
| Payee Debit Block | The payee's bank account has a restriction that blocks direct debits. | Contact the payee to lift the block. |
| Consumer verification negative. | The system failed to verify the identity or bank account of the consumer. | Double-check all personal identification data. |
| Invalid Electronic Check Service (ECS) Account ID | The ECS account identification number is missing or incorrect. | Verify the ECS ID number. |
| Credit Card Information Missing or Invalid, contact XXXXXXXXX | The credit card details are incorrect, expired, or missing completely. | Call the provided internal contact number for account verification. |
| Error: transaction failed, unknown contact id / missing contact id mapping | The transaction cannot map to a valid contact record in the CRM. | Verify that the contact profile exists and is active. |
| Payment Stopped | The consumer or the bank issued a stop-payment order on this transaction. | Confer with the consumer and /or the bank issuing the stop-payment |
| Payee not a VBA account | The designated payee account is not configured as a valid Virtual Bank Account. | |
| Account Closed | The consumer's bank account on file has been permanently closed. | Collect new banking information. |
| Missing Bank Information | General banking details are completely absent from the processing request. | Verify the bank information is loaded into the CRM. |
CFT Pay Gateway Errors
| Error Message | Cause | Resolution |
| A duplicate schedule with ID already exists; | A schedule with these exact identification numbers is already active. | Do not submit a duplicate; create a brand-new schedule. |
| A duplicate withdrawal schedule already exists; | ||
| A duplicate schedule with ID and externalId already exists. | ||
| Can not reverse CFT owned fee. | System restriction: You cannot reverse a transaction fee that belongs natively to the CFT platform. | |
| Can not schedule a CHECK_OVERNIGHT payment on a LOCK BOX address | Courier restrictions prevent overnight check delivery to a PO Box/Lock Box style address. | Change the delivery address or payment type. |
| Can not schedule the fee type with id as the enrollment has not subscribed to the associated service. | The client enrollment profile is missing the specific service subscription required for this fee type. | Add the service to the enrollment first. |
| Deposit with external reference already exists; | A transaction record matching this external ID reference already exists in the system. | Check the ledger to confirm it was not already processed. |
| Fee with external reference already exists; | ||
| Payment with external reference already exists; | ||
| Withdrawal with external reference already exists. | ||
| Enrollment with id does not exist. | The enrollment record linked to this payment cannot be found in the system. | |
| External account with ID does not exist for the payee. | The payee profile does not have an external bank account mapped to the specified ID. | |
| Fee cannot be created. The maximum fee amount for this fee type is $xx.xx. | The requested fee exceeds the maximum allowed limit configured for this specific fee rule. | |
| No settlement exists for the debt with id or externalId | There is no approved debt settlement plan tied to this transaction ID. | |
| Settlement with externalId does not exist. | The external reference ID provided for the settlement plan is invalid. | |
| Validation failed. | Generic data validation failure. | Check all contact, enrollment, and payment fields for completeness. |
| You cannot schedule Payment on an enrollment in CANCELLATION_INITIATED status. | The enrollment is in the process of being canceled. | No new transactions can be scheduled until the enrollment is finished with being canceled. |
| fee with id and externalId does not exist. | The specific fee configuration ID cannot be found in the system. | Verify the fee configuration ID again. |
| payment with amount, date and id and externalId already exists. | A payment with identical parameters (same amount, date, and ID references) is already registered in the system. | Verify the amount, date, id, and external id for the newly proposed payment. |
Assistance
For further assistance, reach out to support@setforth.com.
Article Revision History
| Version | Effective Date | Changes Made |
| Basic | 06/01/2026 | Initial Release |
0.1 |
07/06/2026 |
Minor formatting updates and language updates. |
|
|