There are a multitude of invoice errors that can occur when submitting to USAS. Below are some of the possibilities and what they mean:


 


Submission failed: Invoice error, purchase order does not exist on purchase order history file


A: This could mean two things - the purchase order being submitted against is a FUTURE status PO, or a PO that SCView does not have access to(or no longer exists). If you can locate the PO in USAS and it is not FUTURE status, you will need to contact your ITC to find out why you can't submit against the PO.


 


Submission Failed: Invoice for PO already on file


A: The invoice number has already been used for this specific PO. You will need to confirm in USAS web if the invoice already exists. If the invoice was already entered, you are attempting to put in a duplicate and can remove the invoice from workflow. If the invoice is different than what is on file, you can use a different invoice number or add additional characters to allow the invoice to submit.


 


Submission Failed: Invoice error, purchase order item is completely filled


A: USAS is reporting back that one of the lines you are attempting to post against has already been marked as full, regardless of the remaining encumbrance. If you are trying to submit a line with $0 but it still has a status and it is against a line that was marked as full, the invoice will fail. Lines being submitted must go against a line that is either new or partial.


A line that was previously marked as full can only be made partial or new again by deleting the invoice that is causing the line to be read as full. If a check has already posted against the invoice, you will need to contact your ITC to make changes or post against a different line.


 


Submission Failed: Vendor number ###### is a Multi-Vendor and may not be used to post invoices or checks.


A: When the invoice was posted to USAS, the vendor number index was not updated from the original multi-vendor value. Update the vendor number index to reflect the vendor number being paid and resubmit


 


Submission Failed: Invoice date not in proper range or is invalid.


A: The invoice date was typed incorrectly and/or is outside of the current fiscal year. Update the invoice date index to reflect a valid date and resubmit.


 


Submission Failed: Vendor number cannot be different from vendor on PO file!


A: The PO in USAS has a different vendor number than what is indexed in SCView. Make sure the vendor on file in USAS matches the vendor number in SCView and resubmit. On the invoice confirmation screen, make sure the vendor number does not revert back to the incorrect vendor number from old indexes/invoices before submitting.


 


Submission Failed: Invalid invoice status, must be 'P', 'F' or 'C'


A: One or more invoice lines were submitted with an amount greater than 0 without a status. Each line being submitted must have a status of partial, full, or cancel. Edit the lower lines on the invoice confirmation screen prior to confirming submission.


 


Submission Failed: Vendor number ###### not on file.


A: The vendor being submitted against is no longer a valid vendor or has been moved to an inactive status. Verify in USAS and then resubmit once the vendor has been restored as a valid vendor.


 


Submission Failed: org.exolab.castor.xml.MarshalException:


A: This is a USAS code error. Please contact SC Support or reach out to your ITC for assistance. 

 


Submission Failed: Unexpected response. Invoice element not returned.


A: The lower line items for an invoice were not available to be read by the system. This usually occurs when an invoice enters the system outside of SCScan. To remedy this, the invoice can either be re-scanned and indexed, or the SYNC button can be used next to the lower line items to pull them in. Once the lower line items exist, they must be edited on the invoice confirmation screen.


 


Submission Failed: Contact Support       OR       Submission Failed:


A: Please contact the SC Support team