This article guides users on how to identify, interpret, and resolve import data errors when submitting sales reports through the system. It focuses specifically on common issues related to Purchasing Entity Names and file formatting, and provides step-by-step instructions for correcting records to ensure successful submission. The objective is to help users confidently manage alerts and errors during both manual entry and data import processes.

Handling Import Data Errors

The system will alert you it receives anything it isn’t expecting for the Purchasing Entity Name field.

For the example detailed below, I input City of Boston into the Purchasing Entity Name. However, the system found issue with that and alerted me appropriately.

The system is telling us our previously input value of City of Boston was recognized and appropriately translated to the accepted value that the organization is expecting to see (Boston).

If you do not take any action, the record will remain in a Missing or Erroneous Data status, and you will not be able to submit your report. To get the record into a final status you will need to:

• Review the alert. Then, at the bottom of the record, click Resave. It will resave with the translated accepted value.

Another error you may see is that your Purchasing Entity Name doesn’t match anything in the accepted values list or match any translation to an accepted value.

To fix this, what you will need to do is Request an Exception. If you’re insistent that the value you’ve input is correct, simply scroll down to the bottom of the record and input an Exception Explanation. Once you’ve done so at the bottom, click Resave with Exception.

This article provides an overview of how the system detects and flags data issues during sales report imports. It emphasizes the importance of using accurate and accepted values—especially in key fields like Purchasing Entity Name—to prevent submission delays. When discrepancies are found, the system offers guidance and feedback to help users identify and correct errors.

Understanding these alerts and how they impact report status is crucial for maintaining data integrity and ensuring timely submissions. The article also reinforces the value of using system tools and support resources to troubleshoot and resolve import challenges efficiently.

If you still require additional assistance, close this tab and return back to the system and submit a support ticket.