Introduction
Anrok integrates with your billing system to understand your nexus and exposure based on US sales tax and global VAT laws. In the case that you do not have an Anrok-compatible billing system or need to supplement those transactions with additional data, you can manually upload transactions for tax calculation and filing purposes.
The Anrok backfill template (attached at the bottom of this article), can be used to import your transaction information into Anrok — and comes prefilled with sample data. Some values are mandatory, whereas some fields can be left blank (all columns must be present though for the file upload format).
Mandatory fields
These are the mandatory fields required when completing a transaction backfill, including definitions and context of their significance:
| Field | Description |
|---|---|
transaction_id |
The invoice number or billing system transaction ID that relates to each invoice or transaction. Note that if you're uploading transactions that originated in a billing system that's connected to Anrok, you should format this field to match the integration source. Feel free to contact us to confirm there's no risk of duplication when uploading the file. |
date |
The date of the transaction. This allows Anrok to apply the relevant tax calculation and present other time-based data to you in the app. |
product_id |
The product IDs for the item sold, which should match the product IDs on your Anrok instance and your billing system. This allows Anrok to understand which tax configuration needs to be applied to the transaction. |
amount |
The revenue generated from each transaction. Negative amounts may be included for credit memos/notes, refunds, etc. following this format: -$XXX.XX. |
customer_address_state |
The abbreviation of the state the transaction took place. |
customer_address_zip |
The 5-digit or 9-digit (XXXXX-XXXX) zip code of the transaction. |
customer_address_country |
The country where the transaction took place. |
Optional Fields
These are the optional fields you can include when completing a transaction backfill, including definitions and context of their significance:
Note: Although the columns below are optional, providing complete data for your transactions will give you a more complete picture of your nexus and exposure. See How to fix your customer data-quality problems.
| Field | Description |
|---|---|
customer_id |
The ID of the customer associated with the transaction (Note: ampersands, question marks, parentheses, and other special characters are not supported.) You can include the billing system prefix (e.g. "quickbooks:") to ensure that billing system transactions for this customer and all associated with the same customer record. |
customer_name |
The name of the customer. This should be included if customer_id is present. |
customer_address_line1 |
The street address for the transaction. |
customer_address_city |
The city for the transaction. |
currency_code |
The currency code in which the transaction was billed. If none is specified Anrok will default to USD. |
customer_vat_registration_numbers |
The customer provided VAT ID associated with the transaction. If multiple VAT IDs are applicable (e.g. Canada federal and local IDs) please include all of them separated by a comma. |
Once you've imported transactions into Anrok, any missing, malformed, or unsupported information will result in an error. To learn more about these errors and their causes, see How do I resolve an error detected on my transaction?