-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
fix: better indicator base amount for Tax Witholding in Journal Entry #44660
Conversation
Hello @ruthra-kumar |
Is there any way to identify a TDS overbooked scenario, especially through Journal? If so, we can simply report it as overbooked through a new column in the report, rather than approximation. |
How about this approach?
This field than forms basis for the base TDS amount. |
I'm not sure. Adding one more field to Journal Entry further increases complexity and maintenance. Unfortunately, using Journal Entry for everything has lead to this unavoidable ambiguity. How about a new doctype just for booking TDS? similar to how Landed Cost Voucher works. This allows for separation of concern and better traceability of TDS amounts |
Agreed
Bigger project. I'll think about it. Until then maybe we keep this fix and take this up as a refactor |
…-44660 fix: better indicator base amount for Tax Witholding in Journal Entry (backport #44660)
…-44660 fix: better indicator base amount for Tax Witholding in Journal Entry (backport #44660)
Support Ticket: https://support.frappe.io/helpdesk/tickets/26923
Use case
Over deduction of TDS from Journal Entry for an expense booked.
Issue
Excess amount reported forms part of income of supplier if reported as is.
Implementation
Base amount for TDS is lower of total JV value or reverse calculation (from tax rate and tax amount being deducted)
This is to based on the assumption that supplier is deducting TDS manually while staying compliant and there is no under deduction.
backport to version-14 and version-15 is expected