Matching to auxiliary files - centrusdesktop - 2024.01

This section provides information on the matching performed by Centrus Desktop to auxiliary files.

Centrus Desktop performs the following steps when matching an input address to an auxiliary file:

1. Centrus Desktop determines if there is an auxiliary file present.

   Centrus Desktop only accepts one auxiliary file. If more than one auxiliary files is present, Centrus Desktop attempts to match against the first file. Centrus Desktop ignores any additional auxiliary files for matching, regardless if Centrus Desktop found a match to the first auxiliary file.

   If a record within the auxiliary files is invalid, Centrus Desktop returns a message indicating the auxiliary file has an invalid record. Centrus Desktop continues to process input addresses against the auxiliary file, but will not match to the invalid auxiliary file record.

2. If an auxiliary file is present, Centrus Desktop first attempts to match to the auxiliary file.

   Centrus Desktop assumes that the auxiliary file is the most accurate data set and first attempts to find a match to the input address in the auxiliary file. If Centrus Desktop cannot find a match in the auxiliary file, it continues to process as normal against the traditional Centrus Desktop datasets.

   Note: Centrus Desktop only matches your input address lists to your auxiliary file if there is an exact match. Therefore, your input address list should be as clean as possible; free of misspellings and incomplete addresses.
3. If Centrus Desktop finds an exact record match to the auxiliary file, it standardizes the match to USPS regulations and returns the output of the auxiliary file match.
   Note: You cannot update the auxiliary file while Centrus Desktop is running. If you want to update the auxiliary file, you need to terminate Centrus Desktop before attempting to replace or edit the file.

Record type matching rules

When attempting a match against an auxiliary file, Centrus Desktop abides by the rules outlined here.

Street record match:

• The input house number must fall within or be equal to the low an high house number values of the auxiliary record.
• The input house number must agree with the parity of the auxiliary record.
• The input ZIP Code must exactly match the ZIP Code of the auxiliary record.

• The input data must contain both a ZIP Code and address line, and they must exactly match the values on the auxiliary record.
• The input address cannot have any other data, such as a house number, unit number, or Private Mail Box (PMB).

Unavailable Centrus Desktop features

The following list outlines the features that do not apply when Centrus Desktop makes an auxiliary file match:

• Centrus Desktop does not match to

  • two-line addresses

  • multi-line addresses

  • intersection addresses

  • dual addresses

• You cannot use auxiliary file matching when processing in CASS mode.

• Centrus Desktop does not perform EWS, ZIPMove, LACS/Link, or DPV processing on auxiliary matches.

Auxiliary match output

Several standard Centrus Desktop outputs do not apply to an auxiliary match since Centrus Desktop matches to an exact auxiliary match and does not perform any additional validation for the match. For example, Centrus Desktop does not return the block suffix, the check digit, or any DPV enum.

Centrus Desktop provides special data type, match codes, and location code values for auxiliary matches.

When Centrus Desktop finds a match to an auxiliary file, the default output is follows the following conventions:

• Centrus Desktop formats the auxiliary file match as a street-style address for output. This excludes PO Boxes, Rural Routes, General Delivery, etc.
• Centrus Desktop follows the casing setting you indicate (by default, upper case) by the casing function. Centrus Desktop does not maintain the casing in the auxiliary file for mixed casing values. For example, Centrus Desktop returns O'Donnell as ODONNELL or Odonnell depending on the setting of the casing function.
  Note: Centrus Desktop does not change the casing for the User Data field.
• Centrus Desktop removes spaces at the beginning and ending of fields in the auxiliary file.
  Note: Centrus Desktop does not remove spaces for the User Data field.