Yesterday we had a funny invoice print - the amount paid  (which comes from the allocated amount field) showed $400 - an amount different to what was paid. When the invoice is printed now it shows the correct amount paid and this matches the allocated amount actually in the database (as revealed by an SQL query).

Trying to replicate the situation, if I invoice for $1234, then finalise and pay, the amount paid shows the actual amount paid ONLY if the account previously had a zero balance.  If there was an outstanding balance, then on the invoice, although it has just been paid in full, it says Amount Paid = $0.

In trying to document this better, I did invoice, finalise, don't pay; new invoice; finalise, pay - but only amount of invoice 2.

The invoice print shows as follows - note the amount paid - it is not what was paid ($1560) but rather $1560 less the remaining account balance.

Here is the Account page showing the paid amount is really $1560

If I print the invoice again, it still shows as above, ie Amount paid=$1289.60. If I look in the database with an SQL query, the allocated amount is indeed $1289.60

Wondering if this is some sort of 'cached in memory' problem, I logged out and back in again and did another invoice. Here is the payment screen for it:

and here is the invoice print:

and here is the account screen again:

If we now print the "unpaid" $270.40 invoice, it shows and amount paid of $270.40 - but (as indicated by the balance) it has not actually been paid.

Conclusion: If the account is running "clean" -ie each invoice entered and then immediately paid, things work OK. However, if there is an outstanding balance, the allocated amount field get wrongly set to the outstanding balance less the amount paid.