NACHA file for Wells Fargo

  • NACHA file for Wells Fargo

    Posted by DSC Communities on February 21, 2017 at 4:51 pm
    • Aaron Robinson

      Member

      February 21, 2017 at 4:51 PM

      Hello,

      We are trying to create a NACHA file to upload into the Wells Fargo portal but when we send them a test file, there are many formatting issues.  Does anyone currently export NACHA files using out of the box functionality in Dynamics AX and upload via Wells Fargo portal?   We are currently on version 2012 R2 CU7.

      Thanks in advance for your help.

      Best Regards,

      Aaron Robinson

       

       

      ——————————
      Aaron Robinson
      Sr. Business Systems Analyst
      Stone Brewing Co.
      Escondido CA
      ——————————

    • Ben Green

      Member

      February 27, 2017 at 10:19 AM

      Working on the same thing, with AX 2009.  It appears that the positioning/spacing is more or less correct, however several areas have some issues

      • Type 1 (Header), spaces 41-63.  WF is looking for the origination bank.  
      • Type 1 spaces 64-86.  AX is inserting the account description rather than the company name.
      • Type 5 spaces 5-20.  WF is looking for company name again in this spot. AX inserted some test data I put in; need to research more.
      • Type 2, Type 5 and Type 8, spaces 4-13, 41-50,45-54, respectively.  WF is looking for the routing number and AX is inserting some other test data I put initial configuration, also need to research this one more.
      • Type 6, spaces 80-94.  AX is inserting a partial payment journal number + a line number.  WF is saying it should be a partial routing number (wow they love their routing number) and a line number.  The spacing is concerning here, because it appears that AX is coded to consume spaces 80-88 with the journal number rather than 80-87 as WF believes should be done.
      • Type 8, spaces 80-87, WF wants a partial routing number.  AX is inserting a string that I’m not sure the origin of.

      In short, it appears some of the inconsistencies can be addressed with config changes of varying palatability however the issues on Type 6 will probably require a code change.  If that’s the case, I will probably end up copying the NACHA file format and call it NACHA-WF or similar.  I would like to avoid that so I’m going to start by giving them the test file as is to see what they say. 

      ——————————
      Ben Green
      Orion Energy Systems
      Manitowoc
      ——————————
      ——————————————-

    • Becky Newell

      Member

      March 2, 2017 at 4:15 PM

      Hi Aaron,

      From what I’ve seen all of the banks have different NACHA file formats.  We’ve built exports for TCF, US Bank and Commerce Bank.  None of the modifications are too complicated (in the neighborhood of 8 – 12 hrs) but they are all slightly different from each other.

      ——————————
      Becky Newell
      VP of Technical Delivery
      Stoneridge Software Inc.
      Barnesville MN
      ——————————
      ——————————————-

    • Shirley Adams

      Member

      March 3, 2017 at 8:03 AM

      You’d think that the NACHA standard should be, well, standard, but it does seem as if the bank’s have added/changed to it for whatever reason (maybe they need new systems!).  This is why we are now including Sandler Kahne (SK global now) in all of our new implementations – both our consultants and the users seem pretty happy with that option, plus it cuts down on development time.

      ——————————
      Shirley
      ——————————
      ——————————————-

    DSC Communities replied 8 years, 6 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘NACHA file for Wells Fargo’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!