Purpose:

The purpose of this article is to document the issue where multiple invoices were stuck in Transfer Failed status due to incorrect XML formatting in the transferresponse.xml file. This article explains the root cause, how the issue was identified, and the actions taken to restore normal processing.

Instructions

• Review transfer response logs to verify whether the task executed successfully.

• Note that the Transfer Response task may still run without showing any errors, even when the XML structure is incorrect.

• Manually validate the transferresponse.xml file structure against the schema file TransferResponse.xsd (screenshot showing the location of the xsd file attached below).

TransferResponse.xsd File Location Screenshot

• Ensure that the XML tags in the transferresponse.xml file follow the exact case sensitivity defined in the schema.

• Compare the contents of transferresponse.xml with TransferResponse.xsd to confirm correct tag names.

• After fixing the transferresponse.xml file and placing it in the inbound location, rerun the Transfer Response Scheduler task.

Problem

Customer reported that several invoices were stuck in Transfer Failed status even though they were successfully processed in the ERP system. It was identified that the transferresponse.xml file contained incorrect tag formatting. The Transfer Response task executed without any errors, which made the issue less visible and required manual XML validation. The root cause was that all XML tags in the transferresponse.xml file were provided in uppercase, which did not match the expected tag names defined in TransferResponse.xsd. Because of this mismatch, the system could not interpret the XML content correctly.

Solution

After applying the correct tag format and case sensitivity in the transferresponse.xml file, the corrected file was placed in the inbound location and the Transfer Response Scheduler task was rerun. All affected invoices were successfully updated from Transfer Failed to Processed status.

Actions Taken

• Customer provided the list of invoices stuck in Transfer Failed status.

• Transfer response logs were reviewed, and the Transfer Response task was running without errors.

• Manual inspection of the transferresponse.xml file revealed that tags were incorrectly capitalized.

• The XML file was corrected based on the proper tag structure from the TransferResponse.xsd schema.

• The corrected file was placed in the inbound location and the Transfer Response Scheduler task was rerun.

• All affected invoices were successfully updated to Processed status.

Example

In the incorrect transferresponse.xml file, tags such as <RESPONSE>, <DOCID>, <DOCUMENTNUMBER>, and <ERROR> were entirely uppercase.

However, based on the TransferResponse.xsd schema, the system expects tags like <Response>, <docid>, <DocumentNumber>, and <Error> with proper case sensitivity. See attached XSD file for checking the word case of the xml tags.   

(Screenshots showing the incorrect and corrected XML tags in the transferresponse.xml file attached).  

Incorrect XML Tags Screenshot

Correct XML Tags Screenshot

Because XML is case sensitive, the system treated the uppercase tags as invalid, preventing invoice status updates. Once corrected, the system processed the file successfully and updated all invoices.