Handling deductions in accounts receivable (AR) is a revenue recovery problem that most teams treat as a reconciliation task.
A short payment lands, gets logged, and from that point most AR teams handle every deduction the same way. Some get chased. Some get written off. Which one happens usually depends on who had time that week, not on whether the deduction was recoverable.
Not All Short Payments Are the Same
The deduction type determines what recovery looks like.
Quality and delivery disputes come from customers claiming an issue with goods or service. These need the customer's documentation before any resolution can move forward. Penalty calculation disputes happen when a customer disagrees with how many days late their payment was. Resolving these requires the original signed contract.
Unauthorized deductions are short payments with no reason given. They are often the most recoverable, and they are also the ones most often written off because nobody followed up.
Chasing a valid deduction damages the customer relationship. Writing off an invalid one means the revenue never comes back.
The TDS Gap
When an Indian B2B customer pays you, they withhold Tax Deducted at Source (TDS) at the rate the applicable section sets, such as 2% or 10% depending on the nature of the payment. That part is expected.
The customer is also required to remit that withheld amount to the income tax department. If they deduct it from your payment but do not remit it, the amount does not appear in your Form 26AS (Form 168 under the Income-tax Act, 2025). Your AR ledger shows a deduction that looks handled. Your income tax record shows a credit that never arrived.
Most companies find this gap during annual income tax filing or an audit. By then, documentation is incomplete, the recovery window is narrow, and the conversation with the customer is difficult. Recording each deduction against its invoice when the payment arrives, then matching it to Form 26AS as each quarter's statement updates, means the gap is raised with the customer within the quarter, while recovery is still practical.
Which Deductions Are Worth Chasing
Picking the right disputes to raise is what drives recovery over time. Statutory withholdings and contractually agreed deductions are not disputes at all; the TDS gap is a follow-up with the customer, not a claim against them.
Making the call requires:
- The original invoice and payment record
- The reason code the customer gave
- The contract terms, particularly payment period and penalty clauses
- That customer's deduction history
Without a system behind it, the decision gets made on deadline pressure. Month-end approaches, someone needs to clear the ledger, and deductions get written off because the alternative involves three handoffs with no tracking.
Lasting reductions in deductions do not come from processing faster. It comes from raising the right disputes and closing the right ones.
Where Manual Handling Breaks
- Detection happens at month-end, not at payment. Deductions accumulate throughout the cycle and the team works backwards to understand them at close, by which point some recovery windows have already passed.
- Ownership is unclear across teams. AR flags the short payment. Sales validates the customer's reason. Finance approves the write-off. Three handoffs, no shared tracking. Deductions age into write-offs because the handoff outlasts the recovery window.
- TDS reconciliation happens at year-end. The gap between what a customer deducted and what they remitted to the income tax department only surfaces during income tax filing or an audit. Recovery at that point is hard, and the relationship conversation is harder.
- Follow-up lives in personal inboxes. There is no record of what the customer committed to, no escalation when they go quiet, and no way to see which disputes are aging.
How AR Automation Changes This
Detection starts at reconciliation. When AR automation reads a bank statement or remittance advice and sees a short payment, it classifies the deduction type before manual review. Most standalone dispute tools assume someone already caught the deduction. AR automation built into the full order-to-cash cycle catches it at the point of payment, before month-end cleanup turns eligible disputes into write-offs.
Once classified, the system checks whether the deduction is eligible to dispute. For a quality dispute, it attaches the original invoice and the customer's reason code. For a penalty dispute, it pulls the contract terms. For an unauthorized deduction, it flags it for recovery. Deductions that should be accepted are closed with a credit note or adjustment.
Each TDS deduction is recorded against the customer and invoice as the payment arrives, then matched against Form 26AS as each quarter's statement updates. If the customer deducted but did not remit, the gap is flagged within the quarter, not at year-end.
Every open dispute carries a follow-up timeline. If the customer does not respond within the defined window, it escalates. The ownership question goes away because the system holds the trail.
Alfred for Finance
Alfred AR handles deduction and dispute management inside the full order-to-cash cycle. Detection happens during cash application, when Alfred reads the bank statement or remittance advice and identifies the short payment. Disputes are then raised and tracked in collections.
When a deduction comes in, Alfred classifies it, checks whether it is eligible to dispute (only a deduction the customer has claimed can be disputed), and raises it with the invoice, reason code, and contract reference already attached. For TDS deductions, it records the amount against the invoice and matches it against Form 26AS each quarter, flagging the gap if the customer did not remit. Follow-up is tracked against every open dispute, with escalation built into the timeline. When the customer responds, the reply lands in Alfred rather than a personal inbox, so the team can see which disputes have been actioned and which are still waiting. Accepted deductions are closed with the appropriate adjustment once a person approves it. Where recovery needs to be pursued, Alfred proposes a debit note and moves it into collections.
Deduction detection depends on reconciliation. You cannot triage a deduction you have not caught. Alfred catches it when the payment arrives, so the dispute is raised before the recovery window closes. Learn more about Alfred for Finance.
If you are dealing with deduction backlogs, unreconciled TDS gaps, or month-end write-offs that should have been disputes, book a meeting now.
