US Bank ACH File - how to map fields correctly in set up for Destination and Sending Institution

Hello there - we are working on our set up transitioning from S3 to FSM. Our ACH file does not seem to meet the US Bank set up specifically when it comes to the Destination Bank, Sending Bank, and Originating DFI ID. At first INFOR consultants led us to needing to customize, but then INFOR support led us down a path of updating our set up fields (which worked for the most part with the exception of one field).

I'm hoping I can get some guidance from those of you who have an ACH being sent to US Bank currently - can you meet the requirements through the set up columns or did you have to create a customized flow?

These are the fields I am not confident on where they pull from in creating the ACH file with fake values for reference -

- Destination Bank - 123456789

- Sending Bank - 786786786

- Destination Name - US Bank

- Senders Name - Pizza Huts

- Company Name - Pizza Huts

- Company ID - 786786786

- ODFI - 12345678

Find more posts tagged with

Accepted answers

All comments

unknown

We created a custom flow

Let us know if you 'd know

sthiemann

The NACHA guide from your bank will help you with any constant values required. Consult docs.infor.com for the Payables and/or Payroll configuration screens that correlate to your NACHA guide.

cleverly

We encountered this same problem when we went live with our first US-based business units (migrating from S3 to FSM) in Q3 of 2021. At the time we experimented with every possible combination of the Payment Clearing File creation options to determine how they influenced what values FSM would use when it generated the ACH file. I'm attaching an Excel spreadsheet that we put together with our findings.

Our bank was happy with what S3 generated. However, no combination of fields / setup in FSM enabled us to produce output exactly like S3 did. We could get close--all but a single field. Because of that we had to take the delivered IPA flow and customize it and use a regular expression to replace one value on either the first or second line of the file.

[View:/cfs-file/__key/communityserver-discussions-components-files/134/FSM_5F00_ACH_5F00_File_5F00_data_5F00_sources.xlsx:320:240]

Nathan Baker

We migrated from Lawson on prem to FSM cloud in 2020. In Lawson we used MHC for documents and they provided a formatting utility to produce our ACH files. When we transitioned to FSM we adopted IDM, losing the MCH utility. We ended up building a small utility in VB.net for AP team to convert the stock Electronic pay output from FSM to the required format for our bank(s). At the time I had less experience with modifying delivered flows, so I defaulted to the .net solution, but its been on my list to transition to modifying the flow.

Copyright © 2025 Infor. All rights reserved.