If your community notices that approved expense claims are not appearing in your ERP system, follow these four steps to identify and resolve the integration bottleneck.

Step 1: Identify the Transaction Run

The first step is to locate exactly which batch the missing expenses belong to.

1. Determine the dates when the missing expense claims were officially Approved in Unimarket.
2. Go to the Insights module and select Transaction Runs.
3. Locate the specific Transaction Run Number that includes those approval dates based on your community's integration schedule.

Step 2: Check for Error Notifications

Unimarket sends error logs if an integration file fails to process.

1. Review the email inbox designated for your community's integration error notifications.
2. Search for alerts corresponding to the date of the Transaction Run identified in Step 1.
3. Critical Rule: If a single expense in a file contains an error, the entire file is rejected by the system to prevent data mismatching.
4. Review the attached error report, correct the data issues (e.g., invalid GL codes or closed periods), and prepare for re-processing.
   • Banner Customers: You can reload and process the expense file manually using the command FZUMEXI.

Step 3: Internal ERP/IT Audit

If no error email was received from Unimarket, the issue may reside within your institution's internal network or ERP logic.

1. Coordinate with your IT Team to review the incoming file logs.
2. Check for any "silent" failures or rejection codes within the ERP system that may have prevented the file from posting after it was received.

Step 4: Resend the File

If your IT team confirms that the file was never received or no errors were found, you can manually trigger a resend.

1. Go to Insights > Transaction Runs.
2. Locate the desired Transaction Run Number.
3. Click Actions and select Resend. This will push the file back into the integration queue for your ERP.

Important Note for Banner Customers

In some configurations, simply resending the file is not enough. You may need to manually run the specific job that "picks up" the file from the server and feeds it into the Banner environment for final posting.