Table of Contents - ImageScan€¦ · Table of Contents . ... The generation of the X9.37 output file and ACH output file and unsetting ... ASCII or EBCDIC 3

Table of Contents

Special Setup Requirements and Workflow for Check 21 and ARC Processing

I. Special Site and Lockbox Setup Requirements ............................ 1

A. Site Settings for Check 21........................................................................1

B. Lockbox Settings for Check 21.................................................................3

C. Site and Lockbox Settings for ARC Processing .......................................7

II. X937 Configuration File................................................................. 9

III. Track Control Configuration File.................................................. 11

IV. Workflow for Check 21 ................................................................ 12

V. Modifying the Check Field for a Payment in Data Editor............. 15

VI. X9.37 and ACH File Generation for Check 21 Batches .............. 17

VII. Unsetting the X9.37 Transmission Flag ...................................... 22

A. Data Editor ...............................................................................................22

B. Manual Reports – Transmission – X937 ..................................................23

VIII. Impacts on RemitTrac Reporting When Using Check 21 Processing......................................................................................... 28

IX. Other Points to Consider ............................................................. 28

Special Setup Requirements for Check 21 and ARC Processing Page 1 of 29

Special Setup Requirements and Workflow for Check 21 and ARC Processing

This document is intended to be used as a quick guide to cover special setup requirements and workflow processing for Check 21 batches. In addition to basic requirements for configuring site and lockbox settings, several setup features specific to Check 21 and ARC* processing are outlined in Section I of this document. The X9.37 output file generation process also requires an X9.37 Configuration File as discussed in Section II. In addition, parameters specific to Check 21 processing in the Track Control Configuration File are discussed in Section III, Workflow procedures for Check 21 are discussed in Section IV, and modifying the check field for payment items using Data Editor are included in Section V. The generation of the X9.37 output file and ACH output file and unsetting X9.37 flags on Check 21 batches are discussed in Sections VI and VII, the impacts on RemitTrac reporting are listed in Section VIII and points of consideration regarding Check 21 processing are included in Section IX.

I. Special Site and Lockbox Setup Requirements IMPORTANT: Before making any modifications to your Site and/or Lockbox Setup settings, you must first bring down the Batch Scheduler and Set Encode background functions and the Transport Manager on the transport workstation. When you are done making modifications to the setups, you can restart the Batch Scheduler and Set Encode background functions and initialize the Transport Manager. If this process is not followed, the modified settings will not be used when processing work through the system. It is recommended that changes to the Site and/or Lockbox Setup settings are made at the beginning of a processing day before running new work, or at the end of a processing day so that the changes are present for processing on subsequent days. It is not recommended that these types of changes be made to setups in the middle of a processing day.

A. Site Settings for Check 21

1. In Configure Management under the “Site Info – Settings” tab, both the “Enable Check 21 Processing” and “Transmit Special Chars” check boxes must be enabled, as shown in Figure 1 on page 2.

The Enable Check 21 Processing option enables Check 21 processing for the site and forces the inclusion of special symbols in the MICR line fields. These characters are required for X9.37 output file generation and/or IRD printing.

The Transmit Special Chars (“Characters”) option enables the ability to set the site level default for including special symbols for MICR line characters in non-X937 output files, such as Standard Invoice, Intraday or other custom output files. These MICR line symbols include the dash, forward slash (/) and space characters for storing and defining the Routing and Transit (“RT”), Auxiliary (Aux) and Account Number values in the output files.

* Contact ImageScan for more information the ARC module.

Select Enable Check 21

Processing and Transmit

Special Chars

Figure 1. Site Information - Settings tab – Check 21 options

2. Optional. If your site does not have a physical transport for encoding work, in Configure Management under the “Site Info – Settings” tab, select the “No Physical Encode Transport” check box, as shown in Figure 2.

Figure 2. Site Information - Settings tab – Check 21 options

Select No Physical Encode

Transport


B. Lockbox Settings for Check 21

1. Lockbox Revised - Options tab

a. Select the “Check 21 Processing” check box to enable Check 21 processing for the lockbox.

b. Select the MICR Repair checkbox and all five MICR fields (Aux, R/T, Account, Tran Code and EPC). All five fields MUST BE selected.

c. MICR Repair MUST BE performed Before Encode.

Figure 3. Lockbox Revised – Options tab – Check 21 Processing, MICR Repair Before Encode and all five MICR Fields selected

Enable the Check 21 Process

option to allow Check 21 batch processing

for the lockbox

Select Before Encode for

MICR Repair

Select MICR Repair and all

five fields

2. Lockbox Revised - Contacts tab

a. To generate reports, including the (937) Block Ticket Report, (937) Block Exception Report and the Exception Report that are automatically generated and printed as part of the X9.37 output file generation process, make sure that the Reports check box on the Contact Address window is enabled for at least one contact. See Figure 4 on page 4.

b. To generate image copies, make sure that the Image Copies check box on the Contact Address window is enabled for at least one contact. See Figure 4 on page 4.

c. Make sure that the number of image copies for the contact is set to at least 1. See Figure 5 on page 4.


Select Image Copies to generate image copies

Select Reports to generate reports

Figure 4. Lockbox Revised - Contacts tab - Image Copies and Reports options

c. From the Contact Address window, choose Image Copy Instructions to display the Image Copies – Special Instructions window. Set the number of image copies for the contact to at least 1 as shown in Figure 5 and choose Save.

Set the number of Image Copies to at

least “1”…

…then choose Save

Figure 5. Image copies set to at least 1 for the contact


3. Lockbox Revised - Transport Options tab – the Front and Rear checkboxes for both the Capture Pass Payment and Capture Pass Scan Doc MUST BE enabled. Rear images are required when a type change is performed on an item.

Figure 6. Lockbox Revised - Transport Options tab – Capture Pass Payment and Scan Doc Front and Rear checkboxes enabled

Front and Rear checkboxes for

both Payment and Scan Doc

must be enabled

4. Lockbox Setup – Retail (Form) - Transport tab - For a retail form, the Front and Rear check boxes for both the Capture Pass RemitDoc and Capture Pass Payment MUST BE enabled. The transport settings defined for the retail form override the transport settings defined for the lockbox account. Rear images are required when a type change is performed on an item.

Figure 7. Lockbox Setup – Retail Form Scanline - Transport Options tab – Capture Pass RemitDoc and Payment Front and Rear checkboxes enabled

Front and Rear checkboxes for both RemitDoc

and Payment must be enabled


5. Lockbox Setup – Retail (Form) - Pocket Assignments tab – If a Check 21 outsort pocket is defined in the Track Control Configuration file (TrakCntl.ini), the outsort pocket cannot be included in the range of pockets defined for the retail form.

In the example that follows, the transport has 8 physical pockets. Pocket 8 is defined as the Check21Outsort pocket in the Track Control Configuration file as illustrated in Figure 8. Figure 9 illustrates the pocket assignment settings for the retail form. In the example, Deposit Outline ID 1 defines the payment pockets as pocket 2 for 3 pockets (pockets 2, 3 and 4) and Deposit Outline ID 2 defines the remittance pockets as pocket 5 for 3 pockets (pockets 5, 6 and 7). Pocket 8 is not included in these pocket assignments and therefore will be used for out sorting the Check 21 IQA failure and Foreign items during the Encode pass.

NOTE: For additional information on defining a Check 21 outsort pocket, see Section III - Track Control Configuration File on page 11. For Retail, if no outsort pocket is defined, Check 21 IQA failure and Foreign items are outsorted to the reject pocket defined for the retail form. See Figure 9 for reject pocket definition.

; New Global or Machine level [WKSxx] variables ; Values passed from TrackManager to Transport thru, SXX Variable only works for NCR

IQATest = YES ; Tell the Track to Turn on IQA Tests, NCR 4.0 only

Check21OnTrack = YES ; Tell the Track to allow Check21 Batches to be outsorted

Check21Outsort = 8 ; Tell the Track the Pocket for Check 21 Outsorts

Figure 8. Track Control Configuration File – Defining the Check21Outsort variable

Reject pocket assignment defined for the retail form

Pocket assignments defined for the retail form

Figure 9. Pocket assignments for the retail form


6. Lockbox Revised - Deposit tab – the deposit outline for each lockbox MUST include a DDA number.

Figure 10. Lockbox Revised - Deposit tab - DDA Number


C. Site and Lockbox Settings for ARC Processing The Accounts Receivable Conversion (ARC) workflow process enables processors to convert original, paper-based items into electronic debit transactions that can be transmitted electronically for deposit. ARC processing is used for both the site and lockbox if the Account Receivable Conversion option is selected in the setup information for the site and lockbox.

NOTE: In order to utilize ARC Processing, the site and lockbox must also be set up for Check 21 Processing. For details on setting up a site and lockbox for Check 21 Processing, see “Site Settings for Check 21” on page 1 and “Lockbox Settings for Check 21” on page 3.

Enter a DDA Number

1. Configuration Management – Site Info - Settings tab

a. Select the “Enable ARC Processing” check box to enable ARC processing for the site.

Figure 11. Site Information - Settings tab – ARC Processing option

2. Lockbox Revised - Options tab

a. Select the “ARC Processing” check box to enable ARC processing for the lockbox.

Figure 12. Lockbox Revised – Options tab – ARC Processing

Select Enable ARC

Processing

Select ARC Processing



II. X937 Configuration File The X9.37 output file generation process uses an X937 Configuration file (X937Config.ini). The X937Config.ini file is stored in the Remitrac\Sitnnnnn directory on the Database Server, where “nnnnn” represents your Site No. For additional details on the X9.37 configuration file, see the document “X937 Configuration File.”

The X9.37 output file defines the following for X9.37 output file generation:

1. Site ID

2. X9.37 Output File Encoding format, ASCII or EBCDIC

3. Destination information for Check 21 batches:

Name of the institution that receives and processes the file

Routing and Transit Number for the institution that receives and processes the file (requires 9 numeric characters)

4. The original contact information:

Name of the contact person at the institution (i.e., originating bank) that creates the file

Phone number of the contact at the institution (i.e., originating bank) that creates the file (requires 10 numeric characters; no dashes allowed)

5. Electronic Return Acceptance Indicator – Code that indicates whether the institution that creates the Check Detail Record will or will not support electronic return processing. Set to a value between 0 - 9 or A - F. Refer to the Sample X937Config file sample for definition of the valid indicators.

6. Test Indicator – Defines whether to create and transmit the X.937 file as a test output file or a production output file. Set to a value of “T” for Test or “P” for Production.

7. TrimSlashInAuxField – Defines whether to include the Slash (/) in the Aux field (Field 2) of Record 25. Set to a value of “Y” to suppress the Slash (/) or “N” to include the Slash (/).

8. FilterTray – Defines whether all of the batches in a tray of work must be encoded before any batch in the tray is included in the file. Set to a value of “Y” if all of the batches in a tray of work must be encoded before any batch in the tray is included in the file. Set to “N” (or leave the variable blank) to include a batch in the file regardless of the encode status of other the batches in the same tray of work.

9. Endorse – Enables the virtual endorsement of data on the rear image of a payment item. The virtual endorsement can be viewed using an X937 File Viewer. Set to a value of “Y” to enable the virtual endorsement. Set to “N” (or leave blank) to not use a virtual endorsement


10. SuppressMessage – Defines whether to suppress the item detail messages that are displayed in the Event Logger during the X.937 file generation process. Suppressing the item detail messages will help decrease file generation time. Set to “Y” to suppress item detail messages or “N” to keep item detail messages in the logger.

NOTE: If set to “N,” error messages and other necessary processing messages are still written to the Event Logger.

11. Blank_EPC* - Defines whether to remove the EPC field from the output file. Set to a value of “Y” to remove EPC field data or to “N” to keep EPC field data.

12. Enable_FED* - Defines whether to generate the X937 file according to Federal specifications. Set to a value of “Y” when sending transmission to the FED or to “N” when sending transmission to Wells Fargo.

13. Immed_Orig_Name* - Defines the value for File Header Record 01 - Field 10 and Cash Letter Control Record 90 - Field 6. If the variable is left blank, the bank name from the database is used.

14. Country_Code* - Defines the value for the File Header Record 01 - Field 12. Set to “US” when transmitting to Wells Fargo. Leave blank or do not include in the configuration file when transmitting to the FED.

15. Fed_Work_Type* - Defines the value for the Cash Letter Header Record 10 - Field 13. Set to a value of “C” when transmitting to Wells Fargo. Leave blank or do not include in the configuration file when transmitting to the FED.

16. BofD_DepBranch* - Defines the bank of first deposit value for the Check Detail Addendum A Record 26, Field 7.

17. Customized bank settings can be defined that override the GLOBAL settings for Destination Bank, Contact Information, Electronic Return Acceptance Indicator, Test Indicator, TrimSlashInAuxField, FilterTray, Endorse, SuppressMessage, Use_DLN_Sequence, DLN_Field_Position, Blank_EPC, Enable_FED, Immed_Orig_Name, Country_Code, Fed_Work_Type and BofD_DepBranch.

* Custom variable for a site


III. Track Control Configuration File The Track Control Configuration file (TrakCntl.ini) is stored in the Remitrac\Sitnnnnn directory on the Database Server. The file must contain a workstation transport definition for X9.37. This is the workstation that will run the Set Encode background task. Following is a sample workstation setting for X9.37 output file generation:

[WKS11]

MachNumb = 937 ;This one variable is UNIQUE and NOT GLOBAL Transport = X937 ;This is the type of Transport (temporary) MachType = X937 ;This is a machine categorization type

There are several parameters defined in the Track Control Configuration file that are used for Check 21 processing. These parameters can be defined in the [GLOBAL] section or in the workstation section [WKSxx] defined for X937. Workstation level parameters override global parameters. Table 1 summarizes the Check 21 parameters.

Table 1. Check 21 Parameters

Parameter Description Sample Value IQATest* Defines whether to turn on Image Quality

Analysis (IQA) testing for all NCR transports. Yes or No

Check21OnTrack Defines whether the items in a Check21 batch that do not meet Check21 requirements get out sorted during the Encode pass. Items that do not meet Check21 requirements include Foreign (FORN) items and items that fail Image Quality Analysis (IQAF) testing. These items get endorsed and encoded, but are not included in the X937 file presentment.

Yes or No

Check21Outsort** Defines the physical pocket to which the Check21 IQA failure and Foreign items get out sorted during the Encode pass. The Check21OnTrack variable must be set to “Yes” for these items to be out sorted to the specified pocket.

n, where n is the value for the physical pocket

* ImageScan has only qualified IQA on NCR transports running WiseIP version 4.00.xx. If your site uses a WiseIP version other than 4.00.xx, please contact your NCR representative as all IQA transport settings are defined by NCR, not by ImageScan. If the NCR transport does not have WiseIP version 4.00.xx installed, the parameter must be set to a value of “No.” ** If no value is defined for this parameter, the IQA failure and Foreign items are outsorted to the Reject Pocket defined in the Track.ini file (Wholesale) or in the Pocket Assignment (Retail).

Following is a sample of how the parameters appear in the [GLOBAL] section of the configuration file:

;New Global or Machine level [WKSxx] variables

IQATest = Yes ;Tells the track to turn on IQA tests, NCR 4.00.xx only Check21OnTrack = Yes ;Tells the track to allow Check21 batches to be outsorted Check21OutSort = 8 ;Tells the track the pocket for Check21 outsorts

IV. Workflow for Check 21 1. Registration, Capture and Item Processing workflow procedures remain the same.

2. Data Entry can be performed After Capture, Before Encode or After Encode. The Data Entry process does not change with Check 21 processing.

3. MICR Repair will occur BEFORE the SET ENCODE process.

When Check 21 processing is utilized, delimiters present in the MICR line of an item are translated to MICR symbols during processing. The symbols are then displayed in the MICR fields for an item during repair. In addition to symbols, any spaces that are present in the Aux or Account field are also displayed in the MICR field. Table 1 lists the delimiters that get translated to symbols during processing.

Table 1. Translation of Delimiter to MICR Symbol

Delimiter Symbol MICR Field

/ (forward slash) Account or Auxiliary On-Us (Aux)

- (dash) Dash (optional separator for values in the Account, Aux, and RT fields)

During MICR Repair, when correcting a MICR field make sure that you key all symbols or spaces present in a field.

For additional information regarding MICR Repair for Check 21 processing, see the MICR Repair document in the RemitTrac Workflow Manual.

4. Once item processing (including MICR Repair) and balancing are complete, the SET ENCODE process occurs. SET ENCODE is a background task that replaces the Encode pass for Check 21 processing. It is required that the SET ENCODE background task be run on a standalone workstation.

The SET ENCODE process sets the ENCODE flag on Check 21 batches and on the non-foreign, non-rejected, and non-zero items included in those batches. These batches and items are included in the X9.37 output file.

Items processed and marked as Foreign (“Yes” to the question Is this Item Foreign?) during Foreign Item Repair are not marked as Encoded by the Set Encode background task and are not included in the X9.37 output file.

Items rejected during Item Processing are not marked as Encoded by the Set Encode background task and are not included in the X9.37 output file.

Check 21 batches that contain Foreign items, IQA failure items and/or item processing rejects are scheduled for the Encode Pass. During the Encode pass, any Foreign and IQA items are out sorted from the eligible Check 21 items and all Item Processing rejects are placed in the reject pocket.



NOTE: If your site does not have a physical transport for encoding work, and the “No Physical Encode Transport” check box in Configure Management under the “Site Info – Settings” tab is selected, the Check 21 batches that contain Foreign items, IQA failure items and/or item processing rejects will not be scheduled for the Encode Pass. These items must be manually removed from the batch and processed using your site’s requirements for these types of items. See “Site Settings for Check 21” on page 1 for information on the “No Physical Encode Transport” option.

5. The X9.37 output file is generated through the Manual Reports Interface on the Transmission tab. See Section VI – X9.37 and ACH File Generation for Check 21 Batches on page 17.

IMPORTANT: The X9.37 MICR Validation Utility can be used to generate a text file that contains the MICR fields for the payment items included in an existing Customer Intraday file that have invalid or missing MICR data. The contents of the X9.37 MICR Validation file can then be used to verify which MICR fields need to be corrected before generating an X9.37 output file. For more details on this utility, refer to the “X9.37 MICR Validation Utility” document.

Depending on the types of items in the batches (Eligible Check 21, ARCd, IQA, Foreign, Item Processing Rejects) an Electronic Block - Check21 Report, Electronic Block Exception Report, Electronic Block - ARC Report, Electronic Block Summary Report, and Exception Item Report by Process Day Report are automatically printed once the X9.37 output file is generated. These individual reports cannot be regenerated; however, the individual reports can be viewed and/or reprinted through “View Reports.” For details on the contents of each of the reports, see the document “Viewing X9.37 Electronic Block and Exception Reports.”

NOTE: A site-level report definition can be created and used to suppress the printing of the Electronic Block - Check21 Report, Electronic Block - ARC Report, Electronic Block – Remittance Report and the Electronic Block Exception Report. For more information, see the document “Suppressing the Automatic Printing of the Electronic Block and Block Exception Reports.”

The automated printing of the Electronic Block Summary Report and Electronic Exception Item Report by Process Day cannot be suppressed. The Electronic Exception by Item Report by Process Day will be printed when exception items exist in any of the batches processed.


The Electronic Block - Check21 Report includes detailed information about encoded batches, and items by type in those batches that processed in the block. Zero dollar batches are also listed on the report.

For Wholesale and Retail work, the Payments section contains information about payments for all lockbox types that processed in encoded batches within the block, including the item sequence number, routing and transit number and encoded amount for each item, as well as the total encoded deposit amount of all payments processed in each batch.

For Retail work, the Remittance section contains information about remittance documents that processed in Retail batches within the block, including the item sequence number, account number captured from the scanline of the remittance document, encoded amount for each item, and the total applied amount of all remittance documents in each batch.

The Report Summary section contains information about all activity from all encoded batches processed in the block. A Report Summary appears in both the Payment and Remittance sections of the report and includes the total number of batches, total number of payments (remittances for Retail), and the total encoded deposit amount of all payments (remittances for Retail) in the block.

The Electronic Block Exception Report includes the same detailed information for encoded batches containing IQA failure and Foreign Items as the Electronic Block -Check21 Report.

The Electronic Block - ARC Report includes the same detailed information for encoded batches containing ARCd items as the Electronic Block - Check21 Report.

The Electronic Exception Item Report by Process Day lists by Lockbox, any batches that were included in the X9.37 output file that contained exception items (IQA failure, Foreign and item processing rejects). For each item, the report lists the transaction number, item sequence number, item type (Remit or Payment), initials of the name of the operator who rejected the item, procedure during which the item was rejected (item processing function, foreign or IQA Failure), Scanline or MICR line and the reject reason. The report also includes Batch Totals, Lockbox Totals, and Report Totals for the number of payments, remittances, scan docs, rejects at registration and deleted batches.

The Electronic Block Summary Report provides a summary of the Payment Counts and Block Totals from the Electronic Block - Check21, Electronic Block - ARC, and Electronic Block Exception reports. The report also provides a Remittance Item Count, Remittance Block Total, count of the Payment Only items, total dollar value for all of the items processed in the Payment Only batches and a count for the number of batches included in the block.

V. Modifying the Check Field for a Payment in Data Editor In Data Editor, the Check field displays the Check Sequence Number for a payment item. By default, if a payment item has an Aux, the Aux value is stored as the Check Sequence Number and is displayed in the Check field in Data Editor. If a payment has a Tran Code, but not an Aux, the Tran Code value is stored as the Check Sequence Number. If a payment does not have an Aux or a Tran Code, but does have an Alternate Field 4 value (value to the left of a dash or slash in the Account field), then the Alternate Field 4 value is stored as the Check Sequence Number. If you need to modify the default value stored in the Check Sequence Number, follow the procedures below to manually change the value in the Check field.

To modify the Check Field

1. Click the Edit Check Field check box next to the Check field. The Check field becomes available for editing.

Figure 13. Modifying Check field - selecting the Edit Check Field check box

Click the Edit Check Field box


2. Click inside the Check field and use the BACKSPACE key to delete the numbers that you want to modify. –or–

Use the mouse to highlight the existing Check value and press Delete to clear the field. –or– If the Check field is empty, click inside the Check field.

3. Type in the new value for the Check field, then click on Save.

Figure 14. Modifying Check field – saving a new value in field

The change is reflected in the Check field and the field is grayed out.

Figure 15. Modifying Check field - change reflected in Check field

…then click Save

Type a new value…

Change made in the Check field


4. When you are done modifying the Check field for an item in a batch, choose Edit Complete. The Edit Complete option informs the system to update the database with the new information.

NOTE: When the Edit Complete option is selected, messages regarding the rescheduling of the modified batch for Lockbox Archive, Float, or Image Print will be displayed if the lockbox is setup for those features.

VI. X9.37 and ACH File Generation for Check 21 Batches X937 and ACH output files are generated using the X937 Output File program under Manual Reports. Only those batches processed for Check21 lockboxes are included in either an X937 output file or an ACH output file. When the X937 Output File program is run, each item in a batch is evaluated to determine if it can be ARCd. If an item can be ARCd, then the item is marked as an ARCd item in the database and is included in an ACH output file. If an item cannot be ARCd, then it is marked as a Check 21 (CK21) item in the database and is included in an X937 output file.

NOTE: X937 and ACH output files do not include items that failed Image Quality Anaylsis (IQA), Foreign items, or item processing rejects.

To generate an X9.37 and ACH file

1. From the Manual Report – Transmission tab, select the X937 File option.

Figure 16. Manual Reports – Transmission tab – X937 File

The X9.37 File Generation window is displayed on the screen as shown in Figure 17 on page 18.

Select X937 File


The default settings on the X9.37 File Generation window are Default Bank for the bank selection and Process Day and Current Day for the date selection.

Figure 17. X9.37 Report Generation window – default settings

Default settings

3. The X9.37 output file generation can be performed for the default bank or a selected bank (can run for all Check 21 lockboxes or selected Check 21 lockboxes), multi-bank (all Check 21 lockboxes only), or a Group.

Figure 18. Report Generation window – bank selection

Select Default Bank, All Banks

or Selected Banks


Figure 19. X9.37 Report Generation window – lockbox selection

Figure 20. X9.37 Report Generation window – group selection

If you selected Default Bank or

a single Selected Bank

you can choose All Lockboxes

or Selected Lockboxes

Choose the Bank(s) and lockboxes (if Default or a single Selected Bank is chosen) to include in the file and then choose Generate

To generate the file for one or more

group(s), enter the group name(s) on

the Group tab…

…then choose Generate

4. Choose Generate.


Once you choose the Generate command, the progress message, as shown in Figure 21, is displayed on the screen.

Figure 21. Progress message displayed during output file generation

During the output file generation process, data is compiled for the output file based on the bank, lockbox and/or group selections and process date selected. Once the data is compiled and generated for the file, the “X9.37File Generation Complete” message shown in Figure 22 is displayed on the screen.

Figure 22. X9.37 File Generation Complete message

While the X937 output file generates in the background, the Event Logger displays information about the file generation process. Figure 23 displays an example of the information captured by the Event Logger during file generation.

Figure 23. Event Logger showing the report generation processes

NOTE: Check the Event Logger for status messages to determine whether a problem exists if the X937 output file fails to generate properly.



X9.37 ouput files are stored in the Remitrac\PDD\rmtdnnnnn\X937File directory, where “nnnnn” represents the two-digit year and Julian date (number of the day within the specified year). For example, rmtd08154\X937File represents a directory that contains X937 output files created on June 2, 2008. In this example, “08” represents the year 2008 and “154” represents the 154th day (June 2) of the current year (2008). The file name is X937BankXXX.NNN, where XXX is the Bank ID and NNN is a value between 001 and 999. Each time an X9.37 output file is generated on a process day, the file extension is incremented by a value of 1 (i.e., .001, .002, .003. etc.).

NOTE: ACH output files are stored in the same directory as the X9.37 output files. The file name is ACHBankXXX.NNN, where XXX is the Bank ID and NNN is a value between 001 and 999. Each time an ACH output file is generated on a process day, the file extension is incremented by a value of 1 (i.e., .001, .002, .003, etc.). An ACH output file will have a corresponding X937 output file.

X9.37 output files can be viewed using an X9.37 File Viewer. ImageScan uses the X9 Viewer provided by All My Papers. For additional information, see the “All My Papers Viewer” document.

Reports are generated and printed (unless printing has been suppressed through a site-level report definition) if a printer is mapped to the workstation. Reports are stored in the Remitrac\PDD\rmtdnnnnn\Report directory, where “nnnnn” represents the two-digit year and Julian date (number of the day within the specified year). You can also use the View Reports program to view an on-screen copy of the reports. See the “View Reports” in the Tools section of the RemitTrac Workflow Manual for information about viewing reports online. For sample reports and information on the contents of each of the reports, see the document “Viewing X9.37 Electronic Block and Exception Reports” or for basic report descriptions, see Section IV – Workflow for Check 21 on page 12.

Once a batch is included in an X9.37 output file for the processing day, that batch can only be included in subsequent X9.37 output file generations for the lockbox if the X937 flags are unset for the batch. The Data Editor tool can be used to unset the X937 flag for individual batches or the Manual Reports – Transmission – X937 option can be used unset the X937 flags for all the batches included in an X9.37 output file. See Section VII – Unsetting the X9.37 Transmission Flag on page 22.

VII. Unsetting the X9.37 Transmission Flag The Data Editor tool can be used to unset the X937 flag for individual batches. The Manual Reports – Transmission – X937 option can be used to unset the X937 flags for all the batches included in an X9.37 output file.

A. Data Editor

In Data Editor, you can unset the X937 transmission flag for a batch from the Manage Batch Flags window. For example, if you modify a batch that was already included in a output file, and you need to include the corrected data in a new output file, you can unset the X937 transmission flag for the batch and then generate another X9.37 output file.

When you first open the Manage Batch Flags window, the transmission flags that are currently set for the selected batch are displayed in the Transmission Flags area. A check mark () indicates that the batch was included in a previous output file. For example, in Figure 24 on page 22 the X937 flag is set for the batch.

X937 flag is currently set for the batch

Figure 24. Transmission Flags – X937 Flag set

To unset the X937 transmission flag for a batch

1. From the Manage Batch Flags window, under the Transmission Flags area, unmark the X937 Set check box.

Figure 25 through Figure 26 illustrate how to unset the X937 flag for a batch. The check mark shown in the X937 Set check box in Figure 25 is removed in Figure 26, indicating that the X937 flag for the batch will be unset when you choose the Change Flags option, as illustrated in Figure 27 on page 23.

Figure 25. X937 Flag option Set

Figure 26. X937 Flag option unset

X937 flag is set for the

batch X937 flag is unset for the

batch


2. Click on Change Flags.

Click on Change Flags

Figure 27. Change Flags option

3. Choose Close to close the Manage Batch Flags window. The Workdays/Deposits tab is displayed.

B. Manual Reports – Transmission – X937 The Manual Reports – Transmission – X937 option can be used to unset the X937 flags for all the batches included in an X9.37 output file.

To unset the X937 transmission flag for all batches included in a previous X9.37 output file

1. From the Manual Report - Transmission tab, select X937 File.

Figure 28. Manual Reports – Transmission tab – X937 File

Select X937 File


2. From the X9.37 File Generation window, click on the Reset Flag tab.

3. Select the current process day, a range of process days, or a specific process date for which you want to view the X9.37 output files generated.

The Current Process Date option is used to display X9.37 output files generated on the current process day. The Current Process Date option is the default date selection for the utility.

The Range of Dates option is used to display X9.37 output files generated between two dates, or within the date range. To set the date range, you must select both a Start Date and Stop Date.

The Other Date option is used to display X9.37 output files generated on a specific process date. To use the Other Date option, you must also select a process date from the Start Date list.

Figure 29. Selecting a date option on the Reset Flag tab

Click on Reset Flag

Select a Date option…


4. Choose Display Files. The files for the selected date or range of dates are displayed in the X9.37 Output Files List.

Choose Display Files

List of the X9.37 output files generated for the selected date(s)

Figure 30. Displaying the X9.37 output files for the selected date option

5. Select an X9.37 output file to display the list of batches included in the file.

Figure 31. Displaying the batches included in the selected X9.37 output file

Select an X9.37

output file

List of the batches included in the selected X9.37 output file


6. To reset the X9.37 flags for all batches in a selected file, choose Reset X937File Complete Flag.

Figure 32. Using the Reset X937File Complete Flag command

Choose Reset X937File

Complete Flag

The Confirm Reset message shown in Figure 33 is displayed on the screen.

Figure 33. Reset flags confirmation message

7. Choose Yes to reset the X937 flags for all the batches in the selected file. –or– Choose No not to reset the flags.

If you choose Yes, the Resetting batches messages shown in Figure 34 is displayed on the screen.

Figure 34. Resetting Batches message


Once the flags are reset, the file is removed from the X937 File list as shown in Figure 36. The file is moved from the Remitrac\PDD\rmtdnnnnn\X937File directory to the Remitrac\PDD\rmtdnnnnn\X937File\X937Reset directory for the batch’s original process day.

Figure 35. X937 File List before resetting the flags

Figure 36. X937 File List after resetting the flags

X9.37 Output File List before resetting the flags for the batches included in the X937bankAEA.002 file

X937bankAEA.002 file for RMTD08133 is removed from the list after resetting the flags



VIII. Impacts on RemitTrac Reporting When Using Check 21 Processing

Configuration/Site Setup Report includes the options for Enable Check 21 Processing and Transmit Special Characters. However, the Lockbox Setup Report does not include the option for Enable Check 21 defined at the lockbox level.

Any administrative changes made in Data Editor after the X9.37 output file generation will not be reflected in the X9.37 output file. All internal bank reports will reflect administrative changes to the batch that were made in Data Editor.

MICR Line fields included on the Foreign Item Report will show any special characters keyed in MICR Repair.

Operator has the option of including or excluding in an Output File, the dash (–), forward slash (“/”), and the space character keyed in the Routing and Transit Number, Account Number and Aux values during MICR Repair. The dash, forward slash and space character are included in output file data for the 04 (Payment) and 05 (Float) Records.

Operator Statistics Report does not include a value for the items processed through Set Encode. However, if you process work through an Encode pass on a transport, the Track Encode Count will include the Foreign and IQA items and the Track Payments Reject will include the rejected items.

Reports that are not generated through RemitTrac’s Manual Reports Interface (i.e., custom coded reports or Reportit reports) that have MICR field data will include the special characters and spaces keyed in MICR Repair (dash, forward slash and space characters).

IX. Other Points to Consider If the value stored in the Check Sequence Number for a payment item needs to be modified, the

Data Editor tool can be used to make any necessary modifications. For detailed instructions on modifying the check field for a payment, see Section V - Modifying the Check Field for a Payment in Data Editor for a Payment on page 15.

Image Quality Anaylsis (IQA) - ImageScan has qualified IQA on NCR transports running WiseIP version 4.00.xx. If your site uses a WiseIP version other than 4.00.xx, please contact your NCR representative as all IQA transport settings are defined by NCR, not ImageScan. If the NCR transport does not have WiseIP version 4.00.xx installed, the IQATest parameter in the Track Control Configuration File (TrakCntl.ini) must be set to a value of “No.”

Due to the fact that the lockbox must be set up for MICR repair on all five fields (RT, Tran, AUX, Account and EPC), there will be an increased number of items that are presented for MICR Repair.

Any special characters keyed in the MICR fields during MICR Repair are not displayed in the fields during Data Entry.


As a default, payments that are processed through Set Encode do not receive the encode endorsement that is defined in the database for the lockbox. The encode endorsement is printed only on the payments that are encoded on a physical transport (i.e., IQA failure and Foreign Items).

You can however define settings that will provide a “virtual” endorsement on the payments processed through Set Encode that are included in the X9.37 output file and do not get encoded on a physical transport (non-foreign, non-rejected and non-zero items). A “virtual” endorsement can contain up to four lines of text. Each line of endorsement is stored in a user defined data entry field. The user defined data entry fields are defined in the Encode section of the Bank Data Configuration file (BankData.ini).

When an X9.37 output file is generated, the payment’s captured rear image is copied and the virtual endorsement is overlaid on the image. The virtual endorsement is not stored as part of the RemitTrac image file and can only be viewed on the image using an X9.37 File Viewer.

NOTE: The virtual endorsement text for a payment item is also included in the user defined data entry fields (DENFld line) of a Manage Flags dump file.

Documents

Table of Contents - ImageScan€¦ · Table of Contents . ... The generation of the X9.37 output file and ACH output file and unsetting ... ASCII or EBCDIC 3