How to Dispute a Wrong Auto-Populated VAT Return (2026)

What You Can and Cannot Dispute

The auto-populated VAT return has two sides: sales (which KRA pre-fills from your eTIMS data) and purchases (which KRA pre-fills from your suppliers’ eTIMS data). KRA treats each side differently for dispute purposes:

Sales side - locked, cannot edit

The sales figure on your VAT return is pulled from your eTIMS transaction history. KRA locks this field in iTax to prevent under-declaration of sales. You cannot reduce it directly - if you believe it is wrong, you must file as-is and dispute via Notice of Objection.

You can add upward adjustments (e.g., sales made outside eTIMS that should have been on the return) - those go in the “Other Sales” field. You cannot subtract - even if a sale is obviously duplicated.

Purchases side - editable

The purchases figure is pre-filled from your suppliers’ eTIMS data, but the field is editable. If a supplier’s invoice is missing from the auto-populated CSV (because the supplier transmitted late or captured your PIN wrong), you can add it manually.

The risk: KRA may later remove manually-added purchases if they cannot verify them against the supplier’s eTIMS data. Always keep the supplier’s original eTIMS-compliant invoice as proof.

For the underlying mechanics of how the auto-populated return pulls your data, see our auto-populated VAT return guide. For how KRA’s VAT ledger works behind the scenes, see our VAT ledger explained guide.

Common Discrepancy Types - and What Causes Them

In our experience handling disputes for Kenyan SMEs, six types of discrepancies account for 90%+ of all auto-populated return issues:

Inflated sales from duplicate eTIMS transmission

You re-transmitted an invoice that had a 'failed' status but actually went through. KRA's duplicate-check service usually catches this, but during outages (peak filing days) it sometimes lets both versions through. The duplicate appears as a phantom second sale on your return.

Missing purchases from suppliers who transmitted late

Your supplier transmitted your eTIMS invoice on the 18th of the month. KRA's auto-population for the current period closed on the 17th. The purchase does not appear on your current return - it will appear on the next period's CSV. You can add it manually to the current return if you have the supplier's invoice.

Missing purchases from suppliers who captured your PIN wrong

Supplier entered one wrong digit in your KRA PIN. KRA matched the invoice to the wrong PIN - your supplier's invoice exists, but on someone else's ledger. The fix: ask the supplier to issue a credit note (against the wrong PIN) and a new invoice (with your correct PIN).

Stock movements misclassified as sales

When you move stock between branches (Nairobi to Mombasa) through eTIMS, the platform sometimes treats the stock movement as a B2B sale. Your sales figure is inflated by the inter-branch transfer. The fix: file a Notice of Objection with the stock transfer documentation.

Credit notes not flowing through to the auto-population

You issued a credit note to a customer through eTIMS (good practice). However, KRA's auto-population service sometimes lags on credit notes - the credit note does not reduce the sales figure on the return. The credit appears on the next period's CSV.

Refund/return invoices misclassified

A customer returned goods. You issued a refund. The refund invoice type in eTIMS may not be properly recognized by the auto-population engine, leaving the original sale in your return with no offsetting refund. Dispute with the original sale invoice, the refund invoice, and the customer return documentation.

The Step-by-Step Dispute Process

Disputing a wrong auto-populated figure requires a structured sequence. Skipping any step weakens your case:

01
Document the discrepancy before filing
Compare the auto-populated figure against your local sales records. Identify exactly which invoices are duplicated, missing, or misclassified. Build a one-page summary: invoice number, date, amount, what KRA shows, what your records show, and the discrepancy. This is your dispute evidence.
02
File the return by the 20th deadline with the disputed figure
Do NOT miss the 20th deadline to dispute. Late filing triggers an automatic KES 10,000 penalty and a KRA risk flag - it does not give you more time to dispute. File as-is, pay any VAT due (including the disputed excess), and prepare to claim it back through the dispute.
03
Submit a Notice of Objection within 30 days
Log into iTax, go to Returns > File Returns > Notice of Objection. Select the VAT return you just filed. Write a clear, factual objection: 'I dispute KES X of sales/inflated VAT on this return because [specific reason]. Evidence attached.' Upload your evidence documents.
04
Wait for KRA's acknowledgment (usually within 7 days)
KRA sends an acknowledgment SMS and email once the objection is logged. The acknowledgment includes a reference number - quote this in all subsequent correspondence. If you do not receive acknowledgment within 7 days, call 020 499 9999 and quote your iTax submission receipt number.
05
Respond to KRA's information request (if any)
KRA's audit team may request additional evidence: bank statements, contracts, supplier confirmations, etc. Respond within the timeframe they specify (usually 14 days). Late responses result in the objection being rejected for 'insufficient evidence'.
06
Receive KRA's decision (30-90 days)
KRA issues a decision letter. If they uphold your objection, an amended assessment is issued - the adjustment flows into your next VAT return as a credit. If they reject, you can appeal to the Tax Appeals Tribunal within 30 days of the rejection letter.

Late objection = forfeited right to dispute

If you miss the 30-day Notice of Objection window, you forfeit the right to dispute that specific return. KRA treats the return as final. The only path forward is a Voluntary Disclosure - which requires paying the disputed amount first and then applying for waiver of penalties. Always engage a tax agent early to keep the timeline on track.

Writing a Notice of Objection - What to Include

A well-structured Notice of Objection dramatically increases the chance of KRA upholding it. Include these seven elements in every objection:

Return reference: the iTax receipt number of the disputed return
Tax period: the month/year of the disputed return (e.g., “July 2026”)
Disputed amount: specific KES figure you dispute
Discrepancy type: duplicate sales, missing purchases, misclassified stock, etc.
Factual basis: one-paragraph explanation of what went wrong
Evidence attachments: list of attached documents (eTIMS exports, supplier invoices, credit notes)
Relief sought: what you want KRA to do - amend the return, adjust the next period, refund the overpaid amount

Keep the notice factual and concise. Avoid emotional language, accusations, or speculation. KRA’s audit team reads hundreds of objections per week - the ones that get actioned are the ones that present clear evidence with no fluff.

Want us to write the Notice of Objection?

We have filed 200+ successful VAT disputes with KRA. We handle the documentation, the iTax submission, and the audit correspondence end-to-end. Flat fee per dispute.

Get Dispute Help

Filing During a Pending Dispute

A common confusion: “My objection is pending for the July return. Do I still file the August return on the 20th?” Yes. Each return is independent. The disputed July return stays as-filed. You continue filing August, September, October returns normally on their 20th deadlines.

Continue filing each month on time

Late filing penalties apply regardless of any pending dispute. Pay the VAT due for each month on time, even if some of it relates to the disputed issue - you can claim it back later.

The dispute does not 'pause' future returns

Each return covers its own tax period. A dispute on July does not extend the August 20th deadline. The only thing that flows between periods is the eventual adjustment - if KRA upholds your July objection, the credit flows into your August (or later) return as an opening adjustment.

Keep a parallel ledger of disputed amounts

Track the disputed KES amount in your own records so you know which future return is supposed to receive the credit. When KRA's decision letter arrives, verify the credit appeared on the correct period's auto-populated CSV.

If KRA rejects the objection, you can appeal

Within 30 days of KRA's rejection letter, file an appeal to the Tax Appeals Tribunal (TAT). The TAT is an independent body that reviews tax disputes. TAT appeals are formal legal proceedings - engage a tax advocate.

Related: The KRA VAT audit process can be triggered by disputes. See our KRA VAT audit guide to know what to expect if your dispute escalates.

Frequently Asked Questions

Can I dispute an auto-populated VAT return figure I think is wrong?

Yes - but only through specific channels. You cannot reduce auto-populated sales values directly in iTax (KRA locks those fields to prevent fraud). To dispute, you must (1) document the discrepancy, (2) file the return with the auto-populated figure as-is by the 20th deadline, (3) submit a Notice of Objection within 30 days of filing, and (4) work with KRA's audit team to correct the underlying eTIMS data. Never skip the 20th deadline - late filing triggers an automatic KES 10,000 penalty regardless of any dispute.

What if the auto-populated sales figure is higher than my actual sales?

Three typical causes: (1) a duplicate invoice was transmitted to KRA and counted twice, (2) a customer returned goods but you did not issue a credit note through eTIMS, or (3) a stock movement was misclassified as a sale. File the return with the inflated figure (pay the excess VAT to avoid late-payment penalties), then submit a Notice of Objection within 30 days attaching: your eTIMS transaction export, your local sales records, and the specific invoices that were duplicated or misclassified. KRA's audit team will adjust the next return.

What if my purchases are missing from the auto-populated CSV?

You can manually add missing purchases to the return - the purchases field is not locked. Download the CSV from iTax, add the missing purchase lines (with supplier PIN, invoice number, date, and VAT amount), save, and upload the modified CSV back to iTax. The system will accept the additions. Keep proof of every added purchase (eTIMS-compliant invoice from the supplier) for 7 years in case of audit. See our auto-populated VAT return guide for the full workflow.

How long does KRA take to resolve a VAT dispute?

Standard Notice of Objection processing time is 30-90 days from submission. Complex cases (large adjustments, multi-period disputes, audit-triggering discrepancies) can take 6-12 months. During this time, you continue filing monthly returns normally - the disputed return stays as-filed. If KRA upholds your objection, they issue an amended assessment and the adjustment flows into your next return.

Will disputing a VAT return trigger an audit?

Not necessarily. KRA's risk engine evaluates each dispute on its merits - a well-documented, single-period dispute with clear evidence rarely triggers an audit. However, repeated disputes, disputes involving large amounts (KES 1M+), or disputes on the same issue across multiple periods do flag your account. Always engage a tax agent to prepare dispute documentation - a poorly-prepared dispute is worse than no dispute.

Can I get a refund of VAT I overpaid due to a wrong auto-populated figure?

Yes. Once KRA upholds your objection and amends the return, the overpaid VAT becomes a credit on your iTax ledger. You can either offset it against future VAT payable (the simplest path - it just reduces next month's payment) or apply for a cash refund. Cash refunds require a separate application and take 3-12 months to process. Offsetting is instant and free - prefer it unless the overpayment is huge.