Experience.FellowshipOne.com

An odd thing - - when scanning checks, if it has 4 zeroes before the account number, it won't scan properly.  The account number does not pop up and has to be entered manually.  It scans 3 zeroes and 5 zeroes, but not 4 !!??

 

BTW, these seem to be all Bank of America checks, so is it something goofy with Bank of America???

 

While I can not say that you are wrong about the problem being related to the number of zero's in front of the account number I would guess that it isn't the problem.  Some checks just don't scan very well.  I am guessing it has more to do with the checks themselves rather than the account number which doesn't really effect the scanning process.  It is always the same family or do you have multiple accounts that are having this issue? 

In any event the issue tends to be related to the check scanner which is an industry leading check scanner.  See if you notice any other checks that have 0000 as the first digits in the account number and you will probably see that they are scanning correctly. 

---

Matthew McMaster
Delivery Manager
Fellowship Technologies

There are problems with the software picking up the check number.  If the first digit of the check number is zero, the software will not accept the number.  If the check number is 5 digits long and the second digit from the left is a zero the software will not accept the check number.  In both sitations the check number has to be manually keyed.  These problems always occur in the preceding documented format and are not related to intermittent micr reading prblems.  Because the F1 software has no control over the format of the check number, the software should not be editing the format of the field.

If by "the software" you mean Fellowship One then it sounds like a bug. I have not heard of this issue from my churches yet.  Of course they might just be assuming that the problem is with the check scanner and not F1.  Please submit a support ticket so that we can resolve this issue. 

---

Matthew McMaster
Delivery Manager
Fellowship Technologies

I know it's nothing Fellowship One related - its a bank thing. I have that same problem - but like you said only with Bank of America Checks.

---

Patty B!

On some checks if the check number is 10001 the micr line for some banks only has printed 0001 (the last 4 digits).  Any time that the leading digit of the check number on the micr line is 0 the software will not accept what is read by the check scanner.  This is the same situation on shorter check numbers as well where the leading digit on the check number on the micr line begins with a 0.  When this situation occurs, the software will never accept the check number.  It is true that there are also occasional situations of not being able to read the number, but in the above situation the number is never accepted.

Hi Patty,

I agree with Matt. Our system is designed to certain specifications, but it sounds like we need to at least evaluate this issue and make certain it is not an issue with our application. Would you mind submitting a support incident on this and just let the support team know that you were advised to do so from Lance on the Experience Site. We can have our Development team analyze the issue and determine how to resolve it if we can.

God Bless,

---

Lance Dacy
Director | Customer Services
Fellowship Technologies

I have the same problem with certain Bank of America checks. I didn't pick up on the number of zeros having anything to do with it. But I will be looking now. It's very frustrating for sure. I just assumed it was either the scanner (at first) then I noticed it was only BOA checks and then I felt the problem was with the checks themselves. Maybe a printing glitch where they left out a certain ingredient in toner that is supposed to scan. I never really thought to bring it to the attention of F1. Has anyone figured this out yet?

Cindy Graves

Stonecreek Church