ETIMS INVOICE NUMBERS | SERPA ODOO ERP FOR AFRICA

A procurement officer has a delivery note, a PDF invoice and pressure to close the month. Then finance asks one question: can KRA verify the eTIMS invoice number against the buyer’s PIN? If the answer is no, the invoice often stops there.

An eTIMS invoice number is now a control point for Kenyan buyers, not a formatting preference. KRA requires valid electronic tax invoices to support many business expense deductions, a requirement that applied from 1 January 2024. Since 1 January 2026, iTax also validates declared income and expenses against TIMS/eTIMS invoice data when taxpayers file 2025 year-of-income or accounting-period returns. Odoo KRA eTIMS integration gives finance teams a way to make that evidence part of the invoicing process rather than a month-end repair exercise.

Why a buyer rejects an invoice without a verifiable eTIMS number

A buyer is usually protecting two positions: the deductibility of a business expense and, where VAT applies, the input VAT claim. A supplier invoice that cannot be validated creates uncertainty in both.

KRA’s current guidance is clear on the underlying requirement. A buyer generally needs a valid electronic tax invoice for an expense to be deductible for income-tax purposes. For VAT, input VAT can only be claimed from a valid TIMS/eTIMS invoice transmitted to KRA with the buyer’s KRA PIN. A printed PIN on an invoice is not enough if that PIN was not captured correctly in the transmitted record.

The practical consequence is direct. Finance teams reject a non-verifiable invoice because accepting it can leave the buyer with an expense that fails iTax validation, or with input VAT that cannot be supported. VAT returns and payments are due by the 20th of the following month, so waiting for a supplier to resolve an invoice after the close can create a real reporting problem.

What the buyer checks

The phrase “eTIMS number” is often used loosely. An ordinary internal invoice number does not become an eTIMS invoice number because it appears on branded stationery. The relevant question is whether KRA can verify a transmitted electronic invoice and whether its data matches the commercial transaction.

A buyer can scan the invoice QR code or use the Invoice Number Checker on iTax. KRA identifies the following invoice details as key verification fields:

| What the buyer checks | Why it matters | | Supplier name and KRA PIN | Confirms the supplier shown on the invoice is the supplier whose invoice was transmitted. | | Buyer KRA PIN | Supports VAT input claims where applicable and allows KRA to match the expense to the right buyer. | | eTIMS invoice number and serial number | Provides the reference used to verify the electronic invoice. | | Invoice date and time | Must align with the actual transaction and the transmitted record. | | Amounts and tax rate | Allows finance to reconcile tax and value to the purchase order or goods receipt. | | Register identifier and QR-code signature | Helps show the invoice passed through the required KRA process. |   The check is not bureaucracy for its own sake. From 1 January 2026, KRA began validating income and expenses declared in returns against TIMS/eTIMS invoices, withholding-tax data and import data. A mismatch that was once found during a manual review can now be exposed during return filing.

The invoice failures we see most often

Most rejected invoices are not caused by a buyer refusing to pay. They are caused by a broken handoff between sales, finance and the eTIMS device or ERP configuration.

1. The supplier created an invoice but did not transmit it

A supplier may issue a PDF from an accounting package, email it, and assume the work is complete. If the invoice was not transmitted through eTIMS, KRA cannot verify it as the required electronic tax invoice.

The right fix is to issue and transmit a compliant invoice. Editing the original PDF or adding an invoice number by hand does not correct the KRA record.

2. The buyer PIN is absent or wrong in the transmitted invoice

This is a common failure in B2B transactions. The supplier may have the buyer PIN on a purchase order, yet the PIN never reaches the transmitted eTIMS invoice because staff entered it only in a free-text field or the ERP mapping was incomplete.

For a VAT buyer, that detail matters because KRA requires the invoice to be transmitted with the buyer PIN for an input-VAT claim. The correction is a reissued and transmitted invoice with the right buyer details, not a revised paper copy.

3. Invoice details do not match what KRA received

A wrong supplier PIN, invoice date or invoice number can cause the verification result to fail. The buyer may also see an amount or tax rate that differs from the purchase documentation.

KRA’s January 2025 guidance points to a practical remedy: correct and retransmit the invoice. Where the transaction needs to be reversed, a credit note may be necessary before the corrected invoice is issued. Informal amendments leave an auditable gap.

4. Finance assumes eTIMS applies only to VAT suppliers

That assumption is costly. KRA requires all persons carrying on business, including non-VAT businesses, to onboard and issue electronic invoices. The income-tax deduction requirement is why a non-VAT buyer can still refuse a supplier invoice without valid eTIMS support.

There are legitimate exclusions. KRA lists salaries and wages, imports, air passenger tickets, investment allowances, interest, financial-institution fees, final-withholding-tax expenses, and services from non-residents without a Kenyan permanent establishment among the exclusions. Do not demand an eTIMS invoice for an excluded item simply because it appears in the accounts. Classify the expense first.

A practical supplier process for compliant invoicing

For an enterprise supplier, the strongest approach is to build tax evidence into the order-to-cash workflow. This reduces rework for sales staff and gives finance an auditable trail.

Step 1: Capture the buyer’s KRA PIN before invoicing

Make the buyer PIN a controlled master-data field for B2B customers. Validate its format and require staff to confirm it against the customer’s supplied tax details before the first invoice.

This is the step many businesses skip. A PIN typed into a note field will not help if the eTIMS transmission is configured to read a different field.

Step 2: Match the invoice to the commercial record

Before posting, reconcile the customer, goods or services, invoice date, taxable values and tax treatment to the order and delivery evidence. The finance team should be able to explain any change without searching through email chains.

For multi-entity groups, keep each Kenyan entity’s tax identity, invoice sequence and configuration separate. A shared customer record is useful. A shared supplier PIN or incorrect issuing entity is not.

Step 3: Send the invoice through KRA validation

KRA provides eTIMS options including the portal, client solutions and system-to-system integration. The right option depends on transaction volume and operating model.

If your finance team issues a small number of invoices each month, the portal may be sufficient. If invoicing is part of a high-volume sales, distribution or service operation, manual portal entry creates duplicated work and weakens controls. In that case, an ERP integration is the better judgement call because the invoice data originates once and follows an auditable process.

Odoo’s Kenya localisation uses an Online Sales Control Unit, or OSCU, to validate, encrypt, sign, transmit and store invoices. After KRA signs the invoice, Odoo presents the KRA invoice number and QR code. This is the operational value of Odoo KRA eTIMS integration: the commercial invoice and the KRA evidence are generated from the same transaction record.

Step 4: Release only the KRA-signed invoice to the customer

Set a clear control: sales should not send an invoice as tax-compliant until the KRA process has returned the invoice number and QR code. Where transmission fails, route the document to an exception queue owned by finance or tax.

That control matters because a customer can reject the invoice immediately. It also prevents staff from trying to resolve a rejected PDF after the period has closed.

Step 5: Monitor exceptions in real time

Track invoices that are pending transmission, rejected by the service, missing a buyer PIN or awaiting correction. Management needs visibility by branch, entity and sales team, not a spreadsheet assembled at month-end.

A useful ERP implementation includes a daily exception review and a defined owner for each failure type. The goal is not zero exceptions on day one. The goal is that every exception has a visible status, a correction path and an audit trail.

Two examples finance teams can recognise

A distributor loses time on a missing buyer PIN

Take a Kenyan industrial-parts distributor with six sales representatives and monthly B2B billing of KES 18 million. Its sales team collected buyer PINs in email signatures, but the invoice clerk copied them into a remarks field that did not flow into the eTIMS transmission. Several VAT customers rejected invoices because KRA could not match the buyer PIN to the transmitted record.

The distributor changed its process so the PIN became a required customer master-data field for taxable B2B invoices. It also held invoices in Odoo until the KRA response returned the invoice number and QR code. The business would have done this earlier because the administrative cost was not the original data capture, it was credit-control calls, reissued documents and delayed collections.

A small supplier needs a different route

Take a small-scale farmer supplying produce to a hotel, with annual turnover below KES 5 million. If the supplier is not VAT registered, Buyer-Initiated Invoicing may be an available fallback. It is accessed through eCitizen, and the seller must approve or reject the buyer-initiated invoice within 30 days.

This route does not apply to VAT-registered sellers. The hotel should not assume it can create supplier invoices for every small vendor, and the supplier should not assume approval is optional. The better long-term choice depends on the supplier’s registration status and transaction pattern, so confirm eligibility before building the payable process around it.

A buyer-side checklist before accepting an invoice

Use this checklist in accounts payable, procurement and vendor onboarding:

1.       Confirm whether the expense requires eTIMS support or falls within a stated KRA exclusion. This prevents both unsupported claims and unnecessary requests.

2.       Verify the eTIMS invoice number through the QR code or the iTax Invoice Number Checker. This confirms that the invoice is verifiable, not merely well formatted.

3.       Match supplier PIN, buyer PIN, date, amount and tax rate to the contract, purchase order and goods receipt. This identifies errors before payment approval.

4.       Reject a non-compliant invoice with a specific reason, such as missing buyer PIN in the transmitted record. A precise rejection gives the supplier a workable correction path.

5.       Require a reissued, transmitted corrected invoice or an appropriate credit note where needed. Do not accept an edited PDF as tax evidence.

6.       Retain the verified invoice and supporting purchase records in the approval file. The record should allow a reviewer to trace the expense from procurement to KRA-verifiable invoice.

For government suppliers, the control is even more immediate. KRA announced eTIMS and IFMIS integration on 31 August 2026. Government suppliers must generate a valid eTIMS invoice before submitting an invoice for IFMIS payment processing, and the submitted details must match eTIMS records.

Frequently Asked Questions

Does every Kenyan supplier need to issue eTIMS invoices?

KRA states that all persons carrying on business, including non-VAT businesses, must onboard and issue electronic invoices. However, whether a particular buyer expense needs eTIMS support can depend on KRA’s listed exclusions, such as salaries, imports and certain non-resident services.

Can a buyer claim VAT from a normal PDF invoice?

No, not where the invoice is not a valid TIMS/eTIMS invoice transmitted to KRA with the buyer’s PIN. KRA states that a manual or non-compliant invoice cannot support an input-VAT claim.

What should a supplier do when a buyer rejects an invoice?

Identify the failed field or missing transmission, then reissue and transmit a corrected compliant invoice. If a reversal is required, process the appropriate credit note. Do not try to repair compliance by editing a PDF or printed invoice.

How can a buyer verify an eTIMS invoice number?

The buyer can scan the invoice QR code or use the Invoice Number Checker on iTax. Check the supplier PIN, buyer PIN, date, serial number, values, tax rate, register identifier and QR-code signature against the commercial documents.

KRA’s eTIMS rules have moved invoice verification from a tax-team task to an operational control for every B2B sale. If your current process relies on staff retyping invoice data into a portal or correcting rejected PDFs at month-end, it is time to assess the workflow. Request a Consultation on Odoo KRA eTIMS integration.