If yours is not here, write to us — the answer usually takes one line.
No. OSCU and VSCU are software control units defined by KRA — modules, not machines. We run the control unit; you call an API. Which of the two applies to you rarely changes anything in your code.
Your invoice queues with us and your till keeps working. We sign the backlog in order and notify your system by webhook the moment each invoice is signed.
No. KRA runs eTIMS and issues the control units; VeTims is the software your system talks to so it never has to speak eTIMS directly. We are Vutia Enterprises, a private company in Nairobi. The name is close to KRA's because the service sits next to theirs, not because we are them.
We are sandbox-registered and mid-certification. Pilots run against the KRA sandbox today and convert to production when certification completes. The sandbox and production speak the same API, so nothing you build now changes later, and the pilot costs nothing while you wait — early pilots shape the onboarding queue.
Two endpoints and one webhook. One POST sends the sale, one handler receives the signature, and the rest is deciding where it prints. Your sandbox token and registered device are set up before you write a line of it.
Send a credit note referencing your original invoice number. We enforce KRA's rules — negative amounts, original-receipt linkage, cancel-once.
Yes. Send VAT-inclusive prices and a tax category per line; taxable and tax amounts come back per line and per category, A through E.
Yes. Devices, invoice sequences and keys are managed per branch under your KRA PIN.
It is processed solely to fiscalize your invoices and power your own reporting. We are a Kenyan company and will sign a DPA.
The four steps, the endpoints, the fields you send, and what happens when KRA or your endpoint is down.
What a free pilot includes, how production is billed, and where certification stands this month.
Write to us with what your system does. We reply with a token, a device and a working example against the KRA sandbox.