Prerequisites
Confirm the following before you connect Anrok:- Each DualEntry company you want to connect has an active Anrok seller account and its own Anrok seller API key. To create a key, follow Anrok’s guide to manage your API keys.
- Product tax categories are enabled in Anrok for the products you sell. If you connect more than one Anrok account, each category is enabled in every account.
- Each DualEntry company you connect has a US address.
- DualEntry has a nexus for every state where you collect tax, under Configuration > Tax Setup > Nexuses. DualEntry checks its own nexuses before it calls Anrok and does not import nexuses from Anrok, so set them up in both places. See US sales tax for how nexuses work in DualEntry.
- Each customer you tax has a complete ship-to address, and taxable customers have a Tax Status of Non-Exempt.
- You have the
integration:editpermission to connect and sync the integration, and theproduct_tax_code:createpermission to add product tax codes. See User roles and permissions.
DualEntry uses one tax provider at a time for a company. If Avalara AvaTax is connected anywhere in your organization, DualEntry uses Avalara for tax calculation and never calls Anrok. Disconnect Avalara before you rely on Anrok.
Step 1: Connect Anrok
Connect each DualEntry company to its own Anrok seller account. Each company can have one Anrok connection, so an organization with several companies can connect several Anrok accounts.- Navigate to Configuration > Company > Integrations and find the Anrok tile.
- Choose Connect. The Connect Anrok dialog opens.
- Optionally enter an Integration Name. It defaults to Anrok.
- In Company, choose the DualEntry company this Anrok account belongs to.
- Paste the seller key into API Key.
- Choose Connect.
Step 2: Review the connection settings
Review the connection settings before you post anything, because the cut-off date decides which documents DualEntry records in Anrok. Open the Anrok integration page and choose Settings to open the Anrok Settings drawer. The table below lists the settings and the defaults DualEntry sets when you first connect:
Set Initial Cut Off Date to your go-live date if you don’t want earlier documents recorded in Anrok, then choose Save changes.
The Danger Zone at the bottom of the drawer has Pause and Disconnect. If you disconnect and connect again, DualEntry creates a new connection with default settings, a new cut-off date, and no mappings.
Step 3: Create Anrok product tax codes
Anrok product tax codes tell Anrok how to tax each item. Create one in DualEntry for each Anrok product tax category you use, then assign it to your items.- Navigate to Configuration > Tax Setup > Product Tax Codes and choose New tax code.
- In the Create Product Tax Code drawer, set Source to Anrok.
- In Code, search for an Anrok product tax category by code or name, and pick it. The list shows only categories that every connected Anrok account has. Description fills in from the category name.
- Choose Create. DualEntry checks the code with Anrok before it saves it.
- On each item you sell, set Product Tax Code to the matching Anrok code.
Step 4: Sync and map products and customers
Anrok calculates tax on a document only when every item and the customer on it are mapped to Anrok records. A sync pulls your Anrok products and customers, matches them to DualEntry items and customers, and exports anything unmatched. On the Anrok integration page, choose Initial sync. Later, the same button reads Sync or Resync. When the sync finishes, the page shows the Products mapping and Customers mapping tabs next to Data Sync.Map products to items
The sync matches each Anrok product to a DualEntry item in this order:- The DualEntry item ID that DualEntry stored on the Anrok product when it exported the item.
- An item whose SKU equals the Anrok product’s external ID.
- An active item with exactly the same name.
No item has this product SKU or name. Map the product manually. When several items or Anrok products share a name, both stay unmapped. The sync never creates items in DualEntry.
With Allow push data on, the sync exports each active item that has an Anrok product tax code and no Anrok product, and maps it. Archived, draft, and inactive items are never exported. Map anything left over on the Products mapping tab.
Map customers
The sync matches each Anrok customer to an active customer of the connected company, first by ID and then by exact name. With Allow push data on, it exports unmatched active customers of that company to Anrok, with their name and email, and maps them. Archived, draft, and inactive customers are never exported. Map remaining customers on the Customers mapping tab. The customer list shows only customers available to the connected company, and each customer can map to only one Anrok customer. Anrok applies its own exemption certificates to the mapped Anrok customer, so map every customer that has an exemption. Check both tabs after you add new items or customers. An unmapped item or customer does not cause an error: DualEntry calculates tax with its native engine instead.When DualEntry uses Anrok to calculate tax
DualEntry calls Anrok on invoices, sales orders, cash sales, and customer credits for a company connected to Anrok. It also calls Anrok when you choose Calculate tax on a quote. Lines Anrok prices carry the Anrok tax code. DualEntry calls Anrok only when every input is in place. The table below shows what happens in each case:
When you save a document, its Anrok tax estimate appears on the Tax Calculation Logs page as Anrok Tax Estimate, and each record and void appears as Anrok Commit (Create/Update) or Anrok Void. To open it from the integration page, choose More actions > Tax Calculation Logs. The page lists entries from every tax provider in your organization, not only Anrok.
What DualEntry records in Anrok
DualEntry records posted invoices, cash sales, and customer credits in Anrok so your Anrok filings match your ledger. It records a document only when it has at least one line with the Anrok tax code, is dated on or after the cut-off date, and Allow push data is on. The table below shows what Anrok receives as you change a document in DualEntry:
DualEntry never sends drafts. Sales orders get Anrok tax but are not recorded in Anrok; the invoice you create from a sales order is. If you turn Allow push data off, DualEntry stops recording new documents but still voids recorded documents that you archive or that stop qualifying.
Current limitations
Keep these limits in mind before you rely on the integration:- US sales tax only: DualEntry never sends a transaction with a non-US ship-to or ship-from address to Anrok, even if your Anrok account has VAT set up. For VAT and GST, use DualEntry’s native tax rates.
- Sales transactions only: Bills and other purchase transactions are not taxed or recorded through Anrok.
- No nexus import: Nexuses and registrations live in Anrok. DualEntry keeps its own nexuses, which you maintain separately.
- One provider at a time: If Avalara AvaTax is connected anywhere in your organization, DualEntry uses Avalara instead of Anrok.
- Mapping is required: One unmapped item or an unmapped customer sends the whole document to DualEntry’s native engine, without an error.
- No item creation from Anrok: The sync matches Anrok products to existing items. It never creates items.
- Edits after filing: Once Anrok locks a transaction for filing, later edits to the document in DualEntry don’t reach Anrok.
- Pause and disconnect: While the connection is paused or disconnected, DualEntry calculates tax with its native engine and doesn’t void documents you archive in Anrok.
- Rate limits: Anrok limits how fast DualEntry can send requests. A large first sync can stop exporting partway with a rate limit error. Choose Resync to export the rest.