Skip to main content
Finance → Accounting → Tax → /tax · Provider mappings → /provider-mappings Kenyan tax compliance runs through eTIMS, the Revenue Authority’s electronic tax invoice system. Nyumba Zetu submits invoices to eTIMS through the DigiTax integration and stores the certified result on the invoice.

​
How tax works on the platform

Tax is exclusive, everywhere. Tax is applied on top of the line amount: a KES 10,000 line at 16% bills KES 11,600. Inclusive tax is deliberately not supported, so no invoice on the platform can be ambiguous about whether tax is inside or outside the figure.
The tax applied to a line comes from its service type, which carries a tax class. The platform default is class D (Non-VAT); VAT-rated items are mapped explicitly. See Chart of accounts.

​
Setup

Tax submission requires a connection per business, configured under the integration setup:
Credentials are held per business. A connection copied from another entity submits that entity’s invoices under your registration. Set up each business’s connection explicitly.
Before submitting real invoices, the item catalogue must be synchronised so that every service type you bill exists on the provider side.

​
Submitting an invoice

1

Issue the invoice

Only issued invoices are submitted.
2

Send to eTIMS

Use the send action on the invoice, or the eTIMS Integration tab. A confirmation dialog states what will be submitted.
3

Watch the status

The invoice’s eTIMS tab shows the submission status with live updates and an audit trail of every attempt.
4

Read the certified receipt

On acceptance the invoice shows KRA eTIMS Certified with the QR code, receipt details and fiscal identifiers, rendered inline on the invoice.

​
Submission statuses

Submissions move through queued → submitted → accepted or failed, with the attempt count and the reason on failure. The eTIMS tab shows why it failed rather than a bare error code.

​
Provider mappings

/provider-mappings is the cross-invoice view of integration state: every submission, its status, provider, document type, correlation and idempotency keys, attempts, and the failure reason. From here you can:
  • filter by provider and status to find everything that failed;
  • retry failed submissions, with background processing hints so you know a retry is in flight;
  • drill into an individual mapping’s timeline and payload.
A per-invoice mappings tab gives the same detail for one document.

​
Available operations

The integration supports the operations eTIMS exposes, including: Operations can also be run individually from the manual capability runner for diagnosis, with a payload builder and the last operation response shown.

​
Re-filing

Re-file resubmits an invoice that eTIMS has already accepted.
Re-filing an accepted invoice reports it to KRA a second time, which double-reports the VAT. The platform has no credit-note-to-KRA path yet, so this is not self-correcting. Use re-file only when you have confirmed the first submission is genuinely not on record with KRA.
The same limitation applies to crediting: raising a credit note against an accepted invoice corrects your books but does not correct the KRA filing. Coordinate with whoever owns tax compliance before crediting a certified invoice. See Adjustments.

​
Tax schedule and withholding

The tax module also covers the tax schedule and withholding tax surfaces, for tracking what is due and what has been withheld on payments.

​
Monthly tax routine

1

Clear the failed queue

Filter provider mappings by failed status and resolve each one. Most failures are tax-class or item-mapping issues, not connectivity.
2

Confirm every issued invoice was submitted

An invoice with no submission is an unreported sale.
3

Reconcile the sales summary

Compare the provider’s sales summary against your revenue for the period.
4

Review credits

Any credit note against a certified invoice needs a decision on how it is handled with KRA.
5

Then close the period

See Accounting periods.

​
Common problems