Skip to main content
Anomaly Detection
Search
Search Indirect Tax Help and Support.

This article applies to:

  • Product: ONESOURCE Determination

Recommended actions by anomaly type

Use these guidelines to decide whether to mark an anomaly as expected or reviewed.

Available actions

For every anomaly type, you can take one of 2 actions:
  • Mark as Expected
    : Use this action for a known or intentional change that the system should not flag again.
  • Mark as Reviewed
    : Use this action for an anomaly that you investigated and addressed, outside the tool if needed.
Each anomaly also includes proposed next steps. Investigate the anomaly. If the cause is a configuration issue, correct the configuration directly in Determination. If the cause is an issue with standard tax content, the tax engine, or the calculator, contact Support instead of trying to resolve it in Determination.

Tax Rate

What to review
Open the anomaly and check the Comparative Analysis table. Compare the
Current Tax Rate / Fee
 column with the
Historical Tax Rate / Fee
 column. In most cases, this table has what you need. Optionally, drill into the affected invoice to see which lines changed. The hexagon indicator marks those lines.
Likely expected
The cause is a known rate update, a jurisdictional legislative change, or an intentional configuration update. Select
Mark as Expected
.
Likely not expected
The cause is an incorrect configuration, a misapplied rate, or a data issue. Investigate further, and then select
Mark as Reviewed
 after you resolve it.

Tax Authority

What to review
Open the affected invoice and compare the
Current Tax Authorities
 column with the
Historical Tax Authorities
 column. Current Tax Authorities shows the authorities that apply to this invoice. Historical Tax Authorities is a consolidated list of every authority that the system has seen for that transaction pattern, not a single past invoice. Select the invoice number to see which lines or tax blocks are involved. The hexagon indicator marks them.
Likely expected
The cause is a new jurisdiction, a legitimate removal of an authority, or a business expansion or supply chain change. Select
Mark as Expected
.
Likely not expected
A required authority is missing, an incorrect authority appears, or a configuration or data issue exists. Investigate, and then select
Mark as Reviewed
.

Exemption Certificate

What to review
Open the anomaly and identify which of the 3 scenarios applies:
  • Missing:
     A certificate that applied before is now absent.
  • Added:
     No certificate existed before, and the system now applies one.
  • Different:
     The system now applies a different certificate.
Open the affected invoice and compare the current certificate state with the historical certificate number for that transaction pattern. Then select the invoice number to locate the impacted lines. The hexagon indicator marks them. For each impacted line, you can see the certificate that applies, or that is missing, for that jurisdiction.
Likely expected
The certificate changed intentionally, the certificate expired and a renewal replaced it, or the customer became newly eligible for the exemption. Select
Mark as Expected
.
Likely not expected
The system removed a certificate incorrectly, the wrong certificate applies, or a data or setup issue exists. Investigate, and then select
Mark as Reviewed
.

Quick reference

Review focus and typical action by anomaly type
Anomaly type
Primary review focus
Typical action
Tax Rate
Comparative Analysis (current rate compared with historical rate)
Mark as Expected or Mark as Reviewed
Tax Authority
Current Tax Authorities compared with Historical Tax Authorities
Mark as Expected or Mark as Reviewed
Exemption Certificate
Current certificate compared with historical certificate
Mark as Expected or Mark as Reviewed