eTIMS

eTIMS Bulk Upload in Kenya: Sending Many Invoices at Once (2026)

K By Kev 23 June 2026 8 min read
Share
eTIMS guide

eTIMS bulk upload is a question for any Kenyan business or developer connecting their own systems to KRA eTIMS. eTIMS bulk upload means submitting many invoices to KRA together rather than one at a time, useful for catching up records or high-volume billing. Whether and how it is supported depends on KRA's current approach and your integration, so confirm with KRA. Each invoice must still be individually compliant. This guide explains the concepts and the practical approach, what to confirm in KRA's official documentation, and when you can skip the build entirely with compliant software. Technical specifics change, so treat KRA's official eTIMS documentation as the source of truth.

Key takeaways
  • Bulk upload submits many invoices together rather than one at a time
  • Support and limits depend on KRA's current approach; confirm with KRA or your provider
  • Each invoice is validated individually and must be compliant
  • Resubmit only failed invoices, never the whole batch, to avoid double-counting
On this page
  1. What bulk upload means for eTIMS
  2. How to approach it
  3. What to check before you build
  4. A wholesaler clears a backlog
  5. When you can skip the integration
  6. Frequently asked questions

What bulk upload means for eTIMS

Businesses with high volume, or those catching up a backlog, often ask whether they can upload many invoices to eTIMS at once rather than issuing them one by one. The concept is straightforward: submit a batch together. The detail of whether, and how, this is supported depends on KRA's current approach and the integration or tool you use.

The constant, whatever the mechanism, is that each invoice in a batch must still be individually compliant, with the buyer PIN where needed and the correct tax treatment, and each gets validated. Bulk upload is about efficiency, not relaxing the rules. Because the supported methods and limits change, confirm the current bulk or batch approach with KRA or your provider rather than assuming a particular method exists.

The cheapest eTIMS integration is often the one you do not have to build, certify and maintain yourself.

How to approach it

A practical path. Confirm exact technical details against KRA's official documentation.

  1. 1

    Confirm the supported approach

    Check with KRA or your provider how batch or bulk submission is currently supported for your integration, since methods and limits change.

  2. 2

    Make each invoice individually compliant

    Ensure every invoice in the batch has the correct tax treatment and buyer PIN, since each is validated on its own.

  3. 3

    Submit and read the results

    Submit the batch and read the validation results per invoice, since some may pass while others need correction.

  4. 4

    Correct and resubmit failures only

    Fix and resubmit only the invoices that failed, rather than re-sending the whole batch, to avoid double-counting.

What to check before you build

Assuming bulk relaxes compliance

Each invoice in a batch is validated individually. Volume does not relax the rules; every invoice must be compliant.

Re-sending a whole batch to fix a few

Resubmit only the failed invoices. Re-sending the whole batch risks double-counting the ones that passed.

Assuming a method exists without checking

Supported batch methods and limits change. Confirm the current approach with KRA or your provider.

A wholesaler clears a backlog

Worked example

A wholesaler in Mombasa needed to record a backlog of invoices and wanted to avoid entering them one by one.

They confirmed the supported batch approach with their provider, made sure each invoice carried the correct tax treatment and buyer PIN, submitted the batch, and read the per-invoice results.

Most validated immediately; they corrected and resubmitted only the few that failed, clearing the backlog efficiently without double-counting anything.

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.

When you can skip the integration

The biggest decision here is whether you need to build an integration at all. Veira is already a compliant eTIMS system: it issues compliant KRA invoices automatically, applies the right tax treatment, captures the buyer PIN, transmits to KRA, and works offline. For many businesses that removes the need to build, certify and maintain a custom integration yourself.

If you do run an ERP or a custom stack, weigh the cost of building and maintaining an integration against running point of sale and invoicing on Veira and reconciling. Veira runs from KES 2,999 a month with a free terminal and a 30-day money-back guarantee. See how Veira works, or book a free demo to talk through your setup.

Frequently asked questions

Can I bulk upload invoices to eTIMS?
Submitting many invoices together is possible depending on KRA's current approach and your integration or tool. Confirm the supported method and limits with KRA or your provider. Each invoice must still be individually compliant and is validated on its own.
Does bulk upload change compliance requirements?
No. Each invoice in a batch is validated individually and must carry the correct tax treatment and buyer PIN. Bulk upload is about efficiency, not relaxing the rules.
What if some invoices in a batch fail?
Read the per-invoice results, then correct and resubmit only the failed ones. Do not re-send the whole batch, which would double-count the invoices that passed.
How does Veira handle high volume?
Veira issues and transmits compliant invoices at volume as you trade, and records offline and syncs when the connection returns, so you avoid manual bulk uploads in the first place.
Do I have to build my own eTIMS integration?
No. Compliant software like Veira already issues and transmits compliant eTIMS invoices, so many businesses do not need to build, certify and maintain a custom integration. Build only if your stack genuinely requires it.
Where is the authoritative eTIMS technical spec?
KRA's official eTIMS API documentation is the source of truth for endpoints, payloads, control units and requirements. Specifics change, so build against the current official documentation, not third-party summaries.

eTIMS bulk upload comes down to the concepts above plus KRA's official documentation for the exact details, and for many businesses the simplest path is compliant software that handles it for you. See how Veira works, or book a free demo. Always build against KRA's current official eTIMS documentation.

For more eTIMS guides and compliance resources, visit our free resource site.

Terms explained

Keep reading

See all eTIMS guides

Veira for your business

Browse Veira by business type