Testing Address Errors
When you’re testing your integration, it’s always a good idea to figure out how you’re going to handle errors. Not all errors from our system are bad - some just mean a user has entered an invalid address (perhaps by making a typo!) - and your system should react accordingly. These address-related errors are to be expected in normal use of your connector.
Sometimes it can be challenging to create this use case on purpose: our system is very good at validating addresses and calculating tax accordingly (albeit at lower precision levels). In fact, due to customer demand, we recently updated the service to allow tax calculation on zip5. This is not always the most accurate tax, but if your business only collects zip codes, we’ll give you something to work with.
If you’re looking for an error case, here are some good ways to create one:
Let’s start with a real, valid address. Our address is: 100 Ravine Ln Bainbridge Island, WA 98110
By changing enough elements, we eventually return JurisdictionNotFoundError in the GetTaxResult. Let’s start with the address line:
1000 Ravine Ln Bainbridge Island, WA 98110
There is no 1000 on Ravine Ln, but that alone won’t fail tax calculation because city, state and zip is enough.
1000 Ravine Ln Bainbrid, WA 98110
I truncated the city too, but even that still returns tax because state and zip is sufficient to determine a tax region.
1000 Ravine Ln Bainbrid, WA 43256
When I change the zip, it returns the error, because there just aren’t enough matching elements for the system to find the location. Finally, our error! By moving through each address element in turn, we get a better picture of how AvaTax uses elements in the tax calculation, and its threshold for bad addresses. Of course, if you want to just go for it, you can always generate an error by making sure that none of your address elements match:
521 Totally Bogus Parkway Tacoma, CA 11111