---
title: "Error Handling & Failure Recovery"
space: "TIMs INCOTEX Intergration"
url: "https://docs.navari.co.ke/tims-incotex/error-handling-failure-recovery"
updated: "2026-06-09"
---

The integration is built with resilience in mind:



**Submission Failure on** `on_submit` If INCOTEX is unreachable or returns an error at invoice submission time, ERPNext does not block the posting of the invoice. The invoice is still submitted locally and the failure reason is captured in the **Response Description** field on the invoice. The `is_filed` checkbox remains unchecked, which flags it for follow-up.



**Scheduler-Based Retry** The background scheduler periodically sweeps for invoices with `is_filed = 0` and retries submission automatically.



**Manual Retry** Users can always trigger a manual re-submission using the **ETIMs Action → Submit E-Invoice** button.



**Device Health Check** The **Health Check** button in TIMs INCOTEX Settings allows administrators to confirm the INCOTEX device is online before troubleshooting individual invoice failures.



**Tax ID Validation (v1.0.2)** As of version 1.0.2, the system validates the customer's Tax ID (PIN) before submission to INCOTEX. This prevents submissions that would be rejected by KRA due to a missing or invalid customer PIN. Additionally, the system no longer triggers a `modified` bump on the invoice record when filing, keeping audit trails clean.