|Input file types that are supported by this function:||X9 support:||ACH support:|
Import allows x9 files to be easily created from input CSV files. Import requires that you provide the values for each field within each x9 record. Import takes your field values and will apply appropriate field construction rules to ensure that an appropriate x9 record is constructed. For example, if the field is required as numeric zero filled, then the value will be padded with zeroes on the left as required by x9 rules. Another example is justification, where the field is justified left or right and then blank filled. X9Assist will perform the appropriate justification and padding per x9 field specifications.
Although you must provide every record in every field, you do not need to provide the accumulated values for the summary counts and amounts in the bundle, cash letter, and file trailer records. Instead, you can supply a value of zero as proxy for those various fields, and then indicate that auto-repair of the trailer records should be run as part of the import process. When you set the trailer counts and amounts to zero, you must then select the trailer repair option on the import panel. Note that this repair will not run all available repair actions, but will ONLY repair the summary accounts and amounts in the various x9 trailer records.
Importing a Previously Exported File
You can use Import to create a new file from an x9 file that was previously exported. This is an logical approach to create a new x9 file if you have complex or repetitive modifications. You can export the x9 file, modify the created CSV file, and them import that resulting CSV file back into X9Assist.
Some tools that create CSV files will include column definitions as header rows on the front of the created file. If you have such a file and cannot easily remove those header lines, import will allow you to provide the number of lines to be skipped. Remember that the first line being imported must always be an “01” for your file header record.
CSV files will typically have all fields enclosed in single or double quotes, with fields separated by either commas or tab characters. Import supports these various formats and will automatically identify and accept those characters appropriately.
The x9 output file created by the Import will always contain images. Images can either be imported from external files, or they can be dynamically inserted by X9Assist. If you provide the images, then a separate tiff file must exist for each front image and back image.
There are several available options. You can directly provide the actual images that you want to include in the x9 file. A separate front image and back image must be provided for each check. Your images will be included and inserted into the x9 file being generated. The import operation will be aborted if your image cannot be found, or if it is determined that the image you have provided is not a valid tiff format and hence is not usable.
You can alternatively insert replacement images for each front and back image using one of the following options:
- Insert missing image documents: missing image documents will be inserted. These images can be customized with your specific missing image design.
- Insert missing image documents that include MICR lines: missing image documents will be inserted, where the front image will contain MICR lines that are constructed from the x9 data.
- Dynamically draw the images from the imported x9 data: images will be redrawn using the information that is being assigned to the type 25 or type 31 check detail record. X9Assist will ensure that the image meets tiff standards. You can select the check format (artwork) on the image templates tab. You can also provide additional customization using the “draft check” tab within program options.
Record Type 52
The x9 check image record is record type 52 (image view data record).
Field 52.18 (check image length): your value for this field is ignored; Import will assign this length automatically from the image itself.
Field 52.19 (check image): there are several options for this field:
- Specify the fully qualified name of the check image file that you have created.
The images can be located within a single folder. In that case, the image file name can be unqualified, and you can instead select the folder which contains the images. Each check will have two images (front and back) and hence they must be uniquely named.
- Image can instead be located in multiple folders. In this case, you would not select an import folder, but would instead provide a fully qualified image file name for each check image.
You should use a file naming scheme that defines the check number and the logical image side. An example would be to name your image files “Check_nnnnn_sssss.tif”, where nnnnn is the check number or record number within the overall x9 file; sssss is either “front” or “back”.
This import example is included in the examples folder and includes the check images. You can actually import the file and examine the results.