Tims Tevin Type C Integration
ERPNext integration Tevin Type-C TIMS device
- Author: navariltd
- Repository: https://github.com/navariltd/TIMS-Tevin-Type-C-Integration
- GitHub stars: 1
- Forks: 1
- License: AGPL-3.0
- Category: Integrations
- Maintenance: Actively Maintained
- Frappe versions: develop, v15
Install Tims Tevin Type C Integration
bench get-app https://github.com/navariltd/TIMS-Tevin-Type-C-Integration
Add the Frappe Gems badge to your README
Maintain Tims Tevin Type C Integration? Paste this into your README:
[](https://frappegems.com/gems/apps/navariltd/TIMS-Tevin-Type-C-Integration)
About Tims Tevin Type C Integration
TIMS Tevic Type-C Integration
Integrating TIMS Tevic Type C with ERPNext
TIMS Tevic Type C app enhances business operations by ensuring compliance with Kenya Revenue Authority (KRA) regulations through real-time submission of invoices and credit notes. This integration streamlines tax reporting, improves operational efficiency, and ensures accurate financial records, reducing the risk of penalties while fostering trust with tax authorities.
Requirements
Purchase the Type C Middleware for Accounting
The middleware is essential for this integration and can be obtained from Tevic.API Server Details
Ensure you have the API server link and senderID provided by Tevic upon purchasing the middleware(Both fir sandbox and production).
Configuration
Setup TIMS Settings in ERPNext
Navigate to the TIMS Settings doctype in ERPNext and fill out the following fields:- Company: Select the company to associate with the integration.
- Server Address: Enter the API server address provided by Tevic.
- Sender ID: Enter the Sender ID from the API credentials.
- Is Active: Check this box to activate the integration.
These details are critical for initializing the connection to the TIMS device.
Invoice Submission Process
Automatic Submission to Tevic
- When an invoice is submitted in ERPNext, the system automatically sends its details to Tevic.
The payload (invoice data) and headers are prepared according to Tevic's requirements.
Successful response will create cu number and QR code on the invoice
Integration Request Doctype
- Upon submission, the transaction is recorded in the Integration Request doctype:
- Status: Initially set to "Queue."
- Response: If successful, the status changes to "Completed," and the response includes:
- A URL
- CU Number
- These details are stored on the respective invoice, and a QR code is generated.
- The QR code will appear on the invoice printout provided to the customer.
- Upon submission, the transaction is recorded in the Integration Request doctype:
Credit Notes
- The same process applies when submitting a credit note. The details are sent to Tevic, and the response is recorded.
Error Handling
Failed Transactions
- If a transaction fails, check the Integration Request doctype:
- The Error field will display the reason for failure.
- Make the necessary changes and attempt resubmission.
- If a transaction fails, check the Integration Request doctype:
Automatic Resubmission
- A scheduled task runs every minute to resend pending invoices.
- Invoices that failed to send are automatically retried until successfully transmitted to Tevic.
Print Format with QR Code
Once an invoice is successfully submitted:
- The CU Number and other response details are stored in the invoice.
- A QR code is generated and embedded in the invoice printout.
- The QR code serves as proof of compliance with KRA requirements and is presented to customers.
Key Notes
- Ensure that all fields in TIMS Settings are correctly configured before submitting invoices.
- Monitor the Integration Request doctype for any failed transactions and resolve errors promptly.
- Keep the middleware and ERPNext updated to avoid integration issues.
This setup ensures smooth and compliant submission of invoices and credit notes to Tevic, maintaining real-time communication with KRA.
Manual/Self-Hosted Installation
Once bench and ERPNext are installed, add Tevic Type C app to your bench by running:
$ bench get-app --branch {branch-name} https://github.com/navariltd/TIMS-Tevin-Type-C-Integration.git
Replace {branch-name} with the desired branch name from the repository. Ensure compatibility with your installed versions of Frappe and ERPNext.
- Install the tims-tevin-typec-integration app on your site by running:
$ bench --site {sitename} install-app tims_tevic_typec_integration
Replace {sitename} with the name of your site.
Frappe Cloud Installation
Sign up with Frappe Cloud.
Setup a bench.
Create a new site.
Choose Frappe Version-15 or above, and select ERPNext, and TIMS Tevic Type-C Integration from the available Apps to Install.
Within minutes, the site will be up and running with a fresh install, ready to explore the app's simple and impressive features.
If assistance is needed to get started, reach out for consultation and support from: Navari.
Troubleshooting
If you encounter any errors during installation, refer to the error messages for guidance.
Ensure all dependencies are correctly installed and compatible with the versions specified.
License
agpl-3.0
Related Integrations apps for Frappe & ERPNext
- Insights — Open Source Business Intelligence Tool
- Raven — Simple, open source team messaging platform
- Frappe Whatsapp — WhatsApp cloud integration for frappe
- Frappe Assistant Core — Infrastructure that connects LLMs to ERPNext. Frappe Assistant Core works with the Model Context Protocol (MCP) to expose ERPNext functionality to any compatible Language Model
- Biometric Attendance Sync Tool — A simple tool for syncing Biometric Attendance data with your ERPNext server
- Frappe React Sdk — React hooks for Frappe
- Frappe Js Sdk — TypeScript/JavaScript library for Frappe REST API
- Mcp — Frappe MCP allows Frappe apps to function as MCP servers