What the Duplicate Invoice Error Actually Means
KRA’s eTIMS platform keys every invoice on a composite identifier: (seller KRA PIN + invoice number). If the platform receives a new invoice whose (PIN, number) pair already exists in its database, it rejects the new invoice with one of these error messages:
ERR_DUPLICATE_INVOICE_NUMBER- same invoice number already used on this PINERR_DUPLICATE_COUPON- same device coupon number already transmitted (hardware OSCU/VSCU only)ERR_INVOICE_EXISTS- generic duplicate error when the platform’s deduplication service fires- “Invoice already transmitted” - informal message shown on eTIMS Client when the same invoice is sent twice
Each of these errors means the same thing in practice: KRA’s system thinks you are re-issuing an existing invoice, and to protect against double-counting sales (which would inflate your VAT payable), it refuses to accept the new one.
Not the same as “invoice rejected”. The duplicate error is a specific rejection reason. For other rejection reasons (invalid PIN, stock mismatch, missing fields), see our eTIMS invoice rejected guide.
Why Duplicates Happen - Five Root Causes
Two devices on the same KRA PIN, no prefix
The single biggest cause. A business has two OSCU devices (one in Nairobi, one in Mombasa) but only one KRA PIN. Both devices start their invoice numbering at 0001 and increment independently. When Mombasa issues invoice 0042 and Nairobi has already issued invoice 0042, KRA sees a duplicate on the same PIN and rejects one of them.
Same device re-issued an invoice after a firmware reset
If the device firmware is reinstalled (by a technician, after a glitch, or after a software update), the internal coupon counter resets to 0. The next invoice uses coupon 0001 - which KRA already has. Until the counter is re-initialised to the correct next number, every invoice triggers a duplicate error.
Same invoice transmitted twice by accident
eTIMS Client sometimes shows 'transmission failed' even when the invoice was actually uploaded - due to a network glitch or a timeout. If the user clicks 'Retry' instead of 'Check Status', the same invoice is sent again, and KRA rejects the second transmission as a duplicate.
Manual invoice was transmitted and then re-entered in eTIMS Client
You issued a manual invoice (e.g., during an eTIMS outage) and transmitted it via eTIMS Lite. Later, the eTIMS Client comes back online and you re-enter the same invoice number in the Client. KRA rejects it as a duplicate of the eTIMS Lite version.
Wrong date / clock on the device
Rare but real: if the device clock is wrong (e.g., set to 2024 instead of 2026), some versions of eTIMS use the date as part of the invoice key. If your old invoices from 2024 are still on KRA's database, the new 2024-dated invoice collides with them. Check the device clock against network time weekly.
How to Fix a Duplicate Invoice Error (Step by Step)
The fix depends on whether the invoice actually needs to be issued, or whether it is already on KRA’s servers and you can ignore the duplicate error.
- 01
Check if the invoice is already on KRA's side
Log into eTIMS Lite (etims.kra.go.ke), go to Transaction History, search for the invoice number. If it appears, the duplicate error is harmless - the invoice is already transmitted. You do not need to do anything. Mark it as 'transmitted' in your local records and move on.
- 02
If the invoice is NOT on KRA, delete the local copy
On eTIMS Client, find the stuck invoice in the local queue. Right-click or long-press and select 'Delete'. If the device is an OSCU, you may need to navigate the device menu - check the device manual for 'delete draft'. This removes the local copy that is causing the duplicate error.
- 03
Generate a new invoice with the next sequential number
Do NOT reuse the same invoice number. Generate a new invoice with the next number in your sequence (e.g., if invoice 0042 had the duplicate error, issue invoice 0043 instead). Tell the customer the invoice number has changed - send a new invoice copy with the new number.
- 04
Transmit and verify
Transmit the new invoice normally. Within 5 minutes, check eTIMS Lite > Transaction History - the new invoice should appear as 'Confirmed' with a server confirmation code. If it still shows a duplicate error, the issue is on KRA's side - call 020 499 9999.
Never reuse an invoice number, even after a duplicate error
Some businesses try to “clear” a duplicate error by reusing the number again with a different invoice content. This is illegal under the VAT Regulations - every invoice must have a unique sequential number. Reusing numbers, even accidentally, creates audit-trail gaps that KRA flags during a VAT audit.
Multi-Device Invoice Prefixing - The Permanent Fix
If you operate more than one eTIMS device (or one device + eTIMS Lite) on the same KRA PIN, you must use a unique invoice number prefix on each device so coupons never collide.
| Device / Branch | Prefix | Example invoice numbers |
|---|---|---|
| Nairobi shop - OSCU 1 | NBO- | NBO-00001, NBO-00002, NBO-00003 |
| Mombasa shop - OSCU 2 | MSA- | MSA-00001, MSA-00002, MSA-00003 |
| Online sales - eTIMS Lite | WEB- | WEB-00001, WEB-00002, WEB-00003 |
| Mobile van - eTIMS Client on phone | VAN- | VAN-00001, VAN-00002, VAN-00003 |
To set a prefix on eTIMS Client: Settings → Invoice Settings → Numbering → Custom Prefix. To set a prefix on a hardware OSCU: call your device supplier - they configure it during the next firmware update or remote session. Prefixes can be 3-6 alphanumeric characters.
Once prefixes are set, each device maintains its own independent sequence - NBO-00123 and MSA-00123 can coexist without colliding because the prefix makes the full invoice number unique. This eliminates 90%+ of duplicate errors in multi-device setups.
Monthly Duplicate Audit - Before Filing Your VAT Return
As a defensive habit, run a quick duplicate audit on the 18th-19th of every month, before you file your VAT return on the 20th. This catches any duplicates KRA may have accidentally accepted (rare, but happens during outages).
- 01
Download your transaction history
On eTIMS Lite, go to Transaction History, select the past month, and download as CSV. The file has every invoice KRA received from your PIN in that period - invoice number, date, amount, status.
- 02
Sort by invoice number and look for repeats
Open the CSV in Excel or Google Sheets. Sort by the 'Invoice Number' column. Any number that appears more than once is a duplicate that KRA accidentally accepted. Note these invoice numbers.
- 03
Compare against your local records
Check your own sales records (POS system, paper invoice book, or eTIMS Client local exports). Each duplicate in KRA's record should map to a single real-world sale - if it does, you may have been double-counted for VAT. If you cannot match it to a real sale, it is a phantom duplicate and needs KRA correction.
- 04
If you find real duplicates, contact KRA before filing
Call 020 499 9999 and explain. KRA can merge or delete the duplicate from their side before you file. Filing with known duplicates inflates your VAT payable and is hard to reverse later.
Related: This monthly audit is part of our monthly VAT filing service. We do it automatically for every client before each VAT return is submitted - see our monthly VAT filing service for the full checklist.
Frequently Asked Questions
What does the eTIMS 'duplicate invoice' error mean?
The error means KRA's eTIMS platform already has an invoice in its database with the same invoice number (or the same device coupon number) attributed to your KRA PIN. KRA rejects the new invoice to prevent double-counting sales. The duplicate can be from your own device (you re-issued an invoice using the same number) or from a different device registered to your PIN that already issued a coupon with that number.
Why does my eTIMS device keep generating duplicate invoice numbers?
Three common causes: (1) you have multiple devices or eTIMS Client installations on the same KRA PIN and they are running the same invoice sequence; (2) your device was deregistered and re-registered - the new registration reset the coupon counter; (3) the device clock is wrong and dates an invoice with the same date-and-sequence as an existing one. The fix is to give each device a unique invoice prefix (e.g., NBI01-001, NBI02-001) so coupons never collide.
How do I fix a duplicate invoice error in eTIMS?
First, check the invoice history on the device - if the invoice was already issued successfully, do NOT re-issue it. If the duplicate is because a previous attempt failed mid-transmission but still saved locally, delete the local copy and re-transmit with a new invoice number. If the duplicate is from a different device, change the invoice prefix on the second device so future numbers do not collide. Never delete an invoice that KRA has already confirmed - that creates a gap in your records.
What is a 'duplicate coupon' error specifically?
A 'duplicate coupon' error is specific to OSCU/VSCU hardware devices. Each device has an internal counter that generates a unique 'coupon number' for every invoice issued. If the coupon counter is reset (e.g., after a firmware reinstall or factory reset), the device starts reusing coupon numbers from the beginning - which KRA already has in its database. The fix is to have the supplier re-initialise the coupon counter to the correct next number, not zero.
Will KRA penalise me for duplicate invoices?
Duplicate invoices that are rejected do not appear on KRA's record - they are simply not transmitted. So no penalty applies to rejected duplicates. However, if a duplicate is accidentally accepted (rare - happens when KRA's duplicate-check service is briefly down), you may be double-counted for VAT on that sale. Run a duplicate-check on eTIMS Lite > Transaction History before filing your monthly VAT return.
Can I issue the same invoice number from two different devices?
Technically no - KRA's platform keys invoices on (KRA PIN + invoice number). Two devices on the same PIN must use different invoice number sequences. The simplest approach is to use a 2-3 letter branch prefix (NBO-001, MSA-001, KSM-001) so each branch's invoices are unique. If you invoice from the same device but in different modes (online vs offline), the device handles this for you - just trust the device's auto-numbering.