Fix: out of range transactions fix on supplemental txns - 3821#3851
Open
AlexZorkin wants to merge 2 commits intodevelopfrom
Open
Fix: out of range transactions fix on supplemental txns - 3821#3851AlexZorkin wants to merge 2 commits intodevelopfrom
AlexZorkin wants to merge 2 commits intodevelopfrom
Conversation
Backend Test Results1 517 tests 1 515 ✅ 11m 27s ⏱️ For more details on these failures, see this check. Results for commit 878729b. ♻️ This comment has been updated with latest results. |
Frontend Test Results 1 files 310 suites 3m 19s ⏱️ Results for commit 878729b. ♻️ This comment has been updated with latest results. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix Summary
Issue: Supplemental reports assessed after the compliance period ended were excluded from Line 17, causing incorrect Line 22 values.
Root Cause: Code checked transaction
create_dateinstead of the report'scompliance_periodto determine if a transaction should be included in the period's available balance.Fix: Modified
calculate_line_17_available_balance_for_period()to:CompliancePeriodtable to get the report's period yearreport_compliance_period <= target_periodinstead ofcreate_date <= period_end_datecreate_datefor historical data without period infoResult: Supplemental reports are now correctly included in Line 17 based on which period they belong to, regardless of when they were assessed. This automatically fixes Line 22 since it's calculated as
Line 17 + Line 20.