Point-of-Sale Data API

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 its native tax functionality. The data in the API response, at a minimum, will contain tax jurisdiction, tax rate and product/service taxability information for each Tax Code and brick & mortar store Location configured in your AvaTax account.

The Point-of-Sale Tax Content File

To begin, let’s take a look at the template for the point-of-sale tax content file. Here are the details for each field included in the tax content file:

ScenarioId This field is used to group tax scenarios together. A tax scenario will consist of a single Location and single Tax Code 1
EffDate The date the tax information becomes effective 01/01/2015
EndDate The date the tax information is no longer effective. Tax data is effective on this date, but is not effective on the following date 12/31/9999
LocationCode Unique location identifier 001
TaxCode Avalara System Tax Code or Custom Tax Code P0000000
ShipToCity The ship-to city Durham
ShipToCounty The ship-to county Durham
ShipToState The ship-to state NC
ShipToPostalCode Postal code associated with the location address 27707-1764
ShipToCountry The ship-to country US
JurisType The jurisdiction type. There are five supported values - Country, State, County, City, Special State
JurisCode Unique numeric, alpha, or alphanumeric code identifying a jurisdiction. This field is optional 001, EKTF0
JurisName The name of the jurisdiction that corresponds to this tax record North Carolina
TaxType The tax type associated with the rate Sales
Tax_Description The description of the tax NC STATE TAX
Tax_Rate The tax rate. "0.03" corresponds to 3%. Exempt records will have a rate of 0. 0.03
Cap Applies a cap to the taxable amount. Amounts up to the cap are taxable. Amounts over the cap are non-taxable. The tax rate applies to the taxable amount. 0
Threshold Applies a threshold to the taxable amount. Amounts up to and including the threshold are non-taxable. Amounts over the threshold are taxable. The tax rate applies to the taxable amount. 100
TaxRuleOptions Applies a special tax scenario rule to the transaction. There is only one supported value at this time: Tax All. With a threshold, this rule taxes the entire amount once the total reaches the threshold TaxAll
Tax_Application_Level This field is not used at this time, but will be leveraged for tax-on-tax scenarios in the future. This field will define the order in which taxes are applied in a tax-on-tax scenario and the tax base for each individual tax N/A

Getting Started

Before we start building our JSON request, you’ll want to ensure you have Locations and Items configured within your AvaTax account. Avalara’s Help Center is a great resource for learning how to Add or Import Company Locations and Add or Import Items .You can also take advantage of our suite of REST v2 endpoints for configuring your AvaTax account with Locations and Items. Please note that the Point-of-Sale data API uses the Tax Codes assigned to your Items to generate a response.

Building our JSON Request

In order to retrieve this file, we’ll need to build a JSON request:

POST /api/v2/pointofsaledata/build

  "companyCode": "AVALARA"

Wow! Only one field! In this JSON request, we only defined a CompanyCode. This means our response will include tax content for all of the Locations and Tax Codes configured in your AvaTax account and will be formatted as a standard JSON response, like this result:

    "ScenarioId": "1",
    "EffDate": "4/1/2012",
    "EndDate": "12/31/9999",
    "LocationCode": "1",
    "TaxCode": "PC040100",
    "ShipToCity":"New York",
    "ShipToCounty": "NEW YORK",
    "ShipToState": "NY",
    "ShipToPostalCode": "10028-2175",
    "ShipToCountry": "US",
    "JurisType": "State",
    "JurisName": "NEW YORK",
    "TaxType": "Sales",
    "Tax_Description": "NY STATE TAX",
    "Tax_Rate": 0.04,
    "Cap": "0.000000",
    "Threshold": "110.000000",
    "TaxRuleOptions": "TaxAll",
    "Tax_Application_Level": ""

But what if you only want to include a couple of Locations or Tax Codes? Or maybe you want to postdate the content included in the response. We can handle these requests with a few additional parameters.

POST /api/v2/pointofsaledata/build

  "companyCode": "AVALARA",
  "documentDate": "12/31/2016",
  "responseType": "csv",
  "taxCodes": [ "P0000000", "PC040100", "PF050001" ],
  "locationCodes": [ "001", "002", "003" ]

Or, even easier, you can request the data file for one location at a time using the individual location point-of-sale data API:

GET /api/v2/companies/12345/locations/56789/pointofsaledata

In this JSON request, we added DocumentDate, TaxCode, LocationCode, and ResponseType parameters. The DocumentDate parameter determines the date associated with the tax content. When the DocumentDate is not specified, the current date is used. The TaxCode and LocationCode parameters limit the response to the specified Locations and TaxCodes. The ResponseType parameter will determine how the response will be formatted. Since we specified “CSV”, our response will be formatted as a Comma Separated Value file.

    ScenarioId,EffDate,EndDate,LocationCode,TaxCode,ShipToCity,ShipToCounty,ShipToState,ShipToPostalCode,ShipToCountry,JurisType,JurisCode,JurisName,TaxType,Tax_Description,Tax_Rate,Cap,Threshold,TaxRuleOptions,TaxApplicationLevel 1,11/01/2014,12/31/9999,001,P0000000,Durham,,NC,27707-1764,US,State,37,NORTH CAROLINA,Sales,NC STATE TAX,0.047500,0.000000,0.000000,, 1,05/01/2013,12/31/9999,001,P0000000,Durham,,NC,27707-1764,US,County,063,DURHAM,Sales,NC COUNTY TAX,0.022500,0.000000,0.000000,, 1,05/01/2013,12/31/9999,001,P0000000,Durham,,NC,27707-1764,US,Special,99063,NC SPECIAL TAX DISTRICT (99063),Sales,NC SPECIAL TAX,0.005000,0.000000,0.000000,,

Let’s update the response type to “xml” to see what an XML-based response looks like:

POST /api/v2/pointofsaledata/build

  "companyCode": "AVALARA",
  "documentDate": "12/31/2016",
  "responseType": "xml",
  "taxCodes": [ "P0000000", "PC040100", "PF050001" ],
  "locationCodes": [ "001", "002", "003" ]

This is an example of an XML response:

    <ShipToCity>New York</ShipToCity>
    <ShipToCounty>NEW YORK</ShipToCounty>
    <JurisName>NEW YORK</JurisName>
    <Tax_Description>NY STATE TAX</Tax_Description>
    <Tax_Application_Level />

We’ve now reviewed all of the available parameters for the Point-of-Sale data API. It’s important to remember that each call made to the Point-of-Sale data API will only provide you with tax content relevant to the day you made your request or the date stated in your request. If you will be using the response data from this API to calculate tax in a disconnected environment regularly, you will need to schedule daily calls to this API to ensure you always have the most up-to-date tax rules and rates.

Recent posts

The 2021 sales tax changes report: midyear update

Your guide to navigating the complicated world of tax compliance and preparing for the future 

The 2021 sales tax changes report: midyear update

Hear tax and industry experts break down the latest legislative updates and industry trends in our upcoming virtual event.

Stay up to date

Sign up for our free newsletter and stay up to date with the latest tax news.