Postal code, ZIP code and CAP: matching address fields safely
Why similar labels can mean the same format but still refer to different addresses.
6 min read · Updated August 9, 2026The label is only half the meaning
ZIP code, postal code, postcode and CAP commonly describe the routing code within an address. That makes them good candidates for semantic matching. It does not mean every postal-code field should receive the same saved value.
The owner’s home, current residence, registered office, local unit and correspondence address may each have a different code. Accurate matching uses the field’s surrounding heading, person role and address type.
Use a structured address
Save street, building number, city, province or state, postal code and country as separate values as well as a complete address. Structured values let a form request one component without forcing software to split a sentence and guess.
- Preserve leading zeroes.
- Do not translate official place names.
- Keep province codes separate from country codes.
- Store registered-office and residential addresses under distinct roles.
What uncertainty should look like
An uncertain match should be visible before it is written to the page. A confirmation panel can show the proposed value, the source document, and why it matched. Confirming the value improves the current form without silently changing unrelated saved data.
A low-confidence value should never be presented as complete. Leaving a field blank is safer than putting a plausible address in the wrong legal section.
A fast review test
Read the heading above the field and finish the sentence: “This is the postal code of ___.” If the answer is not obvious, open the field explanation or the issuing authority’s guidance. That small test catches most address-role errors.