If your business is registered for VAT in Kenya, KRA now requires every tax invoice to be validated through eTIMS before it reaches your customer. ERPNext handles the accounting side well — VAT tax templates, Sales Invoices, Credit Notes and the general ledger — but out of the box it has no concept of eTIMS. It cannot sign an invoice through the Slade360/OSCU or VSCU pipeline, it cannot stamp a control-unit serial number or a KRA QR code onto your printout, and it cannot report your stock movements to KRA. That gap is exactly what leaves finance teams re-keying invoices into a separate eTIMS portal, reconciling two systems by hand, and worrying about non-compliant documents during a KRA audit.

We build a dedicated Frappe app — a proper kenya_kra_etims app with its own module, not a pile of loose customizations — that lives inside your ERPNext site and talks to the eTIMS API for you. New DocTypes hold your eTIMS credentials and device/branch registration, item classification codes (KRA UNSPSC), and a transmission log that records every request and response. We hook into the ERPNext document lifecycle through hooks.py doc events: when a Sales Invoice is submitted, a server-side handler builds the eTIMS payload, calls the API through a whitelisted method, receives the control-unit serial, internal data and signature, and writes them back onto the invoice — all within the submit transaction so a failed transmission blocks the document instead of silently producing a non-compliant invoice.

Technically, the integration is built the Frappe way. Doc events (on_submit, on_cancel) drive Sales Invoice and Credit Note transmission; a custom KRA-compliant Print Format renders the control-unit serial, receipt signature and QR code so your printed invoice matches KRA's specification. VAT is mapped from your ERPNext Item Tax Templates to eTIMS tax categories (A/B/C/D/E), P9A and withholding-tax handling is configured against your Chart of Accounts, and Stock Ledger movements are reported as import/purchase/stock entries. Scheduler events retry any transmission that failed while eTIMS was unreachable, and a whitelisted frappe.client-style API plus a dedicated Role Profile give your accountants controlled access to re-send, view logs and reconcile without touching server code. Client scripts add the on-form actions — a "Transmit to eTIMS" button, status indicators and validation prompts — so the workflow feels native to ERPNext.

Because this is a product, ECOSIRE builds it for you rather than handing over a generic download. We start with a short scoping call to confirm your eTIMS onboarding type (OSCU device vs. VSCU virtual), your branches, item catalogue and tax setup, then build against Frappe/ERPNext v15/v16. You get the app installed on a staging site first for UAT with your own invoices, a rollback plan, and the full git repository handed over so the code is yours. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window while you run your first live KRA-validated invoices.