Why reconciliation gets harder with each branch
With one till, reconciliation is straightforward: you check that day's sales against that day's eTIMS filings on one system. Add a second branch and you are now checking two systems, possibly with different staff, different discipline around compliance, and sometimes different POS setups entirely.
The real risk is not usually outright non-compliance at a branch; it is a quieter gap, like a branch whose device was offline for a stretch and did not sync, or a till that was set up slightly differently and misses a tax code. Multiply that across five or ten branches and small gaps compound into a real reconciliation headache at month end.
Want to see it running in your own business first?
Sign UpHow to reconcile eTIMS across branches
The practical checklist for a growing, multi-location business.
- 1
Use one system across branches where possible
A single POS platform used consistently at every branch removes the variable of different setups behaving differently.
- 2
Check for offline gaps per branch
Confirm each branch's sales synced and filed correctly, especially after a known outage or connectivity issue at that location.
- 3
Compare branch-level totals to the consolidated total
A mismatch between what one branch reports and what shows in the combined view is the first sign something needs investigating.
- 4
Set a regular reconciliation cadence, not just at month end
Catching a gap weekly is far easier to fix than discovering it during a VAT return three months later.
- 5
Assign clear ownership per branch
Someone at each location should be responsible for confirming their branch's daily filing, even if head office does the final consolidated check.
Mistakes to avoid
Running different POS setups per branch
Inconsistent systems make it harder to spot when one branch is configured differently and quietly filing incorrectly.
Only checking reconciliation at month end
A gap that ran for weeks is much harder to trace back than one caught within days.
No single consolidated view
Manually combining separate branch spreadsheets is slow and error-prone, and it delays noticing a real problem.
Assuming head office would notice a branch going offline
A branch can operate normally to staff and customers while quietly failing to sync in the background.
A worked example
A retail chain running four branches on different POS setups discovered during a VAT return that one branch had a stretch of unsynced offline sales going back several weeks.
Moving all four branches onto one consolidated system with a single dashboard meant head office could see each branch's filing status daily, rather than discovering a gap months after it started.
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
Veira gives multi-branch businesses one consolidated dashboard across every till and location, so every branch's eTIMS filing status is visible in one place rather than reconstructed from separate spreadsheets.
Each sale at every branch issues a compliant invoice automatically and keeps working offline, syncing once the connection returns, so a branch-level gap is visible quickly rather than discovered later. See how Veira works for multi-branch businesses, or book a free demo.
Frequently asked questions
What makes eTIMS reconciliation harder with multiple branches?
How often should a multi-branch business reconcile eTIMS?
Does using one POS system across branches actually help?
Can Veira show eTIMS status across all my branches at once?
Should each branch have its own eTIMS setup or share one?
How do I find which branch is causing a discrepancy?
Multi-branch eTIMS reconciliation is really about visibility: the more branches you run, the more a consolidated, real-time view matters over reconciling separate spreadsheets after the fact. Veira gives every branch one dashboard, from KES 2,999 a month. See how Veira works, or book a free demo. For the login process itself, see [Veira's KRA eTIMS login guide](/blog/kra-etims-login).
Need help, or want to talk it through first? Chat with us on WhatsApp