KRA’s eTIMS-IFMIS integration brings government payments deeper into the tax validation trail
For businesses dealing with government, getting an expense accepted for tax purposes has become as much about the electronic record as the payment itself. The KRA eTIMS-IFMIS integration comes at an interesting moment, just months after KRA acknowledged that some legitimate expenses incurred when dealing with government could be difficult to support with eTIMS invoices.
On 31 August 2026, the Kenya Revenue Authority, working with the National Treasury, announced the successful integration of the Electronic Tax Invoice Management System (eTIMS) with the Integrated Financial Management Information System (IFMIS). The announcement requires suppliers doing business with government entities to generate valid eTIMS invoices before submitting supplies for payment processing through IFMIS.
It also introduces another requirement that could prove just as important for businesses: the details on invoices submitted to government entities must correspond precisely with the invoices generated and recorded in eTIMS.
The announcement comes as KRA continues validating the income and expenses taxpayers declare in their returns against electronic records.
The Problem KRA Was Already Being Asked to Solve
The issue became particularly visible during KRA’s rollout of income and expense validation for the 2025 Year of Income.
A business could incur a genuine expense while dealing with government, such as a business permit or licence, but the government entity involved might not provide an eTIMS invoice. That left the taxpayer with a practical problem. The expense could be real, necessary for the business and supported by other documentation, yet the electronic tax record KRA wanted to see might not exist.
That question was put directly to Hakamba Wangwe, KRA’s Chief Manager responsible for eTIMS, during a discussion on the new validation regime.
Wangwe acknowledged that government-related transactions presented a challenge. She explained that taxpayers still needed to account for such expenses in their income tax returns, while KRA was working on a mechanism that would allow taxpayers to input the expenses themselves. The Authority could then validate the information against government data and other available records.
That was an important admission because it showed that the problem was not simply taxpayers failing to comply. There were legitimate transactions where the electronic evidence KRA wanted was not yet being generated at the point of the transaction.
KRA Was Planning More Controls
The conversation with Wangwe also provides useful context for what KRA has done since then.
She explained that the first year of the validation exercise required some flexibility because there would be transactions that were not adequately covered by the available systems. At the same time, she made clear that KRA intended to introduce more controls as the system developed.
She also advised taxpayers to use 2026 to conduct their due diligence and make sure their expenses were properly supported by the end of the year.
That advice now reads differently in light of the August announcement.
KRA is putting more transaction data into systems that can communicate with one another, while the temporary accommodation for unsupported expenses has already been expressly limited to the 2025 Year of Income.
The direction is therefore clear even where individual transactions may still require clarification.
Why Section 16(1)(c) Matters to Businesses
At the heart of the issue is Section 16(1)(c) of the Income Tax Act, which restricts deductions for expenditure where the transaction invoice has not been generated through an electronic tax invoice management system, subject to applicable statutory exceptions.
The tension discussed with Wangwe was whether a taxpayer should lose the ability to claim a legitimate business expense simply because the other party did not provide an electronic tax invoice.
That question became more complicated because Section 23 of the Tax Procedures Act places obligations around the issuance of tax invoices, while Section 16(1)(c) deals with the deductibility of expenditure.
During the interview, the argument was made that the two provisions should be delinked where taxpayers could provide other credible evidence that a genuine business transaction had occurred.
Wangwe’s response was revealing. She explained that KRA’s objective with electronic invoicing was to create an authenticated channel through which transactions could be validated and to protect the integrity of the data flowing into tax returns. Accepting a wide range of alternative documents, she cautioned, could create another verification problem because KRA would have to establish whether those documents were genuine.
That is the fundamental policy tension. Businesses want flexibility where a legitimate transaction cannot produce the expected electronic invoice. KRA wants evidence that can be independently authenticated at scale.
The 2025 Accommodation Was Always Temporary
This is where the 2026 filing cycle becomes important.
KRA allowed taxpayers filing returns for the 2025 Year of Income to declare valid business expenses that were not supported by eTIMS or TIMS invoices. The Authority provided a mechanism through which such expenses could be declared and subsequently subjected to validation.
But that accommodation was specifically tied to the 2025 return.
KRA stated that from the 2026 Year of Income, declared income and expenses would have to be supported by valid electronic tax invoices generated and transmitted through eTIMS or TIMS, subject to the applicable rules and exemptions.
That means taxpayers preparing their 2026 accounts should not assume that the same manual route will be available when those returns are filed in 2027.
The distinction matters. The 2025 filing cycle gave businesses room to deal with gaps in the electronic system. The 2026 cycle is being built around a stronger expectation that transactions will already have an electronic trail.
What the IFMIS Integration Actually Changes
The new KRA notice is significant because it brings that electronic trail directly into government payment processing for suppliers.
A supplier providing goods or services to a government entity must generate a valid eTIMS invoice before submitting the supply for payment through IFMIS. The information on the invoice submitted to the government must then correspond with the information recorded in eTIMS.
That creates a connected chain between the supplier’s invoice, KRA’s tax records and the government’s financial management system.
It also means the government payment process becomes another point at which discrepancies can be detected.
Suppose a supplier submits an invoice to a government entity for an amount that differs from the eTIMS invoice. The two records can be compared. If an invoice submitted to government does not correspond with an electronic tax record, there is another discrepancy for the systems to identify.
The government’s financial transaction and the tax invoice are no longer operating as completely separate records.
This Does Not Automatically Mean Every Government Fee Will Generate an eTIMS Invoice
There is an important qualification here.
The 31 August notice specifically addresses suppliers doing business with government entities and requires them to generate eTIMS invoices before payment processing through IFMIS.
That is not necessarily the same thing as saying every licence, permit, statutory fee or other payment a business makes to a government agency will now automatically produce an eTIMS invoice.
That distinction should be maintained.
The IFMIS integration strengthens the government-side data available to KRA. It does not, from the notice alone, establish the precise electronic invoicing treatment for every type of payment made by taxpayers to government.
This matters because the earlier concern raised with Wangwe included transactions where the taxpayer was paying government, rather than supplying government.
For those cases, the question remains how the relevant government transaction will be represented in the electronic tax records and how KRA will validate it where a conventional eTIMS invoice is not applicable.
The Bigger Change Is the Data Behind Section 16
Wangwe’s explanation of Section 16 provides perhaps the most useful way to understand where KRA is heading.
During the January discussion, she argued that Section 16 had always existed. What had changed was KRA’s ability to back its application with data. In her explanation, Section 23 was about having the data required to support the administration of the rules, while the other provisions of the Income Tax Act continued to operate as before.
That distinction matters.
The electronic tax system does not necessarily create the underlying tax obligation. It gives KRA a much stronger mechanism for checking whether what appears in a taxpayer’s return corresponds with information already held by the Authority.
That is why the government’s integration of IFMIS with eTIMS matters beyond the technical connection between two systems.
It gives the tax authority another structured source of transaction information.
KRA Is Building a Larger Validation Network
Income and expense validation was never solely about eTIMS.
KRA has described the exercise as involving several sources of information, including electronic tax invoices, withholding tax data and Customs records. The purpose is to compare what taxpayers declare against information already available to the Authority.
Wangwe also acknowledged another problem during the earlier interview: fictitious invoices. She explained that as technology develops, people can also find ways to misuse it, making data intelligence and enforcement important parts of KRA’s response.
That helps explain KRA’s insistence on authenticated transaction channels.
A PDF invoice or receipt can show that somebody claims a transaction happened. An electronic record that can be matched against another government system gives KRA a different level of verification.
The IFMIS integration adds another potential connection to that network.
Businesses Need to Reconcile More Than Their Books
For businesses, the practical implication is simple but important: keeping an accounting record of an expense is no longer the whole exercise.
Where eTIMS applies, the business needs the underlying electronic invoice, accurate transaction details and a record that can be reconciled with the tax information available to KRA.
That makes periodic checks of eTIMS and iTax records worthwhile, particularly for businesses with large volumes of transactions.
A company could have correctly recorded an expense in its accounting system and still encounter a problem if the corresponding electronic invoice was issued incorrectly, associated with the wrong taxpayer PIN or otherwise fails to appear as expected in KRA’s records.
The same principle applies to suppliers dealing with government. The invoice generated in eTIMS, the invoice submitted to the government and the transaction ultimately processed through IFMIS should agree.
The 2026 Tax Year Will Test the New Architecture
The real test will come when businesses file their 2026 income tax returns in 2027.
By then, the special accommodation that applied to the 2025 Year of Income is not expected to provide the same fallback. At the same time, KRA will have more electronic transaction data with which to compare taxpayers’ declarations, including data generated through the government financial system.
That does not mean every mismatch will automatically result in a disallowed expense. Businesses still need to consider the statutory rules, exemptions and the nature of each transaction.
But it does mean that relying on a paper receipt, payment confirmation or internal accounting entry without establishing how the transaction fits into the applicable electronic tax framework is becoming a riskier approach.
For businesses, the sensible response is to resolve documentation gaps during the year rather than waiting until the return is being prepared.
Seven Months After the Warning, the System Is Catching Up
The most revealing part of the KRA-IFMIS announcement may be how closely it connects with the concerns raised during the earlier eTIMS rollout.
In January, Wangwe acknowledged that taxpayers could have genuine government-related expenses that were difficult to support electronically. KRA’s proposed answer was to allow those expenses to be entered and then validated against government data.
She also said the first year would require flexibility, while KRA worked toward stronger controls backed by better data.
Now, seven months later, KRA and the National Treasury have connected eTIMS to IFMIS and placed an electronic invoicing requirement directly into the government supplier payment process.
The immediate question for taxpayers is therefore no longer simply whether they have kept a receipt. It is whether the transaction can be followed through the electronic records KRA is building around the tax system.
That is the real significance of the integration.
KRA is gaining more data with which to apply existing tax rules, while the temporary flexibility that helped businesses navigate the first year of income-and-expense validation is giving way to a system where electronic records are expected to do much more of the evidentiary work.
For taxpayers, 2026 is the year to make sure those records are right.
Real ESG impact doesn’t happen in panels alone, it happens in the rooms where financiers, operators, and policymakers actually align. Our GreenShift Forum 2026 cuts the noise, bringing together the people rewiring Africa’s sustainability and energy frameworks for one focused day in Nairobi. Secure your seat.
Go to TECHTRENDSKE.co.ke for more tech and business news from the African continent and across the world.
Follow us on WhatsApp, Telegram, Twitter, and Facebook, or subscribe to our weekly newsletter to ensure you don’t miss out on any future updates. Send tips to editorial@techtrendsmedia.co.ke
