Business

The Compliance a Kenyan Pharmacy Carries

K By Kev 5 November 2026 Updated 7 November 2026 12 min read
Share
Business guide

A pharmacy carries two sets of obligations at once, and they are usually managed by two different people who do not talk. The professional side — premises, practice, dispensing, storage — sits with the Pharmacy and Poisons Board. The commercial side — invoicing, VAT, records — sits with KRA. What makes a pharmacy hard to run is that the same daily actions feed both, and a system built for one will not produce what the other expects.

Key takeaways
  • Two regulators want different things from the same counter action.
  • Individual logins are what make a dispensing record worth having.
  • Batch and expiry must be captured at receiving or they cannot be reconstructed.
  • Thermal rolls fade; records you may need years later need a durable form.
  • Two separately maintained records of one day will always disagree.
On this page▾
  1. Two regulators, one counter
  2. Making one action serve both
  3. Where pharmacies come unstuck
  4. A worked example: two records of the same day
  5. How Veira handles it
  6. Frequently asked questions

Two regulators, one counter

The professional obligations attach to practising: who may dispense, under what supervision, from premises meeting a standard, with records showing what was dispensed and by whom. This is specialist ground and your pharmacist, not a software vendor, is the authority on it.

The commercial obligations attach to trading: a tax invoice for every sale, correct tax treatment per line, records that support what you file, registered details that match what KRA holds: what a compliant invoice shows.

Where they meet is the counter. One act — dispensing and selling an item — has to produce a dispensing record and a tax invoice, and it either does both automatically or somebody does the second one twice.

Want to see it running in your own business first?

Sign Up

Making one action serve both

Five things that stop the duplication.

  1. 1

    Individual logins, always

    A dispensing record that cannot name who dispensed is thin. Individual logins produce the attribution as a by-product of serving customers rather than as a separate log.

  2. 2

    Batch and expiry captured at receiving

    Traceability runs on batches, and a batch not captured at the door cannot be reconstructed later: pharmacy inventory.

  3. 3

    A compliant tax invoice from the sale itself

    Not a second device, not a second keying. The dispensing and the invoicing are one action or they will disagree.

  4. 4

    Records that survive

    Thermal rolls fade. What you need to be able to produce years later has to be held in a form that lasts: record keeping.

  5. 5

    Correct tax treatment per product

    A pharmacy's range is not uniform in its tax treatment, and defaulting everything to one rate produces a return that cannot be reconciled.

Where pharmacies come unstuck

One shared login at the counter

Convenient, and it removes the attribution the dispensing record exists for.

Expiry managed on a spreadsheet

Accurate until the pharmacy is busy, which is the condition it most needs to survive.

Treating KRA and the Board as the same problem

They want different things from the same action, and a system that satisfies one is not automatically satisfying the other.

A second device for eTIMS

Double keying at a counter where accuracy is not optional: eTIMS device alternatives.

Letting registered details drift

A changed premises, a changed superintendent, a changed address — each one matters to somebody, and the invoicing failure is usually how you find out: KRA PIN requirements.

Keeping the two sets of records in two places

The dispensing book at the counter and the invoicing system in the office will diverge, because they are updated at different moments by different people. One action producing both is the only arrangement that does not drift.

A worked example: two records of the same day

Worked example

A pharmacy kept a careful dispensing book at the counter and issued tax invoices from a separate system afterwards, usually at the end of the day.

The two records never quite matched. Items dispensed late in the day were occasionally invoiced the following morning, a few were missed entirely, and a returned item appeared in one record and not the other.

Neither record was dishonest and both were maintained conscientiously. They disagreed because they were produced by two separate acts of writing things down, and one of those acts always happened when the counter was quiet rather than when the sale did.

Business impact

Trading without eTIMS-compliant tax invoices risks KRA penalties, blocked VAT input claims for your customers, and receipts a business buyer cannot expense.

Veira signs every sale to KRA eTIMS automatically, so each receipt is compliant the moment it prints, with no separate device to reconcile.

How Veira handles it

Veira makes one action produce both records: the sale names the item, the batch, the staff member and the time, and as a KRA-certified eTIMS integrator it issues the compliant tax invoice at the same moment.

Stock is held by batch with expiry captured at receiving, so lines approaching expiry surface as a warning rather than as a discovery, and each member of staff signs in as themselves.

Selling continues when the connection does not — a pharmacy cannot stop dispensing while a network returns — and the invoices queue and transmit on reconnect rather than being skipped.

Frequently asked questions

What are the two sets of obligations?
Professional — premises, practice, supervision, dispensing records, storage — which sit with the Pharmacy and Poisons Board, and commercial — tax invoices, VAT treatment, records, registration — which sit with KRA. The same counter actions feed both.
Who should advise on the professional side?
Your pharmacist and the Board, not a software vendor. Software can produce the records that side expects; it cannot tell you what the practice requirements are or whether you meet them.
Why do dispensing records need individual logins?
Because a record that cannot name who dispensed is weak evidence of anything. Individual logins produce that attribution automatically, as part of serving the customer rather than as a separate log somebody maintains.
Can expiry be managed on a spreadsheet?
Until the pharmacy gets busy, which is exactly when it matters. A spreadsheet is accurate only while somebody updates it, and the updating is the first thing dropped on a difficult day.
Does a pharmacy need a separate eTIMS device?
Usually not, and a second device means double keying at a counter where accuracy is not optional. If the POS is a certified integrator the invoice comes from the sale itself.
What is the most common compliance failure?
Two records of the same day that disagree, because the dispensing record and the invoice are produced by two separate acts. Making one action produce both removes the category of problem rather than reducing it.

The pharmacy problem is not either regulator; it is that one counter action has to satisfy both, and most setups make it two actions. Make the sale produce the dispensing record and the tax invoice together, and the disagreements stop having anywhere to come from.

Need help, or want to talk it through first? Chat with us on WhatsApp

Keep reading

See all Business guides

Veira for your business

Want the full picture for this trade? Veira for pharmacies and chemists covers the counter, the stock and the KRA side together.

Browse Veira by business type · Who we serve