ACH Transactions

Options
We are trying to implement ACH options through OXP. However, our first transaction received an Invalid Routing Number error. Working with Knowledgebase and Support, it appears that there is a likelihood that the routing number on the check, and provided in the OXP example, is not necessarily the correct routing # to be used. I wanted to see if anyone successfully uses the ACH option, and how they address the donors if it is invalid.
Tagged:

Comments

  • JoAnn Strommen
    JoAnn Strommen ✭✭✭✭✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic
    While the # on most checks is the routing number, there are some financial entities that do not use the traditional routing # on their checks. I've only encountered this one time in my years but was able to verify that the # on the donor's check was not the routing number and obtain the correct #.


    Contact your donor. If they've done any other similar ACH transactions they may be aware of this already.
  • Marianne, I ran into this twice in my 11 years of handling ACH transactions. Once, a donor gave me the routing number from his deposit slip which - for that bank anyway - was different from the routing number on the checks (incoming vs outgoing revenue flow). Contacting the donor is always best.


    The last time, I did stumble across a very useful tool at the American Bankers Assn. (Click here.) With just the bank name and city/state (often printed on the checks above the memo line), you can look up any bank's routing number. Conversely, you can also use the routing number to find the bank name, in case you need a name for entering the bank info into the RE tables.
  • Thank you for the response. It is good to know that this is not a common occurrence.


    We tested a different bank and had no issue. We continue to have a problem with the current donor. She re-entered her information, I verified it was correct and then it reverted to the incorrect routing number in BBMS. Support is now addressing the issue as it appears to be a glitch. We are hoping this is just a one-time issue.



Categories