Payables Discipline Is a Compliance Function
Hospital TDS and vendor payment compliance is usually treated as accounting housekeeping, which understates it. Tax deducted at source is a statutory obligation where the hospital is the deductor, and failure to deduct correctly, deposit on time, or report accurately creates exposure that sits with the organisation and sometimes with named officers. It is a compliance function that happens to be performed by the accounts team.
The exposure is broader in a hospital than in many businesses because of the payment mix. A hospital pays salaried staff, visiting consultants on professional fee arrangements, revenue-share doctors, housekeeping and security contractors, equipment maintenance providers, rent, and a long tail of goods suppliers. Several of these attract different treatment, and the classification decision is made by whoever raises the payment.
This article is conceptual. TDS sections, rates, thresholds, and return timelines are amended and are fact-specific. The structure below tells you where to place controls; a qualified tax professional should tell you what to deduct.

Where TDS Applies Across a Hospital's Payment Mix
The practical work is classification. Payments for professional or technical services, contractual work, rent, commission, and purchases of goods each have their own treatment under the relevant provisions, and the applicable threshold and rate follow from that classification. The error that causes the most trouble is not choosing the wrong rate; it is classifying a payment as a goods purchase when the substance is a service.
Maintenance contracts illustrate the problem well. An annual maintenance contract on biomedical equipment may be substantially a service arrangement even where the invoice emphasises parts. Housekeeping and security contracts, laundry, catering, and IT support are all service arrangements delivered by entities that sometimes invoice like suppliers. The substance of the arrangement governs, and the substance is in the contract, not the invoice narration.
Build the classification into vendor master data rather than deciding it per invoice. When a vendor is onboarded, its payment nature is determined once, reviewed by someone competent, and applied automatically thereafter. Per-invoice classification by an accounts clerk under month-end pressure is the reliable source of error.
Payment categories to classify at vendor onboarding
- Professional and technical services, including visiting consultants
- Contractual services such as housekeeping, security, catering, and laundry
- Equipment maintenance and annual maintenance contracts
- Rent for premises and equipment
- Purchase of goods, pharmacy stock, and consumables
- Commission, brokerage, and referral-adjacent arrangements
Doctor Payouts and Deduction Handling
Doctor remuneration is the area where hospitals most often carry unexamined risk, because the arrangements vary and the classification consequences are significant. A salaried employee, a full-time consultant on a professional retainer, a visiting consultant paid per case, and a revenue-share arrangement are legally different relationships even where the clinical work looks similar.
The distinction that matters most is employment versus professional engagement, because it determines the entire deduction and reporting treatment. That determination rests on the substance of the relationship — control, exclusivity, how remuneration is structured, and what the contract actually says — not on what the arrangement is called internally. Hospitals that have never had this reviewed for their consultant panel should treat it as a priority.
Operationally, doctor payouts need the same rigour as vendor payments: a calculation traceable to source data, a deduction applied per the determined classification, an approval trail, and a statement the doctor can reconcile. Payout disputes with consultants consume disproportionate senior time, and almost all of them trace to a calculation the doctor cannot independently verify.

“Every consultant payout argument we have had was really an argument about a number nobody could reproduce. Once the statement showed the working, the arguments ended.”
Vendor Onboarding and Identifier Validation
The vendor master is where payables compliance is either established or lost. A vendor should not become payable until its legal name, PAN, GST registration where applicable, bank details, contract, and payment classification are captured and validated. Onboarding a vendor with incomplete data to unblock an urgent payment is how permanent gaps are created, because nobody ever goes back.
Validate identifiers rather than merely collecting them. PAN and GST numbers should be checked against the issuing authority's records, and the legal name and bank account should be verified against the entity, not against the invoice. Bank detail changes deserve particular care — a request to change a vendor's bank account, arriving by email, is a well-known fraud vector and should require verification through a channel independent of the request.
Review the vendor master periodically for dormant records, duplicates, and vendors whose registration status has changed. A vendor master that only ever grows accumulates records that are a control weakness rather than a business relationship.
Vendor master controls
- Mandatory PAN and, where applicable, GST registration validated at source
- Legal name and bank account verified against the entity
- Payment nature and deduction classification determined and recorded
- Bank detail changes verified through an independent channel
- Segregation between who creates a vendor and who approves payment
- Periodic review for duplicates, dormant records, and status changes
Three-Way Matching in a Hospital Context
Three-way matching — reconciling the purchase order, the goods receipt or service confirmation, and the invoice — is the core payables control, and it works in a hospital with two adaptations. First, a substantial share of hospital spend is on services where there is no goods receipt, so the third leg becomes a service confirmation from the department that received the service. Second, emergency purchasing genuinely happens and needs a defined path rather than a workaround.
For services, the confirmation should come from someone with knowledge of whether the service was actually delivered — the biomedical engineer for an equipment service visit, the facilities lead for housekeeping. A confirmation signed by accounts because the invoice looked reasonable is not a control, it is a formality.
Emergency and after-hours procurement should have a documented exception route with post-facto approval within a defined window, and the exception rate should be monitored. A hospital where a large share of purchases go through the emergency route does not have an emergency problem; it has a planning problem wearing an emergency costume.

Payment Run Controls and Segregation of Duties
The payment run is the last point at which an error or a fraud can be stopped, and it deserves explicit controls. The essentials are unglamorous: the person who creates a vendor cannot approve a payment to it, the person who enters an invoice cannot release the payment, approval limits are tiered by value, and every payment traces to an approved invoice traced to an approved commitment.
Duplicate payment prevention is worth a specific mention because it is common and quietly expensive. Invoice numbers should be unique per vendor and the system should block a repeat. Hospitals that pay from scanned copies without this check will pay some invoices twice, and will usually find out only when a diligent vendor mentions it.
A platform such as HealUDoc can hold purchase orders, goods receipts, and vendor invoices in one place so the match is systematic rather than manual, and so approval limits are enforced rather than remembered. The controls themselves — who approves what, at what value — remain a hospital governance decision that should be documented and reviewed annually.
Payment run controls to verify
- Segregation between vendor creation, invoice entry, and payment release
- Tiered approval limits enforced by the system, not by convention
- Duplicate invoice number blocking per vendor
- Payment only against matched and approved invoices
- Exception report for payments released outside the standard route
When to Involve a Professional Advisor
The boundary is reasonably clear. Process design, segregation of duties, master data validation, and matching discipline are internal capabilities a finance team should own confidently. Rates, thresholds, section applicability, return timelines, and the classification of a specific contractual arrangement are matters of current law applied to your facts.
The arrangements that most reward professional review are the doctor engagement structures, any arrangement whose substance differs from its label, and payments to non-resident vendors, where a separate and more demanding set of considerations applies. Get these reviewed once properly and revisit when the arrangement changes.
Keep the review documented. When a question is raised later — internally, by an auditor, or by an authority — a written position prepared at the time by a competent advisor is a materially stronger place to stand than a recollection of what someone decided was reasonable.



