> This page is for Documentation, version Integration guides (default). > For other versions, use one of these documentation indexes: > - Integration guides (default): https://avalara.ferndocs.com/docs/integration-guides/llms.txt > - Refactor guides: https://avalara.ferndocs.com/docs/refactor-guides/llms.txt > - Get certified: https://avalara.ferndocs.com/docs/get-certified/llms.txt > - Agent to Agent (A2A): https://avalara.ferndocs.com/docs/agent-to-agent-a2a/llms.txt > - AI use cases: https://avalara.ferndocs.com/docs/ai-use-cases/llms.txt > - API versioning: https://avalara.ferndocs.com/docs/api-versioning/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://avalara.ferndocs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://avalara.ferndocs.com/_mcp/server. # Scoring * [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/special-tax-jurisdictions) * [Next Chapter](https://developer.avalara.com/communications/dev-guide_geo_soap/customizing-geocoding-requests) AFC Geo SaaS Pro Soap provides a confidence score when returning a location. The score is based on how well street database values match the input ([address](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/address-geocoding/) or [latitude/longitude coordinate pair](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/lat-long-geocoding/)). A score of 1.0 (100%) indicates an exact match. Scoring is based only on the fields provided in the input - the score is not lowered because you do not include the Zip code, for instance. The score is impacted, however, if incorrect information is supplied, such as the wrong Zip code. ### Address Scoring The values of the address fields are scored based on an algorithm that calculates the minimum number of single-character changes, removals, or additions required to convert the input value into the street database value. The more typos you make, the larger the difference between the input and street database values. A 0 difference produces a perfect score (1.0), and so on. The combined score for the resulting location is computed as a weighted average of the individual scores by field. ### Fallback Score #### 1.01 Score The fallback score is 1.01 and is returned in the event that the address cannot be geocoded, but a match is found using a combination of the zip code, the Zip+4 (if available in the input address), and the location name. The 1.01 score indicates that the geocode data is not available, but the jurisdiction information has been retrieved anyway. A 1.01 score doesn’t impact [CASS validation](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/cass/). The [CASS-validated](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/cass/) address may still be returned in the results if you turn on [CASS validation](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/cass/) (`CassCertify` set to `true` ) and the [CASS validation](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/cass/) process is successful. #### Street Number Snapping Links exist in the data set that do not have an address range assigned due to a new street being digitized, but no houses have been built yet. Links without address ranges are approached using these rules: * Links without address ranges aren't considered unless the Street Number Snapping (Options bitwise value 1) is used * A single street within the address range is used, even if it the only link available * Streets, especially in new developments, may not have any address ranges assigned - AFC Geo SaaS Pro Soap returns an arbitrary segment on the street to get you in the proper area Use Street Number Snapping ([Options](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/options/) bitwise value 1) to return a result when a street number can’t be found in the street database. #### Postal Code Centroid Postal Code Centroid ([Options](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/options/) bitwise value 2) reverts to the centroid of a postal code area when: * Geocoding fails to produce a match * Zip code (`Zip`) is supplied in the input address * Street data set contains at least one street in the Zip code The centroid is a very coarse approximation of the real location. * [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/geocode/special-tax-jurisdictions) * [Next Chapter](https://developer.avalara.com/communications/dev-guide_geo_soap/customizing-geocoding-requests) > **Note** > > Part of the **Communications Geo SaaS Pro SOAP guide** integration guide. [Open the full "Scoring" milestone on Avalara](https://developer.avalara.com/products/communications/integration-guides/dev-guide_geo_soap/geocode/) to see every page in this section.