Continuing the discussion from Build customer accounts interface (for enterprise user):
In the order cycle report, payment method, there seems to be a way to handle customers balance, while the customer management is not yet fully operational in the back office.
Maybe I have not understand this report, and maybe it’s because there is something we don’t use properly in the platform, but the report seems a bit strange (I just hided the phone and mails of the people as this post is public ;-))
- It seems aggregation is done based on the email, if I understand well. That would be great for each line to indicate what has been paid, but also the true price of the order after recalcultion, and the balance corresponding after this payement
- Also it seems the aggregation is actully sometimes working and sometimes not. The different lines display properly the different amounts paid by a given person, but the last column, “balance”, displays sometimes very strange figures, for example if I take all the lines corresponding the user “Bendik”, a member of our buying group
whereas the real balance is 36…
Do you have any idea about where those strange figures come from?
For some people the balance displayed is right, but for most of them it’s not, and with totaly unrealistic figures (like the one for Bendik), and we tried to look in different directions but didn’t see any reason…
Also, would it be possible, as it is done for the order total by supplier for example, or total by customer, to have in the report:
For each user,
- one line for each payment, with the amount paid / final amount due for the order / balance of the client after that payement
- and a “recap” line per user after all the lines of the user, where we see the final balance today of this client? Or maybe if it’s easier another colum with “final balance”…
Today we follow our customers’paymene info (amount paid for the order/ real order after adjustment / balance due or owed) into excel as we can’t follow all that in OFN (until now ;-))
Ping @lin_d_hop, I’m sure you will have some clue understand the bug we get on that very useful report