Is this only happening with pre-pays? Does the data pass the data integrity check? Could you run a DIC prior to running Period End?

If the data is damaged, we would like to take a look at it.

We've been working with Doug to try and track this down, but to date have not been able to duplicate the situation. As you said, it does not happen all the time so that makes things a little more difficult.

Using the current release of Recievables 6.8B and our sample data, I tried doing a pre-payment, an invoice for a slightly larger amount, a zero cash entry to match the pre-payment to the invoice, and a Period to clear transactions to History, and the Aged Trial Balance report showed the correct (small) amount.

There are 2 different ways to enter a pre-payment in Receivables; one is to simply enter the payment amount at the top and not apply it to a particular document, and the other is to click New and type in a future invoice number. Which way do you enter pre-payments? If the latter, do you actually post the invoice with the same document number or use a new one? I tried both methods for the above steps with success.

After period end, take a look at all three transactions for the customer (the pre-payment, the invoice, and the zero cash to match them) - do the current amounts have appropriate and expected values?

Perhaps this situation is related to a very specific sequence that is used during the entry of a transaction, which is why it happens only some of the time.

Well after a short discussion with R&D, it may be that a very peculiar situation was found, and your particular situation has been marked as fixed for the next Service Pack for Adagio Receivables.

Without getting into it too much, the scenario was related to very specific amounts used for the payment and the invoice, and how calculations were rounding. It only happened when using certain values, which was why it was very hard to track down.

Look for this to be released fairly soon (probably within the month, but don't quote me!!)