KRA eTIMS compliant POS for Kenyan retailers
SalesLife POS signs sales and refunds through a local VSCU agent inside the sale itself, stores the fiscal QR on the document, and keeps trading if the signer is briefly unreachable.
The signing flow, step by step
What happens to every sale, and what happens when signing cannot complete.
- 01Till
Capture buyer details
Add the customer's KRA PIN when the invoice needs it.
- 02VSCU agent
Sign the sale
The local VSCU agent signs the sale following the KRA specification.
- 03Till
Store the QR
The fiscal QR payload is stored on the document.
- 04Offline queue
If signing fails
Unsigned invoices queue and a background worker retries.
- 05Supervisor
Retry with control
Retry one invoice or a batch, with supervisor approval.
- 06Compliance
Escalate breaches
Invoices that breach the SLA go to a compliance officer task queue.
Result Every sale fiscalised or escalated
How eTIMS signing works in SalesLife
Fiscal compliance is part of the checkout flow, so cashiers never see a separate compliance step.
Signed in the sale
Sales and refunds are signed through a local VSCU agent that follows the KRA specification (v2.0).
Fiscal QR on the document
The fiscal QR payload is stored on the sales document so it can be printed and traced.
Buyer PIN capture
Capture the customer's KRA PIN at the till when a buyer needs it on the invoice.
Offline queue
If an invoice cannot be signed right away, it is queued and a background worker retries it.
SLA escalation
Invoices that breach the signing SLA move to a compliance task queue for an officer to resolve.
Controlled retries
Retry one invoice or a batch from the fiscal retry queue, with supervisor approval.
Test eTIMS without a live VSCU
A simulator mode lets your team run user acceptance testing and train cashiers before the live signer is connected. Integration secrets are kept in a credential locker on the till rather than in files.
- Simulator mode for UAT without a live VSCU
- Demo providers for training environments
- Operations-health view for the fiscal and sync queues
- Compliance task queue for eTIMS SLA breaches
Tax and finance reports beside eTIMS
The same platform produces the tax paperwork finance teams ask for.
Withholding tax certificates
Generate, issue and export WHT remittance certificates.
VAT reporting
VAT summary and zero-rated disclosure reports, with PDF and CSV export.
ERP posting
Posted sales reach Dynamics 365 Business Central or SAP Business One through SalesLife HQ.
When the network drops
Cash sales continue offline. Cloud fiscal signing pauses until connectivity returns, and unsigned invoices wait in the offline queue, then are retried automatically. Nothing is lost, and the escalation path catches anything that stays unsigned.
Common questions
What is KRA eTIMS?
eTIMS is the Kenya Revenue Authority's electronic tax invoice management system. Businesses issue tax invoices and receipts through it.
Does SalesLife sign invoices at the till?
Yes. SalesLife POS signs sales and refunds through a local VSCU agent as part of the sale, and stores the fiscal QR payload on the document.
What happens if the signer is offline?
Unsigned invoices are queued and a background worker retries them. Anything that breaches the signing SLA is escalated to a compliance task queue.
Can we test before going live?
Yes. A simulator mode lets you run user acceptance tests without a live VSCU.
Which ERPs does SalesLife post to?
Dynamics 365 Business Central and SAP Business One, through SalesLife HQ.
Keep exploring
See SalesLife on your products, your branches and your ERP.
Book a live demo with a SalesLife retail specialist, or email hello@saleslife.com.
