Share
Report
148Hello Community,
I am troubleshooting the standard Sales Taxes Collected report, report 24, in the United States version of Dynamics 365 Business Central.
I am assuming the standard report and base application code are working as designed. I do not want to modify the base report. I am trying to identify whether a required sales-tax setup, master-data relationship, or historical posting configuration is missing or incorrect.
When I run the report, Business Central creates separate sections for different Report-to Jurisdiction values. However, the same document numbers, taxable sales amounts, non-taxable amounts, exempt amounts, and sales-tax totals appear repeatedly under multiple Report-to Jurisdiction sections.
I expected the report to work as follows:
Report-to Jurisdiction
→ Tax Jurisdictions assigned to that reporting jurisdiction
→ VAT Entries where the Tax Jurisdiction Code matches the current Tax Jurisdiction Code
For example, under TX-STATE, I expected to see only VAT Entries where Tax Jurisdiction Code is TX-STATE. Under TX-HOUSTON, I expected only entries where Tax Jurisdiction Code is TX-HOUSTON. Instead, the same transaction population and the same total tax amount appear under several reporting sections.
I reviewed the standard report relationship. The VAT Entry data item is linked to the current Tax Jurisdiction using Tax Jurisdiction Code, Tax Group Used, and Posting Date. Based on this, my understanding is that the VAT Entry Tax Jurisdiction Code should match the current Tax Jurisdiction Code.
Initially, the report returned an empty-report message. I found that the original Tax Jurisdiction records had blank Report-to Jurisdiction values. The standard report skips Tax Jurisdictions where Report-to Jurisdiction is blank.
For testing, I populated self-referencing values such as:
- OK-STATE reports to OK-STATE
- OK-GARVIN reports to OK-GARVIN
- TX-STATE reports to TX-STATE
- TX-HOUSTON reports to TX-HOUSTON
After this change, the report generated, but the same entries and totals appeared under each reporting section.
I then reviewed the Tax Jurisdiction setup. The original configuration contained codes such as CA, OK-COUNTY, OK-GARVIN, OK-NORMAN, OK-STATE, TX-HOUSTON, TX-METRO, and TX-STATE.
I reviewed the Tax Detail setup. It contains a mixture of blank, NON, TAX, and TAXABLE Tax Group Codes.
The active rates are assigned to TAX, while TAXABLE has zero-rate records. For example:
- TX-STATE with TAX has 6.25%, while TX-STATE with TAXABLE has 0%.
- TX-HOUSTON with TAX has 1%, while TX-HOUSTON with TAXABLE has 0%.
- TX-METRO with TAX has 1%, while TX-METRO with TAXABLE has 0%.
The Oklahoma setup also appears inconsistent because OK-COUNTY with TAX has 4.50%, while OK-STATE with TAX has 4.125%.
I have prepared a corrected working setup using TAX for taxable and NON for non-taxable. However, the existing VAT Entries were posted before these master-data corrections.
I am running the report with the following options:
- Report Type: Detail
- Include Sales: Yes
- Include Purchases: No
- Include Use Tax: No
- Code: Blank
- Report-to Jurisdiction: Blank
- Tax Group Filter: Blank
- Date Filter: Valid posting-date range
Could someone please advise which configuration should be checked to prevent this repetition?
Specifically:
- Should state, county, city, transit, and other local jurisdictions report to themselves, or should they report to a parent filing authority such as the Oklahoma Tax Commission or Texas Comptroller?
- Is a separate parent Tax Jurisdiction record required for the filing authority?
- Can an incorrect Report-to Jurisdiction hierarchy cause the same VAT Entry population to appear under multiple reporting sections?
- Should each Tax Area contain separate Tax Area Lines for every applicable state, county, city, transit authority, and special-purpose district?
- Can blank or inconsistent Tax Group Codes such as blank, TAX, TAXABLE, and NON cause unexpected calculation or reporting behavior?
- Is it expected for the same invoice number and taxable base to appear under multiple jurisdictions when one invoice has multiple tax components?
- If the same invoice appears under multiple jurisdictions, should each jurisdiction show only its own tax component rather than the complete invoice tax amount?
- Is there another required setup or relationship that I may have missed, such as Tax Areas, Tax Area Lines, Tax Jurisdictions, Report-to Jurisdiction, Tax Details, Tax Groups, Customer or Ship-to Tax Area Code, Tax Liable, Item or G/L Account Tax Group Code, or Tax Setup default accounts?
My objective is to understand the correct standard setup and correct the configuration or historical data. I am not planning to customize or change Microsoft’s base report.
An example of a correctly configured state, county, city, and reporting-authority structure would be very helpful.
Thank you.
All responses (
Answers (
