Skip to main content
Avalara Help Center

Handle duplicate or erroneous transactions

You have unintentionally submitted multiple duplicate or erroneous tax calculation or adjustment transactions due to:

  • Errors that cause transactions to be submitted more than once
  • Accidental submissions
  • Running test transactions in Production rather than in Sandbox

The AFC Tax Engine does not check for duplicate transaction data.  The engine accepts whatever is sent to it (for example, the engine does not check that an adjustment has a corresponding tax calculation).  The Customer Portal Data Explorer aggregates all totals submitted in the current period and reports on all data processed, whether it is duplicate data or not.

Identify duplicate transactions

Duplicate and erroneous transactions can often be identified using the Customer Portal Data Explorer.

  • Set up and preview a Transaction Detail Report.

    • Select the appropriate reporting time period, which might span multiple months

    • Add common columns that you use when running transactions, such as Document Code or Optional Key fields.
    • Remove unused columns from the report to limit the amount of data to review.
    • Sort by or group by columns that might show duplicate data, such as Tax Rate or Charge.

Use Commit functionality

The Commit functionality is a possible solution to avoid submitting duplicate or erroneous transactions.  Committing allows you to:  

  • Group transactions by a bill run or invoice.
  • Use a unique Document Code for each group of transactions (for example, a GUID).
  • Use a generic Document Code, such as "QUOTE", for transactions not intended to be be committed or reported.
  • Set a Commit flag for each transaction.
  • After the transaction has been submitted, use the Commit endpoint (/api/v2/afc/commit) to commit or uncommit a Document Code.

Run adjustments to negate erroneous transactions

Run an adjustment transaction to negate duplicate or erroneous transactions.

  1. Set up an AFC SaaS Pro REST v2 transaction that replicates the duplicate transaction.
    • Assign the Transaction (tran) and Service (serv) Pair.
    • Set the Invoice date (date) to the reporting period where the adjustment applies.
    • Set Charge (chg) to the overage amount.
    • Update other details, such as Customer Type (cust) and exemptions (exms).
  2. Set the Adjustment flag (adj) to true.
  • Was this article helpful?