Skip to content

[29.X]-[BE] Intervat XML Report 11307 Does Not Include Non-Deductible VAT Amount Reflected in VAT Statement Preview - #13484

Open
Fixes4BC (neeleshsinghal) wants to merge 1 commit into
releases/29.xfrom
bugs/Bug-657372-29X-Intervat-XML-Report-11307-Not-Include-Non-Deductible-VAT-Amount
Open

Fixes4BC (neeleshsinghal) wants to merge 1 commit into
releases/29.xfrom
bugs/Bug-657372-29X-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#657372

@neeleshsinghal
Fixes4BC (neeleshsinghal) requested a review from a team October 31, 2026 06:36
@neeleshsinghal
Fixes4BC (neeleshsinghal) requested a review from a team as a code owner October 31, 2026 06:36
@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 29.1 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 is validated as Amount or Base, while still clearing it for unsupported amount types. This matches the flag's own validation and the existing VAT Statement calculation: Amount adds non-deductible VAT, and Base subtracts it. Both Preview and the Intervat declaration call that calculation, including through row totaling. The updated test directly exercises the previously failing Amount-to-Base transition, and the new test checks that switching to Unrealized Base still clears the flag. No correctness blocker was found.

Problem-solution fit

Fit: Strong

The change fixes the conflicting validation rules that silently removed an explicitly selected flag from Base lines. It uses the existing calculation and export paths without changing formulas or forcing the flag onto lines where it was not selected.

Suggestions

None.

Risk assessment and necessity

Risk: The affected output is financially sensitive, but the regression surface is limited to one Belgian table-field validation condition. Amount retains its existing behavior, Base now preserves the selected flag, and all unsupported types still clear it. There are no posting changes, new database writes, schema changes, or public procedure or event signature changes. Previously cleared flags are not restored automatically and must be selected again where appropriate.

Necessity: Without this fix, changing or revalidating a Base line can silently clear the flag and leave non-deductible VAT in its reported base. The workaround is to select the flag again after setting the amount type and verify the statement configuration before exporting. Aligning the two validation rules is a proportionate fix for this reporting risk.


[AI-PR-REVIEW] version=1 promptVersion=4 system=github pr=13484 round=1 by=alexei-dobriansky at=2026-10-31T08:18:11.5776125Z lastSha=db6c033040b0fe7be980d35a2984446223fa6da0 reviewKey=8e3b65de4794f5bae9451a0a3043e80ddae85d56ca9469fed98b2b0b0488532f suggestions=none

This branch was previously deployed

1 inactive deployment
triage — db6c0330 Deployed Oct 31, 2026 by neeleshsinghal via Classify team ownership #9650
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