You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing an issue with deficits for organizations that have deficits multiple years in a row. On Dev the company 'bcm' has multiple years of deficits: 2021, 2022, and 2023. Until a 2024 report is made, the ending balance deficits appear to be correct, but when a 2024 report is created the 2022 balance is duplicated and the 2023 numbers disappear.
2023 MYR ending balance:
ASSESSED BALANCE AT END OF SEPT. 30, 2024 | A | Unspecified
• Credit Deficit | (60.00) | (25.00)
• Credit Deficit | 0.00 | (17.06)
• Credit Deficit | (97.16) | (45.05)
2024 MYR starting balance:
CREDIT BALANCE AT END OF SEPT. 30, 2024 | A | B
• 2021 Deficit | 0.00 | (17.06)
• 2022 Deficit | (97.16) | (45.05)
• 2023 Deficit | (97.16) | (45.05)
This means that the ending balance for 2024 is lower than expected.
The above is from dev so using all fake data
The text was updated successfully, but these errors were encountered:
emi-hi
added
Bug
Something isn't working
High
High priority ticket but not critical at this time
labels
Nov 21, 2024
We are experiencing an issue with deficits for organizations that have deficits multiple years in a row. On Dev the company 'bcm' has multiple years of deficits: 2021, 2022, and 2023. Until a 2024 report is made, the ending balance deficits appear to be correct, but when a 2024 report is created the 2022 balance is duplicated and the 2023 numbers disappear.
2023 MYR ending balance:
ASSESSED BALANCE AT END OF SEPT. 30, 2024 | A | Unspecified
• Credit Deficit | (60.00) | (25.00)
• Credit Deficit | 0.00 | (17.06)
• Credit Deficit | (97.16) | (45.05)
2024 MYR starting balance:
CREDIT BALANCE AT END OF SEPT. 30, 2024 | A | B
• 2021 Deficit | 0.00 | (17.06)
• 2022 Deficit | (97.16) | (45.05)
• 2023 Deficit | (97.16) | (45.05)
This means that the ending balance for 2024 is lower than expected.
The above is from dev so using all fake data
The text was updated successfully, but these errors were encountered: