Date Determination

The dates your ERP system provides are converted by Determination into calculation-specific dates. The table below shows the various dates you may pass from your ERP to Determination. In order to generate a tax calculation, you always need to pass Invoice Date within your input XML—all the other dates are optional. If you only pass the invoice date, then Determination will use either its default logic or your determination date configurations to determine Tax Determination Date, Tax Exchange Rate Date, and Tax Point Date.

Date determinations include currency conversion, the application of rates, rules, and exemption certificates, and all other date-specific validation and calculation.

Date Type

Description

Used in Calculation?

Invoice Date

The Invoice Date is always required, regardless of the type of document you are processing (invoice, quote, movement, or any other type of document).

Yes

Movement Date

The Movement Date indicates the physical or logical movement of goods between locations or entities.

Yes

Original Invoice Date

The date of the original invoice.

Yes

Original Movement Date

The date of the original movement.

Yes

Tax Determination Date

The date used to determine the applicable rules and rates for the transaction. If the system configuration parameter TAX_DATE_DEFAULT_MOVEMENT_DATE equals Y then Determination would use the first available date from the following list:

  1. Original Movement Date
  2. Movement Date
  3. Original Invoice Date
  4. Invoice Date

This date is included in the output for printing.

Yes

Tax Exchange Rate Date

The date on which any applicable currency exchanges will be calculated, using the exchange rate in effect at that date. It is included in the output for printing.

Yes

Tax Point Date

The date on which a tax liability has been established for the transaction. Primarily used for reporting purposes. It is included in the output for printing.

No

Fiscal Date

This date can be optionally used to contain another date matching your business requirements; for example, the date on which revenue was recognized.

No

In a simple scenario, Tax Determination Date, Tax Exchange Rate Date, and Tax Point Date could be driven by Movement Date or Invoice Date, and all three could be the same. However, individual authorities or your business processes may require more complex date handling. Using Date Determination, you can configure this complex date handling. You can configure fallback logic by setting the Configuration parameter TAX_DATE_DEFAULT_MOVEMENT_DATE, which determines whether Invoice Date or Movement Date is used when no date determination rules apply to a transaction.

Date Determination Logic

Date Logic defines exceptions to standard processing for each of the three date types (Tax Determination Date, Tax Exchange Rate Date, and Tax Point Date). ONESOURCE Indirect Tax Research provides Date Determination Logic as part of the Determination Tax Content offerings and updates logic as necessary to support changes in tax law.

If you configure your own custom Date Determination Logic, it could have unintended consequences for your tax calculations. You should engage Consulting Services for assistance if you wish to make configurations is this area.

Examples of logic which could specify Tax Point Date determination include:

  • Use the Invoice Date or the Movement Date, whichever is earlier.
  • Use the Invoice Date unless it is greater than 14 days from the Movement Date. Otherwise use the Movement Date.
  • Use the Movement Date if the Invoice Date is after the last day of the month following the month of the movement. Otherwise, use the Invoice Date.
The actual logic expression for the first example above is:
  1. isNull(movementDate) ? invoiceDate :

  2. invoiceDate.before(movementDate) ? invoiceDate : movementDate

Date Determination Rules

Date Rules specify the application of Date Determination Logic to specific transactions based on criteria such as authority name or type, document type, movement type, product, or customer.

Rules are processed in rule order with custom rules (1-4999) processed before Tax Data Provider rules (5000-10000). A transaction must match all attributes indicated by a rule for the rule to apply. The first matching rule for each date type is applied; therefore, a transaction may apply up to three different rules.

For example, rules 1-3 may all apply the "Invoice or Movement Date, whichever is earlier" logic expression to the Tax Determination Date, Tax Exchange Rate Date, and Tax Point Date respectively for a certain authority or authority type. For complete information on rule matching, see Date Rules.

ONESOURCE Indirect Tax Research provides Date Determination Rules as part of the Determination Tax Content offerings and updates rules as necessary to support changes in tax law. In addition, a fallback rule provides default logic for each date type for each authority.

You can also configure your own Custom Date Determination Rules with the assistance of Consulting Services.