4043: Account 2100 with No Payable
TSEQ = XXXX, TPDATE = MMMDDYY, TDRAMT =YYYY.YY, TCRAMT = ZZZZ.ZZ TSOURCE = AA, TDESC = BBBBBB
Detects Transactions on A/P Account 2100 with no payable or no vendor linked to it.
Opening and closing transaction are not included.
It was added to the Complete Diagnostic Report on Feb 17, 2011.
Because it is new, it may uncover transactions that are many years old.
Very old releases of PF did not have the controls to prevent this situation.
If the transaction is linked to a payable but not a vendor, it is a simple matter to link it to the correct vendor.
Find the vendor that is linked to the payable, and then use the Transaction detail window to link it to the same vendor.
If the trx is not linked to a payable, there are 2 options to fix this
1. Re-open periods back to the oldest post date shown on the error list.
Change the account number on the transaction (using the TRX Details window ) to account that is not A/P
Reclose periods.
This will change the balances on A/P and the other account number, so you may not want to use this method if older periods have been finalized.
2. There is a batch procedure that will insert a “Fake Payable”, and link all the transactions with errors to it, so they will no longer will show as errors.
PROG > Procedures > Procedures 2 > 4043: Attach FTR to Payable if Missing
Inserts a vendor “MISC” if it is not already entered.
You may be prompted to enter the first date in the first open period. Do not change this date.
Inserts a Payable header with the reference number of the date.
Connects all error transactions to this payable. They can be seen by clicking on A/P TRX on the payable window.
Results of #2:
If the Balance due on the fake payable is 0.00, that’s great and you are done.
If there is a balance, you must see if the diagnostics also report Error #4044, A/P Transactions do not balance with open Payables.
Compare the balance on the fake payable to the delta amount on error 4044.
Please call us for the recommended fix.
If this error shows up again please contact us! It should not.
Last Revision: 5/12/11, AG