Error Handling & Submission

Error Handling & Resubmission

Failures happen. Common causes include:

Temporary network interruption between your server and Tevin's API
Tevin API server downtime or maintenance
Invalid or missing fields in the invoice payload (e.g., missing customer PIN for B2B invoices)
Expired or incorrect Sender ID
KRA TIMS system unavailability

Go to Integration Request and find the failed record
Read the Error field: it will contain the HTTP status code and error message from Tevin
Correct the root cause (fix the invoice, update TIMS Settings, resolve network issues)
The scheduled task will retry automatically — no manual resubmission button is needed

If you need to force an immediate retry rather than waiting for the scheduler:

bench --site {sitename} execute tims_tevic_typec_integration.tasks.retry_failed_submissions

Replace the function path with the actual module path from the app's codebase if it differs.

Error	Likely Cause	Fix
`401 Unauthorized`	Incorrect Sender ID or Server Address	Verify TIMS Settings fields; contact Tevin to confirm credentials
`422 Unprocessable Entity`	Invalid payload (missing required fields)	Check the Request Data field in Integration Request; ensure all invoice fields are populated
`Connection refused` / timeout	Server can't reach Tevin API	Check outbound internet access from your server; verify the Server Address URL is correct
`500 Internal Server Error`	Tevin or KRA TIMS server error	Wait and let the scheduler retry; check Tevin's status page or contact their support
`Invoice already submitted`	Duplicate submission attempt	The invoice may have already been registered; check with Tevin whether a CU number exists for it