MICR Codeline Match Parameters

Table 1 shows the parameters in the profile that are used to control MICR codeline matching. The name of each parameter is made up of the field name (one of the column names in the table) substituted for the fieldname portion of the parameter name listed in the table. The X indicates to which fields the parameters apply. The default value column shows the default profile parameter value.

Table 1. MICR Codeline Matching Parameters
Parameters Aux OnUs Field EPC Field Routing Field OnUs 2, 3, and 4 Fields Amount Field Default
fieldnameAcceptableNumOfDE X X X X X 1
fieldnameIgnoreSelectorFieldDE X X X X X off
fieldnameIgnoreLeadingZeros X   X X   off
fieldnameZeroForAble         X off
fieldnameMissingFieldMatches X       X on
fieldnameIncludeDashes X   X X   off1
fieldnameRoutingCorrection     X     off
Note:
  1. Dashes are on for fields to which this parameter does not apply
AcceptableNumOfDE
With these parameters, a user defined maximum number of digit errors in the applicable MICR codeline fields is set. If the maximum number of digit errors involved in a field match is exceeded, a match is not possible. Increasing this value increases the chance of matching codeline values.
Note: Characters that are matched with Don’t Care characters do not count against the AcceptableNumOfDE value.

IgnoreSelectorFieldDE
With these parameters, the match engine is instructed to ignore digit errors in the codeline fields that are supplied with the analyzeWithCodeLine() function call. This allows for matching only on good characters within the supplied fields. If an entire selector field contains digit errors and they are specified to be ignored, a match is highly likely. The only exception to this is if the field lengths of the selector field and the MICR codeline field are different.

IgnoreLeadingZeros
With these parameters, the match engine is instructed to ignore leading zeros in both the applicable selector field and the MICR codeline field. For example, the value 000004271 read from the MICR codeline On Us 2 field matches a value of 04271 or 4271 in its corresponding selector field.

ZeroForAble
With this parameter, the match engine is instructed to substitute zero characters for the character "A", which is used as high order digit padding by some capture sources in the amount field.

MissingFieldMatches
With this parameter, the match engine is instructed to assume a match on the amount field if the field is missing from the MICR codeline image. This field is printed on the document post processing at the capture source. Sometimes, it is not printed and this parameter is used to force the match.

The matching of the AuxOnUs field can also be configured to assume a match if the field is missing from the MICR codeline image. This allows institutions to use the AuxOnUs field for their own use when it is not present on the original image.

IncludeDashes
With these parameters, the match engine is instructed to keep or discard dash characters read from the associated field of the MICR codeline. As a result, dash characters are included or excluded in the match.

RoutingCorrection
This parameter is used to instruct the match engine to attempt to correct a single digit error in the MICR routing field that Image Compliance read from the image before the actual match began. The MICR routing field can appear in the following formats:
  • nine-character format
  • four-four (4-4) format
  • five-three (5-3) format (Canadian)
The routing correction is only attempted when the routing field is in the nine-character format.
The following rules apply as to whether correction is attempted by Image Compliance:
  • The MICR routing field does not contain the following characters: "-" (dash), "a", "b", or "c". The "a", "b", and "c" characters indicate Image Compliance found a special symbol where data is expected.
  • The MICR routing field does not contain a digit error in the position where the dash would appear in the 4-4 or the 5-3 formats.
  • The MICR routing field does not contain more than a single digit error in its nine (9) characters.

When Image Compliance performs this MICR routing field digit error correction, the XML output for the routing field contains an attribute called correction, which contains a value of pos1 through pos9 to indicate which position was corrected.