Skip to main content
Avalara Help Center

Import transactions (legacy)

This article applies to:AvaTax

Importing is the easiest way to get us your transactions or adjust existing transactions in bulk. There are two common reasons you might need to do this:

  • You don't have an integration (Avalara Connector or Extractor) that imports them automatically.

  • You have transactions in your business application that aren't in Avalara.

Tip icon

Keep in mind that importing transactions only works one way; it doesn't update the data in your business application.



  1. From the Avalara Home page, go to Transactions > Import transactions (legacy) and select Download the transaction import toolkit
  2. Find in your downloads folder. Right-click the file, select Extract All, and then open either ImportTransactionsTemplate.xlsx or ImportTransactionsTemplate.csv. 
  3. Fill out the required fields, with a row for each transaction, and then save the file:
    • ProcessCode: A number that represents the action Avalara takes on the transaction. For new transactions, use 3.
      (See Import transactions template guidelines for the full list of ProcessCodes.) 
    • DocCode: The unique ID for the invoice, credit memo, or return included in the transaction.
    • DocType: A number that represents the type of tax document: 
      • 0 = Sales order

      • 1 = Sales invoice

      • 2 = Purchase order

      • 3 = Purchase invoice

      • 4 = Return order

      • 5 = Return invoice

      • 6 = Inventory transfer order

      • 7 = Inventory transfer invoice

      • 8 = Reverse charge order

      • 9 = Reverse charge invoice

      • 10 = Customs invoice

      • 11 = Customs order

    • DocDate: The transaction document's date, in the format yyyy-mm-dd or mm/dd/yyyy.
    • CustomerCode: The ID associated with a customer in your business application.
    • LineNo: The transaction's line number.
    • Amount: Total sale for the line item.
    • OrigRegion and DestRegion: A state or province abbreviation for the transaction's origin and destination.
    • OrigPostCode and DestPostCode: A ZIP code or Canadian postal code for the transaction's origin and destination.
      Tip icon

      If you're enrolled in a Streamlined Sales and Use Tax Agreement (SST) program or have transactions from outside the U.S. or Canada, the required fields are different. See Import transactions template guidelines for details.

  4. On the Import Transactions page in Avalara, drag and drop the import template file to the area in the center of the page.
    You can click Browse Instead and select the file from your computer if you prefer.
  5. Wait for the import to complete. How long this takes depends on the size of the import template file.
    Your transaction data is now in Avalara, and a record of the import file appears at Transactions > Transaction Import History.
  • Was this article helpful?