Skip to content

[28.x] [All-e]Fixed asset report 5607 and 4413 showing different results with Declining Balance#8421

Closed
neeleshsinghal wants to merge 1 commit into
microsoft:releases/28.xfrom
neeleshsinghal:bugs/Bug-636726-Fixed-asset-report-5607-and-4413-showing-different-results
Closed

[28.x] [All-e]Fixed asset report 5607 and 4413 showing different results with Declining Balance#8421
neeleshsinghal wants to merge 1 commit into
microsoft:releases/28.xfrom
neeleshsinghal:bugs/Bug-636726-Fixed-asset-report-5607-and-4413-showing-different-results

Conversation

@neeleshsinghal
Copy link
Copy Markdown
Contributor

@neeleshsinghal neeleshsinghal commented Jun 2, 2026

Issue: Report 4413 (Fixed Asset Projected Value Excel) calculates incorrect depreciation amounts for Declining Balance assets when projections cross a fiscal year boundary, producing different results than the legacy Report 5607.

Cause: In InsertProjectedEntries, EntryAmounts[3] (depreciation in fiscal year) was reset to 0 before accumulating the current period's depreciation, causing the last fiscal period's depreciation to spill into the new fiscal year and shifting the effective book value base back one month.

Solution: Moved AccumulateProjectionEntryAmounts before the fiscal year boundary reset (EntryAmounts[3] := 0) so the outgoing fiscal year's final depreciation is fully accumulated before the counter resets, matching the order used in Report 5607.

@github-actions github-actions Bot added AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork Linked Issue is linked to a Azure Boards work item labels Jun 2, 2026
@github-actions github-actions Bot modified the milestone: Version 28.2 Jun 2, 2026
@neeleshsinghal neeleshsinghal reopened this Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AL: Apps (W1) Add-on apps for W1 From Fork Pull request is coming from a fork Linked Issue is linked to a Azure Boards work item

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant