Troubleshoot Expense Issues
Review the following sections for information about commonly known expense issues or behaviors.
Check Constraint Error When Trying to Move Approved Expenses to Vista
Resolve the check constraint error when moving approved expenses to Vista.
The following error indicates corruption with the 1099 status for one of the vendors in a batch:
The INSERT statement conflicted with the CHECK constraint
“CK_bAPHB_V1099YN.” The conflict occurred in database "Viewpoint", table
'dbo.bAPHB", column 'V1099YN'. Cannot insert the value NULL into column 'BatchSeq',
table 'Viewpoint.dbo.bAPLB'; column does not allow nulls. INSERT fails. The
statement has been terminated.
To resolve this error:
- In Vista, open the AP Vendors ().
- Select the Add'l Info tab.
- Confirm that the Subject to 1099 reporting checkbox is either checked or unchecked (should not have a black square).
PO Coding Removed After Matching Expense Receipt to a Credit Card Transaction
If you code an expense item on an expense receipt to a purchase order and then link that receipt to a credit card transaction, the PO coding is removed from the expense item.
This is expected behavior. Initially, the purchase order that you coded to the expense item was written to the vendor associated with your employee number.
When you matched the receipt to a credit card transaction, the vendor changed to the credit card vendor. As a result, the initial purchase order information was cleared from the expense item, allowing you to code that item to a purchase order that was written to the credit card vendor.
