Address Verification for Salesforce

These addresses are always hard to deal with. The status means an apartment, suite or other secondary number was given on the street line, and it isn't recognized. That can happen for many reasons. The number might be wrong, or a typo. It might also be correct but unregistered.

The only way to know for sure is to ask the person. Even then, if the number is correct, the mail carrier might not deliver to it. The regular carrier might know that "Apt A" is a certain door, but a different carrier on another day might not, because the door isn't marked.

Each business needs to decide how to treat these addresses. Whatever you decide, follow up to make sure the number isn't a typo.

The import runs in batch mode to create the records. Salesforce refuses to start a batch process from inside a batch process. Our app has to run in batch code, so it cannot be called from a batch process.

We recommend a job that runs once a night, or more than once a day, to verify the imported records.

If you buy your Smarty.com lookups through us, to get the discount on the app, we check your use once a month. If you get close to your annual number, you choose: upgrade to a bigger package, or wait until the end of your license term and pay an overage at the same rate as your current package. The best choice depends on how far over you will go.

If you buy your lookups directly from Smarty.com, you can set up an automatic renewal. Without one, the lookups stop working when you reach the limit. This does not happen if you buy through us.

The full error also says: "If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names."

This happens because Salesforce adds new fields with each release. Sometimes these fields are not fully available to all clients, and errors like this one appear. Upgrade to the latest version of our app to fix it.

First, make sure the object's page layout has a section called "Address Information". You can change this name in the Object Setup on the Configure page.

If the error stays, do this:

1. In Setup, search for Tabs.
2. Under Custom Object Tabs, click New.
3. For Object, choose √ Layouts, the Address Verification layout object. Pick any tab style.
4. Click Next, then Next, then Save.
5. Open the App Launcher and search for √ Layouts.
6. Delete all the records you find there.
7. Open the Auto Complete page again. It rebuilds these records.
8. You can now delete the tab you created.

1. Open Configure, then Data Mapping.
2. Edit the object you want to run the batch job on. If it isn't listed, click "Add Support Object".
3. In the object, click the Active Job Id Field.
4. Paste the API name of a text field that already exists on the object. The field must hold at least 18 characters.

If this value is blank, no batch jobs can run on the object.

The Deputy object is a temporary object used during verification. Our batch jobs work in three steps:

1. The address on the source record is copied to a new Deputy record.
2. The Deputy records are verified. This avoids the slowdowns that flows, triggers, record locks and validation rules cause on the source records during a batch job.
3. The verified data is copied back to the source records.

After that, the Deputy records are marked complete, and a scheduled Apex job deletes them. The implementation guide shows how to set up that scheduled job.

Update these fields, and Address Verification treats the address as fully verified, the same as through its own process:

• Verified checkbox: TRUE.
• Last Verified date and time: today.
• Return Code: "Confirmed".
• Footnotes: "Manually Set to Verified", or similar.

No. Smarty.com does not support the NCOA database. It used to, but its clients did not find it useful enough. You can read more on Smarty.com:

• Will your service tell me if somebody lives at an address?
• Is Move Update (NCOA) required?

We send no personally identifiable information (PII) in the calls to outside data services, such as Smarty.com or the email and phone services. We don't even send a record ID that could trace a call back to a record in your org. That information stays inside your Salesforce org, and we have no access to it. We stay out of PII handling completely.

The app is installed entirely in your own Salesforce org. When you install it, you give it access to your fields and objects, but no outside party or system can reach your data. Everything starts from your side. Your org sends anonymous data to the outside services, and they send the corrected data back. That data holds nothing that lets the service connect it to a person, so it is fully PII compliant with all FTC standards.

Smarty.com, which holds the address data and answers our calls, also takes HIPAA and PII seriously:

• Smarty.com and HIPAA
• Smarty.com on personally identifiable information

If you want no trace of your requests at all, Smarty.com sells an "Enhanced Data Privacy" upgrade, also called "Incognito mode". It is expensive. Smarty.com describes it this way:

"Enhanced Data Privacy" also referred to as "Incognito mode" is an optional Upgrade feature that Enterprise Clients may elect to purchase which prevents Client Data and or Personally Identifiable Information (PII) from ever being logged at the point of submission to Provider's APIs. Client Data submissions are accessed only momentarily in Random Access Memory (RAM), just long enough to process and deliver results back to Client. Upon completion of such process, any residual Client Data in the System's RAM is dumped or "garbage collected" and written over by subsequent transactions. Such processing methods render requests for data deletion, destruction, correction, blocking, or exportation back to Client not feasible due to the nature of the transitory process.

Yes. By default, a US verification does not change the country. To make it consistent, fill in "Fixed Name for USA Verifications" on the Configure page with "US", "USA" or "United States". Every verified US address then uses that name.

We recommend that you do not show the Verified checkboxes on the page layout. They tell the app whether the address is verified. If a user checks or clears one by hand, the process breaks. Rely on the Status fields for billing and shipping instead.

We recommend only the Status formula field for each address, plus any optional fields that fit your business process. Review the list of fields in the implementation guide. Decide which ones to map so you collect that data, and which of those to show to users.

Users enter the Street, and either the City and State or the Zip code. The verification process fills in everything else.

No. Smarty.com collects updates from USPS and publishes them on the first of each month. Those updates are not pushed into your Salesforce org.

For example, say you verified an address before it was registered. It shows as "Bad or Blank Address" in your org. Only when you verify it again does it come back as a valid address.

Verified US addresses are CASS-Certified to USPS standards. Each other country has its own standards, and the Smarty.com data follows them.

The maximum length depends on the fields you create in Salesforce. The standard Salesforce address fields have these lengths:

• Address.Street: TextArea, 255 characters.
• Address.City: String, 40 characters.
• Address.State: String, 80 characters.
• Address.PostalCode: String, 20 characters.
• Address.Country: String, 80 characters.

Verification usually removes punctuation. "100 Main St." becomes "100 Main St".

No. Verification recognizes some abbreviations, but the verified address spells the city name out.

No. The address might still verify with them there, but the app has an optional field that receives the urbanization code during verification.

The app comes with four permission sets:

• Address Verification (Admin), for anyone who administers the app.
• Address Verification (User), for all other users.
• Two more for Salesforce Site guest users and for Community users.

To assign one:

1. Click the gear icon, then Setup.
2. Open Users, then Permission Sets.
3. Click the permission set you need.
4. Click Manage Assignments, then Add Assignment.
5. Pick the user who needs the app, then save.

You can also set up a Flow that assigns the permission set to each new user.