Mapping

ACH Universal > Mapping

Overview

ACH Universal will conform to your data, not the other way around.  To achieve this, mapping instructs ACH Universal what each field means in the context of an ACH transaction.  For example, amount may be in the first field and date in the second field.  Each of these is required in an ACH file.  Mapping instructs ACH Universal of where it can find the appropriate fields.

Without mapping, ACH Universal would be unable to determine which of your data fields correspond to which ACH field.

All imports, whether transaction or profile, must be mapped.  However, ACH Universal will retain each mapping.  If your data is always formatted the same, you will only be required to map it on the first transactional import.  Afterwards, ACH Universal will

remember your mapping and apply it to each file.

In creating a mapping, there are two distinct steps:

1.  Decide what to map

2.  Map the data.

Even though transactions and profiles are likely to contain different fields, the most important step is to decide how each of your organization's data fields correlate to ACH fields.  See Deciding What to Map to learn how to make thee decisions.

Page url: http://www.treasurysoftware.com/Help_ACH_Universal/index.html?mapping.htm