Skip to main content
Avalara Help Center

Geo SaaS Standard to Geo Batch API migration guide

AFC Geo SaaS Standard allows customers to geocode multiple US addresses within a batch input file that is uploaded to an FTP server. The Geo SaaS Standard functionality will be disabled on March 31, 2020. The ability to geocode multiple addresses in a batch file is still available via new Geo Batch REST API endpoints. See the AvaTax for Communications Developer Guide for the full Geo Batch API documentation.

A warning icon

All customers that use Geo SaaS Standard will need to migrate to the Geo Batch REST API endpoints before March 31, 2020.

 

Key differences

There is very little difference in the functionality between Geo SaaS Standard and the Geo Batch REST API endpoints. This migration document is intended to assist in the transition by providing a breakdown of the key differences.

  File transmission method File formats File name requirements
Geo SaaS Standard Files uploaded to ftp.billsoft.com
  • *.LTL (latitude/longitude combinations)
  • *.TXT (addresses)

See this guide for details on the required column headers.

Specific filename formatting is required, and each file name must be unique.
Geo Batch API Files sent via REST API

*.CSV (for both addresses and latitude/longitude combinations)

See this guide for details on the required column headers.

There are no specific filename formatting requirements.

File names do not need to be unique.

Differences in column headers

Several Geo SaaS Standard column headers are not available via the Geo Batch REST API. They are still factored into the results, but default to the following values:

Column header Default value
Minimum Score 0.7
Offset 3
CASS certify flag True
Options 312

 

  • Was this article helpful?