Kenya eTIMS Requirements: A Finance Team Guide

Kenya eTIMS requirements are broader than many finance teams first assume. In Kenya, eTIMS generally applies to persons carrying on business, not only VAT-registered businesses. A compliant electronic tax invoice is expected to carry the seller's KRA PIN and invoice identifiers, the issue date and time, gross and tax amounts where relevant, item detail, unique identifiers, a QR code, and the buyer's PIN when the buyer wants to support an expense claim or input VAT. Since January 1, 2026, the compliance risk has also increased because the Kenya Revenue Authority (KRA) now validates declared income and expenses against TIMS or eTIMS data, withholding income tax gross amounts, and customs import records, as explained in KRA's November 2025 notice on return validation.

That combination makes Kenya electronic tax invoice requirements more than a document-format issue. Finance teams need to know who is in scope, which transactions are carved out, what fields must be present, and how invoice data flows into later expense and return checks. Treating eTIMS as a standard VAT-invoice checklist misses the wider control logic behind the regime.

This Kenya eTIMS guide is built as a working reference for accountants, AP teams, and business owners. It focuses on the operational questions that matter in practice: whether the business or transaction belongs inside the rules, what an eTIMS invoice must contain, and how buyer PINs, correction notes, stock records, and validation checks affect day-to-day finance work.

---

Who Must Use eTIMS, and What Is Excluded

KRA's position is intentionally broad: all persons engaged in business are expected to onboard eTIMS and issue electronic tax invoices. That reaches well beyond the group many teams would usually place inside a VAT-only invoicing rule. Companies, partnerships, sole proprietors, associations, trusts, informal-sector businesses, and taxpayers with income tax obligations can all fall inside the regime. KRA's FAQ also makes clear that businesses supplying VAT-exempt goods or services are not automatically outside the system just because they are not VAT registered.

There are two practical qualifications finance teams should separate from that general rule. First, KRA says that where a supply is received from a small business enterprise with annual turnover not exceeding KES 5 million, the purchaser issues the tax invoice on the seller's behalf through buyer-initiated invoicing. Our guide to Kenya buyer-initiated invoicing for small-trader procurement breaks down the eCitizen consent step, the KES 5 million threshold, and how that workflow differs from reverse invoicing. Second, the Tax Procedures (Electronic Tax Invoice) Regulations, 2024 list transactions that are excluded from the requirement for an electronic tax invoice. Those exclusions include emoluments, imports, investment allowances and internal accounting adjustments, airline passenger ticketing, interest, fees charged by financial institutions, expenses subject to withholding tax that is a final tax, and services supplied by a non-resident without a permanent establishment in Kenya.

That distinction matters. The scope question asks whether the person is carrying on business and should be operating within eTIMS. The exclusion question asks whether a specific transaction is outside the electronic tax invoice requirement even though the business itself may still be inside the wider eTIMS environment. Finance teams should map both before they design approval rules or supplier checks, because a control built around "VAT registered or not" will miss how the KRA eTIMS requirements are actually framed.

What a Compliant Kenya eTIMS Invoice Must Contain

The 2024 regulations give a field-level checklist for a compliant invoice. For review and processing purposes, it helps to group those items into four buckets:

• Seller and invoice identifiers: the seller's KRA PIN, the serial number, the unique system identifier, and the unique invoice identifier.
• Timing and values: the invoice issue date and time, the total gross amount, and the total tax amount where tax applies.
• Supply detail: the item code prescribed by the Commissioner, a brief description of the goods or services, the quantity supplied, the unit of measure, and the applicable tax rate.
• Verification elements: the QR code and any additional information KRA may specify.

If the buyer intends to claim the expense or input VAT, the buyer's PIN also becomes part of the required invoice data. That is one reason Kenya eTIMS invoice requirements are not just about whether a PDF looks professional. The invoice needs the right fields in a format that supports transmission, validation, and later review by finance and tax teams.

For multinational teams, it helps to think of this as an e-invoicing control framework rather than a template exercise. Our broader guide on how e-invoicing systems differ from standard PDF invoicing is useful context here: a valid electronic tax invoice is expected to carry structured data that can be checked later, not just present a readable document on screen.

Buyer PIN, Debit Notes, and Credit Notes Are Control Points

The buyer's PIN matters when the buyer wants to rely on the invoice to support a business expense, a deductible expense position, or an input VAT claim. In other words, this is not an optional detail that only matters to tax teams after the fact. If AP receives an invoice without the buyer PIN in a case where the buyer intends to claim the expense or input tax, the problem starts at document capture and carries forward into return preparation.

That is why finance teams should treat buyer-PIN capture as an intake control. When the transaction is meant to support deductibility or input VAT, the PIN should be confirmed before the invoice is posted, not chased later during month-end cleanup. This is especially important now that eTIMS data is being used more directly in validation workflows.

Corrections need the same discipline. Under the regulations, a debit note or credit note must refer back to the original invoice number. That creates an auditable chain between the original supply and the adjustment. Without that link, the correction document becomes harder to reconcile, harder to defend, and more likely to trigger rework when finance is matching records or explaining differences. If you are translating those controls into a system rollout, our Kenya eTIMS API integration guide explains how VSCU or OSCU choices, sandbox onboarding, and same-solution credit-note rules shape the implementation.

If your team wants a broader refresher on debit note rules and original-invoice references, use it alongside your Kenya-specific controls. In practice, the safest approach is to treat every debit note and credit note as a linked record that must preserve the original invoice trail, not as a standalone document that replaces the past.

Stock Records and Purchase Records Are Part of eTIMS Compliance

Kenya eTIMS stock records are part of the compliance picture because the regulations do not stop at issuing the invoice. Users of the system are also expected to maintain stock-in and stock-out records in the system, record each local purchase and import, and notify KRA around business closure events. For finance teams, that means eTIMS compliance touches inventory movement and purchase documentation as well as invoice issuance.

In workflow terms, stock-in records support what came into the business, stock-out records support what moved out, and local purchase or import records help preserve the transaction trail behind those movements. That matters because invoice validation becomes much stronger when the tax authority can compare invoice data with the wider records around purchases, goods flow, and imports.

This is one of the main ways Kenya differs from a narrow invoice-checklist article. A compliant invoice is necessary, but by itself it is not the whole control environment. Teams dealing in goods should make sure invoice review, purchasing records, and stock movement records can be tied together. Service businesses may have a lighter stock burden, but they still need to treat transmission, invoice content, and supporting records as part of one compliance process.

---

A Finance Workflow Checklist for January 1, 2026 and Beyond

The most practical response to the 2026 validation environment is to turn the rules into repeatable finance controls:

• Confirm whether the entity is carrying on business and whether the specific transaction is inside the electronic tax invoice requirement or falls under a listed exclusion.
• Check invoice content before posting: seller PIN, invoice identifiers, issue date and time, amounts, tax fields where applicable, item detail, unique identifiers, and QR code.
• Capture the buyer's PIN up front whenever the expense claim or input VAT position depends on it.
• Require every debit note and credit note to point back to the original invoice number.
• Keep stock, local purchase, and import records in a way that supports the invoice trail, especially for goods-based businesses.
• Reconcile records before return filing so declared income and expenses do not conflict with TIMS or eTIMS data, withholding income tax gross figures, or customs import records.

For multinational teams, documentation discipline still matters after the invoice is issued. Our guide to cross-border invoice retention rules for multinational finance teams is a useful companion if Kenya sits inside a wider regional process. The operational takeaway is straightforward: once the January 1, 2026 validation checks are in play, weak invoice controls are more likely to surface as filing problems instead of staying buried in manual files.