| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 3861 |
| Technical Name |
l10n_ke_etims_pos_receipt |
| 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) • Point of Sale (point_of_sale) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 3861 |
| Technical Name |
l10n_ke_etims_pos_receipt |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Kenya eTIMS POS
KRA OSCU/VSCU certification of Point of Sale orders — control unit number & QR on every receipt
Certify Odoo Point of Sale orders with the Kenya Revenue Authority eTIMS system. Each paid order and refund is signed by your Online or Virtual Sales Control Unit and the returned control unit number, receipt signature and QR code are stored on the order — ready for the Jan 2026 income & expense validation enforcement in retail and hospitality.
POS order certification
Every order is mapped to the eTIMS sales-transaction document with A/B/C/D/E tax-type bucketing — 16% standard, 8%, zero-rated, exempt and non-VAT — per-line item list and the POS payment method mapped to the eTIMS payment-type code.
Refund handling
POS refunds are submitted as credit receipts referencing the original certified receipt, with the reversed magnitudes carried to the control unit exactly as KRA expects.
Control unit number + QR on the receipt
The SCU ID, receipt signature, internal data and receipt number are captured after clearance. A KRA receipt-verification QR is rendered to a PNG and a formatted fiscal footer block is prepared for the printed receipt.
Auto-certify at payment or session close
Choose to certify each order as it is paid, drain the session's orders when it closes, or leave it manual — per company and per shop. An optional batch cron retries anything left pending.
OSCU & VSCU submission
Reuses the documented eTIMS REST API and the bring-your-own-key device connection from the Kenya eTIMS e-Invoice connector. Sandbox and production endpoints are editable; requests retry with exponential backoff and every call is logged.
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 registered customers, with a Kenya POS rule set layered on the engine's EN 16931-style core.
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.
Compatible with Odoo 18 and Odoo 19.
Disclosure
This module transmits POS order 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. It builds on the Kenya eTIMS e-Invoice connector and the shared e-Invoice Core Engine.
This is a receipt-format generator plus a bring-your-own-key (BYOK) transport connector using your own KRA-registered PIN and OSCU/VSCU device credentials. We are not a KRA-accredited eTIMS integrator and do not register your business with KRA on your behalf. Support and any refund are handled by the publisher at odoo@gencbaris.com.
Screenshots
Ke Etims Pos Receipt Certifi
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