Menu

Modelling eTIMS Reverse Invoicing for Agro Processors: Supplier Identity, Consent and Immutable Invoices
📰

Modelling eTIMS Reverse Invoicing for Agro Processors: Supplier Identity, Consent and Immutable Invoices

DEV Community: database·Isaac Mwendwa Muthui·about 13 hours ago
#8gvnC460
#devtodatabase#devto#dev#invoice#etims
Long article (2172 words) — no AI summary yet.
Reading 0:00
15s threshold

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.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.