What's new

The issue where scheme opening balances were incorrectly migrated as ledger opening balances has been resolved. This occurred when a scheme was redeemed in the current financial year and the party's data was migrated again from the previous year. Going forward, even if a party's scheme is closed and the data is migrated again, the amount will be correctly imported as a scheme opening balance.

The issue where the system incorrectly enforced the "pincode is mandatory" validation for all account groups has been resolved. With the upcoming update, the pincode field will be mandatory only for the following account groups: sundry debtors sundry creditors unsecured loans for all other account groups (such as indirect expenses), users can now save the ledger without providing a pincode. The validation is applied only to the applicable account groups as intended. This fix has been tested and verified.

An issue was identified where certain account ledger were not appearing in the ledger transaction report, while still being visible in the trial balance. Root cause: the issue occurred when the branch associated with the ledger had been changed. Impact: affected ledgers were not displayed in the ledger transaction report. Users were unable to open the corresponding vouchers for those entries. Resolution: the issue has been fixed, ensuring that ledgers are now correctly displayed in the ledger transaction report regardless of branch changes. Users can now successfully view and access the related vouchers. This fix has been tested and verified