Prerequisites
Confirm the following before connecting:- An active Avalara AvaTax account, with your Account ID and License Key available.
- The companies you want to use exist in both DualEntry and AvaTax. DualEntry does not auto-create companies in AvaTax.
- Tax nexuses are configured in AvaTax for every jurisdiction where you collect tax.
- You know how each DualEntry company should map to an AvaTax company.
Step 1: Connect the integration
Authorize DualEntry to call AvaTax with your account credentials.- Navigate to Configuration → Company → Integrations → Avalara.
- Enter your Avalara Account ID and License Key.
- Choose the environment: Sandbox or Production.
- Choose Connect. DualEntry validates the credentials against AvaTax and confirms the connection.
Step 2: Run the initial sync
After connecting, DualEntry pulls reference data from AvaTax automatically:- The list of AvaTax companies on your account.
- The tax nexuses configured for each company.
- Custom tax codes (optional, if your AvaTax account uses them).
Step 3: Map companies
Each DualEntry company must be mapped to a corresponding AvaTax company before transactions can be taxed.- Open Configuration → Company → Integrations → Avalara → Companies.
- For each DualEntry company, choose the AvaTax company it corresponds to. The DualEntry
company_idis sent to AvaTax as the company code on every transaction. - Save the mapping.
Step 4: Confirm nexus matching
DualEntry auto-matches nexuses by country plus region or state. For example, AvaTaxUS-CA matches DualEntry US-CA. Global nexuses where country equals region (e.g., US-US) are skipped.
- Open Configuration → Company → Integrations → Avalara → Nexuses.
- Review the matched nexuses for each company.
- If a nexus is missing, create it in AvaTax and run Sync again.
Step 5: Set up product tax codes
Map the AvaTax product tax codes you plan to use, then attach them to your DualEntry items so AvaTax can apply the correct exemptions or reduced rates.- Open Configuration → Tax Setup → Product Tax Codes and add each AvaTax tax code you plan to use.
- On each DualEntry
item, set the Product Tax Code field to the appropriate code. - On each DualEntry
customer, set the customer as Taxable or Tax Exempt.
DEFAULT taxable code.
Step 6: Validate and go live
Once mappings are in place, confirm the integration is ready for transaction flow.- Verify every active DualEntry company is mapped to an AvaTax company.
- Verify every required nexus is matched.
- Verify items that need specific tax treatment have a product tax code assigned.
- The integration is now marked Setup Complete, and tax is calculated automatically on new transactions.
What syncs
The integration moves reference data one way and calls AvaTax in real time for tax calculation:
Tax is calculated when you create any of these transaction types:
invoice, sales_order, cash_sale, customer_credit. The customer’s shipping address determines the jurisdiction.
Mapping reference
The integration relies on the following field mappings between AvaTax and DualEntry. Company mapping
Nexus mapping
Tax code mapping
Current limitations
A few aspects of the integration are worth knowing before you rely on it:- Posted transactions only. Draft transactions do not call AvaTax; tax is calculated on post.
- Shipping address required. Customers without a complete ship-to address cannot be taxed accurately. Verify ship-to and ship-from addresses on every taxable transaction.
- One-way reference sync. DualEntry does not push companies, customers, or items into AvaTax. Both systems must be configured independently.

