Hello,
Version: AP 8.0A 05 11 22 (and I believe 06 03 30 as well)
In responding to a problem where a the GL AP control acct and the AP subledger did not balance I found the following (after much digging I might add

) :
<a> MC transaction applied to IN and CN transactions.
<b> CN only partially used leaving a balance on this CN trans.
<c> Period End with Clear Transaction History eventually
purged the MC Transaction <d> Subsequent DIC reported "Computed Bal. vs. Stored Bal." problem on the CN transaction
<e> Rebuild run and repaired errors believing the "Computed Bal." to be correct - It was not !!!
<f> Rebuild "forced" Stored Bal. to match incorrect Computed Bal.
<g> GL/AP ledgers now out of balance since "rebuild" passes no GL entry
While the above was created using the previous release of AP, I see no mention of a fix in the release notes of the current release and therefore suspect that the problem would still be present.
I guess the answer is to not let AP clear the MC (or any) trans. that are required to compute the difference in another transaction's Original vs. Current Amount even if its current amount is 0.00
However, food for thought: Should there be some warning when the methods used by the Rebuild process could cause an imbalance between the GL and its Sub-Ledgers ?
Regards, Peter
PS: You really need at least a [Print] button for the DIC window. Add an [eMail] button that automatically brings up their "support contact's email address" and that would be really cool

BTW - we don't want to buy another module (DC) to do this
