In orgs using NPSP with the Household Account model, address data on Household Accounts is managed through NPSP Address records (npsp__Address__c), not by editing the Billing Address fields on the Account directly. NPSP copies the record flagged as Default Address onto the Account's Billing fields on every save. Editing the Billing Address directly on the Account will be overwritten by NPSP on the next save.
When the SmartyStreets address verification package (namespace: smartystreets) is also installed, an additional behavior occurs: when a new Default Address is saved, SmartyStreets may re-verify the address against USPS Publication 28 standards and write back an abbreviated form (for example, converting "Appleridge Drive" to "Apple Rdg Dr"). This means that even after correctly marking the long-form Address record as Default, SmartyStreets can abbreviate it again during the save process.
To set a long-form address as permanent default when SmartyStreets is installed, make both changes in a single edit:
NPSP will copy the long-form address to the Account's Billing fields and automatically uncheck Default Address on the previously default record.
Optional — prevent future re-verification on a specific Account: The SmartyStreets package installs a field called Billing Do Not Verify (smartystreets__Billing_Do_Not_Verify__c) on the Account object. Checking this field prevents SmartyStreets from re-verifying that Account's Billing Address on subsequent saves. The Shipping equivalent (smartystreets__Shipping_Do_Not_Verify__c) works the same way.
Note: To change the global address standardization behavior for all Accounts, the controls are in Setup → Custom Settings → Smarty Settings → Manage — an admin-level decision outside the scope of individual record management.
Additional Resources:
005387166

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.