---
title: "Trouble Shooting Guides"
space: "TIMS Tevin Type-C Integration"
url: "https://docs.navari.co.ke/tims-tevin/trouble-shooting-guides"
updated: "2026-05-26"
---

## Troubleshooting Guide

### Integration Is Installed But Invoices Are Not Being Submitted

**Checklist:**

1. Is **Is Active** checked in TIMS Settings?
2. Is the correct **Company** selected in TIMS Settings?
3. Is the **Server Address** correct and reachable from the server? (`curl {server_address}` from the terminal)
4. Is the **Sender ID** correct?
5. Is the bench **scheduler running**? (`bench scheduler status`)
6. Is the **background worker** running? Check `supervisor` or `systemd` logs

### QR Code Is Not Appearing on the Print Format

**Checklist:**

1. Check the Sales Invoice record: is there a value in the CU Number field and the QR code field?
2. If yes, the print format template may not be referencing these fields: update the Jinja2 template
3. If no, the submission may have failed: check Integration Request for this invoice
4. Submitted Invoices Are Showing Status "Queued" Indefinitely

This almost always means the **scheduler is not running**. Run:

```sh
bench --site {sitename} scheduler status
bench restart

```



### Duplicate CU Numbers

This should not happen under normal operation. If you suspect it:

1. Do not cancel and resubmit invoices unless Tevin confirms the original was not registered
2. Contact Tevin support with the invoice number and Integration Request details

### Testing in Sandbox Before Going Live

Always use the **sandbox Server Address** during initial setup and UAT. Run through the full workflow:

1. Configure TIMS Settings with sandbox credentials
2. Create and submit a test Sales Invoice
3. Confirm the Integration Request shows "Completed"
4. Confirm the CU Number and QR code appear on the invoice
5. Print the invoice and scan the QR code to verify

Only after successful end-to-end sandbox testing should you switch to the **production Server Address**.