I'm hellping out a buddy w/ Avalara. What is everyone doing to block outgoing restlet calls from their transactions? I've set tax override to checked but still looks like a client avalara transaction log is getting requests that calls a restlet just to tell us that its exempt. We knew that so we checked the tax override box.

Why would you want to block it? Just use another taxcode if you dont wan't it to trigger

Is this related to integrations causing multiple saves/calls to avalara and multiplying the bill unnecessarily? It's possible to add a web services exclusion to AVA_functions in a few places. Need a careful dev and cowboy management though.

Still not sure why anyone would mess with that - you have Avalara for a reason, if you start fiddling with it any guarantee of compliance goes down the drain

Some customers are tax exempt and shouldn't call out to Avalara. They pay for a pool of request calls to Avalara and they want to cut those down significantly as they are overpaying as the majority of the requests are from these exempt customers.

@creece This was a while back with an older instance - first time was when avatax was written in SS 1.0, 2nd was after they moved to 2.x. I documented the process but the documentation stayed with the old company. Pretty sure the functions related were the transaction_tab ones. There were already exclusions hardcoded in, if(runtime.executionContext==x y z){return} and just added the relevant contexts. Again, if memory serves. Not sure of your exact use case.

You're correct, maybe they just missed one for a client call.

Nasty