One integration, any KRA device.
A device-agnostic layer fiscalises to KRA TIMS/eTIMS across eight device makes from one integration — so adding a device is configuration, not a rebuild — and an offline queue holds every receipt until the network comes back, never dropping a sale.
maintenance-register
maintenance-register
deployment-record
KRA TIMS / eTIMS fiscalisation & compliance
Device-vendor SDKs · In-house eTIMS builds · SAP DRC
One integration drives eight device makes — Incotex, Tremol, DateCS, DTR, Tevin, Novitus, NEXGO and Pergamon — with an offline queue and a managed service behind it, so fiscalisation is a solved problem, not a per-device project. maintenance-register
| DEVICE | MAKE | SITE | STATUS |
|---|---|---|---|
| ETR-014 | Pergamon | Nairobi | FISCALISING |
| ETR-021 | Incotex | Mombasa | FISCALISING |
| ETR-033 | Tremol | Nakuru | FISCALISING |
| ETR-042 | DateCS | Nairobi | FISCALISING |
| ETR-055 | DTR | Kisumu | FISCALISING |
| ETR-061 | Tevin | Eldoret | OFFLINE · QUEUED |
| ETR-070 | Novitus | Thika | FISCALISING |
| ETR-084 | NEXGO | Nairobi | FISCALISING |
| 8 makes · 8 devices | 7 live · 1 queued |
Eight device makes, one integration.
Device-agnosticA driver layer abstracts the device, so the same integration fiscalises across Incotex, Tremol, DateCS, DTR, Tevin, Novitus, NEXGO and Pergamon — a new make is a config entry, not a fresh build. maintenance-register
→ queue local SQLite buffer (not dropped)
→ reconnect 09:14 auto-flush
→ fiscalised CU 0061-88213 KRA acknowledged
A dead network never drops a receipt.
ResilienceWhen the link to KRA drops, invoices queue in a local buffer instead of failing at the counter — and flush automatically the moment the network returns, so the fiscal receipt is late, never lost.
| TIME | EVENT | GAP |
|---|---|---|
| 13:59 | Last invoice, prior flow | — |
| 14:00 | Cutover — Sage → KRA TIMS | 0 min |
| 14:01 | First invoice, direct-fiscalised | — |
| MID-BILLING-CYCLE | ZERO DOWNTIME |
Cut over mid-cycle, with zero downtime.
CutoverMoving a live business onto direct fiscalisation usually means a stop. Our first portfolio cutover went the other way — executed mid-billing-cycle, Sage to KRA TIMS, with not a minute of downtime. deployment-record
| SERVICE | CADENCE | STATE |
|---|---|---|
| Device-health monitor | continuous | GREEN |
| KRA certificate renewal | per expiry | TRACKED |
| OEM firmware update | on release | CURRENT |
| ONE CONSOLE | FLEET-WIDE |
Managed, not just installed.
ManagedA managed compliance service runs the fiscal estate — device-health monitoring, certificate renewals and OEM firmware kept current — so fiscalisation stays a service you buy, not a system you babysit.
Everything in the fiscalisation line.
In this line| KRA TIMS / eTIMS Engine (multi-device) | Live | One integration, device-agnostic. |
| Multi-OEM Device Driver (8 makes) | Live | Incotex, Tremol, DateCS, DTR, Tevin, Novitus, NEXGO, Pergamon. |
| SageTIMS Middleware | Live | Sage → KRA TIMS real-time. |
| SAP-to-KRA TIMS | Live | Fiscalises SAP B1 / S/4HANA documents. |
| Manual DTR Desktop Tool | Live | Standalone KRA fiscalise tool, no ERP. |
| Fiscalisation Monitoring Console | Live | Live transaction monitor, device health. |
| Offline Store-and-Forward Queue | Live | Edge-resilient SQLite buffer. |
| TIMS-AMC Managed Service | Live | Run-the-system fiscal compliance. |
| ZRA VSDC (Zambia Smart Invoice) | Designed | Extends the engine beyond Kenya. |
| Leysco Akili In-ERP eTIMS Connector | Designed | Native .NET fiscalisation, not built. |
| Leysco Akili Native Tax-Determination Engine | Early access | In-platform tax determination, early access. |
| Laravel In-ERP Native eTIMS | Roadmap | Marketed vision, in-ERP e-invoicing. |
A device can flatline. A receipt never does.
Signature · Synthetic trace, real fleet behaviourEvery receipt the fleet fiscalises lands at KRA as a beat on one trace — eight makes of fiscal device, one integration behind them all. When a device drops offline its beat flatlines, but its receipts don't vanish: they queue on the store-and-forward buffer and flush the moment it reconnects, each one landing with its KRA ACK. maintenance-register
maintenance-register
Eleven enterprises run their KRA compliance on this fleet under active maintenance — one integration, eight device makes, an offline queue and a managed service — including the first direct-fiscalisation cutover we ran with zero downtime.
On Leysco Akili, the in-ERP eTIMS connector is designed .NET, not built, and the native tax engine is in early access — the multi-device fiscalisation fleet is the Leysco100 strength today.
- fiscalise to KRA TIMS/eTIMS across mixed device makes from one integration
- keep selling when the KRA link drops — queue now, fiscalise on reconnect
- cut a live business onto direct fiscalisation without stopping billing
- hand the whole fiscal estate to a managed compliance service
A separate integration per device make, and a counter that stops when KRA does → one integration, an offline queue, a managed fleet
Part of the house.
RelatedPOS at the till
The same fiscal engine, at the checkout.
LiveSAP Bridge
Fiscalise SAP B1 / S/4HANA documents.
LivePayments Hub
The rails the fiscalised sale settles on.
LiveThe house has worked SAP Business One since 2017. company-books