By Isaac Muthui, CEO, Tamalaki Business Network Ltd. Originally published at factoraerp.com.
If you build or integrate procurement systems for agro processors in Kenya, eTIMS reverse invoicing is a data-modelling problem before it is an API problem. A dairy, tea factory or grain miller pays hundreds or thousands of smallholder farmers per cycle. Under Kenyan tax law, those expenses need eTIMS invoices to be deductible, and KRA's answer is to let the buyer generate the invoice on the farmer's behalf.
KRA documents two routes:
- Reverse invoicing (system-to-system): the buyer's own billing system integrates with eTIMS through OSCU or VSCU, after KRA KYC approval. The system creates a secondary device per seller and notifies the seller by SMS. eTIMS validates seller PIN, onboarding status and VAT status, and runs PIN validation, rate validation and duplicate detection. (KRA)
- Buyer Initiated Invoicing (BII): invoices raised through the KRA profile on eCitizen, *222# or a .csv upload. eTIMS blocks invoices for VAT-registered sellers, and the seller has 30 days to accept or reject via SMS/USSD before automatic rejection. (KRA)
Either way, the integration only works if the records underneath are clean. Five design decisions matter:
-
Supplier master as the single source of identity. One
supplierrow per farmer withkra_pin,etims_phone,vat_registered(boolean, with achecked_atdate) andconsent_id. Grower numbers become aliases, not keys. A PIN that fails validation should block invoice generation, not be silently skipped. -
Consent as a first-class record. KRA requires formal seller consent and a buyer-seller agreement. Store
consentwith supplier, date, channel, agreement version and the phone number used. No consent row, no invoice. -
Invoice lines derived from intake, never typed. Each invoice line should reference one or more
goods_receiptrows (supplier, date, item, grade, quantity). Price comes from a versionedprice_ruleeffective for that payment cycle, so rate validation failures can be explained. -
Immutable invoices, corrections as credit notes. KRA's guidance is to correct errors with a credit note against the original. Model
credit_notewith a foreign key to the invoice and a reason code (quality deduction, weighing error, price revision). Never update a transmitted invoice. -
Explicit invoice state for BII.
draft → submitted → pending_seller → accepted | rejected | expired(30 days). Onlyacceptedinvoices support the expense. Reconcile intake quantity, invoiced quantity and paid amount per supplier per cycle, and surfacepending_sellerandexpiredas exceptions.
Records must be kept for at least five years with an audit trail, so append-only event logs on invoice state are worth the storage.
Below is the full operations checklist I wrote for processors, including the legal basis and an FAQ.
If your factory buys milk, tea leaf, coffee cherry, grain or fruit from smallholder farmers, you probably pay hundreds or thousands of suppliers who will never run an invoicing system of their own. Under Kenyan tax law, that is your problem as much as theirs: expenses must be backed by eTIMS invoices to be allowed as deductions.
This week the Kenya Revenue Authority (KRA) again urged farmers who supply factories to use eTIMS reverse invoicing, where the buyer generates the invoice on the farmer's behalf. Speaking at a KRA Citizen Assembly at Murang'a University, the Commissioner for Micro and Small Taxpayers, George Obell, said that a factory buying agricultural produce "can generate an invoice on behalf of the farmer, thereby documenting the transaction in eTIMS", which "enables the purchasing business to support its expense claims with the requisite documentation" (Tuko, Pulse Kenya).
This eTIMS reverse invoicing checklist is for dairies, tea and coffee factories, grain millers, fruit and vegetable processors and other agro processors in Kenya that buy produce from many small suppliers. It is a practical operations guide, not tax or legal advice. It reflects KRA's public guidance at the time of writing; confirm the details with KRA or your tax adviser before you change anything.
What KRA actually offers: two routes
KRA describes two ways for a buyer to issue an invoice on a seller's behalf.
1. Reverse invoicing (system-to-system). According to KRA's reverse invoicing page, large buyers generate invoices for small-scale sellers through their own existing billing system, integrated with eTIMS through OSCU or VSCU. KRA says it is best suited to structured supply chains "such as tea, coffee and similar" ecosystems, and gives the example of a dairy processor generating an eTIMS invoice for each farmer, reflecting the quantity and price of milk delivered. Key conditions:
- The buyer must be approved by KRA through a Know Your Customer (KYC) process before implementation.
- The buyer needs a trusted Trader Invoicing System capable of system-to-system integration with eTIMS.
- Seller consent must be formally obtained, and buyer-seller agreements must set out each party's roles. KRA also mentions a Service Level Agreement and a Declaration of Compliance.
- The system creates a secondary device for each seller, and the seller is notified by SMS. Sellers can monitor and validate invoices issued in their name.
- eTIMS validates the seller's PIN, eTIMS onboarding status and VAT registration status. KRA lists PIN validation, rate validation and duplicate detection as controls.
- Errors are corrected with a credit note, not by editing the original invoice.
- The buyer keeps invoice records for at least five years, with an audit trail.
2. Buyer Initiated Invoicing (BII). KRA's BII guide describes a lighter route: the buyer logs into the KRA profile on eCitizen (or 222#), selects "Initiate Buyer Invoice" and enters the seller's ID or PIN, date, description, unit price, quantity and amount, or uploads a .csv file. eTIMS checks the seller's PIN and onboarding status and **blocks invoices for VAT-registered sellers. The seller gets an SMS or USSD prompt and has **30 days to accept or reject*; after that the invoice is automatically rejected. KRA warns that misuse can lead to immediate deactivation of the buyer's eTIMS.
The legal basis, as the BII guide sets out, is Section 16(1)(c) of the Income Tax Act (eTIMS invoices as a condition for deducting expenditure) and Section 23A(3A) of the Tax Procedures Act (a purchaser may issue an electronic invoice on behalf of a small-scale seller).
Why now. Tuko reports that KRA first introduced reverse invoicing on 27 December 2024, and that a KRA public notice of 10 November 2025 confirmed that, from 1 January 2026, income and expenses declared in tax returns would be validated against eTIMS records. That is what turns a missing farmer invoice into a disallowed expense.
The 12-point eTIMS reverse invoicing checklist
Decide and prepare
1. Count what you are not invoicing today. Pull last month's produce payments and split them into: suppliers who issued their own eTIMS invoice, suppliers covered by a buyer-generated invoice, and the rest. The last group is your exposure. Do it by value as well as by headcount.
2. Choose the route that fits your volume. BII through eCitizen or .csv upload can work for a few dozen occasional sellers. If you pay hundreds of farmers every cycle from a milk, leaf or cherry payroll, KRA designed system-to-system reverse invoicing for you. Write down the decision and the reason.
3. Name one owner. Reverse invoicing touches intake, procurement, finance, IT and the field team who talk to farmers. Give one person responsibility for KYC approval, supplier onboarding, the payment-to-invoice match and exceptions.
4. Start the KRA approval early. For the system route, KRA requires KYC approval before implementation and publishes a KYC questionnaire and OSCU/VSCU technical specifications on its reverse invoicing page. Integration and sandbox testing take time; do not plan to go live on the same week you apply.
Clean the supplier data
5. One supplier record per farmer, with a valid KRA PIN. eTIMS validates the seller's PIN and onboarding status. Duplicate grower numbers, names spelt three ways and missing PINs will fail validation or, worse, put a delivery on the wrong person's invoice. Fix the supplier master before you connect anything. Our item master data checklist covers the same discipline for items.
6. Flag VAT-registered sellers. Under BII, eTIMS blocks buyer-initiated invoices for VAT-registered sellers. Larger growers, transporters and aggregators who are VAT-registered must issue their own invoices. Keep a status field on the supplier record and review it regularly.
7. Record consent and the agreement. KRA requires formal seller consent and a buyer-seller agreement. Keep a signed or digitally recorded consent per supplier, dated, with the phone number registered on eTIMS, because that is where notifications go. Explain to farmers in plain language what they will receive and why. Tuko reports that KRA expects buyers, not farmers, to carry the operational cost of the reverse invoicing functionality.
Make every invoice match a delivery
8. Invoice from intake records, not from the payment list. The invoice should reflect what was actually received: supplier, date, product, quantity and price. That means weighbridge or milk-collection records must be complete and tied to the supplier ID at intake. See our dairy milk intake checklist and supplier intake checklist.
9. Classify products and prices consistently. KRA's conditions require products to be "clearly specified and accurately classified", and the system runs rate validation. Use one item code per produce type and grade, and keep the price list or price-per-kilogram rule that applied to each payment cycle on file.
10. Correct with credit notes, never by editing. Rejected deliveries, quality deductions, weighing errors and price revisions happen. KRA's guidance is to generate a credit note against the original invoice. Agree in advance who can raise one and how it is approved.
Reconcile and prove it
11. Reconcile three numbers every cycle. Intake quantity, invoiced quantity and paid amount per supplier should agree. Under BII, track pending and rejected invoices: an invoice the farmer has not accepted within 30 days is automatically rejected and does not support your expense. Make this part of your month-end close.
12. Keep five years of records and test a sample. KRA requires buyers to keep invoice records for at least five years with an audit trail. Each quarter, pick ten random farmer payments and trace each one back to the intake slip, the eTIMS invoice and the consent record. If any link is missing, fix the process, not just the file.
A simple test
Pick any farmer payment from last month. Can you show, within ten minutes, the delivery it paid for, the eTIMS invoice issued for it, the farmer's consent and any credit note? If yes, your reverse invoicing is ready to scale. If not, the gap is in your intake and supplier records, and that is where to start.
How FactoraERP helps
FactoraERP records goods receipts by supplier, item, lot and date as produce arrives, keeps one supplier and item master, and links receipts to supplier bills and payments, so each payment can be traced to the delivery behind it. See factoraerp.com.
Free download: eTIMS readiness checklist for factories
If you want a free eTIMS readiness checklist for factories, sign up for the FactoraERP Insights newsletter at https://isaacmuthui.substack.com. You will get practical operations notes for food and agro manufacturers. No spam; unsubscribe anytime. For background, read our guide to eTIMS for food and agro manufacturers in Kenya.
FAQ
What is eTIMS reverse invoicing?
A KRA arrangement in which a registered buyer generates eTIMS tax invoices on behalf of sellers for goods or services it receives. It is designed for sectors with many small-scale suppliers, such as farmers supplying processors.
What is the difference between reverse invoicing and Buyer Initiated Invoicing?
Reverse invoicing runs through the buyer's own billing system integrated with eTIMS (OSCU or VSCU) and requires KRA KYC approval. Buyer Initiated Invoicing is done through the KRA profile on eCitizen, *222# or a .csv upload, and each invoice must be accepted by the seller.
Does the farmer have to approve each invoice?
Under BII, yes: the seller accepts or rejects through SMS/USSD within 30 days, otherwise the invoice is automatically rejected. Under system-to-system reverse invoicing, the seller gives formal consent to onboarding and is notified of each invoice, and can monitor and validate them.
Can I issue a buyer-initiated invoice for a VAT-registered supplier?
No. KRA says eTIMS blocks buyer-initiated invoices for VAT-registered sellers. They must issue their own eTIMS invoices.
Why does this matter for my tax return?
Section 16(1)(c) of the Income Tax Act links the deduction of expenses to eTIMS invoices, and Tuko reports that from 1 January 2026 KRA validates expenses declared in returns against eTIMS records. Produce purchases without a valid invoice risk being disallowed.
How do I fix a wrong quantity or price?
Issue a credit note against the original invoice, as KRA's guidance describes, then issue the correct invoice if needed.
How long must records be kept?
KRA's reverse invoicing guidance says at least five years, with an audit trail.
Who pays for the system?
Tuko reports that KRA stipulates buyers must absorb the operational costs of reverse invoicing rather than passing them on to farmers.
Isaac Muthui, CEO, Tamalaki Business Network Ltd
Top comments (0)