Account TDS Deduction
Overview
Account TDS Deduction is built for businesses operating under Indian TDS regulations (or any similar withholding-tax regime) that need to deduct tax at source on vendor bills and payments without leaving the standard Odoo Accounting workflow. Instead of manually calculating withholding amounts or creating separate journal entries by hand, an accountant configures TDS thresholds once on the relevant expense accounts, and the system takes over: it watches individual and PAN-aggregated transaction totals, warns the user in real time, and lets them post a fully reconciled TDS entry from the Bill or Payment form itself.
2 Hours of FREE Support Included
Every purchase includes up to 2 hours of free support â for help with installation, configuration, or fixing any bug you find in this module. Buy with confidence; we're here to make sure it works for you.
Key Features
- Setup TDS Deduction control on the Chart of Accounts level, per expense account.
- Set thresholds for Individual and Aggregated transactions, triggering an alert directly on the Bill form.
- Configure more than one TDS setup for each expense account when multiple slabs or sections apply.
- Reusable alert engine that shows a clear summary of the applicable amount at the moment of posting.
- Start Date and End Date fields in Accounting Settings to control the period used for TDS threshold computation.
- Automatic alert and chatter logging of the TDS summary when a Bill's individual or PAN-aggregated total exceeds the configured threshold.
- TDS entry creation from the Bill - a dedicated TDS button appears automatically once the Bill is confirmed.
- TDS entry creation from the Payment - the same TDS button is available after Payment confirmation.
- Automatic reconciliation - the TDS entry created from a Bill is reconciled with that Bill immediately on confirmation.
- PAN-based vendor aggregation using a new PAN Card No. field on the vendor (Partner) master, so totals are correctly aggregated across all vendors sharing the same PAN.
How This Module Helps Your Business
For finance teams handling statutory withholding tax, this module removes the two biggest risks in a manual process: missed deductions and incorrect threshold tracking across vendors.
- Compliance by design: TDS thresholds are enforced at the Chart of Accounts level, so no expense line can slip through without a check.
- Vendor-level visibility: PAN-based aggregation catches cases where the same vendor is entered under multiple contact records, a common cause of under-deduction.
- Audit trail: Every alert and TDS computation is logged in the chatter of the Bill, giving auditors a clear record of why and when TDS was applied.
- Faster month-end closing: Automatic reconciliation between the TDS entry and the originating Bill eliminates a manual matching step for the accounting team.
- Flexible periods: Start Date/End Date settings let you re-baseline aggregated thresholds for a new financial year without touching historical data.
Who Is This For
- Companies in India (or any country with a similar withholding-tax requirement) that must deduct TDS on vendor bills and remit it separately.
- Accounting teams currently tracking TDS thresholds in spreadsheets outside Odoo.
- Businesses with high vendor bill volume where individual and aggregate threshold monitoring needs to be automatic rather than manual.
- Odoo Accounting users who want TDS entries created and reconciled from the same Bill/Payment screen they already work in.
Installation and Configuration
1. Install the Account TDS Deduction module
After installation, new fields appear in Accounting Settings. Fill in the TDS Journal, TDS Withholding Account, Start Date and End Date:

2. Go to Accounting -> Configuration -> TDS Configuration

3. Open and create the TDS Configuration records and TDS slabs to be deducted
4. Create the relevant tax in the Tax master and link it to the TDS slabs created above. Note: the percentage on the tax master should be entered as a negative value
5. A new PAN Card No. field is added on the vendor (Partner) master. It is used to compute the aggregated amount across all vendors sharing the same PAN

6. Go to the Chart of Accounts
7. Open the relevant account and complete the TDS setup where deduction is required
8. Create a Bill and select the configured account at the line level. On confirmation, if the individual or PAN-aggregated total exceeds the configured threshold, an alert is triggered and logged in the chatter, showing which TDS section applies, the Individual/Aggregated configuration, and the aggregated total by vendor PAN

9. The alert identifies the TDS section to deduct. Click the TDS button to open the wizard, enter the details, and click Confirm to deduct the TDS

10. The TDS entry is created and automatically reconciled with the Bill

11. TDS entry shown reconciled against the Bill

12. The same TDS button is available on the Payment form

13. Select the TDS section, enter the base amount, and confirm

14. TDS entry created from the Payment

Why This Module Matters
Withholding tax rules leave no room for missed thresholds or inconsistent vendor tracking - both lead to compliance exposure and reconciliation headaches at closing time. Account TDS Deduction embeds the threshold logic directly into the Chart of Accounts and vendor master, so the check happens automatically every time a Bill or Payment is confirmed, with a permanent chatter record of what was applied and why. Because the TDS entry is created and reconciled from the same screen the accountant is already working in, there is no separate spreadsheet, no duplicate data entry, and no gap between the business transaction and its statutory deduction.
Frequently Asked Questions
Does this module work with standard Odoo Accounting Bills and Payments?
Yes. The TDS button appears directly on the confirmed Vendor Bill and on the Payment form - no separate
screens or duplicate data entry are required.
How does the module know when to alert me?
Thresholds are configured on the Chart of Accounts, individually and/or as an aggregate across a
vendor's PAN Card No. When a Bill or Payment crosses either threshold within the configured Start
Date/End Date period, an alert is shown and logged in the chatter.
Can one expense account have more than one TDS rule?
Yes. Multiple TDS configurations/slabs can be linked to the same expense account when different
sections or rates apply.
What happens to the TDS entry once it's created?
When created from a Bill, the TDS entry is automatically reconciled against that Bill. When created
from a Payment, you select the TDS section and enter the base amount to generate the entry.
Is support available if I need help with configuration or customization?
Yes, direct support, customization, and implementation help are available - see the contact details
below.
Website: https://www.nimmutechnologies.com
Email: subashmca2017@gmail.com
Telegram: https://t.me/Chubbu007
We aim to respond to all support requests within one business day.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module