VDS and TDS: who deducts, how much, and what you must issue

Deduction at source catches businesses out because the obligation sits with the wrong party's instinct. It is not the supplier's job to tell you to deduct. It is your job to deduct before you pay them — and if you do not, the liability is generally yours, not theirs.

Two separate regimes

VDS is VAT deducted at source, under the VAT and Supplementary Duty Act. TDS is tax deducted at source, under the Income Tax Ordinance. They have different rates, different rules about which payments they apply to, and different certificates. A single supplier payment can attract both.

Treating them as one thing — a single 'withholding' line on a payment — is the root cause of most reconciliation trouble, because the two amounts are deposited against different heads and certified on different forms.

Who has to deduct

The withholding entity categories are defined by the rules and include government bodies, NGOs, banks and financial institutions, educational institutions, limited companies and businesses above specified thresholds. If your business falls into a withholding entity category, the obligation attaches to payments you make for specified services regardless of whether the supplier raises it.

The four-step obligation

1. 1Deduct the correct amount at the time of payment or credit, whichever is earlier
2. 2Deposit the deducted amount to the treasury within the prescribed time, against the correct code
3. 3Issue the certificate to the supplier so they can claim credit for what you withheld
4. 4Report the deduction in your own return for the period

Failing at step one creates an exposure for the full amount you should have deducted. Failing at step two turns money you are holding into a default. Failing at step three does not usually create a penalty for you, but it makes your supplier's position impossible and damages the relationship. Failing at step four causes the mismatch that gets noticed.

Why spreadsheets fail here specifically

Deduction at source has an unusual data shape: one payment produces a reduced cash outflow, a liability to the treasury, a document owed to a third party, and a line on a return. Four consequences from one event. In a spreadsheet each one is recorded separately, by hand, and they fall out of agreement quietly.

The specific failures worth watching for:

• Deduction calculated on the VAT-inclusive amount when it should be on the base, or the reverse
• The deducted amount netted into the expense rather than held as a liability, so the deposit has no matching balance to clear
• A deposit made for a total that cannot be traced back to the individual supplier deductions inside it
• Certificates issued from a manually maintained list that has drifted from the payment records
• Threshold-based deductions missed because nobody was tracking cumulative payments to that supplier across the year

Making it structural

The design that holds up is one where the deduction is an attribute of the payment rather than a separate process. When you record the supplier payment, the rate applicable to that supplier and service category is applied, the gross, deduction and net stay linked on one record, the liability posts automatically, and the certificate is generated from that same record rather than retyped from a register.

At that point the four consequences cannot disagree with each other, because they are four views of one entry rather than four entries.