Skip to main content
Avalara Help Center

Reporting Best Practices

Stick to these Reporting Best Practices to complete a successful Report Reconciliation. 

  • Include no tax transactions when running a Transaction Detail report that is to be used in reconciliation.
  • Understand dates.
  • Ensure that you are looking at the correct date range.  The date method and selected Date Field value make a difference on what data is returned and used in Compliance reporting.
  • Reconcile often, after each bill cycle
    • Reconciling after each bill cycle allows you to quickly identify variances and provides a smaller data set to work with
  • Use commit!  Review what has been committed and not committed.  Commit in real time.
    • Use the Commit endpoint to quickly and easily commit all transactions associated with a document code.
  • Understand what you return in your data. 
    • For example, do you return non-billable (NBA) taxes?  NBA amounts are returned in reporting, but you may not have your session configured to return NBA taxes.
    • Be mindful of rounding and precision when storing the tax results. 
  • Keep in mind client configurations such as overrides, exclusions, exemptions, and bundles.
    • Notify your Returns Specialist of any client configurations you use during the tax calculation.
  • Wait a couple hours to do the reconciliation.  The data takes time to flow into the Reporting engine.
  • Set a variance ahead of time, prior to reconciling. 
    • Totals may not match exactly due to rounding when comparing the Explorer Compliance Report totals to totals saved locally. 
    • Large bill cycles can result in larger variances because differences in totals, even down to the hundredth of pennies, adds up over a large amount of transactions.
    • Establish a variance by looking at the previous month and adding a percentage to that total to account for expected growth.
  • Use filters to reconcile by a smaller unit such as by jurisdiction or by tax type. 
  • Aggregate columns to make it easier to review and identify unexpected variances.
  • Add or remove columns to your report so that you are reviewing only the data you need.
  • For REST v2: Use the Reporting fields, such as Billing Cycle Reference (bcyc), on the tax calculation to filter reports.
    Reporting Field Key Description Found in...
    glref General Ledger Reference LineItem
    acct Account Reference Invoice
    custref Customer Reference Invoice
    invn Invoice Number Reference Invoice
    bcyc Bill Cycle Reference Invoice
    bpd BillingPeriod object
    • Optional object for passing billing period
    • Fields included in BillingPeriod:
    BillingPeriod Key Description
    month Billing period month
    year Billing period year
    Invoice
    ccycd Currency Code Invoice
  • Was this article helpful?