Sage 100

My client who banks with Wells Fargo just uses regular ACH processing, like normal.  They actually got it setup with GoToMyERP to have it sweep the folder where the ACH file is created on a regular basis and automatically ftp it to Wells Fargo.

@Beth Bowers WF offers another ACH service that goes way beyond the Sage 100 ACH capabilities; it distinguishes between the delivery methods, payment types, international routings, etc. and requires address fields, etc. etc. I've attached a sample of the .rpt and these fields all all required!  I had one of these several years ago and it took months to work through the testing process and get the file exactly the way they wanted it.  This was the same experience (weeks, not months, since a lot was learned from the first one).  Anyone with clients who purchased this more robust WF ACH service?

My client who banks with Wells Fargo just uses regular ACH processing, like normal.  They actually got it setup with GoToMyERP to have it sweep the folder where the ACH file is created on a regular basis and automatically ftp it to Wells Fargo.

Ah, I think I do have a client using this - but they also have a full internal IT team including multiple programmers, who take a Sage check form printed to a TXT file and convert it into whatever WF is requiring, so not much help for you there!

@Beth Bowers WF offers another ACH service that goes way beyond the Sage 100 ACH capabilities; it distinguishes between the delivery methods, payment types, international routings, etc. and requires address fields, etc. etc. I've attached a sample of the .rpt and these fields all all required!  I had one of these several years ago and it took months to work through the testing process and get the file exactly the way they wanted it.  This was the same experience (weeks, not months, since a lot was learned from the first one).  Anyone with clients who purchased this more robust WF ACH service?

My client who banks with Wells Fargo just uses regular ACH processing, like normal.  They actually got it setup with GoToMyERP to have it sweep the folder where the ACH file is created on a regular basis and automatically ftp it to Wells Fargo.

Commas in any kind of output, exported to CSV, will be wrapped in quotes by the CR export process.
We've had to do this a few times for different purposes (not WF ACH).  If you need meticulous output, when the export to CSV is unreliable, we put everything into one long formula field for each line, then export to text file format (not CSV).  The trick there is to make sure your page size is wide enough, and use the same characters per inch value (tested for the report with wide example data).


Or write an ODBC VBScript instead, which gives much more reliable output formatting without users having to export the data to a file.
Of course, ODBC won't work with any PII values, and I think Sage said vendor banking information is about to be encrypted in v2023, so probably not a good strategy for this.

Thanks, @Kevin Moyes .  Unfortunately since WF requires a .csv file, exporting directly to text won't work for them.  I'll see if anyone on my team is technical enough to take on that VBscript.  Re. encrypting bank info, I think we're good because technically all of the data in the file is from AP, none is actually Bank info.  Thanks again!

Commas in any kind of output, exported to CSV, will be wrapped in quotes by the CR export process.
We've had to do this a few times for different purposes (not WF ACH).  If you need meticulous output, when the export to CSV is unreliable, we put everything into one long formula field for each line, then export to text file format (not CSV).  The trick there is to make sure your page size is wide enough, and use the same characters per inch value (tested for the report with wide example data).


Or write an ODBC VBScript instead, which gives much more reliable output formatting without users having to export the data to a file.
Of course, ODBC won't work with any PII values, and I think Sage said vendor banking information is about to be encrypted in v2023, so probably not a good strategy for this.