Skip to content

[Master]-[BE] Intervat XML Report 11307 Does Not Include Non-Deductible VAT Amount Reflected in VAT Statement Preview - #13481

Open
Fixes4BC (neeleshsinghal) wants to merge 1 commit into
mainfrom
bugs/Bug-657370-Intervat-XML-Report-11307-Not-Include-Non-Deductible-VAT-Amount
Open

Fixes4BC (neeleshsinghal) wants to merge 1 commit into
mainfrom
bugs/Bug-657370-Intervat-XML-Report-11307-Not-Include-Non-Deductible-VAT-Amount

Conversation

@neeleshsinghal

@neeleshsinghal Fixes4BC (neeleshsinghal) commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Fixes AB#657370

@neeleshsinghal
Fixes4BC (neeleshsinghal) requested a review from a team as a code owner October 31, 2026 06:15
@github-actions github-actions Bot added the Team: Finance GitHub request for Finance area label Oct 31, 2026
@github-actions github-actions Bot added this to the Version 30.0 milestone Oct 31, 2026
@alexei-dobriansky

Copy link
Copy Markdown
Contributor

Good Sense Reviewer - Round 1

Recommendation: Accept

What this PR does

The change preserves Incl. Non Deductible VAT when a Belgian VAT statement line changes to Amount or Base, and still clears it for unsupported amount types. The new condition matches the flag's own validation. The pinned VAT Statement calculation already adds non-deductible VAT for Amount and subtracts it for Base; both Preview and Form/Intervat Declaration use that calculation, including row totaling. The revised positive test now calls Amount Type validation after setting the flag, so it exercises the exact defect and would fail with the old trigger. The added negative test confirms that changing to Unrealized Base still clears the flag. Existing numeric preview coverage verifies Base minus Non Ded. VAT Amount. No correctness blocker was found.

Problem-solution fit

Fit: Strong

The change directly fixes the inconsistent validation that silently cleared a supported flag on Base lines. It preserves the existing calculation rules and does not try to compensate for unrelated statement configuration errors.

Suggestions

None.

Risk assessment and necessity

Risk: VAT declaration amounts are financially sensitive, but the regression surface is narrow: only the Belgian Amount Type validation changes. Amount continues to preserve the flag, Base now preserves it as the flag validation and report calculation already expect, and all other amount types still clear it. No posting logic, ledger entries, field definitions, public signatures, or events change. Sales and Purchase ledger reports use the same VAT Statement calculation. Other country tables are unchanged. The fix does not automatically re-enable flags already cleared or add missing statement rows.

Necessity: Without this change, changing or revalidating Base can silently disable the non-deductible VAT adjustment and produce an incorrect declared base. Users must notice the cleared flag and enable it again after choosing Base. Keeping valid statement settings intact is important for reliable VAT reporting, and this targeted trigger change is proportionate.


[AI-PR-REVIEW] version=1 promptVersion=4 system=github pr=13481 round=1 by=alexei-dobriansky at=2026-10-31T08:18:19.6565640Z lastSha=a96b46810c62c2178e92f11f0c5f700104060171 reviewKey=376e9d1f8715f2a321b9504724f2532b00a4d8cd3f02afc101f88b6fedce39cb suggestions=none

This branch was previously deployed

1 inactive deployment
triage — a96b4681 Deployed Oct 31, 2026 by neeleshsinghal via Classify team ownership #9643
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team: Finance GitHub request for Finance area

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants