Payment and invoices not matching properly

We have a problem with one of our sites where, every now and then, a payment doesn't seem to match properly and we can't figure out why.  For the latest case, the symptoms visible in GACCDUDATE were:
- Payment: PAYLOC/CUR = 0, TMPCUR/LOC = 0, FLGCLE = 1
- Invoices: PAYLOC/CUR = 0, TMPCUR/LOC = amount paid, FLGCLE = 4

FLGCLE is not always set to 4 when this happens but it is always a case that the PAY & TMP amounts are out of sync and require a manual table update to fix and then to be matched manually.

An easy check we use is to see whether SUM(AMTCUR) is equal to SUM(AMTCUR-PAYCUR),  which it should be if everything has matched and posted correctly.  If there are payments still to be posted then SUM(AMT) should equal SUM(AMT-PAY-TMP), obviously taking SNS into account for all these calcs.

Variations on the above that we've seen are (I'm using xxxCUR to explain but it is the same for xxxLOC):

  • PAYCUR and TMPCUR on the payment are correct, i.e. PAYCUR = AMTCUR AND TMPCUR = 0 but some or all of the invoices on the payment have PAYCUR = 0 and TMPCUR = amount paid
  • PAYCUR = TMPCUR, which should never be the case on a matched payment.

This used to happen on PU8 but still happens now on V12 2021 R4.

Has anyone out there come across this before?

  • Yes, we have experienced the same issue.  we are on version 12.0.24 V12 2020 R4.

    Just last week a payment bank record paid in full 1/4/2022, was updated and now has an open balance.  The record was marked closed, and has been reopened.

    The situation for us maybe slightly different, in that for this customer is this BAN was closed and paid in full but matched with lowercase letters.  Last week it was reopened with an unpaid balance.

    We have many entries for this customer with lowercase letters assigned - 2184 records with lowercase.  I need analyze, line by line, why they aren't matched with uppercase.  

    In the meantime, I will manually update GACCDUDATE for this BAN entry.