Kenya Buyer-Initiated Invoicing: eTIMS Guide

Kenya buyer initiated invoicing is the eTIMS workflow the Kenya Revenue Authority (KRA) describes for cases where a buyer receives a supply from a small business enterprise whose annual turnover does not exceed KES 5 million and must issue the tax invoice on the seller's behalf. In practice, the buyer records the transaction in eCitizen, the seller confirms it through eCitizen or the USSD channel written by KRA as *222#, and the finished invoice becomes the compliant tax document for that purchase. KRA also separates this from reverse invoicing, which it describes as a different, system-to-system process in its buyer-initiated invoicing guidance.

That definition matters because many Kenyan finance teams buy from suppliers who are real businesses but do not always operate with the same invoicing maturity as larger vendors. A produce buyer dealing with small-scale farmers, a processor buying from small traders, or an SME sourcing from low-formality suppliers may still need a valid eTIMS record that supports the purchase properly. Buyer-initiated invoicing is KRA's route for that scenario.

The easiest way to think about it is this: the workflow exists to solve a documentation problem, not to give the buyer a free choice about who issues invoices. When the transaction falls within the rule, the buyer becomes the party that raises the eTIMS invoice on the seller's behalf. When it does not, the ordinary supplier-issued invoice remains the correct path.

The rest of the workflow comes down to five questions: who qualifies, how consent works, what information the buyer needs to enter, how the rule differs from reverse invoicing, and when the buyer should stop and use the ordinary supplier-issued route instead.

Which Suppliers Qualify and When the Buyer Must Issue the Invoice

The core eligibility question is whether the supply comes from a small business enterprise within KRA's buyer-initiated invoicing rule. The threshold that anchors the decision is annual turnover not exceeding KES 5 million. If the supplier falls within that bracket and the transaction belongs in this workflow, the buyer issues the invoice through eTIMS on the seller's behalf.

In practice, this question usually arises when a business is buying from suppliers such as market traders, aggregators sourcing from small-scale farmers, or other low-turnover vendors who may not be the party practically generating the tax invoice in the standard way. The rule is designed for that reality.

A useful internal test is to ask three questions before anyone enters data:

1. Is the supplier actually within the small business enterprise threshold?
2. Is this one of the transactions KRA expects to move through buyer-initiated invoicing rather than normal supplier issuance?
3. Would the supplier otherwise be the correct party to issue the invoice in the ordinary course?

If the answer to the third question is yes, the buyer should not treat buyer-initiated invoicing as a convenience shortcut. The workflow is not there to let organized suppliers offload invoicing duties to customers. It exists for a narrower compliance situation tied to supplier status and transaction context.

The same logic explains why a buyer-issued invoice may arise in small-scale farmer transactions. The farmer example matters because it illustrates the type of low-formality procurement environment that the rule was built to handle. For teams comparing agricultural procurement controls across jurisdictions, Albania's farmer self-invoice requirements show how buyer-issued documentation can also hinge on compensation wording and payment-threshold checks. Finance teams should document that logic clearly, because the threshold decision comes before the eCitizen steps and before any consent request is sent.

How the eCitizen and USSD Consent Workflow Works

Once you know the purchase belongs in the Kenya eCitizen buyer initiated invoicing route, the next task is to run the sequence in the same order KRA expects it to happen.

First, the buyer confirms internally that the supplier and transaction fit the buyer-initiated rule. That means checking the supplier profile, confirming why the buyer rather than the seller will be issuing the invoice, and making sure the transaction details are ready before anything is keyed into the system.

Second, the buyer enters the transaction through eCitizen. The purpose of this step is not just to create a record. It is to create the eTIMS tax invoice on behalf of the seller using the details of the actual supply.

Third, the seller must confirm the invoice. KRA allows that consent step to happen through eCitizen or through the USSD channel written as *222#. This matters operationally because some suppliers may not be handling their affairs through a desktop workflow but can still complete the confirmation through a mobile device. Consent is part of what makes the document valid within the buyer-initiated model, so finance teams should treat it as a required control, not a soft follow-up item.

Fourth, the buyer should verify that the consent has actually been completed and that the final invoice record matches the underlying transaction. If the supply details, values, or supplier identity are wrong, the problem is no longer just an AP mismatch. It becomes a tax-documentation problem.

In practice, the most common friction point is not the system screen itself. It is coordination. Procurement may have the commercial facts, AP may be entering the invoice, and the supplier may need help understanding why a confirmation request has arrived. Teams that document a short internal procedure for each party usually handle buyer-initiated invoicing more consistently than teams that treat it as an ad hoc exception.

What Information the Buyer Needs to Capture and Keep

Buyer-initiated invoicing works best when the eTIMS entry is treated as the last step in a documented purchase trail rather than the first proof that the transaction happened. The buyer should be ready to capture the supplier's identifying details, the nature of the supply, transaction date, values, and any other invoice information needed to raise the eTIMS record accurately on the seller's behalf.

From a controls perspective, the invoice should line up with the documents your team already relies on: purchase requests, goods-received evidence, weighbridge or delivery details where relevant, approval records, and payment support. If the business later needs to show why a cost was deductible, the buyer-initiated invoice should fit cleanly into that wider file instead of standing alone without context.

This is why the process matters for deductible business expenses. The objective is not merely to generate an electronic invoice. It is to preserve a valid, supportable purchase record in situations where the supplier is not the party practically issuing the invoice themselves. That is especially important in mixed-formality supply chains where underlying transaction evidence may sit across procurement, operations, and finance.

Your team should also separate this narrow workflow from the broader Kenya eTIMS rule set. Questions about overall eTIMS scope, buyer PIN treatment, and validation requirements belong in the wider guide on Kenya eTIMS scope, buyer PIN, and invoice validation rules. For the buyer-initiated process, the key point is simpler: a buyer-issued eTIMS invoice only works well when the supply details, consent evidence, and supporting purchase records all agree.

Buyer-Initiated Invoicing vs Reverse Invoicing vs Supplier-Issued Invoices

The terminology problem is one of the main reasons teams mis-handle this topic. Kenyan guidance, advisory posts, and news coverage sometimes use overlapping language, but the workflows are not interchangeable.

Workflow	Who effectively issues the invoice	Typical use case	What to remember
Buyer-initiated invoicing	The buyer issues the eTIMS invoice on the seller's behalf	Purchases from a qualifying small business enterprise within the KES 5 million threshold, with seller consent	This is the eCitizen-driven workflow most AP teams are trying to understand
Reverse invoicing	A separate system-to-system model described by KRA	Structured billing ecosystems where invoice creation happens through integrated systems	It is not the same thing as the buyer entering a transaction in eCitizen and waiting for seller confirmation
Standard supplier-issued invoice	The supplier issues its own invoice	Ordinary purchases where the supplier should handle normal invoice issuance	This remains the default route unless the buyer-initiated rule clearly applies

That table matters because "reverse invoicing" can sound like a catch-all label for any buyer-led invoice process. In Kenya, that shortcut creates confusion. Buyer-initiated invoicing is the practical workflow for the threshold-based small-supplier scenario discussed in this article. Reverse invoicing refers to something narrower and more system-driven.

It can help to compare Kenya's rule with other buyer-issued models, but only carefully. For example, a buyer-issued purchase invoice model in Chile and recipient-created tax invoice rules in Australia show that buyer-generated tax documents exist in multiple jurisdictions. They do not replace the need to follow Kenya's own terminology, eligibility tests, and consent steps.

If a supplier should be issuing a normal invoice, that is still the correct route. The safest approach is to treat buyer-initiated invoicing as a distinct compliance tool for a specific supplier profile, not as a synonym for every form of self-billing or buyer-side invoice creation.

When Not to Use Buyer-Initiated Invoicing and the Controls to Apply

The biggest control failure is using buyer-initiated invoicing too broadly. If the supplier should issue its own invoice, if the supplier does not fit the small business enterprise rule, or if the team cannot support the transaction facts properly, the buyer should stop and re-check the workflow before creating anything in eTIMS.

A practical control checklist looks like this:

1. Confirm why the supplier qualifies for the buyer-initiated route and record the basis for that decision.
2. Make sure the transaction details are complete before the invoice is entered.
3. Obtain and evidence the seller's consent through the approved channel.
4. Match the issued invoice to purchasing, receiving, and payment records.
5. File the invoice with the rest of the support needed to defend the purchase as a deductible business expense.

These controls matter because Kenya buyer initiated invoicing is not just a labeling exercise. It is a workflow for handling purchases from small traders and similar suppliers in a way that produces a usable tax invoice without breaking the logic of the underlying transaction. If teams skip the eligibility step or treat consent as an afterthought, the document trail weakens quickly.

A short internal briefing prevents most repeat errors. Procurement, AP, and bookkeeping staff should know the KES 5 million threshold, understand that the process is tied to specific supplier situations, and recognize that the ordinary supplier-issued invoice still remains the default in many purchases. When everyone uses the same decision rule, buyer-initiated invoicing becomes a controlled exception rather than a recurring source of confusion.