Skip to content

v14.74.0

Compare
Choose a tag to compare
@frappe-pr-bot frappe-pr-bot released this 11 Sep 05:11
· 47 commits to version-14 since this release

What's Changed

  • We've added a new filter called Handle Employee Advances in the "Accounts Payable" report to ensure that expense claims, payment entries, and journals linked to employee advances are accurately reported. #43073
  • We’ve fixed an issue where a common party advance journal entry wasn't being canceled when canceling a Sales Invoice, ensuring all related entries are now properly handled. #43096
  • We have fixed an issue in the Stock Ledger Entry to ensure the Quantity is recorded correctly after transactions. #43104
  • We’ve fixed an issue with the Process Payment Reconciliation form to correctly handle the Default Advance Account field, ensuring smoother payment reconciliations. #43091
  • We have fixed an issue where creating an invoice in a foreign currency for a common party would cause a multicurrency error on the Journal Voucher form. Now, the multi-currency checkbox is enabled based on the account currency, ensuring smoother transaction creation. #43119
  • We've updated the Available Batch Report to show the current date by default in the On This Date field, instead of showing the date from one month prior. #43124
  • We've fixed an issue where navigating to the respective voucher type after reconciling a payment entry against an invoice had failed. #43126
  • We have fixed the Delivery Note form to ensure validation error messages are now properly translated for better clarity. #43128
  • We’ve fixed the "actual cost" calculation in the Procurement Tracker report to display the correct values, ensuring more accurate reporting. #43137
  • We've fixed the Party Details function to ensure it always returns consistent and error-free information. #43135
  • We’ve added a new report called "Invalid Ledger Entries" to help you quickly identify discrepancies between your Trial Balance report and AR/AP reports caused by cancelled documents that failed to cancel their associated ledger entries. #43147
  • We have fixed an issue where the BOM Update Log sometimes remained "In Progress," preventing users from creating a new log to update costs. The system will now allow a new log if the previous job is not completed within one day. #43156

Full Changelog: v14.73.2...v14.74.0