How to Become eTIMS Compliant in Kenya: Step-by-Step Guide

Becoming eTIMS compliant in Kenya is not a single software setting. It is a chain of records: the sale at the counter, the tax treatment applied to each item, the invoice sent to the customer, the response from KRA, and the report your accountant uses at month end. If any link is missing, the business may still be trading normally while its tax records are incomplete.

This guide sets out a practical sequence for a shop, wholesaler, restaurant or distributor. It focuses on what the business must prepare and test before relying on electronic invoicing in daily operations. Tax rules, rates and onboarding requirements change, so confirm your position with KRA or a qualified tax adviser before go-live.

What eTIMS compliance actually requires

eTIMS is KRA’s electronic Tax Invoice Management System. For a business that already uses a POS, accounting or ERP system, compliance usually means connecting that system to an approved invoicing route and keeping evidence of what was submitted and accepted.

Three things must be true at the same time:

• The invoice is correct. Business details, customer details where required, item lines, quantities, prices, tax rates and totals must match the sale.
• The submission is traceable. The business must be able to show which invoices were submitted, which were accepted, and how failures or uncertain outcomes were handled.
• The records reconcile. Sales, payments, credit notes and VAT reports must agree with the invoices that were issued.

A till that prints a tax-looking receipt is not proof of compliance. Ask instead: which system created the invoice, which route submitted it, and where is the result stored? For a fuller explanation of the integration routes and testing process, read the eTIMS integration guide.

Step 1: Confirm your VAT and eTIMS obligation

Start with your registration status, turnover and the nature of your supplies. VAT-registered businesses have different invoicing obligations from businesses outside VAT, and the eTIMS route available to a small taxpayer may differ from the route used by a larger company.

Write down:

• Your KRA PIN and the exact registered business name.
• Whether you are VAT registered, and the effective date of registration.
• The products or services you sell and their VAT treatment: standard-rated, zero-rated or exempt.
• Your outlets, branches or warehouses and the identity used by each one.
• Who creates invoices today, and which system holds the authoritative record.

Do not assume that every item in the shop carries the same tax treatment. Mixed baskets are common in retail, and a single wrong tax code can distort the invoice and the VAT return.

Step 2: Choose your eTIMS route

KRA provides different ways to meet electronic invoicing requirements. For system-to-system integration, the main routes are the Online Sales Control Unit (OSCU) and the Virtual Sales Control Unit (VSCU). The appropriate route depends on your software, how consistently you are online, and the approval and onboarding requirements that apply to your business.

Ask these questions before committing:

• Which route does the proposed POS or accounting system actually support?
• What onboarding, approval or credentials are required before production use?
• What happens when the internet drops during a sale?
• How does the system distinguish an accepted invoice from a rejected or uncertain submission?
• Who is responsible for retries, corrections and support?

Vega has fiscal-signing integration workflows, but activation depends on a supported connection, business configuration and successful testing. Confirm the current route for your business rather than assuming that a demonstration equals production approval. KRA publishes its own system-to-system integration guidance.

Step 3: Clean up business and product data

Integration work exposes weak master data. Before testing invoices, review the data that will be sent:

• Business identity: registered name, PIN, address and outlet details should match official records.
• Products: consistent descriptions, units of measure and pack sizes. Cartons and pieces must not be mixed casually.
• Tax categories: every product should have a deliberate VAT treatment, not a default inherited from an old spreadsheet.
• Prices: confirm whether prices are VAT-inclusive or VAT-exclusive, and how discounts are applied.
• Customers: where buyer details are required, make sure the customer record is accurate and complete.

If your catalogue has thousands of items, fix the highest-risk records first: fast movers, high-value goods, items with mixed units, and anything whose tax treatment has changed. A clean import is cheaper than correcting invoices after staff have started using the system.

Step 4: Configure invoices and tax in your POS

The invoice layout and the tax configuration must agree. Check the fields the customer will see, the sequence used for invoice numbers, and the way credit notes are issued. In a retail environment, the cashier should not be able to change tax rates or invoice identities casually.

Set clear permissions around:

• Voiding or correcting a sale.
• Issuing a credit note or refund.
• Changing prices, discounts or tax settings.
• Reopening a closed shift or editing a submitted document.

The goal is not to make everyday selling difficult. It is to ensure that exceptions leave a record and that only authorised people can change the figures that affect tax.

Step 5: Test the invoice lifecycle

Do not test only a simple cash sale. Use representative transactions and watch what happens at each stage:

1. Create a normal multi-item sale.
2. Apply a discount or a price list change.
3. Split the payment between cash and M-Pesa.
4. Issue a credit note or process a return.
5. Disconnect the internet during a transaction, then reconnect.
6. Check the final invoice, the stored response and the monthly report.

Record the expected result for each test. A successful demonstration is useful only if you can explain what the operator sees when something fails. For an uncertain outcome, the team must know how to check the original status before resubmitting, so the same sale is not invoiced twice.

Step 6: Train staff and define exception handling

Cashiers need a short, practical routine: sell, collect payment, confirm the invoice result, and escalate clearly when the result is not normal. They should know what information to provide when asking for help: invoice reference, time, outlet, amount and the visible error message.

Supervisors need a different routine: review failed or uncertain submissions, approve corrections, and check that credit notes are supported. Keep passwords and integration credentials out of shared chat groups and public screenshots.

Step 7: Reconcile every month

Compliance is not finished when the invoice is accepted. At month end, reconcile:

• Sales recorded in the POS.
• Invoices issued and accepted through the eTIMS route.
• Payments received by cash, M-Pesa, card or bank.
• Credit notes, refunds and voids.
• Output VAT and input VAT in the VAT report.

If the numbers do not agree, investigate before filing. A difference may come from an unrecorded sale, a duplicate submission, a wrong tax code, or a credit note that was issued but not reflected in the report. The POS system Kenya guide explains how sales, stock, payments and VAT reporting fit together in one workflow.

eTIMS compliance checklist

Common eTIMS compliance mistakes

• Treating the POS as the only record. The fiscal submission result must also be stored and reviewable.
• Ignoring offline behaviour. A plan for lost connections is part of the process, not an afterthought.
• Using one tax code for everything. Mixed baskets need deliberate tax treatment.
• Letting anyone edit invoices. Corrections should be permissioned and traceable.
• Reconciling only at filing time. Monthly checks catch problems before they become filing problems.

Frequently asked questions

Is a POS automatically eTIMS compliant?

No. A POS must be configured for the correct tax treatment and connected through an approved route, and the business must be able to show the submission result. Compliance also depends on process, training and reconciliation.

Can I become compliant without changing my POS?

Sometimes. It depends on whether your current system supports a compatible integration route and whether the underlying data is clean. An assessment should establish this before you commit to new software.

What happens if an invoice fails to submit?

The team should record the failure, check the original status, and follow the agreed recovery process. Do not assume that resubmitting is always safe. The correct action depends on the route and the actual response.

Does eTIMS compliance replace VAT filing?

No. Electronic invoicing and VAT filing are related but separate obligations. You still need accurate VAT reports, supporting records and timely returns.

Next step

If you are planning an eTIMS project, start with a scoped assessment rather than a generic software demo. Review your current invoices, outlets, product data and reporting process, then test the actual route you intend to use. See the eTIMS integration page or request a setup discussion with Vega.

Related guides: POS system Kenya, wholesale and distribution POS, liquor store POS and payroll software Kenya.

This guide is general information, not tax advice. Confirm current eTIMS requirements, VAT rates and filing deadlines with KRA or your qualified adviser.