Troubleshooting Common Rejections
for Bronco Hub Financial Transactions
Purpose: This document is intended to help troubleshoot common rejection reasons for financial transactions created and submitted in Bronco Hub. This document does not provide step by step instructions for editing transactions in Bronco Hub but does provide a link to each instruction set.
To jump to a specific section of this document, click the transaction type below:
Troubleshooting Rejected Expense Reports
There are three common reasons Expense Reports are rejected.
[Workflow System] Incorrect expense template in Bronco Hub.
The Expense Report module in Bronco Hub is configured to automatically reject Expense Reports billed to a Project Fund on a non-POET template. To avoid the rejection of an Expense Report for incorrect template, ALWAYS select POET template if the expenses are being reimbursed with Sponsored Project funds.
Instructions for selecting the correct template are outlined in the Submitting an Expense Report job aid.
Incorrect funding segment string coded to the Expense Report.
To avoid rejections for incorrect funding segment strings, refer to the All Segment Values Report and confirm segments with your department Business Manager prior to submitting the transaction.
Expense Report is submitted under the preparer name rather than employee being reimbursed.
To avoid this type of rejection, select the name of the employee being reimbursed prior to creating the Expense Report.
Correcting the transaction:
Rejection reasons 1 or 2:
Edit the existing Expense Report by following the instructions on the Withdrawing and Editing an Expense Report job aid.
Rejection reason 3:
A new Expense Report must be created. Follow the instructions on the Submitting an Expense Report job aid.
Troubleshooting Rejected Invoice Payments
There are six common reasons Invoice Payments are rejected.
[Workflow System] Asset Tracking.
The Invoices module in Bronco Hub is configured to automatically reject an Invoice Payment if an asset account code (begins with 6 or ends in 25) is included in the Distribution Combination AND the option for "Track as Asset" is not checked. To avoid this rejection, ALWAYS check the Track as Asset option on invoice lines coded with an account segment (4th segment) beginning with 6 or ending in 25.
Instructions for asset tracking on Invoice Payments can be found in the Submitting Invoice Payments job aid.
[Workflow System] Missing POET information.
The Invoices module in Bronco Hub is configured to automatically reject Invoice Payments if aProject Fund segment is included in the Distribution Combination and POET information is not entered on the same line. To avoid this rejection, ALWAYS include POET fields when submitting a transaction that includes Sponsored Project funds.
Instructions for adding POET data to Invoice Payments can be found in the Submitting Invoice Payments job aid.
Incorrect funding segment string coded to the Invoice Payment.
To avoid rejections for incorrect funding segment strings, refer to the All Segment Values Report and confirm segments with your department Business Manager prior to submitting the transaction.Incorrect Invoice Number.
To avoid rejections for Invoice Number, use the Invoice Numbering Convention to confirm accuracy of input.Incorrect Supplier Information.
If the Supplier and/or Supplier Site is not set-up accurately in Bronco Hub, the Invoice Payment can not be processed for the supplier. To avoid rejections for supplier information, confirm accuracy of supplier set-up in Bronco Hub by running the Supplier Search and verifying Supplier Remittance details. Follow the instructions on the Inviting Vendors to PaymentWorks job aid to get new suppliers added to Bronco Hub.
Invoice Payment already paid.
To avoid rejections due to duplicate payment attempts, review Invoice Payments previously submitted and paid by following the steps outlined in the Reviewing Invoice Payment Status job aid.
Correcting the transaction:
Rejection reasons 1, 2, 3 or 4:
Edit the existing Invoice Payment by following the instructions on the Edit a Rejected Invoice Payment job aid.
Rejection reason 5:
A new Invoice Payment must be created and initiated through the approval workflow. Follow the instructions on the Submitting Invoice Payments job aid.
Rejection reason 6:
No further action is needed.
Troubleshooting Rejected Requisitions
There are six common reasons Requisitions are rejected.
[Workflow System] Missing POET information.
The Purchase Requisitions module in Bronco Hub is configured to automatically reject a Requisition if the Project segment (7th segment) is anything other than all zeros and POET fields are not completed. To avoid this rejection, ALWAYS include POET fields when submitting a transaction that includes Sponsored Project funds.
Instructions for adding POET data to Requisitions can be found in the Submitting Purchase Requisitions job aid.
No quote or contract attached.
To avoid this type of rejection, confirm you have acquired the appropriate documentation/quotes for the intended purchase and have attached them to the Requisition in Bronco Hub.
Requisition is submitted with one line when it should include multiple lines.
To avoid this type of rejection, confirm you have entered one Requisition line for each type of item being procured. Total number of Requisition lines should match total number of lines on the quote provided by the vendor/supplier.
Incorrect funding segment string coded to the Requisition.
To avoid rejections for incorrect funding segment strings, refer to the All Segment Values Report and confirm segments with your department Business Manager prior to submitting the transaction.Incorrect Line Type.
To avoid this type of rejection, select the appropriate line type (Goods, Services or Construction Sponsored Projects) for the item being purchased.
Purchase has already been made, Requisition is submitted with invoice attached.
To avoid this type of rejection, keep in mind that Requisitions are submitted before a purchase is made.
Correcting the transaction:
Rejection reasons 1, 2, 3 or 4:
Edit the existing Requisition by following the instructions on the appropriate job aid:
Rejection reason 5:
A new Requisition must be created and submitted through the approval workflow. Follow the instructions on the appropriate job aid:
Rejection reason 6: Do not submit or edit the requisition.
If you have an invoice that needs paid and the purchase is tied to a Purchase Order (PO), submit the Purchase Order Payment Approval Smartsheet.
If you have an invoice that needs paid and the purchase is not tied to a PO, submit an Invoice Payment.
Need help with the steps above?
If you have questions about procurement or payment processes, please contact Procurement and Vendor Services (Procure to Pay).
If you experience a system issue/error OR have suggestions to improve the instructions in this job aid, please submit an OCI Service Request ticket.