Frequently Asked Questions

FAQ's » MTD ITSA FAQ's » HMRC MTD ITSA HTTP status 404 (Not Found)

MTD ITSA HTTP status 404 (Not Found)

HMRC server may return an error 404 (Not Found). Software will display a message: Your submission has not passed HMRC server validation. It has returned an error message 404, No data found for the requested date range on HMRC MTD system when Making Tax Digital MTD commercial software retrieving data.

Symptoms:

When customer is attempting to retrieve Making Tax Digital MTD ITSA data to and from HMRC, customer may get a message in the MTD ITSA software:

HMRC server has returned an error message:
HTTP status: 404 (Not Found), Code: NOT_FOUND
No data found for the requested date range on HMRC MTD system.
This issue is not caused by Andica software, the software is simply relaying the response received from HMRC's server.

Cause and suggestion:

HMRC MTD ITSA service had returned an error message HTTP status 404 NOT_FOUND.

This message suggests that the data that you are trying to retrieve does not exist on HMRC MTD ITSA system. May be there are no MTD for Income Tax returns matching the NINO and quarter for which you are retrieving the data.

HMRC MTD ITSA system can only supply data that has been processed under the MTD ITSA system.

Also ensure you have:

  • Registered correctly with HMRC for MTD for Income Tax and have authorised the software.

  • The NINO you have recorded within the software is correct.

If the issue persists, you will need to contact HMRC Online Services helpdesk and speak with their MTD ITSA team. We cannot access HMRC systems to check what is wrong within your digital account and the clients MTD ITSA registration.

Software Message (Symptoms) HMRC Error scenario HMRC Error code Cause Solution
HMRC server has returned an error message:
HTTP status: 404 (Not Found),
Code: MATCHING_RESOURCE_NOT_FOUND No endpoint could be found in the API for the request path.
No endpoint could be found in the API for the request path MATCHING_RESOURCE_NOT_FOUND No endpoint could be found in the API for the request path
Top