Skip to main content
Avalara Help Center

Understanding Dates

Select the appropriate date method based on how you collect your data.  Date Method defines what date or field is used when compliance files are generated.  

AFC SaaS Pro REST v2

REST v2 uses these date fields to generate reports:

Additional dates, such as Invoice date and Billing Period, can be used to further limit the report through filters, but the report is initially generated based on Committed date or Server date if the commit functionality isn't used.

Date Description Reporting Scenario
Committed The most recent date a transaction has been committed.  This date looks for all transactions whose document code was committed (cmmt = true) within the specified date range regardless of when the transaction was originally processed. Throughout the months of December 2018 and January 2019, you submit several transactions to the AFC Tax Engine for processing at the time each sale occurs.  These transactions are committed on January 31, 2019.  Compliance files are generated on February 1, 2019, using a date range of January 2019.  The date on the report reflects all transactions committed in January 2019, regardless of the Date (date) field value or date when the transaction was submitted.
Server The date the transaction was submitted to the AFC Tax Engine.  This date is displayed in UTC time.  Server date is used when the commit date isn't set.

Throughout the month of January 2019, you submit several transactions to the AFC Tax Engine for processing at the time each sale occurs.  Compliance files are generated on February 1, 2019, using a date range of January 2019.  All of the transactions received in January are returned on the report, regardless of the Date (date) field value.

AFC SaaS Pro REST v1 and Legacy Products

This section details the date methods for REST v1 and Legacy products, such as AFC SaaS Pro Soap and AFC SaaS Pro Standard.  The date method doesn't impact taxation, only compliance reporting.  

  • Date Method 0 uses the date that the transaction is passed to the engine.
  • Date Method 1 uses the transaction_date field specified in the request.
  • Date Method 2 is a custom month and year date, set as YYYYMM in the Optional10 field, used to specify into which month the transaction falls.
Date Method Date Field Used Description Scenario
Date Method 0 Server Date
  • The date the transaction is submitted to the AFC Tax Engine
  • Also called Submitted Date or Start Date
Date Method 0 is the default method.  This date method pulls compliance data based on when the transaction was submitted to the tax engine.  The submitted date must fall within the current month for the tax data to show on the current compliance files. Reporting Scenario 1:  Throughout the month of January 2019, you submit several transactions to the AFC Tax Engine for processing at the time each sale occurs.  Compliance files are generated on February 1, 2019, pulling in all of the transactions received in January, regardless of the Date field value.
Date Method 1 Date
  • The value of the the Date field passed in a transaction. 
  • Also called Invoice Date or Tax Date
This method processes data based on invoice date. We gather all transactions that have an invoice date of the previous month and generate the compliance files from that data on the first day of every month. Reporting Scenario 2:  Throughout the month of January 2019, you submit several transactions with the date field set to January 2019. Compliance files are generated on February 1, 2019, pulling in all of the transactions with a  Date field set between January 1 and January 31. 

Reporting Scenario 3:  On February 1, 2019, the Compliance files for January 2019 are generated.  Additional transactions with the Date field set to a January 2019 date are processed after the Compliance files have been generated.  

  • AFC SaaS Pro (Soap) - Check the Missing Transactions reports to validate that your transactions are captured.  The tax data captured on the Missing Transactions reports is automatically sent to the Communications Returns team.
  • SaaS Standard -  process the back-dated transactions as normal.  Contact your Communications Returns analyst to request the new transactions be included in the current returns cycle.
  • On-premise - process the back-dated transactions as normal.  Contact your Communications Returns analyst to request the new transactions be included in the current returns cycle.  Provide the new reports as part of the request.
Date Method 2 Optional10
  • The value of the the Optional10 field passed in a transaction using the YYYYMM format. 
  • Also called Billing Period
  • REST v2 doesn't support the Optional10 field.
This method processes data based on the Optional10 field. Populate Optional10 with the year and month (YYYYMM format) for which you want the transaction to show up in compliance files. When AFC generates the compliance reports, it only includes transactions from the previous month, based on the Optional10 field. Reporting Scenario 4:  Transactions for January 2019 are processed in the AFC Tax engine with the Optional10 field set to 201901.  Compliance files are generated on February 1, 2019, pulling in all of the transactions with an Optional10 field set to Janaury 2019 (201901).

Reporting Scenario 5:  On February 15, 2019, you process an adjustment for a transaction that took place on January 15, 2019.  Set the Date field on the adjustment transaction to the date of the original transaction (01/15/2019), but set Optional10 to 201902 since the adjustment is being handled during February. The tax adjustment is included in the February 2019 compliance reports, which are generated in March 2019.

Reporting Scenario 6:  On February 1, 2019, the Compliance files for January 2019 are generated.  Additional transactions with the Optional10 field set to 201901 are processed after the Compliance files have been generated.   

  • AFC SaaS Pro (Soap) - Check the Missing Transactions reports to validate that your transactions are captured.  The tax data captured on the Missing Transactions reports is automatically sent to the Communications Returns team.
  • SaaS Standard -  process the back-dated transactions as normal.  Contact your Communications Returns analyst to request the new transactions be included in the current returns cycle.
  • On-premise - process the back-dated transactions as normal.  Contact your Communications Returns analyst to request the new transactions be included in the current returns cycle.  Provide the new reports as part of the request.
  • Was this article helpful?