Kenya eTIMS Invoice Requirements & Rejections | SERPA

A procurement officer in Nairobi receives a supplier invoice with a PIN printed at the top, but the invoice fails the iTax check. The goods may have arrived and the commercial details may be correct, yet finance cannot approve the document until the electronic tax record is verified.

That is why eTIMS invoice requirements matter at the point of purchase, not only during a tax review. Since 1 January 2026, KRA has validated income and expenses declared in 2025 income-tax returns against TIMS and eTIMS records, withholding-income-tax data and Customs data. A dependable invoicing process helps suppliers keep customer confidence, protect payment cycles and maintain traceable accounts. Odoo KRA eTIMS integration can embed these controls in everyday sales and finance operations.

The phrase “invoice without an eTIMS number” is useful shorthand, but it misses the actual failure. A buyer may reject an invoice because it was never transmitted to KRA, because the buyer PIN was absent or incorrectly transmitted, or because the invoice details do not match the underlying transaction.

Why Kenyan buyers are refusing supplier invoices

Kenyan businesses need records they can defend. KRA expects valid electronic tax invoices to support relevant business expenses, and VAT-registered buyers need verified invoice data to support eligible input VAT claims. A supplier PIN printed on a PDF is not evidence that the underlying invoice was correctly transmitted through eTIMS. Reliable electronic invoicing helps buyers process compliant invoices with confidence.

KRA validation has made invoice checks more important in purchasing workflows. If an invoice cannot be verified, buyers may hold it while the supplier corrects the record. Suppliers that maintain accurate, verifiable invoices can reduce preventable disputes and unnecessary payment delays.

This affects more than the accounts-payable queue:

| Buyer concern | What finance checks | Why the invoice may be rejected | | Expense support | Whether the invoice is valid and electronically transmitted to KRA | An unverified invoice creates a risk that the expense will not stand up in a return review. | | Input VAT support | Whether validated invoice data is available, including the buyer PIN where applicable | The buyer cannot rely on a printed PIN alone when the transmitted data is incomplete. | | Supplier master data | Supplier PIN, legal details and invoice identifiers | Incorrect data can prevent verification or create a mismatch against the purchase record. | | Audit trail | Original invoice and any linked credit or debit note | A replacement invoice without the correct transaction trail leaves an unresolved control gap. |   As of October 2026, the practical question from a buyer is no longer, “Does this document look like an invoice?” It is, “Can we verify it in the KRA record, and does it support our claim?”

What KRA requires on the electronic invoice

The Tax Procedures (Electronic Tax Invoice) Regulations, 2024, effective 28 March 2024, set mandatory particulars for an electronic tax invoice. The invoice must carry:

●        Supplier PIN, issue date and issue time.

●        Serial number and the buyer PIN where the buyer intends to claim an expense or input tax.

●        Gross total and tax totals.

●        Item code, description, quantity, unit of measure and tax rate.

●        A unique system identifier, a unique invoice identifier and a QR code.

Each field exists because KRA needs the electronic record to identify the seller, purchaser, goods or services, tax treatment and invoice trail. The buyer PIN is particularly important when the purchaser intends to support an expense or input-tax claim.

Source: Kenya Revenue Authority guidance on eTIMS and the Tax Procedures (Electronic Tax Invoice) Regulations, 2024.

The distinction most suppliers miss: printed is not transmitted

The recurring error is treating an invoice layout as a compliance process. A supplier may add a PIN, an invoice number and even a QR code to a document, but that does not establish that the transaction reached KRA correctly.

KRA’s iTax invoice checker allows the user to verify an invoice number and buyer details. If a buyer cannot verify the record, the supplier should investigate the transaction in the invoicing system before sending another PDF. Finance staff should not guess which field failed, because a buyer PIN may be visible on the document but wrong in the transmitted data.

Consider a wholesaler processing a high volume of invoices. Customers reject some documents because the buyer PIN was omitted from the transmitted records, even though the PIN appeared in the customer master. The finance team should investigate the original eTIMS transaction, make the correction through the appropriate process and retain a clear link to the original record. The stronger solution is to validate customer data and transmission status before an invoice is released.

This is where a unified ERP process matters. Sales orders, deliveries, invoices, customer master data and accounting entries should use a consistent buyer record. Reducing manual re-entry helps teams trace transactions, resolve exceptions faster and maintain a stronger audit trail.

What suppliers should do when a buyer rejects an invoice

A rejection needs a controlled correction, not a hurried reprint. We recommend that finance and operations use the following sequence.

1. Identify the exact reason for rejection

Ask the buyer whether the problem is the invoice number, buyer PIN, supplier PIN, invoice date, transmission status or another mandatory field. This matters because “no eTIMS number” can conceal different defects that require different corrections.

Use the KRA iTax invoice checker to confirm the invoice number and buyer details. The person reviewing the exception should compare the checker result with the ERP invoice, sales order and customer master record.

2. Check whether the buyer PIN was required and correctly transmitted

Where the purchaser intends to claim an expense or input tax, the buyer PIN must be on the electronic tax invoice and correctly included in the eTIMS data. A PIN printed on the invoice is insufficient if the transmitted invoice has no buyer PIN or a different PIN.

The control everyone skips is customer onboarding. Validate and approve buyer PINs in the customer master before the first taxable invoice is issued. Do not leave this to a salesperson editing a single invoice under pressure at month-end.

3. Correct the transaction without breaking the trail

KRA guidance states that suppliers should issue a proper replacement through eTIMS, transmit it correctly to KRA and include the buyer PIN where applicable. Where the original invoice requires correction, use a credit note that references the original invoice number. A debit note must also preserve the reference to the original invoice.

Do not simply create a fresh invoice with the same commercial amount and ignore the original. That approach can leave duplicate or unmatched records in the buyer’s books and in the supplier’s eTIMS trail.

4. Send the buyer verifiable evidence

Provide the corrected electronic invoice and give the buyer the details needed to check it in iTax. The buyer should be able to see the correct invoice number and buyer data in the KRA record before releasing payment or accepting the expense.

5. Record the root cause and change the control

Classify each rejection. Common categories are missing buyer PIN, incorrect buyer PIN, failed transmission, wrong supplier details and incorrect original-invoice reference. A monthly exception report gives the CFO and operations head real-time visibility of a compliance issue that otherwise appears as a collections problem.

Take a distributor supplying branches of a multi-entity Kenyan group. One branch sends its PIN by email, but the supplier invoices the group’s head-office record because that is the account selected in the ERP. The buyer rejects the invoice, since its branch expense cannot be supported with the wrong purchaser data. The supplier should credit the original where required, issue the corrected eTIMS invoice with the right buyer PIN and change the master-data rule so that each legal purchasing entity is separately approved. The mistake is common because commercial account structures and tax identities do not always match.

Who must issue eTIMS invoices, and where the exception sits

All persons carrying on business, including non-VAT businesses, must electronically generate and transmit invoices through eTIMS. Do not assume that being outside VAT registration removes the electronic-invoicing obligation.

KRA describes a buyer-initiated invoicing route for eligible small business enterprises and small-scale farmers, subject to turnover and other procedural conditions. Where that route applies, the buyer initiates the invoice through the prescribed channel and the supplier must respond within the applicable period. Eligibility should be checked against current KRA guidance before either party relies on the arrangement.

Businesses that do not qualify for buyer-initiated invoicing should maintain the appropriate supplier-side eTIMS process. Eligible businesses should still document who initiates, reviews and approves the invoice. The objective is to choose the correct regulatory route without leaving gaps in the purchase-to-payment record.

Some purchases may have specific exclusions or different treatment. The right judgement call is to identify the transaction type before demanding a supplier-issued invoice, rather than applying one rule to every purchase. This depends on the facts of the transaction and should be checked against current KRA guidance.

How Odoo supports a controlled eTIMS process

For businesses processing significant invoice volumes, disconnected invoicing tools can create avoidable duplication between sales, finance and tax records. Odoo’s official Kenya documentation describes its OSCU integration as validating, encrypting, signing, transmitting and storing invoices. The signed invoice includes the KRA invoice number, mandatory details and a unique KRA QR code. This can bring fiscalisation closer to the underlying transaction rather than treating it as a separate afterthought.

An effective implementation also defines responsibility for customer master data, credit notes, transmission failures and exception reviews. Technology supports the process; clear ownership and internal controls make it dependable. With the right design, businesses can improve invoice acceptance, strengthen their audit trail and give finance better visibility over unresolved transactions.

A SERPA-led Odoo ERP implementation can be designed around the following controls:

1.       Customer data governance: Restrict changes to buyer PINs and retain an auditable approval record. This reduces incorrect transmitted purchaser data.

2.       Invoice-release rules: Prevent release where mandatory fields are absent. This catches errors before an invoice reaches the customer.

3.       KRA status monitoring: Make transmission failures visible to finance, sales operations and IT. A failed invoice should not be treated as a completed receivable.

4.       Credit and debit note workflow: Require reference to the original invoice. This preserves the transaction trail KRA and the buyer need.

5.       Multi-entity configuration: Separate legal entities, branches and purchasing identities where their PINs differ. This is essential for groups with central procurement but local expense ownership.

Source: Odoo official Kenya fiscal localisation documentation, accessed October 2026.

Business benefits of an integrated eTIMS workflow

A well-designed integration helps reduce invoice rejections, gives finance faster visibility of transmission issues, supports more reliable collections and creates a consistent record for customers, auditors and management. The value is not merely producing compliant invoice layouts; it is building a dependable sales-to-tax process that can scale with the business.

Frequently Asked Questions

Does a supplier PIN printed on an invoice make it eTIMS compliant?

No. The invoice must be valid and electronically transmitted through eTIMS. Where the buyer intends to claim an expense or input tax, the buyer PIN must also be correctly included in the transmitted invoice data.

Why did invoice rejection become more common in 2026?

KRA began validating income and expense declarations against relevant TIMS and eTIMS, withholding-income-tax and Customs records. This has increased the importance of invoice verification before buyers approve transactions.

What should we do if the buyer PIN on the invoice is wrong?

Review the original transaction, correct the buyer data and follow the KRA correction process. Where the original invoice needs correction, issue a credit note that references the original invoice number, then issue and transmit the corrected invoice through eTIMS.

Do non-VAT businesses need eTIMS?

KRA states that persons carrying on business, including non-VAT businesses, generally must electronically generate and transmit invoices through eTIMS, subject to applicable exclusions and special procedures. Certain eligible suppliers may use buyer-initiated invoicing. Confirm the current conditions with KRA before adopting that route.

An invoice rejection is often a sign that sales, finance and tax records are not working as one controlled process. SERPA helps businesses assess their invoicing workflow, strengthen customer-data governance and configure Odoo eTIMS controls for reliable compliance. Contact SERPA for a tailored consultation and quotation based on your operating requirements.