What the eTIMS sandbox is for
The sandbox is a test version of eTIMS. It behaves like the real system, so you can authenticate, create invoices, sign and transmit them, and receive control numbers, but nothing you do there affects your live tax records.
That makes it the safe place to find and fix problems: a wrong tax mapping, a failed authentication, or a credit note that will not link. You want to discover those in testing, not during a real sale.
What to test in the sandbox
Cover the real situations your business will hit, not just the happy path:
- 1
Authentication and connection
Confirm your system authenticates and stays connected through your control unit.
- 2
A standard invoice end to end
Create, sign, transmit and receive a control number for a normal sale, then check it carries the right details.
- 3
Different tax types
Test standard-rated, zero-rated and exempt items so each is treated correctly.
- 4
Credit notes and corrections
Issue a credit note against a test invoice to confirm returns and corrections work.
- 5
Offline then sync
If your system sells offline, test recording offline and syncing so held invoices transmit correctly when reconnected.
Mistakes to avoid
Testing only the happy path
A single clean invoice is not enough. Test tax types, credit notes and offline scenarios, because those are where real problems hide.
Going live with known sandbox failures
If something fails in testing, it will fail in production. Fix it before go-live.
Not testing reconciliation
Confirm control numbers come back and records match, so you know compliance is real.
Skipping the sandbox entirely
Going straight to live to save time risks failed invoices during trading. The sandbox exists to prevent exactly that.
A worked example
A team integrating a POS tested one clean invoice in the sandbox, saw it work, and went live, only to hit failures on zero-rated items and credit notes.
They went back to the sandbox, tested every tax type and a credit note, found and fixed the mappings, and re-launched. The second go-live was clean because the edge cases had been covered in testing.
The lesson: test the situations your business actually meets, not just the simplest case, before going live.
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.
How Veira helps
With Veira, this validation is handled as part of onboarding, so your invoices are tested to sign and transmit correctly before you start trading, without you running a sandbox yourself.
You get a clean go-live without managing the test environment. See how Veira works or book a demo.