Effective May 2026, the Kenya Revenue Authority (KRA) has taken a decisive step in tightening VAT compliance by integrating export processes in the Integrated Customs Management System (iCMS) with VAT return filing on iTax.

Under this framework, validated export values are now automatically pre-filled in VAT returns once the relevant export documentation is issued and confirmed by Customs. This effectively closes the gap between customs declarations and VAT reporting, ending the long-standing practice where exporters manually declared zero-rated supplies.

But this is not an isolated reform. It sits within a broader, deliberate shift by KRA toward pre-completed VAT returns, driven by transaction-level data from multiple systems.

What Has Changed in May 2026

The immediate change is straightforward, but its implications are far-reaching:

• Export declarations made in iCMS, once validated by Customs, now flow directly into iTax
• These values are automatically reflected as zero-rated supplies in the VAT return
• Manual entry of export figures has effectively been eliminated

The trigger point is important; only exports backed by issued and validated customs documentation will populate the VAT return. This introduces a hard link between customs clearance and VAT recognition.

In practice, the VAT return is no longer a primary declaration tool it is now a system-generated output of verified transactions.

The Pre-Filled VAT Return Agenda

To understand the significance of this change, it needs to be viewed alongside KRA’s earlier move toward pre-populated VAT returns.

In December 2024, KRA introduced pre-filled VAT returns for November 2024 transactions. These draft returns were populated using data from the Tax Invoice Management System (TIMS) (including eTIMS), Kenya’s e-invoicing platform. Taxpayers were required to review and confirm their returns by 20 December 2024.

KRA was explicit in its position:

• VAT returns would increasingly rely on transaction-level data submitted in real time
• Input VAT would only be allowed where validated through TIMS/eTIMS or supported by customs import declarations
• Unvalidated claims would not qualify for a deduction

At that stage, VAT returns remained formally self-assessed, but the direction of travel was clear. The May 2026 iCMS integration completes another piece of that architecture by bringing export data into the same pre-filled ecosystem.

How the System Now Works End-to-End

Kenya’s VAT reporting environment is evolving into a fully connected system:

• Sales data → captured through TIMS/eTIMS (e-invoicing)
• Import VAT → validated against customs import declarations
• Export values → now sourced directly from iCMS

The VAT return effectively becomes a consolidated output of validated data streams, rather than a document built from scratch by the taxpayer.

For exports specifically:

1. Goods are declared in iCMS
2. Customs validates and issues export documentation
3. The system transmits the verified value to iTax
4. The VAT return is pre-filled accordingly

This removes interpretation and replaces it with system certainty.

Why This Matters: A Structural Shift, Not Just Automation

1. The “single source of truth” is now enforced

Export values in VAT returns must match customs data because they originate from it. This eliminates one of the most common sources of audit queries.

2. Refund integrity is strengthened

Exporters in refund positions will now be assessed against verified export transactions, not self-declared figures. Missing or delayed validations will directly impact refund claims.

3. Compliance risk has moved upstream

Errors are no longer “fixed” at VAT return stage. If the customs declaration is wrong, the VAT return will also be wrong. The correction process becomes more procedural and less flexible.

4. The VAT return is becoming a confirmation tool

The role of the taxpayer is shifting from preparing returns to reviewing and confirming system-generated data.

Practical Considerations for Businesses

This shift requires a change in operational mindset:

• Customs accuracy is now tax-critical; Export declarations must be treated as VAT-relevant data points, not just logistics documentation.
• Validation timing matters; Exports declared but not validated within the tax period will not appear in that month’s VAT return.
• Reconciliations must move earlier in the process; Waiting until VAT filing stage is no longer sufficient.
• Internal alignment is essential; Tax, finance, and customs teams must work from the same dataset and timelines.

Kenya in the Global Context

Kenya’s approach reflects a broader global trend often described as the “Death of the VAT Return” where traditional periodic reporting is gradually replaced by real-time or near real-time transaction reporting.

This model typically combines:

• E-invoicing (TIMS/eTIMS)
• Transaction-level reporting
• System validations (customs, invoicing platforms)
• Pre-completed VAT returns

In Africa, adoption is still uneven. Angola is one of the few jurisdictions that has also introduced pre-filled VAT returns at scale. Kenya’s multi-system integration linking invoicing, customs, and tax reporting places it among the more advanced implementations on the continent.

Key Risks and Transitional Issues

Despite the clear policy direction, exporters should expect some friction:

• Timing mismatches between export declaration and customs validation
• System dependencies, particularly where corrections are required
• Initial reconciliation gaps during the transition phase

These are not design flaws they are typical of systems moving from manual to data-driven compliance models.

Conclusion

The integration of iCMS with iTax is  a critical milestone in Kenya’s VAT digitalisation journey. It does more than automate export reporting it fundamentally redefines it.

VAT returns are no longer imput manually, they are assembled by the system. The taxpayer’s role is increasingly to validate, reconcile and confirm.

When viewed alongside TIMS-driven pre-filled returns, this reform signals a clear end-state: a VAT environment where compliance is embedded in transaction systems, not reconstructed at filing stage. The takeaway is simple but consequential get the data right at source, because that is now what the VAT return reflects.

Source: Kenya Revenue Authority