---
title: "Configuration"
space: "TIMS Tevin Type-C Integration"
url: "https://docs.navari.co.ke/tims-tevin/configuration"
updated: "2026-05-26"
---

### TIMS Settings Doctype

Once installed, you must configure the integration before it will function. All configuration lives in a single doctype: **TIMS Settings**.



**Navigation:** `Search Bar → TIMS Settings` or `ERPNext → Settings → TIMS Settings`

![](/files/imagef72c8d.png)
*TIMS Settings*

#### Fields Reference


| Field              | Type           | Description                                                                                                                                                                           |
| ------------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Company**        | Link (Company) | The ERPNext company entity for which this integration is active. If you run multiple companies, each may have its own TIMS Settings record.                                           |
| **Server Address** | Data           | The full API URL provided by Tevin. Use the **sandbox URL** during testing and switch to **production** when going live. Example: `https://api.tevin.eu/v1/`                          |
| **Sender ID**      | Data           | Your unique Sender ID from Tevin. This is sent as part of every API request header to authenticate your submissions.                                                                  |
| **Is Active**      | Check          | Toggle to enable or disable the integration. Set to **checked/active** for the integration to submit invoices. If unchecked, no submissions will occur even when invoices are posted. |


#### Configuration Best Practices

- **Always test with the sandbox URL first.** Post a few test invoices, confirm the CU numbers and QR codes appear, then switch to the production URL.
- **Do not share your Sender ID.** Treat it like an API key as it is tied to your KRA registration and Tevin account.
- **One TIMS Settings per company.** In multi-company ERPNext setups, each legal entity will have its own Tevin credentials. Create separate TIMS Settings records for each.
- **Deactivate during migrations.** If you are migrating data (bulk-importing historical invoices), temporarily uncheck **Is Active** to avoid submitting historical invoices to KRA. Re-enable after migration.