Regularly update your applications

Oct 13, 2025 by magicalceylontours.com 134 views

Introduction

In this article, we will delve into the IMS error, a common issue encountered by users of the India Compliance module in ERPNext. The error is characterized by a TypeError, which occurs when the system attempts to perform a subtraction operation between two values of different types. We will analyze the error message, identify the root cause, and provide a step-by-step solution to resolve the issue.

Information about Bug

App Versions

The following are the versions of the applications involved in this issue:

{
	"erpnext": "15.54.3",
	"frappe": "15.57.2",
	"frappeauth_app": "0.0.1",
	"goyalapp": "0.0.1",
	"hrms": "15.41.0",
	"india_compliance": "15.16.3",
	"payments": "0.0.1"
}

Route

The route involved in this issue is:

Form/GST Invoice Management System/GST Invoice Management System

Traceback

The traceback provides a detailed sequence of events leading to the error:

Traceback (most recent call last):
  File "apps/frappe/frappe/app.py", line 115, in application
    response = frappe.api.handle(request)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/api/__init__.py", line 49, in handle
    data = endpoint(**arguments)
           ^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/api/v1.py", line 36, in handle_rpc_call
    return frappe.handler.handle()
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/handler.py", line 51, in handle
    data = execute_cmd(cmd)
           ^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/handler.py", line 87, in execute_cmd
    return frappe.call(method, **frappe.form_dict)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/__init__.py", line 1734, in call
    return fn(*args, **newargs)
           ^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/handler.py", line 337, in run_doc_method
    response = doc.run_method(method)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/model/document.py", line 1007, in run_method
    out = Document.hook(fn)(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/model/document.py", line 1367, in composer
    return composed(self, method, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/model/document.py", line 1349, in runner
    add_to_return_value(self, fn(self, *args, **kwargs))
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/model/document.py", line 1004, in fn
    return method_object(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "apps/frappe/frappe/utils/typing_validations.py", line 31, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "apps/india_compliance/india_compliance/gst_india/doctype/gst_invoice_management_system/gst_invoice_management_system.py", line 79, in autoreconcile_and_get_data
    IMSReconciler().reconcile(filters)
  File "apps/india_compliance/india_compliance/gst_india/doctype/gst_invoice_management_system/__init__.py", line 33, in reconcile
    self.reconcile_for_rules(GSTIN_RULES, purchases, inward_supplies)
  File "apps/india_compliance/india_compliance/gst_india/doctype/purchase_reconciliation_tool/__init__.py", line 777, in reconcile_for_rules
    self.reconcile_for_rule(
  File "apps/india_compliance/india_compliance/gst_india/doctype/purchase_reconciliation_tool/__init__.py", line 805, in reconcile_for_rule
    and abs((purchase.bill_date - inward_supply.bill_date).days)
             ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
TypeError: unsupported operand type(s) for -: 'NoneType' and 'datetime.date'

Request Data

The request data involved in this issue is:

{
	"type": "POST",
	"args": {
		"docs": "{\"name\":\"GST Invoice Management System\",\"owner\":\"sg@goyalironsteel.com\",\"docstatus\":0,\"idx\":0,\"company\":\"GOYAL IRON & STEEL (NAGPUR) PVT LTD\",\"doctype\":\"GST Invoice Management System\",\"__last_sync_on\":\"2025-03-11T04:56:12.501Z\",\"data_state\":null,\"company_gstin\":\"27AAACG7196G1ZD\",\"__unsaved\":1,\"period\":\"\"}",
		"method": "autoreconcile_and_get_data"
	},
	"headers": {},
	"error_handlers": {},
	"url": "/api/method/run_doc_method",
	"request_id": null
}

Response Data

The response data involved in this issue is:

{
	"exception": "TypeError: unsupported operand type(s) for -: 'NoneType' and 'datetime.date'",
	"exc_type": "TypeError",
	"_exc_source": "india_compliance (app)"
}

Version

The versions of the applications involved in this issue are:

ERPNext: v15.54.3 (version-15)

Frappe Framework: v15.57.2 (version-15)

Frappeauth App: v0.0.1 (master)

Goyal App: v0.0.1 (main)

Frappe HR: v15.41.0 (version-15)

India Compliance: v15.16.3 (version-15)

Payments: v0.0.1 (version-15)

Relevant log output / Stack trace / Full Error Message.

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Conclusion

In this article, we have analyzed the IMS error, a common issue encountered by users of the India Compliance module in ERPNext. The error is characterized by a TypeError, which occurs when the system attempts to perform a subtraction operation between two values of different types. We have identified the root cause of the error and provided a step-by-step solution to resolve the issue.

Solution

To resolve the IMS error, follow these steps:

Check the data types: Verify that the data types of the values involved in the subtraction operation are correct. In this case, the bill_date field is of type datetime.date, while the purchase.bill_date field is of type NoneType.
Handle the NoneType value: Modify the code to handle the NoneType value by checking if it is None before attempting to perform the subtraction operation.
Update the code: Update the code to use the correct data types and handle the NoneType value.

By following these steps, you can resolve the IMS error and ensure that your India Compliance module functions correctly.

Additional Tips

Regularly update your applications: Regularly update your applications to ensure that you have the latest features and bug fixes.
Test your code: Test your code thoroughly to ensure that it functions correctly and does not produce any errors.
Seek help when needed: If you encounter any issues or errors, seek help from the community or the developers of the applications involved.
IMS Error: A Comprehensive Q&A Guide =====================================

Introduction

In our previous article, we analyzed the IMS error, a common issue encountered by users of the India Compliance module in ERPNext. The error is characterized by a TypeError, which occurs when the system attempts to perform a subtraction operation between two values of different types. In this article, we will provide a comprehensive Q&A guide to help you understand and resolve the IMS error.

Q: What is the IMS error?

A: The IMS error is a TypeError that occurs when the system attempts to perform a subtraction operation between two values of different types. In this case, the error occurs when the system tries to subtract a NoneType value from a datetime.date value.

Q: What are the common causes of the IMS error?

A: The common causes of the IMS error are:

Incorrect data types: The data types of the values involved in the subtraction operation are incorrect.
Missing or null values: The values involved in the subtraction operation are missing or null.
Incorrect code: The code is incorrect or outdated, leading to the TypeError.

Q: How can I resolve the IMS error?

A: To resolve the IMS error, follow these steps:

Check the data types: Verify that the data types of the values involved in the subtraction operation are correct.
Handle the NoneType value: Modify the code to handle the NoneType value by checking if it is None before attempting to perform the subtraction operation.
Update the code: Update the code to use the correct data types and handle the NoneType value.

Q: What are the best practices to prevent the IMS error?

A: The best practices to prevent the IMS error are:

Regularly update your applications: Regularly update your applications to ensure that you have the latest features and bug fixes.
Test your code: Test your code thoroughly to ensure that it functions correctly and does not produce any errors.
Use try-except blocks: Use try-except blocks to catch and handle any errors that may occur during the execution of your code.

Q: Can I seek help from the community or developers?

A: Yes, you can seek help from the community or developers if you encounter any issues or errors. The community and developers are always available to provide assistance and guidance.

Q: What are the common tools and resources available to help me resolve the IMS error?

A: The common tools and resources available to help you resolve the IMS error are:

ERPNext documentation: The ERPNext documentation provides detailed information on how to use the system and resolve common issues.
Community forums: The community forums provide a platform for users to ask questions and receive help from other users and developers.
Developer tools: The developer tools provide a set of tools and resources to help developers debug and resolve issues.

Conclusion

In this article, we provided a comprehensive Q&A guide to help you understand and resolve the IMS error. The IMS error is a common issue encountered by users of the India Compliance module in ERPNext, and it is characterized by a TypeError that occurs when the system attempts to perform a subtraction operation between two values of different types. By following the steps outlined in this article, you can resolve the IMS error and ensure that your India Compliance module functions correctly.

Additional Tips

Regularly update your applications: Regularly update your applications to ensure that you have the latest features and bug fixes.
Test your code: Test your code thoroughly to ensure that it functions correctly and does not produce any errors.
Seek help when needed: If you encounter any issues or errors, seek help from the community or the developers of the applications involved.