0047774: Error, NOT BALANCED: the amount of collections / payments ends up in a financial account for a higher amount (does not correctly

Description

When a "Payment in" is recorded in the "Financial Account" the amount that is recorded is different (because the decimal separators are incorrectly applied)
By having different amounts, it does not allow the "Financial Account" to be counted and leaves it in the "Unbalanced" status.

The accuracy of the currency was checked in the application and they are fine
The fin_payment.finacc_txn_amount field records an amount that seems to be not properly linked to the Format.xml (which is not the case with the fin_payment.amount field, which is formatted well), and ends up generating an inconsistent bank transaction.

Steps To Reproduce

Could not detect a step by step to follow to reproduce the problem.
The document with the client's example is attached
The client to solve the error:
-Reactivate and delete the bank transaction.
-Reactivate "eliminating lines" the billing document and return to "Add Payment Details".
-Finally, re-process payment and deposit.

Tags

No tags attached.

Attached Files

29116_PDF.pdf [^] (446,505 bytes) 2021-09-28 23:56

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0132080) vmromanos (manager) 2021-09-30 11:57	This is a basic flow, with a very good automatic test coverage in our CI. It is widely used by our customers and nobody has reported something similar, and obviously you can't reproduce it in a standard environment. This looks like a configuration problem in that concrete instance, not a bug in the Product. The issue is rejected. I recommend you to dig into that instance to understand the configuration problem that they might have. Format.xml is the candidate to review. More info: http://wiki.openbravo.com/wiki/Format.xml [^]

Issue History
Date Modified	Username	Field	Change
2021-09-28 23:52	lbressan	New Issue
2021-09-28 23:52	lbressan	Assigned To	=> Triage Finance
2021-09-28 23:52	lbressan	Modules	=> Core
2021-09-28 23:52	lbressan	Regression date	=> 2021-10-26
2021-09-28 23:52	lbressan	Triggers an Emergency Pack	=> No
2021-09-28 23:56	lbressan	File Added: 29116_PDF.pdf
2021-09-30 11:57	vmromanos	Review Assigned To	=> vmromanos
2021-09-30 11:57	vmromanos	Note Added: 0132080
2021-09-30 11:57	vmromanos	Status	new => closed
2021-09-30 11:57	vmromanos	Resolution	open => unable to reproduce
2021-12-09 13:27	eugeni	Issue Monitored: eugeni