An invoice can look professional and still fail the test that matters for tax compliance. A PDF created in Word, Excel or ordinary invoicing software is not automatically an eTIMS invoice. For eTIMS compliant invoicing Kenya businesses can rely on, the sales transaction must follow an approved Kenya Revenue Authority workflow and the electronic invoice must be generated or transmitted through eTIMS.
That distinction affects how an SME chooses billing software. The right question is not only, "Can the system print an invoice?" It is, "How does this sale reach eTIMS, how do we confirm it was accepted, and what happens when the connection or data is wrong?"
This guide reflects KRA information checked on 6 October 2026. Tax rules and KRA systems can change. Confirm unusual cases with KRA or a qualified Kenyan tax professional before changing your compliance process.
Who needs eTIMS and why the workflow matters
KRA states that all persons engaged in business are required to onboard eTIMS and issue electronic tax invoices. Its guidance includes companies, partnerships, sole proprietorships, associations and trusts, along with people carrying on business whether or not they are registered for VAT. KRA also explains that, from 1 January 2024, a business expense generally needs support from an electronic tax invoice for the purchaser to claim it, subject to stated exclusions and special processes. KRA explains the scope and expense rule.
That means eTIMS is not merely a VAT receipt feature. It affects sellers who need to issue compliant invoices and buyers who need reliable purchase records. A practical system should help the business capture correct customer, item, tax and payment information while preserving the KRA response attached to the transaction.
KRA lists exclusions from the requirement for an eTIMS-supported expense, including salaries and wages, imports, air passenger ticketing, investment allowances, interest, fees charged by financial institutions, expenses subject to withholding tax that is a final tax, and services from a non-resident without a permanent establishment in Kenya. Do not treat that list as a shortcut for normal sales. Check the current KRA guidance for the exact transaction.
Qualifying small suppliers: buyer-initiated invoices
KRA qualifies the general rule for supplies from a small business or small-scale farmer whose annual turnover does not exceed KES 5 million: the purchaser issues the invoice on the seller's behalf through Buyer Initiated Invoicing. KRA's BII guidance describes buyer entry of transaction details and seller approval or rejection. It says the workflow blocks VAT-registered sellers and allows 30 days for seller consent before automatic rejection.
Build a separate purchasing workflow for these transactions. Record supplier eligibility, the buyer's request and the final status; an invoice awaiting seller consent is not an approved invoice. Confirm the current route and eligibility with KRA rather than treating the turnover threshold as a general exemption from onboarding.
Choose the eTIMS route that fits your volume
KRA provides several eTIMS options. The right one depends on transaction volume, number of outlets, existing software and how much automation the business needs. KRA lists the current solution families.
Online and simplified options
A small business that raises a limited number of invoices may use KRA's online or simplified tools. These options reduce the need to build an integration and can suit a business whose sales process is mostly manual. The tradeoff is duplicate entry if the business also keeps separate accounting, stock or customer records.
Before buying a custom system, calculate the real cost of manual entry. Ten invoices per week may be manageable. Hundreds of invoices across several branches can create delays, inconsistent item names and reconciliation work.
eTIMS client options
KRA also provides client solutions for supported devices and operating environments. A client can suit businesses that need a dedicated invoicing process without connecting a larger enterprise system. Confirm the currently supported client, device and onboarding path on KRA's eTIMS pages because availability changes over time.
System-to-system integration
Businesses with an existing point of sale, ERP, billing platform, hospital system, school system or custom workflow may need system-to-system integration. KRA identifies OSCU and VSCU as integration routes. It describes development, testing, vetting and certification for self-integration or third-party developers. Ask for evidence that the proposed implementation has completed the required KRA process, or use a KRA-verified third-party integrator. A sandbox demonstration alone is insufficient evidence of production certification. In this model, the business system exchanges invoice data with eTIMS through the approved interface instead of requiring staff to re-enter every sale.
Integration is not just an API request added to the end of checkout. It affects item registration, tax classification, customer data, invoice sequencing, credit notes, retries, audit trails and reconciliation. The system should distinguish a local draft from an invoice accepted by eTIMS.
What an eTIMS-ready invoicing system should capture
A reliable system starts with clean source data. At minimum, review how it handles the following:
Seller identity, KRA PIN and the eTIMS device or integration identity.
Buyer PIN and buyer details when required for the transaction.
Invoice date, internal reference and the eTIMS invoice reference.
Items or services, quantity, unit price, discounts and totals.
Tax type, taxable amount and tax amount.
Payment method and the link between payment and invoice.
Credit notes or corrections tied to the original invoice.
KRA acknowledgement, status, QR code or signature data returned by the approved workflow.
User, branch and timestamp information for an audit trail.
KRA's public guidance for electronic tax invoices identifies features such as the trader's PIN and name, invoice time and date, serial number, gross amount, tax amount, tax rate, net amount, a unique register identifier and a digital signature represented by a QR code. The exact fields and applicability depend on the taxpayer and solution. Your system should use the current KRA specification instead of recreating fields from a sample invoice. KRA lists the main invoice features.
The workflow from sale to accepted invoice
A useful eTIMS invoicing workflow has clear states. Avoid using one vague label such as "sent" for every step. A practical sequence is:
1. Draft: The seller captures the customer, items, prices and tax treatment. 2. Validated locally: The system checks required fields, totals, item mappings and obvious formatting problems. 3. Submitted: The system sends the invoice through the approved eTIMS route. 4. Accepted: The KRA response confirms successful processing and the system stores the returned identifiers. 5. Delivered: The customer receives the resulting invoice by download, email or print. 6. Paid or partly paid: Payment is reconciled without changing the original tax invoice. 7. Corrected: A credit note or other approved correction references the original transaction.
The accepted state is important. Staff should not assume an invoice is compliant because the local system generated a PDF. If submission fails, the system needs a visible retry queue and a way to prevent accidental duplicates.
Integration controls SMEs often overlook
Idempotency and duplicate prevention
A slow response can tempt a user to click submit again. The software should reuse a stable transaction reference and prevent the same sale from creating multiple electronic invoices. Administrators need a report that compares local sales with eTIMS acknowledgements.
Failure handling
Internet connections and external services sometimes fail. The system should preserve the sale, record the error, retry safely and alert the right person. It should never silently mark a failed submission as accepted. Define how long unresolved invoices may remain and who follows up. Under regulation 5 of the Tax Procedures (Electronic Tax Invoice) Regulations, 2024, a user unable to use the system must notify the Commissioner in writing within 24 hours, record sales by the means the Commissioner specifies, and enter those sales when use is restored. A retry queue does not discharge these duties. Confirm the accepted written-notification channel with KRA and retain evidence of the notice; do not assume a support ticket is sufficient.
Credit notes and corrections
Do not delete or overwrite an accepted invoice to correct a mistake. Preserve the original and use the approved correction or credit-note process. KRA says credit notes must be generated in the solution that raised the original invoice. See its solution guidance. The user interface should make the relationship visible to finance staff and auditors.
Access control and audit logs
Separate the ability to create, approve, submit and reverse transactions when the business is large enough to support role separation. Record who changed customer details, prices, tax treatment or integration settings. Protect credentials and never expose them in a browser or printed report.
Reconciliation
Reconcile at least three records: the business system, eTIMS acknowledgements and payments. If M-Pesa is used, the M-Pesa receipt should link to the business transaction, but it does not replace the electronic tax invoice. A payment confirmation proves money moved; an invoice records the taxable supply.
Keep stock movements within the implementation scope
KRA's 7 September 2026 stock-management notice calls for accurate records of goods purchased or received, sold, transferred, returned, adjusted or disposed of. If your business sells goods, include those movements in requirements and ask KRA how its stock functionality applies to your solution. The notice announced consultations, so do not invent a universal implementation deadline from it.
What to ask an invoicing software vendor
A demo should show the difficult cases, not only a successful invoice. Ask the vendor to demonstrate:
The exact KRA solution and current specification used by the integration.
How sandbox testing and production onboarding are handled, with evidence of required KRA certification or current KRA-verified integrator status.
How the system proves that an invoice was accepted by eTIMS.
What users see when KRA rejects a submission or the network times out.
How duplicate submissions are prevented.
How credit notes and corrections reference the original invoice.
How item and tax mappings are maintained.
How buyer PIN details are captured for business transactions.
How branches, tills and users are separated.
How daily reconciliation and exception reports work.
Who monitors changes to KRA specifications and deploys updates.
How data is backed up, exported and retained.
Be cautious if the answer is only, "Our invoice has a QR code." A QR image by itself does not prove a live, approved integration. The workflow, acknowledgement and audit trail matter.
Decide between a standalone tool and an integrated system
A standalone KRA solution is often the simplest option for a small business with few invoices and basic reporting needs. It avoids unnecessary development and lets staff follow KRA's supported process directly.
Integration becomes valuable when duplicate entry is causing errors, stock must update with every sale, several branches share one catalogue, customer balances need real-time updates, or management needs one view of invoices and payments. A custom business system can connect sales, stock, approvals and reporting, but it should not be built merely to replace a free tool that already meets the need.
Estimate the annual cost of manual work and mistakes before commissioning an integration. Include onboarding, certification or testing effort, support, specification changes and staff training. Ask who owns the integration after launch.
Implementation checklist for an SME
1. Confirm the business's tax obligations and the current KRA onboarding requirement. 2. Choose the KRA solution that matches invoice volume and existing systems. 3. Clean the item catalogue, tax mappings and customer data. 4. Document invoice, payment, credit-note and cancellation workflows. 5. Test successful, rejected, duplicate and offline scenarios. 6. Train staff to distinguish drafts, submitted invoices and accepted invoices. 7. Reconcile local sales, eTIMS records and payments daily during rollout. 8. Keep exportable records and test backups. 9. Assign an owner for KRA updates and integration incidents. 10. Review the process with your accountant or tax adviser before going live.
Frequently asked questions
Is a PDF invoice automatically eTIMS compliant?
No. A PDF is a presentation format. The underlying transaction must be generated or transmitted through an approved eTIMS solution, and the business should retain the resulting KRA identifiers and status.
Do non-VAT businesses need eTIMS?
KRA's current public guidance says all persons engaged in business are required to onboard eTIMS and issue electronic tax invoices, including businesses that are not registered for VAT. Qualifying supplies from small enterprises or small-scale farmers with annual turnover not exceeding KES 5 million follow buyer-initiated invoicing, with seller consent, through the applicable KRA process. Confirm how the rule applies to your activities and any exclusions with KRA or a tax professional.
Must every SME build an API integration?
No. KRA provides online, client and simplified options as well as system-to-system integration. Integration is useful when an existing sales or billing system and higher volume make manual entry inefficient.
Does an M-Pesa receipt replace an eTIMS invoice?
No. The M-Pesa receipt confirms payment. The eTIMS invoice records the sale for electronic tax invoicing. A good system links them for reconciliation while preserving both records.
What happens if eTIMS submission fails?
The software should retain the unsent transaction, show the failure, retry safely and prevent duplicates. Staff need an exception queue and a documented escalation path. Never label the invoice accepted until the approved eTIMS workflow confirms it.
Build the process around proof, not appearance
The core requirement for eTIMS-compliant invoicing in Kenya is a trustworthy chain from sale data to an accepted electronic invoice and a record that can be reconciled later. Choose the simplest KRA solution that fits the business. Add integration when it removes meaningful duplicate work and can be supported properly.
Mocky Digital builds business systems for billing, stock, approvals and M-Pesa workflows. For an existing system that needs an eTIMS-ready workflow, request a technical assessment with your invoice volume, branches and current software. Tax interpretation remains with KRA and your professional adviser.
