What are Batch Match Types and How do they Correspond to Pre-Cleaned Addresses?
Associated product(s): Product name: Batch
Views: 213 | Created: 2 years ago | Last updated: 2 years ago
Countries:
United Kingdom
The table below summarises the various match types employed by QAS Batch and why they are appended to processed addresses with reference to the raw data
MATCH TYPE | CODE | POSTCODE | ADDRESS | ACTION |
VERIFIED | B | ü | ü | Replace Address with PAF Address |
CLOSE VERIFIED | C | ü | Minor mistakes | |
FULL MATCH | D | Missing, incomplete or incorrect | ü | |
EXPANDED MATCH | K | ü | Missing elements, no mistakes | |
CLOSE FULL MATCH | E | Missing, incomplete or incorrect | Minor mistakes | Requires |
POSTCODE VERIFIED | P | ü | Most of address is correct but unable to identify delivery point | |
POSTCODE MATCH | I | Missing, incomplete or incorrect | ||
HALF SECTOR MATCH | H | Missing, incomplete or incorrect | Incomplete, probably to street level | manual |
SECTOR MATCH | G | Missing, incomplete or incorrect | Incomplete probably to street level, perhaps locality level | validation, |
DISTRICT MATCH | F | Missing, incomplete or incorrect | Incomplete probably to district or town level | with |
MULTIPLE MATCH | J | With the address supplied there are several possible addresses | Batch | |
UNMATCHED | A | Batch was unable to match address | Interactive | |
FOREIGN | Z | Contains foreign country, city name or string of numbers at end of address. | ||
BLANK | Y | Batch Automatic could not find any input address fields | ||
UNPROCESSED | L | Signifies that input address was not processed or returned address is too large for output location. | ||
INTERACTIVE ACCEPT | M | Address search in Batch Interactive has produced satisfactory result and has been accepted | ||
INTERACTIVE REJECT | N | No suitable address was found with Batch Interactive and address was rejected by the user | ||
The above table is an approximation of Batch matching and should only be used as a guide.
