Gakahu & Rosana Advocates
Back to Tax Law

Tax Law

4 August 2026

VAT Invoices, Debit Notes and Credit Notes in Kenya: eTIMS Compliance

By Christopher N. Rosana

A muted-teal retail counter and flowing receipt-like light paths in a deep-green interior, showing a controlled transaction record without text.

For a Kenyan business using the prescribed electronic tax-invoicing system, each sale should be recorded and an electronic invoice generated through that system. If the original supply later needs correction, the proper response is usually a credit note or debit note that refers to the original invoice—not an informal replacement document or a changed spreadsheet entry. The VAT Act, the Tax Procedures Act and the 2024 Electronic Tax Invoice Regulations work together: they govern who must issue an invoice, the data and system trail that support it, and how a change is evidenced. Good controls connect the order, delivery or service record, eTIMS invoice, adjustment note, return and accounting ledger.

Start with the invoice obligation and the electronic-system rule

Section 42 of the Value Added Tax Act, 2013 requires a registered person making a taxable supply to issue a tax invoice. It also prevents a person who is not registered from issuing a tax invoice, and prevents a registered person from issuing one for a non-taxable supply. The question is therefore not merely whether a customer asks for an invoice. The supplier must first identify its registration status and the VAT character of the actual supply.

The electronic-invoicing obligation has a broader operational reach. The Tax Procedures (Electronic Tax Invoice) Regulations, 2024 apply to persons carrying on business in accordance with section 23A of the Tax Procedures Act, subject to their exclusions and any exemption. A “system” is an electronic tax-invoicing or receipting system maintained and used under those Regulations. In practice, a business should confirm whether its activity is within the eTIMS requirement or an applicable exclusion or exemption before designing its billing process around an assumed rule.

Under regulation 4, a system user must record each sale in the system, generate an invoice for each sale through it, send the invoice to the buyer and transmit invoice details to the Commissioner in the prescribed manner. This means eTIMS is not simply an end-of-month compliance upload. It is a transaction-recording process. Sales, credit control, finance and technology teams should agree which event creates the sale record and who may correct it.

What a compliant electronic invoice should evidence

An electronic tax invoice is evidence of a transaction, not a substitute for the underlying commercial facts. Regulation 7 requires specified particulars, including the user’s PIN, the time and date of issue, the invoice serial number, a unique system identifier, a unique invoice identifier and a quick-response code. The Regulations prescribe further particulars, so system configuration should be checked against the current text rather than built from an old invoice template.

The invoice should match the contract, purchase order, delivery confirmation or service acceptance record. Inconsistent descriptions, quantities, customer identifiers or dates create both commercial and tax risk. A purchaser considering an input-VAT claim also needs documentation that corresponds with the actual taxable purchase; Part 19 addresses those input-tax conditions and denial risks. A supplier should not treat the presence of an electronic invoice alone as proof that the supply, amount or VAT treatment is correct.

For practical control, lock the core transaction data once an invoice has been issued, reserve correction permissions for trained staff and keep an audit trail showing who requested, approved and processed a change. Where an enterprise system feeds eTIMS, test the interface after product-code, tax-code or software changes. The Regulations require a system capable of maintaining records and logging activities; a control failure can therefore be as important as a missing paper record.

When to issue a credit note or debit note

A credit note records a downward adjustment to an earlier invoice, such as a returned item, price reduction, cancellation, overcharge or a reduction in tax properly attributable to the supply. A debit note records an upward adjustment, for example where the taxable value or tax was understated and the supplier must document the additional amount. Whether an adjustment is appropriate depends on the facts and the VAT Act; it should not be used merely to alter a completed transaction to produce a preferred return position.

Section 43 of the VAT Act governs credit and debit notes following a change in the taxable value or tax payable. Regulation 7 of the 2024 Regulations adds an essential electronic control: a credit note or debit note issued by a system user must refer to the original invoice number to which the supply relates. The original invoice should remain traceable. Deleting it and issuing a fresh invoice loses the explanatory link that an auditor, customer or finance reviewer needs to see.

Before issuing a note, record the reason for the adjustment, the original invoice identifier, the affected goods or services, the corrected amount and the supporting evidence. That may include a return record, signed variation, approved discount, revised measurement, customer correspondence or proof of a mistaken tax code. The timing of the correction can affect the VAT return in which the adjustment is reported, so finance teams should reconcile issued notes to both the sales ledger and the relevant return.

Manage outages, corrections and record retention deliberately

System disruption does not make the compliance obligation disappear. Regulation 5 requires continuity of operations. Where a user cannot use the system, the user must notify the Commissioner in writing within twenty-four hours and record sales manually while the system is unavailable; when access is restored, those sales must be entered into the system. The exact response should be tested in an outage procedure, with current KRA instructions checked before an incident rather than during it.

A business should distinguish a genuine correction from a system error, a cancellation before supply, a customer dispute and a bad debt. Each may require a different commercial approval and evidence set. The common control is traceability: the records should explain what happened, when it happened, who authorised it and how the eTIMS, accounts receivable and VAT-return figures were brought into line. Repeated credit notes against one customer, product line or employee should trigger a management review, not simply be treated as routine administration.

Records must also remain available after the invoice is sent. The Tax Procedures Act contains the general record-keeping framework, and the Electronic Tax Invoice Regulations require system capacity to maintain records and activity logs. Retain the original invoice, adjustment note, source documents, approval and reconciliation together under a secure retention policy. A customer-facing PDF, email copy or accounting export may help operationally, but it should not be mistaken for the complete electronic audit trail.

A workable monthly control checklist

At month end, reconcile system-issued invoices to the sales ledger, bank or receivables movements and the VAT return. Review gaps in invoice numbering, voids, manually recorded outage sales, duplicate invoices and credit or debit notes without a clear reason. Confirm that every adjustment note points to its original invoice and that tax codes are consistent with the supply classification. Part 20 discusses the different consequences of standard-rated, zero-rated and exempt supplies; Part 21’s focus is ensuring that the chosen treatment is accurately documented and corrected.

  • Confirm that the supplier, supply and VAT treatment support issuing a tax invoice.
  • Use the prescribed electronic system where the Regulations apply, unless a valid exclusion or exemption is established.
  • Generate and transmit the sale record through the system, with the required invoice particulars.
  • Use a credit or debit note for a supported post-invoice adjustment and link it to the original invoice.
  • Document outages, manual sales, corrections and approvals so they can be reconciled later.
  • Keep the transaction evidence and system trail together for the applicable statutory retention period.

The safest approach is not to regard an invoice as a document created after the sale. It is part of the transaction record from the outset. A controlled eTIMS workflow, disciplined adjustment process and reconciled evidence file reduce the risk that a valid commercial correction becomes a VAT compliance problem.

Official sources: Tax Procedures (Electronic Tax Invoice) Regulations, 2024; Value Added Tax Act, 2013.

Part 21 of 37 in this series.

Do you need legal counsel?

Contact us