Sage 100

Avalara has no concept of a Transaction Date.  Transactions are recorded by Invoice Date, regardless of type, i.e.  IN, CM, DM, FC, etc.  Avalara has over 1,200 connectors (ERP, shopping carts, marketplaces, etc) and they all are captured in the same database. 

Invoice Date versus Transaction Date is a routine challenge of reconciling Avalara reports/Returns to Sage.  I use AR Invoice History Inquiry ALE to locate mis-matches which almost always results in solving a reconciliation difference.

Invoice Dates prior to a previously reported period would still be selected by Avalara Returns if being used because they would be Committed but not Locked.  If only using AvaTax and self-filing, they could be missed when reporting on the current unreported month.  I always recommend against back-dating an Invoice Date for those reasons, although the Transaction Date could be back-dated for book purposes.

Avalara has no concept of a Transaction Date.  Transactions are recorded by Invoice Date, regardless of type, i.e.  IN, CM, DM, FC, etc.  Avalara has over 1,200 connectors (ERP, shopping carts, marketplaces, etc) and they all are captured in the same database. 

Invoice Date versus Transaction Date is a routine challenge of reconciling Avalara reports/Returns to Sage.  I use AR Invoice History Inquiry ALE to locate mis-matches which almost always results in solving a reconciliation difference.

Invoice Dates prior to a previously reported period would still be selected by Avalara Returns if being used because they would be Committed but not Locked.  If only using AvaTax and self-filing, they could be missed when reporting on the current unreported month.  I always recommend against back-dating an Invoice Date for those reasons, although the Transaction Date could be back-dated for book purposes.