Creating an application specific type tree

These procedures describe how to create NACHA type trees for your specific application.

Using a subset type tree, as described here, can improve mapping run-time performance, as there are fewer application group partitions to test during validation. In addition, the size (disk space required) of the type tree source file can be reduced (minimized). Data validation of a type tree starts at the top, and moves down the list of SEC subtypes, attempting validation of each subtype against the data until a match is found. Use the procedures in this section to "prune" the appropriate version of the Automated Clearing House (ACH) type tree to meet your needs.

Instead of merely deleting the unneeded types directly in the type tree, there is a two-step process that is required to "prune" the tree in order to make it the most efficient:

First, create a tree by copying the current ach_vnnnn, or ach_vnnnn_sfmt file and deleting unnecessary application types.
Note: In the file names above, nnnn indicates the year of the application standards, for example, 2009, or 2015.
To remove unused components from the type tree that was created in the previous step, create another tree and merge the File type into it.