Are there any Cloud customers out there that are using Electronic Processing to create an ACH file?
Our bank requires a PPD Payment and it appears that Epicor only supports CCD?
Is my only option professional Services?
I am struggling to get this to work - i am just a call away from having RAMP do this 
I cannot use the INternational - error about banks only outside the US.
I cannot use the US_ACH_Domestic - CCD only
I cannot use the PayrollElectronicDeposit - No error nothing happens
From my recollection, it will do both types of payments in one file. We’re still in the testing phase, but our issue is that our bank doesn’t like mixing PPD and CCD in one file, but we weren’t planning on doing PPD, so I just had to edit a few lines in a copy of the Domestic ACH script. It was like an afternoon of work to dissect the script and the bank reference.
I’d think you’d be able to set a “PPD ACH” payment method, attach it it to indivduals in your Vendor table. Then create a PPD Electronic Interface and point it to a tweaked US Domestic ACH C# script.
Mr. John: Thank you for the suggestion.
We are cloud based – so we do not have access to eh C# file (that I know of).
DaveO
I have heard you can get the file from the cloud team. PPD is done but only for payroll.
The cloud team sure did give me a lot of kickback getting our C# files, they wanted only to release to Epicor CSG.
All of Epicors Electronic Interfaces are just blah. I just spent 3 months building ACH CCD, PPD, WEB, CTX in EI and Functions, once I built both we decided to just do it in Functions because an EI runs during Payment Processing and there is 0 guarantee that the file is accepted by the bank, and you may want to read a response file which may come 15 minutes later. You are stuck holding your group hostage (not posting it) until the Bank Accepts the files, otherwise you go into VOID hell. You also might want to configure SFTP Upload among other things which Epicor doesnt support out of the box.
TLDR; We did EFX and Dashboard.
Maybe this inspires the next generation @JeffLeBert to use EFX instead of EI 
oh did I mention that I simply get my data via a BAQ. Forgot to mention to be able to label the EFX via Process Set got a SQL Script on-prem but will make an idea for that too!
https://www.epiusers.help/t/snippet-executebaq-efx/117659
This is a good example @Epic_Santiago why for example on-prem limiting File.Write via Sandbox to certain folders is bad, because we have other processes that pickup and move things via SFTP just because you dont have things like that in the cloud, shouldn’t stop the on-prem folks of utilizing C# we are on-prem and paying for an on-prem license. perhaps consider a whitelist vs limiting it to Company ur User Folder. Some write or read from/to \\UNCPATH\
When folks say they save money being on the cloud, they forget how much time they waste working around limitations. You saved on hosting but I can do in 30 hours what takes you 130 with workarounds. 
technically I saved more than you in the long run. We just added WinSFTP.exe to our Custom Assemblies folder and SFTP is ready to go, no micro-service needed.
Yeah! I love Epicor Function (EFX) usage instead of Electronic Interfaces (EI). 
The current Sandbox functionality for file I/O is not finished. It is limited to Company and User folders only because of time constraints. When complete you will be able to get to all the “special folders” you have access to. Don’t worry, we won’t lock you out of legitimate folders.
We haven’t decided the exact way we would allow access to external folders yet. Until we have a usable replacement, you will have standard file I/O.
Nice! Perhaps a whitelist where you can add them to some Directory White List Maintenance.
Understatement. The canned EI stuff straight sucks and clearly hasn’t been updated in eons. The second I saw “I just did a function” I thought “of course, it’s so obvious”. I’d certainly prefer to keep everything in the DB rather than deal with loose files on the server. You’re going to be writing C# anyway, and I’m a big proponent of keeping all code in as few places as possible.
This wasn’t an issue for me since users would drop the file into a web portal and get instant verification. A fully automated workflow definitely sounds awful.
