0014424: Wrong GL Posting when there is a payment with "write off"

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0014424

Openbravo ERP

Z. Others

public

2010-09-03 14:12

2010-12-09 16:06

Reporter

networkb

Assigned To

eduardo_Argal

Priority

urgent

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

2.50

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Advanced Payables and Receivables Mngmt

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0014424: Wrong GL Posting when there is a payment with "write off"

Description

There is a wrong posting when a payment is done using the option of write off. When the payment is done, the amount "written off" goes directly to a Loss account (correct). When we reconcile, the amount of "write off" should not appear in the GL posting.

Steps To Reproduce

To reproduce it, please follow these steps:
1) We create one invoice "Invoice No. 100018" of amount 206.30 and business partner "Proveedor USA" (Screenshot 1.png)
2) Then we create a register in "Receive Payments" with No. "400033" and write the amount of 206. When we click on "Add Payment details" we check "Write off the difference" (Screenshot 2.png)
3) We process it selecting "Process received payment(s)" (Screenshot 3.png)
4) Then we see there is an entry in the General Ledger Journal associated to this transaction: Screenshot "4.png". If we navigate through it, we go to the invoice No. "100018".
5) If we add the transaction into the "Financial Account" we find Screenshot "5.png".
6) If we see the GL Journal, we see two more entries related to this operation: Screenshot "6a.png" and "6b.png". Then we see two entries to 694. Moreover, if we try to navigate through the Journal entry shown in "6b.png" gives as an error, shown in "7.png".

Proposed Solution

Additional Information