Avalara Developer Network Developer blog

AvaTax Developer Blog Posts

Point-of-Sale Data API

One of the most common questions we get from our point-of-sale customers is about the need to operate in a disconnected environment, while maintaining the same level of accuracy of a connected environment. Many businesses can face periods of intermittent internet connectivity, preventing live calls to our tax engine. Some businesses wish to operate entirely disconnected. In either scenario, businesses require the means to calculate tax locally. Today, we’ll walk through a new API launching in the AvaTax 2.16.12 release - an API that generates a tax content file that can be consumed by a merchant’s point-of-sale (POS) application, supporting...

REST v2.16.12 Patch Notes

This article is about the December 2016 monthly update to the AvaTax REST v2 API. UPDATED 2016-12-07 - The team added the definition of “Mixed” sourcing to the client library to address California sourcing scenarios prior to launch. Launch has been rescheduled for Tuesday, December 13th. Environment URL Release Date Sandbox https://sandbox-rest.avatax.com 2016-12-01 Production https://rest.avatax.com 2016-12-13 POST /api/v2/transactions/create The sourcing field on TransactionLineModel had a mismatch between its documentation and its return value. In release 2.16.11, the field was documented as a string, but its value was being returned as an integer. Many libraries would still successfully parse this value...

Types of Transactions

AvaTax is a full service engine for calculating transactional taxes, including sales, use, VAT, and many other tax types. In order to properly calculate taxes in these different circumstances, AvaTax must also support a wide variety of transaction types. In today’s article, I will walk you through the differences between these transactions and describe how to map them to your business processes. Orders vs Invoices Our customers require both the ability to estimate tax for a transaction, and to record the actual tax for that transaction. Many customers use AvaTax as a way to predict taxes before taking action -...

Geocoding in REST v2

The tax on your transactions is heavily dependent on where the transactions occur. In the US sales and use tax world, transactions are generally taxed based on either the “Origin” or “Destination” - but for most retail sales, these two addresses are almost always the same. When you visit your local grocery store, they charge you a single rate based on product type and the location of the store; but if you place an order online, the tax you pay will be influenced by a number of factors including the origin location of the warehouse and the destination address where...

Estimating Tax with REST v2

The AvaTax REST API provides lots of different levels of estimated tax values, and sometimes it may be hard to know the right way to estimate tax for your customers. For today’s blog article, I will be walking you through the different types of estimates that are available in AvaTax REST v2 and how they can help you. AvaTax is of course built on correctly identifying the exact tax amounts for an invoice; and to do this, we incorporate dozens of factors including the origin and destination address, dollar amounts, taxability rules, nexus declarations, registration rules, customer exemption certificates, and...

REST v2.16.11 Patch Notes

REST v2.16.11 Patch Notes AvaTax REST v2.16.11 has now adopted the naming system used by AvaTax SOAP (API version/year/month). Environment URL Release Date Sandbox https://sandbox-rest.avatax.com 2016-11-02 Production https://rest.avatax.com 2016-11-09 POST /api/v2/taxrates Corrected a bug that caused the TaxRates API to show duplicate rates. POST /api/v2/transactions/create New fields have been added to the API. These fields are optional and do not require changes to your existing code. Added new fields on the create transaction model: debugLevel (string, optional): If the user wishes to request additional debug information from this transaction, specify a level higher than 'normal'. Enum, possible values = ['Normal',...

Batched Transactions in REST v2

Uploading Batched Transactions One of the most common inquiries we get at Avalara is about the need to reconcile, or publish, a full list of a company’s transactions at the end of the month. Many businesses work by cash register day by day, and at the end of each month they produce a report listing all the transactions that they processed. Sometimes businesses will have one report for each location, or cash register, or salesperson; and they need a batch process they can use to upload all of these transactions into AvaTax for later reconciliation, or for filing tax returns....

REST v2.3.1 Patch Notes

REST v2.3.1 Patch Notes For those of you who participated in the AvaTax REST v2 Preview program, I’d like to take this opportunity to thank you for your time and effort helping us debug a huge software release. We’ve now implemented a clean, modern, consistent REST API that covers tax functionality from top to bottom - and we’ve established a great platform for continuing improvements. Now that the program is winding down, please take note of a few differences between the final release of REST v2 and the preview program you tested in August/September: New URL for REST v2 The...

Subscribe via RSS!