Discrepancy categories

Understand why transactions are missing between AvaTax and your ERP system and how to identify and resolve the gaps.

Missing transactions occur when a transaction exists in 1 system but not in the other. Reconciliation identifies these gaps and categorizes them based on where the transaction is absent.

Missing from AvaTax

A transaction exists in the ERP system but doesn’t appear in AvaTax.

Common root causes

• API error during synchronization

• Transaction not yet invoiced

• Address validation failure

• Connector disabled or paused

Table 1. Detection and resolution

Root cause

Detection method

Resolution path

API error during sync

Review the audit trail for failed API calls, including error codes 300, 303, 304, or 309

Correct the data issue in the ERP system, then resync or manually create the transaction

Transaction not yet invoiced

ERP transaction is in order or quote status

No action is required. Transaction will sync when invoiced

Address validation failure

Audit logs show error 309 (InvalidAddress) or 317 (InvalidPostalCode)

Correct the address in the ERP system and recalculate the tax

Connector disabled or paused

Gap in transaction dates correlates with connector downtime

Perform bulk synchronization for the affected period

Missing from ERP

A transaction exists in AvaTax but doesn’t appear in the ERP system.

Common root causes

• Manual entry in AvaTax

• Different source system

• Test transaction

Table 2. Detection and resolution

Root cause

Detection method

Resolution path

Manual entry in AvaTax

Transaction has no matching ERP reference

Verify legitimacy. Create ERP entry or void the transaction in AvaTax

Different source system

Document code pattern indicates webstore, POS, or other source

Search for the corresponding ERP transaction and document the relationship

Test transaction

Document code contains “test” or transaction exists in a sandbox company

Void if in production, or ignore if appropriate