As published by the Kenya Revenue Authority, eTIMS invoicing has been required since 1 January 2024 for VAT-registered taxpayers, with non-VAT-registered taxpayers, including many freelancers and small traders, brought in shortly after. KRA's own eTIMS portal describes two system-to-system integration routes: an Online Sales Control Unit (OSCU) for businesses that invoice continuously online, and a Virtual Sales Control Unit (VSCU) for bulk or offline invoicing, each reached by self-integration or through a certified third-party vendor and requiring KRA certification before use (as published — confirm current requirements with your adviser).
LATYNEX Digital builds the workflow around the invoice data your OSCU or VSCU integration needs. This page covers it for Nairobi businesses. The general service is at Workflow Automation & Systems Integration, and the market overview is at LATYNEX Digital for businesses in Nairobi. Delivery is in English, and this page names no client.
Typical industries
- Small and mid-sized retailers and service businesses
- Freelancers and independent professionals
- E-commerce and online sellers
- Wholesalers and distributors invoicing in bulk
- Finance and back-office teams preparing invoice data
Common lead-handling problems
- Sales recorded in a spreadsheet, then re-keyed for invoicing
- Bulk invoice batches assembled by hand before a VSCU submission
- No record of which invoices were rejected and why
- Invoice data split across several tools with no single source
- A missing field found only when a certified integration rejects a batch
Direct answer
If your Nairobi business or freelance practice issues invoices that need to reach eTIMS, LATYNEX can build a workflow that turns your existing sales or billing records into one clean invoice data set, checks it against the fields your certified OSCU or VSCU integration expects, and gives every rejected or exception invoice an owner before it is resubmitted.
Why the global page and the Nairobi hub are not enough
The global Workflow Automation & Systems Integration page has no tax-invoicing data set to design around, and the Nairobi hub is broad discovery for the market. Here the design point is that OSCU and VSCU are certified, system-to-system routes with their own technical review, so the workflow has to produce data those routes will actually accept, not a generic export.
What we configure and build
The work sits before your certified OSCU or VSCU integration, not in place of it.
- An invoice data workflow pulling from your existing sales, billing or POS records
- Field checks against the specification your certified integrator or KRA sandbox testing confirms
- A queue for rejected or exception invoices, with an owner and a status
- Separate handling for continuous (OSCU-style) and batch (VSCU-style) invoicing patterns
- A log of what was submitted, when, and the outcome, plus a written handover
What stays with you and your certified integrator
Certification of an OSCU or VSCU integration, and the actual submission to KRA, stay with you and your certified third-party vendor or your own certified self-integration. Whether your invoicing meets eTIMS requirements is for you and your adviser; we prepare the data, we do not certify or submit it.
What needs API support or custom scope
LATYNEX claims no KRA, OSCU or VSCU certification and no direct submission capability. Any connection to your certified integration, your accounting system or your POS is scoped per project through the documented API or export format if access is permitted, after technical review.
What we do not do, and where LATYNEX is not the right fit
LATYNEX does not give tax or legal advice, does not certify an OSCU or VSCU integration, does not submit invoices to KRA, and holds no KRA accreditation. It has no Nairobi office or named clients, and delivery is in English only. If you already run a certified eTIMS integration that reads directly from your accounting system, this page is not for you.
How delivery actually works
LATYNEX Digital has no office in Nairobi and does not claim one. We work with Nairobi businesses remotely, over video calls and written updates, in English, with the same team and process as in every other market.
Questions
Do you have an office in Nairobi?+
No. We work with businesses in Nairobi remotely, over video calls and written updates, in English, and we do not imply a local presence.
Do you certify or submit our OSCU/VSCU integration?+
No. Certification and submission stay with you and your certified third-party vendor or your own certified self-integration. We prepare and check the invoice data beforehand.
Does this apply to freelancers too?+
As published by KRA, eTIMS covers VAT and non-VAT registered taxpayers, which can include freelancers and small traders. Whether it applies to your specific situation is for you and your adviser.
What is the difference between OSCU and VSCU?+
As published by KRA, OSCU suits invoicing systems that operate continuously online, and VSCU suits bulk or offline invoicing. Both are system-to-system integrations reached by self-integration or a certified third-party vendor.
Does this make our invoicing compliant?+
No. We give no tax or legal advice and cannot say your invoicing meets requirements. Confirm current requirements with your adviser; we build to the data set they and your certified integrator specify.
How are you invoiced, and in what currency?+
In EUR, by Latynex Trade OÜ, a company registered in Estonia (EU). Tax treatment for a client in Kenya is confirmed on the quote, and we do not give tax advice.
What happens next
- 01
We map the process and the tools
Where the work starts, what is done by hand, which systems are involved.
- 02
We pick the simplest reliable route
A platform, a workflow or a little custom code — whichever is simplest and safest for this outcome.
- 03
Scope and price in writing
One scope and one price for you to approve. Nothing starts before you agree.
- 04
We build it with failure handling
Retries, duplicate protection and a named person told when something breaks, in accounts you own.
- 05
Test, monitor, hand over
We check it against real cases, agree who watches it, and document how it works and what to do when it fails.
Who you would be working with
- Company · Who you would be working with
- LATYNEX Digital is a service line of Latynex Trade OÜ, a company registered in Estonia (EU). Contact: info@latynexdigital.com.
- How we work · Delivery
- Remote, in English, with the person who would run the project. No local office is implied in any market.
- How we work · Commercial terms
- One scope and one price, agreed in writing before work starts. Your accounts, code and domain stay yours; any access we use is granted by you and can be withdrawn.
There are no client case studies on this page, and none are implied. What LATYNEX has built and runs itself is on the portfolio, each system labelled by stage. Published prices are on the pricing page; anything not listed there is scoped and quoted after review.