| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2861 |
| Technical Name |
l10n_ke_etims_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2861 |
| Technical Name |
l10n_ke_etims_einvoice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Kenya eTIMS e-Invoice
KRA OSCU/VSCU electronic tax invoicing for Odoo — control unit number & QR on every customer invoice
Connect Odoo to the Kenya Revenue Authority eTIMS system. Sales invoices and credit notes are signed by your Online or Virtual Sales Control Unit and the returned control unit number, receipt signature and QR code are stored on the move — ready for the Jan 2026 income & expense validation enforcement.
OSCU & VSCU submission
Device initialisation, sales submission and purchase recording over the documented eTIMS REST API. Sandbox and production endpoints are editable; requests retry with exponential backoff and every call is logged.
Control unit number + QR
The SCU ID, receipt signature, internal data and invoice number are captured after clearance. A KRA receipt-verification QR is generated and rendered to a PNG for the printed invoice.
Accurate eTIMS document
Lines are bucketed into the A/B/C/D/E tax types — 16% standard, 8%, zero-rated, exempt and non-VAT — with item classification codes and credit-note referencing of the original receipt.
Real KRA PIN validation
An 11-character KRA PIN validator (leading A/P class letter, nine digits, trailing check letter) runs on the company and partners, with individual / non-individual taxpayer-class detection.
Business-rule validation
A Kenya rule set layered on the engine's EN 16931-style core checks seller/buyer PINs, line tax categories, KES currency and the eTIMS branch before anything is submitted.
Bring-your-own-key
Your device serial and communication key (cmcKey) live on the connection record, never in the module. They are transmitted only to the KRA endpoint you configure — nowhere else.
Guided onboarding
A wizard captures your KRA PIN, branch, control-unit type and device credentials, validates the PIN, optionally initialises the control unit and leaves the company ready to issue eTIMS invoices. An optional cron drains posted documents to KRA in batches.
Compatible with Odoo 18 and Odoo 19.
Disclosure
This module transmits invoice data only to the KRA eTIMS endpoint you configure. Your device communication key and PIN are stored solely on your own database and are never sent anywhere else.
Screenshots
Ke Etims Invoice Generated C
Ke Etims Engine Document Gen
Onboarding
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module