Multiple Prepayment Application from Voucher and Adjustment Entry

(0) Share

Report

Posted on by C Conner

300

In SL2018 CU1, client has used the multiple prepayment application option in Voucher and Adjustment entry. After the batch was saved, it was noticed that the prepayment reference number was associated with the intended vendor and document reference, as well as the next record. Has anyone else seen this behavior or know of a resolution?

*This post is locked for comments

All responses (2)

Answers (0)

CFROTON 4,710 on at

Like (0)

Report

RE: Multiple Prepayment Application from Voucher and Adjustment Entry

hello C Conner,

Were you able to get this issue resolved with the response given. Let us know if we can assist you further

Best Regards,

Jana MacDonald
Suggested answer

CFROTON 4,710 on at

Like (1)

Report

RE: Multiple Prepayment Application from Voucher and Adjustment Entry

Good day -

I ran this by our financial specialist and this is his reply:

It sounds like they are saying that a prepayment for vendor A was somehow applied to a voucher for vendor A, and also a voucher for vendor B. No, I haven’t seen that. At least not in a released batch. I’ve seen some pretty messed up voucher batches that were suspended with incorrect prepayment information. The way I usually resolve those is to remove the prepayment reference number from the voucher, which can typically be done in the voucher entry screen by deleting the prepay reference number. But in some cases, I have had to just go into sql and remove the ap_ppapplic records for the batch, like this:

delete from AP_PPApplic where batnbr = '012345'

Then they can usually release the batch. There won’t be any prepayment applications in the batch, but they can use the 03.070.00 prepayment application screen to apply the prepayments. In the case of this customer though, they are saying the batch has been released and there are incorrect prepayments. I would want a support case for that one. We would need to look at some records in SQL Server and see if we need to update or delete records to ‘fix’ the data.

I hope this helps.

Thank you

Caroyln

MSDSL Technical Support