| AWRA OpsHub

 Search
Advanced Certificate on pass

KRA eTIMS E-Invoicing

Connect your own KRA PIN, initialise your eTIMS device, and file compliant tax invoices — manually or automatically — with the receipt signature and QR on every invoice.

3 lessons 40 min 5-question assessment 70% to pass
Take the assessment

What you’ll learn

  • Explain how eTIMS works in AWRA (per-taxpayer, device initialisation)
  • Set up credentials and initialise the device in sandbox, then production
  • File invoices manually and via the auto-file-on-issue toggle
  • Understand how the receipt signature and QR make an invoice compliant

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Reading 13 min

How eTIMS works in AWRA

KRA eTIMS is Kenya's electronic tax invoicing system. Integration is per-taxpayer: every business files under its own KRA PIN, so in AWRA each tenant enters their own PIN, branch ID and a device serial number. AWRA submits invoices to KRA on your behalf using your registration — it is never anyone else's.

Before you can file, you initialise the device. AWRA sends your PIN, branch and serial to KRA and receives back a communication key (cmcKey) plus your device identifiers and taxpayer name. That key authorises every later call. Initialisation happens once per device; after that the connector shows as connected.

There are two environments, chosen per tenant. Sandbox is for testing against KRA's test service; Production files real, legally binding invoices. You always validate in sandbox first, then switch to production when you are ready.

Key takeaways

  • eTIMS is per-taxpayer — each tenant uses their own KRA PIN, branch and device serial.
  • Initialising the device exchanges your credentials for a communication key.
  • Sandbox is for testing; Production files real invoices.
  • AWRA files under your registration, never someone else's.
02
Lesson 2 of 3 Workshop 14 min

Filing invoices: manual and automatic

Once connected, an invoice can reach KRA two ways. Manually: each customer invoice has a "File to eTIMS" button (greyed out until eTIMS is connected). Automatically: turn on "auto-file on issue" in the connector settings, and every new invoice is filed the moment it is issued — no click.

The two paths are reconciled so an invoice is never filed twice. Both dispatch the same background job; the job is unique per invoice (so a manual click and the auto-file cannot run at once) and it skips any invoice already marked filed. You can safely have auto-file on and still use the button — the button just no-ops if it is already done.

Filing runs on the queue and never blocks invoice creation. If KRA rejects a submission, the invoice is flagged as failed with the error message and the job retries with backoff; the invoice itself is still created normally.

Key takeaways

  • Manual "File to eTIMS" button per invoice; optional auto-file on issue.
  • Both use one unique, idempotent job — an invoice is never filed twice.
  • Filing is queued and never blocks creating the invoice.
  • A rejected filing is flagged with the error and retried; the invoice still exists.
03
Lesson 3 of 3 Practice 13 min

The signed receipt, QR, and going live

When KRA accepts an invoice it returns a signed receipt — a receipt number, a control-unit signature, internal data, and QR content. AWRA stores these on the invoice and prints a compliant KRA eTIMS block, including the scannable QR, on the invoice PDF. That signature and QR are what make the document a legally compliant tax invoice.

Go live deliberately. Initialise and test in Sandbox until a test invoice comes back accepted; only then switch the environment to Production. In production a test invoice is a real filing, so treat it accordingly. Changing the PIN, branch, serial or environment requires re-initialising the device.

If filing fails, read the exact resultMsg KRA returns — codes are specific (e.g. an unregistered device). Most first-time issues are that the PIN/branch/serial are not yet enrolled for eTIMS on the KRA side, which is fixed on the KRA portal, not in AWRA.

Key takeaways

  • KRA returns a receipt number, signature, internal data and QR on success.
  • AWRA stores these and prints the QR + signature on the invoice PDF for compliance.
  • Validate in Sandbox, then switch to Production; changing credentials means re-initialising.
  • Read the exact KRA error message — many issues are PIN/device enrolment on KRA's side.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

More in this path

Workflow Builder Basics

Open course

Connectors Directory Basics

Open course

Google Sheets Register Export

Open course

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center