Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: utility report for identifying invalid ledger entries (backport #43144) #43147

Merged
merged 5 commits into from
Sep 10, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Sep 10, 2024

On rare cases, where a cancelled document like Sales Invoice, Journal or Payment Entry has failed to cancel is associated ledger entries, your normal Trial Balance report and AR / AP report will start to differ. On such, cases, it is very hard to identify the cause. This report is to serve the purpose of quickly identifying such invalid entries.

This is very simple report with filters for Company, Date range and account.
Report will fetch all active ledger entries based on the filter and check if the vouchers associated with those entries are cancelled. If so, it will be reported.

no-docs


This is an automatic backport of pull request #43144 done by Mergify.

@github-actions github-actions bot added the needs-tests This PR needs automated unit-tests. label Sep 10, 2024
@ruthra-kumar ruthra-kumar merged commit 6895efe into version-14-hotfix Sep 10, 2024
11 checks passed
@ruthra-kumar ruthra-kumar deleted the mergify/bp/version-14-hotfix/pr-43144 branch September 10, 2024 10:30
@frappe-pr-bot
Copy link
Collaborator

🎉 This PR is included in version 14.74.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
needs-tests This PR needs automated unit-tests. released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants