The fixed file, rep108.php, can be downloaded here.

Joe

Just waiting for a response from @hannelie. I guess we should make this change anyhow, but it would be nice if it also helps @hannelie.

/Joe

When the customer balance of the specific customer in question is incorrect on the statements, does the statement add up correctly?  If not, the problem is a arithmetic error; otherwise, if the statement does add up, the problem is either missing or additional transactions, given that the balance is correct when viewed in other ways.   

When you said that the customer statement shows an additional credit that is not correct, it made me suspect the latter case.  If the problem is indeed an extra transaction (i.e. credit) that should not be there, and cannot be found elsewhere in the system, then I am guessing that this is a voided transaction, although I do not have a theory why the "show also allocated" would make any difference.  In any case, it would suggest that the sql to locate transactions on the customer statement report is in error, if those transactions are not the same as shown in other parts of the system.

If you can isolate the problematic transaction, which perhaps you already have, then you can examine the database for more clues, using the data from this transaction to find it using the mysql client.

I also added void screening to the customer statement in https://github.com/braathwaate/frontac24/blob/master/rep108.php.  You could try replacing your core/rep/rep108.php with this file.  However, it is just a wild guess at this point that it would work.

Can you also state what version of FA you are using.

I have made some investigations into this and I cannot find anything wrong. Please help me. It might be an old bug belonging to the  voiding history.

@Braate Wathe, if you have a possible solution, please provide it, so we can help @hanneli.

Joe

Joe