Electronic invoicing becomes frustrating when a business chooses software before understanding its own sales process. The right starting point is not a download button; it is a clear picture of what you sell, how often you invoice, where staff work and whether an existing system already creates bills.
KRA provides several eTIMS routes rather than one identical product. Choosing carefully can reduce duplicate work and make daily invoice records easier to control.
What eTIMS for Kenyan business is meant to do
KRA describes eTIMS as its electronic Tax Invoice Management System. It allows eligible businesses to issue and manage electronic tax invoices through options designed for different devices and transaction volumes.
The invoice is part of the business record. It should reflect the real supplier, customer where required, goods or services, value and tax treatment. eTIMS does not replace the need to understand what the business sold or to keep supporting documents.
KRA's current guidance says persons engaged in business are expected to onboard and issue electronic tax invoices, subject to rules and special processes that may apply to particular cases. Tax obligations can change and individual situations differ, so confirm the position for your business with KRA or a qualified adviser.
Do not install a file sent through a messaging group. Begin from the official KRA eTIMS pages, eCitizen route or approved app listing.
Map the real invoicing workflow first
Spend one ordinary business day writing down how an invoice moves from sale to record. Note who confirms the price, who identifies the customer, who receives payment and who checks the day-end total.
Answer these questions:
- Does the business sell goods, services or both?
- Is stock control required?
- How many invoices are issued on a normal and busy day?
- Are sales made at one counter, several branches or in the field?
- Is internet access reliable at every point of sale?
- Does accounting or point-of-sale software already exist?
- Who is authorised to cancel, correct or review an invoice?
These answers are more useful than choosing an option because a friend uses it. Two businesses with the same turnover can have very different operational needs.
Compare the official eTIMS options
KRA's help material describes a range of solutions. Availability and eligibility should be checked on the current official page, but the broad choices help frame the decision.
eTIMS Lite web and USSD routes are aimed at simpler transactions and access needs. The USSD route can be useful where mobile data is unavailable. Mobile options support eligible smaller operations using compatible phones.
The online portal suits certain service businesses and browser-based invoicing. Client software is intended for operations that need functions associated with goods, branches or pay points. System-to-system integration connects an existing automated billing or enterprise system through approved technical routes.
Do not assume the most complex option is the most professional. A simple official route that staff use correctly is better than an expensive integration that produces inconsistent data.
When eTIMS Lite may be enough
A sole proprietor or small operation with straightforward sales may value an option that works from a phone or browser without maintaining a full point-of-sale system.
Check the current eligibility and feature limits. Ask whether the option supports the products or services you sell, the number of invoices you issue and the reports you need.
USSD can support continuity when internet access is poor, but a small phone screen requires careful data entry. Create written product names and prices so the same sale is described consistently.
Web access is easier for reviewing text, but it depends on a secure device and connection. Never save an eTIMS password in a public browser. Sign out and remove downloaded customer documents after using a shared machine.
Small does not mean informal recordkeeping. Reconcile invoice totals with payment records and bank or mobile-money statements regularly.
When the online portal or client makes sense
A service business that issues a limited number of detailed invoices may prefer a browser-based portal. Staff can type with a full keyboard, review customer details and download records in an organised environment.
A business selling goods or operating several pay points may need the client features described by KRA. Confirm device and operating-system requirements before purchasing hardware. KRA's guidance may specify which platforms are supported.
Plan for updates. Identify who is responsible for installing approved versions, backing up business records and checking that invoices transmit after a connection returns.
Do not let every employee use an owner's password. Where the system supports users and roles, assign the minimum access required. A cashier may need to create sales but not change core settings or approve reversals.
Test the workflow with ordinary and unusual sales before relying on it at peak time.
When system-to-system integration is justified
An established company may already create invoices in an ERP, accounting or sector-specific system. Re-entering every transaction into a second interface can produce delay and errors.
KRA describes OSCU and VSCU integration routes for automated systems and publishes information about certification and approved third-party integrators. This is a technical project, not simply a plug-in purchase.
Before selecting a vendor, define transaction volume, branches, offline behaviour, returns, credit notes, user permissions, support hours and reporting. Verify the provider against KRA's current approved information.
Ask who owns the configuration and data, how failures are queued, what audit logs exist and how the business exits the vendor relationship. Put service levels and responsibilities in writing.
A staged test should compare source sales, transmitted invoices and accounting totals. Do not declare success because one sample invoice received a number.
Prepare clean business information for onboarding
Use the business's official KRA PIN and registration details. Confirm the phone number and email linked to the relevant tax profile because verification codes or notices may go there.
Prepare a consistent catalogue of products or services. Avoid several spellings for the same item. Decide units of measure, standard prices and tax treatment with appropriate professional guidance.
Document branches, pay points and staff roles. If an appointed representative handles setup, use the formal appointment process described by KRA and withdraw access when the work ends.
Create a secure folder for onboarding confirmations, signed forms, user guides and support references. Do not mix passwords into the same folder as ordinary documents.
If information on the portal is wrong, correct it through the official process rather than building an invoicing system around the error.
Design the daily invoice routine
Technology works only when the routine is clear. Create a short operating procedure that staff can follow during a normal sale, a failed connection and a customer correction.
The routine should state:
- How the seller confirms item, quantity and price.
- When customer details are required and how they are checked.
- Who creates the electronic invoice.
- How the customer receives it.
- How payment is matched to the invoice.
- Who reviews cancelled, corrected or unusual transactions.
- How the day total is reconciled.
Do not delete or recreate an invoice casually to make totals match. Use the proper correction process and preserve the reason.
Supervisors should review exceptions, not just revenue. Repeated failures at one device can signal training, connection or configuration problems.
Protect accounts and customer information
Use unique passwords and approved multi-factor verification where available. Keep owner, administrator and cashier access separate.
Do not send login credentials to a support person through an ordinary chat. An approved provider should have a controlled support process and should never need the owner's personal one-time code.
Lock devices when unattended and remove access immediately when a staff member leaves. Restrict exported invoice files because they may contain customer names, PINs or contact details.
Back up records according to the system guidance and the business's legal obligations. Test that a backup can be restored; a folder of unreadable files is not a recovery plan.
Report suspected compromise through official KRA and internal channels. Change passwords from a trusted device rather than a link in a surprise email.
Handle downtime without inventing invoices later
KRA explains that some eTIMS routes require internet while others can continue in specified offline or USSD modes. Understand the behaviour of your chosen solution before a connection fails.
Keep the official downtime procedure at the sales point. Staff should know whether transactions queue, what proof to give the customer and how to confirm successful transmission later.
Record the time, device and error message. Avoid repeatedly pressing submit if that could create duplicates.
When service returns, reconcile queued sales against payments and stock. Escalate unresolved failures with screenshots that hide unnecessary personal data and include the official support reference.
Business continuity is a designed process, not a promise that “we will enter everything tomorrow.”
The eTIMS decision checklist
Before onboarding, confirm:
- The business's tax position with a reliable source.
- Goods, services, transaction volume and branch needs.
- Internet and device conditions.
- The official eTIMS option that matches those needs.
- User roles, correction approvals and daily reconciliation.
- Training, support and downtime steps.
- Data protection and access removal.
eTIMS for Kenyan business should make a truthful sales record easier to issue and review. Start with the workflow, choose the least complicated suitable official option and build disciplined daily habits around it.
