Error submitting EFT File to Bank

Tyler Lester

Hello all:

I'm running into a sticky error that I can't seem to resolve on my own. I submit an EFT file - a NACHA file - to our bank, Chase. However, they return a few errors.

1- “Batch 1: We can't accept this file because the service class code (located in the Batch Header Record in row 5) indicates the batch has mixed transactions. The service class code must be 220 or 225. (Error code: 57106)”

2-"We couldn't find an eligible Chase account in the file. In your Nacha file software:

1. Confirm the account is eligible for ACH payments or collections. The system administrator can see an account's status on the company activation screen found at the top of ACH Payment Services > Schedule payment.
2. Find the company discretionary data field and update the Chase account number (must be 20 numbers with all zeroes before the account number).
3. Generate a new file and upload it again."

I haven't seen a customizable “Service Code” field, as I assume that would be coded in Blackbaud as one or the other.

Also, Blackbaud limits the account number field to 19 characters - so I cannot enter a 20 digit account number with extra front end zeros. This may not be necessary - it may be on Chase's side, but I'd like to see if I can experiment on my end.

Anyone run into one of these errors with their banks and figured out their resolution? I've got a support ticket open, but unless I end up speaking with one of their more seasoned tech people or even an engineer, I'm stuck.

Tyler Lester

@Tyler Lester
If anyone ever has some of the same problems, just know that Financial Edge NXT outputs 200 as the Service Code - which is mixed credits and debits. This has to be manually changed either to 220(payments) or 225(collections), from 200, unless your bank isn't picky (Chase is). This number is found positions 2-4 on the Batch Header/Footer (Batch Header is Line 2, Footer is… line 4 I believe. Might change with some options).

Also, the account number for your bank doesn't seem to be natively output either. This has to be manually entered on Line 2, positions(columns) 21-40. Lot of leading zeros. For Chase its twenty digits, which means leading zeros ahead of your account number.

Last but not least, the effective date (at least for Chase) has to be modified to 1 business day ahead for vendors, or 2 days for “individuals,” probably dependent on how you classify. This is at the end of Line 2, the Batch Header. This is their “processing date” and they want it pushed out a little.

Lisa Olscamp

@Tyler Lester
The only “issue” we have ever had with the EFTs is the date also. Our bank processes these overnight, whereas some do same day. We adjust the date by 1 also.

Leia Bridgham

@Tyler Lester

Thank you. It is wild that the Service Code is not an editable field in the bank. Manual manipulation of EFT files leaves so much room for error. Additionally, we have found that the FE field for Company Identification only allows 9 digits. 10 digits, strangely all 0's, are required in the Chase for Business ACH file. Would love to hear any updates.

Tyler Lester

@Leia Bridgham Same problem on my end. Interestingly, we were able to get around that. In Database mode, you can go into the bank, and modify the EFT optional information. Have to go to Accounts Payable, select bank, go to account options for the bank, find payments, select the EFT field, and select “Edit payment options.”

The 10 zeroes is slightly tricky - in “Company ID Prefix," select “User Defined” and in the field that becomes available, put a single zero. Then, in the “Company ID Number” field, put those 9 zeroes in. That should solve that.

As far as manually editing the file, it should be pretty quick. Once you output it, save it and then use notepad to open it.

Modify lines 21-40 in the batch header - I think FE NXT puts “Direct Deposit” there normally, so replace that- to include your account number, and then all leading zeroes until you have 20 digits.

The "effective date" is on the right next to the “descriptive date”, I believe, and you have to modify the Effective Date to be one business day forward.

Finally, the service class code is at the beginning of the batch header and on the batch footer - up top it's preceded by a 5, so it usually will look like this “5200” and the bottom seems to be usually preceded by an 8, so it looks like this" 8200."

For payments, just change the 200 number to 220 on both. It'll look like this when you're done -

“5220," and “8220.”

When you're all done, you can check the file to see if it's still 94 units wide - any additional numbers or out of place digits will make it physically wider as you look at it in notepad.

When you submit it to Chase, the only error that should pop up is that it will process payments as vendor payments unless “Payroll” is in the entry description. Which typically says “ENTRDESCR” I believe as default.

Let me know if that works for you. If you end up submitting the file a day or two late, remember you'll have to change the “effective date” to one business day forward of the day you plan to submit the file to Chase.

Leia Bridgham

@Tyler Lester
Thank you, changing the prefix should be helpful! I still think its absurd that these are not fields/options that can be edited prior to generating the file. Does every BB Client have to manually edit their EFT File.

Tyler Lester

@Leia Bridgham I don't think so. It would depend if certain banks accepted Tax ID numbers or account numbers in certain positions on the file - Chase is just specific, and has the account number in a position that is typically for miscellaneous bank information instead of where the company ID position usually is.

Though the service code not being modifiable is odd.