When an expense transaction run is exported from Unimarket to Banner, the data must pass through Banner’s standard financial validation logic. If a report fails to load or remains in an "Incomplete" status, it is typically due to accounting (FOAPAL) restrictions or vendor setup issues for the employee being reimbursed.
Diagnostic Tools: Where to Find the Error
To identify the specific cause of a failed expense upload, use the following Banner resources:
- FZRGURA Table: Query this table using the Expense Report ID to find the literal error string returned by the Banner API.
- FGRIDOC Form: Search for "Incomplete" documents. Expense reimbursements often appear here as incomplete Invoices (I-numbers).
Common FOAPAL & Accounting Errors
| Error Message | Cause | Resolution |
| Fund/Org/Account is Inactive | The accounting string used on the expense line has been closed in Banner. | Coordinate with Finance to temporarily reopen the code or perform a "Change Request" in Unimarket to use a valid code. |
| Fund Terminated | Common with Grant funds that have expired between the date of travel and the date of reimbursement. | Coordinate with Finance to temporarily reopen the code or have Finance extend the date to allow the final reimbursement. |
| User does not have authority to post to chart | The integration user (e.g., UNIEXP) lacks security permissions for the specific Chart or Org. |
Update the UNIEXP user profile in FOMPROF to include the necessary Chart/Org authority. |
| NSF (Non-Sufficient Funds) | The reimbursement amount exceeds the remaining budget in Banner for that FOAPAL. | Increase the budget in Banner or override the NSF check for the integration user. |
Vendor & Employee Setup Errors
For Unimarket Expenses to bridge to Banner, the employee must be established as a Vendor in the FTMVEND form.
| Error Message | Cause | Resolution |
| Vendor ID not found | The Banner ID associated with the Unimarket user does not exist in the FTMVEND table. |
|
| Invalid Address Type/Sequence | The employee record in Banner is missing a "Remit To" or "Accounts Payable" address type. | Ensure the employee has a valid address sequence in FTMVEND and an Accounts Payable Type Code and Sequence Number default. |
| Vendor is on Hold | The employee's vendor record has been placed on hold, preventing any new invoices from being created. | In FTMVEND screen, change status in the Payment Hold Code dropdown. |
Fiscal Year & Timing Errors
| Error Message | Cause | Resolution |
| Period is Closed | The transaction date on the expense run falls in a month that has already been closed in Banner. | Adjust the transaction date in the upload file to the first day of the next open period. |
| Fiscal Year Mismatch | Occurs during the June/July transition if the "Order Date" (Expense Incurred Date) and "Transaction Date" (Payment Date), cross the fiscal boundary in an unsupported way. | Adjust the transaction date in the upload file to the first day of the next fiscal year's open period. |
Duplicate Document Errors
| Error Message | Cause | Resolution |
| This Vendor Invoice already exists |
This occurs if an expense run is accidentally uploaded twice. Banner checks the combination of Vendor ID + Invoice Number. Note: Since Unimarket Expense IDs are unique, this usually happens if a previous manual entry was made in Banner using the same reference number. |
If the previous attempt was incomplete, delete the record from FAAINVE and re-upload. If it was already paid, the new upload must be cancelled. |
Pro-Tip: If many reports fail due to "Invalid Account," use the Unimarket Expense Export to identify the affected users and perform a bulk update of their default FOAPAL strings to prevent future errors.