Table of Contents

Search

  1. Preface
  2. Version 5.16.2
  3. Version 5.16.1
  4. Version 5.16.0
  5. Version 5.15.0
  6. Version 5.14.0
  7. Version 5.13.0
  8. Version 5.12.0
  9. Version 5.11.0
  10. Version 5.10.0
  11. Version 5.9.0
  12. Version 5.8.x
  13. Version 5.7.0
  14. Version 5.6.0
  15. Version 5.5.0
  16. Version 5.4.x
  17. Version 5.3.x
  18. Version 5.2.x

Release Guide (On-Premises)

Release Guide (On-Premises)

United States

United States

Informatica Address Verification introduces the following features and enhancements for the United States:
Support for CASS Cycle O requirements
Effective in version
5.9.0
,
Address Verification
adds features to support the proposed requirements of the Coding Accuracy Support System (CASS) Cycle O standard. The United States Postal Service has not introduced Cycle O certification at the time of the 5.9.0 release.
To prepare for the Cycle O standard,
Address Verification
includes the following features:
  • Private mailbox and commercial mail receiving agency identification.
    The United States Postal Service updates the CASS requirements for private mailbox (PMB) addresses and commercial mail receiving agency (CMRA) addresses in Cycle O. To meet the Cycle O standard,
    Address Verification
    adds PMB as a prefix before a private mailbox number in a CMRA address. If a pound sign (#) precedes a private mailbox number in the address,
    Address Verification
    converts the pound sign to PMB. To comply with the Cycle O standard,
    Address Verification
    does not use the PMB number to verify Delivery Point Validation (DPV) data for an address.
  • SuiteLink verification for default records.
    The United States Postal Service updates the conditions that determine when CASS-certified software must query the SuiteLink reference data.
    The address
    verification
    operation must compare high-rise default and street default addresses to the SuiteLink reference data. Additionally, if an address contains secondary information that does not match a DPV address, address
    verification
    must compare the address without the secondary information to the SuiteLink reference data.
    If the SuiteLink data contains a match with the input address, the address
    verification
    operation must add any valid secondary information from the SuiteLink address to the address. The 11-digit bar code for the updated address must match the bar code for the SuiteLink address.
  • Post office box street address (PBSA) identification.
    The United States Postal Service accepts post office box addresses in a street address format when the street address identifies the post office that contains the box. For example, the following address identifies box number 3094 at a post office on South Center Street:
    131 S Center St Unit 3094 Collierville TN 38027-0419
    The Cycle O standard specifies "Unit" as the post office box descriptor in a PBSA.
    The United States Postal Service adds the value PB as a Delivery Point Validation footnote to a PBSA.
    Address Verification
    writes the value as a DPV footnote.
  • R777 address identification.
    The United States Postal Service assigns physical addresses that do not receive mail to carrier route R777. An R777 carrier route is known as a phantom carrier route.
    Address Verification
    writes the value R7 as a DPV footnote to any address with an R777 carrier route designation.
  • Form 3553 completion.
    Address Verification
    also adds a ZIP+4 3553 flag that indicates whether an address is valid for inclusion in the total address count on Form 3553.
    Address Verification
    returns N for any address that passes delivery point validation but does not include a valid ZIP+4 Code. For example,
    Address Verification
    returns N for an address on an R777 carrier route. When you compile Form 3553, omit any address with a ZIP+4 3553 value of N from the total count.
  • Verification of primary house or building numbers that include trailing alphabet characters.
    If the primary house number or building number in a non-valid address includes a trailing alphabet character, CASS standards permit an address
    verification
    operation to check the address without the trailing character.
Improved parsing of non-standard first-line data in United States addresses
Effective in version
5.9.0
,
Address Verification
parses non-standard mailbox data from the first line of the address to sub-building elements. For example, the non-standard data might identify a courtroom or a college campus mailbox.
Address Verification
identifies C345 as a sub-building element in the following address:
<InputData> <AddressElements> <Country Item="1" Type="NAME">UNITED STATES</Country> <Locality Item="1" Type="COMPLETE">ATHENS</Locality> <PostalCode Item="1" Type="UNFORMATTED">247121000</PostalCode> <Province Item="1" Type="COUNTRY_STANDARD">WV</Province> </AddressElements> <AddressLines> <DeliveryAddressLine Line="1">COLLEGE BOX C345</DeliveryAddressLine> <DeliveryAddressLine Line="2">PO BOX 1000</DeliveryAddressLine> </AddressLines> </InputData>
Support for global preferred descriptors in United States addresses
Effective in version
5.9.0
, you can return the short or long forms of the following elements in a United States address:
  • Street descriptors
  • Directional values
  • Sub-building descriptors
For example, you can configure
Address Verification
to abbreviate STREET to ST and FLOOR to FL. Use the
GlobalPreferredDescriptor attribute
to configure
Address Verification
to return the short or long form or to preserve the form that the input address uses.
You can also configure
Address Verification
to return the element values in the default format of the reference data.

0 COMMENTS

We’d like to hear from you!