Embedded Files
The new Insight Reporting Tool soft-launches Dec 14!
Home > Accounts Payable > FAQs > Error Messages and Troubleshooting
Accounting Period closed - transaction not allowed. (A1598)
Remove the Record Date in the Header Tab within the General Information Section, or add/update the BFY, FY, and Period within the General Information section of the Header Tab.
How do I resolve the error: The MDDFEV for APEVXW Check Number and APEVXW Check Status on the header do not equal the MDDFEV values derived for the accounting line. (A3250)
Resolution: If you receive the MDDFEV for APEVXW Check Number and APEVXW Check Status on the header that do not equal the MDDFEV values derived for the accounting line (A3250), you will need to discard the current MD transaction and begin a new one. The error will result consistently if, at any time, the MD transaction is validated before an Accounting Line is added, resulting in the Check/EFT Status generating Warranted, which is a violation of the MD Default Event Type, which can only be Disbursed. Once this error is generated, the transaction must be discarded and a new transaction created.
You can find the steps to creating a new MD Transaction by following the steps of the Process a Wire Transfer Using a Manual Disbursement (MD) Transaction job aid found on the Accounts Payable page.
How do I resolve the error "The Vendor Customer Does Not Exist on the Vendor Customer Table (A761)" on a payment transaction?
To resolve this error message, you will want to make sure that the record date that you have entered is not before the Active From date or after the Active To date listed on the vendor VCUST Record. If the record date is before the date the vendor became active in CORE or after the Active To, you will want to modify/edit the transaction to correct the record date.
Example:
The vendor has an Active From on the VCUST table listed as 05/12/2021, so if you enter a record date in your CORE Transaction to anything before 5/12/2021, the vendor will not show up in CORE.
Example:
The vendor has an Active To on the VCUST table listed as 12/31/2023, so if you enter a record date in your CORE Transaction to anything after 12/31/2023, the vendor will not show up in CORE.
Why am I getting the following error on my GAX transaction "Vendor Invoice on Vendor Invoice Registry has been paid for $XXXX.XX (A1807) error?
This error could occur for multiple reasons:
You may have data entered in the Payment Instructions section of the Header tab. It overrides the information in the Payment Instructions section of the Accounting tab. The best practice is to leave the Header tab Payment Instructions section blank and only enter the Payment Instructions section on the Accounting Tab.
You may have the same invoice number listed for all the Accounting Lines in the General Information Subsection. You will need to update the lines consecutively (Vendor Invoice Line 1 on Accounting Line 1, Vendor Invoice Line 2 on Accounting Line 2, etc.) if you are using the same vendor invoice number. This should clear the errors, and the transactions should be able to validate successfully.
The Invoice number has been paid on a previous GAX transaction. You can use the Vendor Invoice Registry (VIR) table and/or the Vendor Transaction History (VTH) to confirm this issue.
Why am I getting the following error on my RTGPF transaction "Vendor Invoice on Vendor Invoice Registry has been paid for $XXXX.XX (A1807) error?
You may have the same invoice number listed for all the Accounting Lines in the General Information Subsection. You will need to update the lines consecutively (Vendor Invoice Line 1 on Accounting Line 1, Vendor Invoice Line 2 on Accounting Line 2, etc.) if you are using the same vendor invoice number. This should clear the errors, and the transactions should be able to validate successfully.
Page updated
Report abuse