Skip to content

Releases: navariltd/TIMS-Tevin-Type-C-Integration

v1.0.0

07 Jan 10:00
@maniamartial maniamartial
v1.0.0
c909b16
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.0.0 Latest
Latest

🚀 What's New

TIMS Tevic Type-C Integration: First Release Notes

Overview

The TIMS Tevic Type-C Integration for ERPNext enhances business operations by ensuring compliance with Kenya Revenue Authority (KRA) regulations. It facilitates real-time submission of invoices and credit notes, streamlining tax reporting and improving operational efficiency. This integration ensures accurate financial records, reduces the risk of penalties, and fosters trust with tax authorities.

Requirements

  1. Purchase Type C Middleware for Accounting

    • Obtain the middleware from Tevic, as it is essential for integration.

  2. API Server Details

    • Ensure you have the API server link and Sender ID provided by Tevic for both sandbox and production environments.

Configuration

Setting Up TIMS in ERPNext

  1. Navigate to the TIMS Settings doctype in ERPNext.
  2. Configure the following fields:
    • Company: Select the associated company.
    • Server Address: Enter the API server address from Tevic.
    • Sender ID: Provide the Sender ID from the API credentials.
    • Is Active: Check this box to enable the integration.

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 Submission:

  • Generates a CU Number and a QR Code, which are stored in the respective invoice.
  • The QR Code appears on the printed invoice, ensuring compliance with KRA regulations.

Integration Request Doctype

  • Upon submission, the transaction is recorded in the Integration Request doctype with the following details:
    • Status: Initially set to "Queue."
    • Response: Includes a URL and CU Number if successful.
    • These details are stored on the invoice, and the QR Code is generated.

Credit Notes

  • The same submission process applies for credit notes.
  • Details are sent to Tevic, and the response is recorded.

Error Handling

Failed Transactions

  • Failed transactions are recorded in the Integration Request doctype.
  • The Error field displays the reason for failure.
  • Make necessary corrections and resubmit.

Automatic Resubmission

  • A scheduled task runs every minute to resend pending invoices.
  • Failed transactions are retried until successfully transmitted to Tevic.

Print Format with QR Code

  • Once an invoice is successfully submitted:
    • The CU Number and response details are stored in the invoice.
    • A QR Code is embedded in the invoice printout.
    • This QR Code serves as proof of compliance with KRA regulations.

Key Notes

  1. Ensure that all fields in TIMS Settings are correctly configured before submitting invoices.
  2. Monitor the Integration Request doctype for failed transactions and resolve errors promptly.
  3. Keep the middleware and ERPNext updated to avoid integration issues.
Assets 2
Loading