By using this website, you agree to our Terms of Use (click here)
We are trying to utilize ACH batch payments in accounts payable but the existing export scenario "Export AP Payment to ACH" appears to be from an older version of Acu and most of the source objects show errors that they no longer exist. Is there any way to get a more current version of this export scenario which is one of the out of the box files?
@m-tepper what version of Acumatica are you running?
@acumatthewca these warnings are not actually an issue. Not sure why this is the case, but these fields still export the data as expected. I just tested this in 2019R2 and 2020R1 in sales demo and get a valid NACHA file output.
I worked with some automation from business events in the past and had to create some fields within an export that invoked the same warning. @timrodman do you have a explanation for this?
I've seen that warning (not error) a few times with export scenarios, even though the export scenarios work.
It's a similar warning to this Import Scenario which also works:
https://www.augforums.com/forums/acumatica-business-events/6-business-events-creating-a-task-automatically-summit-2019-session-examples
But I don't understand why the warnings appear unfortunately.
@kevin-ruppert and @timrodman Thanks so much for the help here!
I should have been more specific on my post - I assumed that was the underlying issue to the actual problem: the NACHA file output wasn't matching the requirements of our bank. I couldn't find the fields in Acumatica that required revisions to match the bank's requirements (immediate origin, immediate destination, control record, etc) and thought it was due to an issue with the export scenario.
So were you able to get the NACHA file output to match the requirements of your bank?
@timrodman Hi Time, is there a sample of this NACHA file export? We have a requirement for a couple of customers. I have done this before, but not in Acumatica.