Kenya KRA eTIMS Integration
The ECOSIRE Kenya KRA eTIMS app connects ERPNext invoices and related tax data to the configured KRA eTIMS integration model. It records transmission state, control-unit data and errors on the ERPNext document so finance can reconcile what was submitted without maintaining a second shadow ledger.
Your exact OSCU/VSCU provider contract, KRA onboarding status, tax mapping, and branch configuration must be validated on staging before any live invoice is sent.
Implementation checklist
- Complete KRA eTIMS onboarding and confirm the assigned integration model.
- Register every relevant branch/device and protect its credentials.
- Map ERPNext tax templates, zero-rated/exempt treatment, item classification, withholding, and credit-note behavior.
- Configure the compliant invoice print format and QR/control-unit fields.
- Test Sales Invoice, return/credit note, cancellation, stock reporting, and temporary-provider-outage scenarios on staging.
- Reconcile every test transmission to the provider/KRA portal.
- Assign finance roles and restrict settings, credentials, and re-send actions.
- Take a verified production backup immediately before enabling live traffic.
Operating controls
- Do not mark an invoice compliant unless the integration has an accepted transmission result.
- Never re-key a failed invoice in another system without documenting and reconciling the duplicate risk.
- Review the transmission log daily and resolve failed or queued entries.
- Use the configured retry/re-send workflow; do not edit control-unit identifiers.
- Reconcile credit notes to their original accepted invoice.
- Keep KRA/provider credentials out of screenshots, tickets, source code, and logs.
Detailed user manual
For the worked finance workflow, status meanings, invoice submission, retry, credit-note handling, and troubleshooting, use the Kenya eTIMS manual.