On this page
  1. TL;DR
  2. Raise the invoice when the sale happens
  3. Send refunds and returns as credit notes
  4. Put delivery on the same invoice
  5. Capture the buyer’s KRA PIN
  6. Choose the connection that fits the shop
  7. Test every order type before going live
  8. Watch the queue after launch
  9. Your next step

An online shop selling 50 orders a day cannot retype them into eTIMS every evening. Someone falls behind, invoices go out late or never, and business buyers stop ordering because they cannot claim the expense. The fix is eTIMS for online shops done properly: every order raises its own invoice, automatically, from the shop itself.

This guide covers when the invoice is raised, how refunds and delivery fit, which KRA connection suits a shop and what to test before the first live order. For the wider choice of routes, read KRA eTIMS: which route fits.

This is not tax advice. Confirm how the rules apply to your business with your tax adviser.

Raise the invoice when the sale happens

KRA requires everyone in business to issue electronic tax invoices, whether or not they are registered for VAT. The open question for a shop is the moment each invoice is raised.

KRA’s VAT guidance sets the tax point at the earliest of three events: the goods are delivered, the invoice is issued, or payment is received. An online shop usually meets one of these first, depending on how it takes money.

How the order is paid What usually comes first When to raise the eTIMS invoice
M-PESA or card at checkout Payment When your server confirms the payment
Pay on delivery Delivery and payment together When the rider confirms delivery and payment
Credit terms for business buyers The invoice or the dispatch At whichever of the two comes first
Deposit or pre-order Part payment Agree the treatment with your adviser

Waiting for dispatch on a prepaid order puts the invoice after the payment. That leaves the invoice trailing the earliest event, and a busy week can stretch the gap to days.

Raise the invoice from your server, never from the customer’s browser. A browser can close halfway through. Your server knows when the money is confirmed by Safaricom or the card processor.

Send refunds and returns as credit notes

Returns are normal in online retail. A wrong size, an item damaged in transit or a change of mind each alters a sale KRA has already recorded.

Send every refund as a credit note against the original eTIMS invoice. KRA’s filing guide adjusts credit notes against your sales when it validates your income tax return. An edited or deleted invoice leaves your records and KRA’s in disagreement.

Four rules keep refunds clean:

  • A part refund gets a credit note for the refunded lines only.
  • A cancelled order that was already invoiced still needs a credit note, even if the money went back the same day.
  • The credit note and the M-PESA or card refund share the order number, so one search shows both.
  • Refunds that cross a year end get flagged for your adviser, because they touch two returns.

Put delivery on the same invoice

Most shops charge for delivery. When your shop collects that charge, it is part of what you sold, so it belongs on the eTIMS invoice as its own line.

Create a delivery item once, with its item classification code and tax type, and have the shop add it to every order that carries a delivery fee. Ask your adviser which tax type fits your delivery charge. Set it once in the item, so no cashier or developer guesses later.

When a courier bills you for deliveries, that is a purchase. You need the courier’s eTIMS invoice against your PIN to claim the cost, as covered in eTIMS expenses and supplier invoices.

Show discounts and coupons on the invoice as well. The invoice total should equal what the customer paid. A mismatch with the amount paid turns every reconciliation into detective work.

Capture the buyer’s KRA PIN

Business buyers can claim your invoice as an expense only if it carries their PIN. KRA validates expenses against invoices where the buyer PIN was correctly captured and sent.

Add an optional “KRA PIN for business purchases” field at checkout. Check its format before payment, so a typo never reaches KRA. Then send the PIN with the invoice, and leave it blank for individual shoppers.

Offices, schools and resellers often choose suppliers on this alone. A shop that issues a correct invoice with their PIN saves them a chase every month.

Choose the connection that fits the shop

KRA offers two system-to-system routes. It describes OSCU as suited to invoicing that is always online, and VSCU as suited to bulk invoicing by businesses that are not always online. A web shop is online by nature, so OSCU usually fits.

Your setup Route that usually fits
A hosted or WooCommerce shop with steady online orders OSCU, through an integrator’s product or your own connection
An online shop plus physical branches on one stock system OSCU, with each branch registered as its own device
Wholesale orders invoiced in batches VSCU
A custom shop, or one linked to an ERP Self-integration over OSCU

Either way, KRA requires certification before you go live. You can use a product from a KRA-verified third-party integrator, which may carry the integrator’s own costs. Or you can self-integrate: build the connection, test it in KRA’s sandbox and take it through KRA’s vetting and certification.

An integrator’s plug-in fits when it supports your shop platform and every invoice type you raise. Self-integration fits a custom shop, or a shop whose plug-in cannot handle credit notes, delivery lines or several branches.

Test every order type before going live

KRA’s sandbox at etims-sbx.kra.go.ke lets you test before anything reaches production. Most shops test one clean order and stop. Test the orders that go wrong instead.

  1. A prepaid M-PESA or card order, invoiced when payment is confirmed.
  2. A pay-on-delivery order, invoiced when the rider confirms delivery.
  3. A full refund and a part refund, each sent as a credit note.
  4. An order with a delivery fee and a coupon, where the invoice total equals the amount paid.
  5. A business order with a buyer PIN.
  6. A payment callback that arrives twice, which must not raise a second invoice.
  7. KRA unreachable for an hour, with orders queued and each sent once when it returns.

Check that the control unit number and QR code appear on the receipt page and the emailed receipt. Store the control unit invoice number next to your own order number. KRA’s guide calls it the unique link between your data and KRA’s.

Watch the queue after launch

A shop connection fails quietly. A credential expires or a new product lacks an item code, and orders keep flowing while invoices stop.

Check one number every morning: orders paid yesterday minus invoices KRA accepted. It should be zero. Anything else is a list of orders to fix that day, while each one is still easy to fix.

Your next step

Take last week’s orders and count three things. Orders with no eTIMS invoice, refunds handled as edits, and business buyers who asked for their PIN on an invoice. Those three numbers tell you how urgent this is.

Our eTIMS service connects online shops to KRA, takes the connection through the sandbox and certification, and queues invoices through outages. If the checkout itself is losing orders, start with five checkout fixes.

Need it built properly? A free 30-minute call with an engineer, then one fixed price in writing.

Book a free call

Keep reading

KRA eTIMS Without the Retyping: Which Route Fits Your Business

KRA eTIMS Without the Retyping: Which Route Fits Your Business

A phone displaying DEMO SHOP as the sender of a text message.

Bulk SMS Sender ID in Kenya: Get Your Name on Every Message

Pay on Delivery in Kenya: Stop Losing Money on Failed Drops

Pay on Delivery in Kenya: Stop Losing Money on Failed Drops