Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0014874Openbravo ERPZ. Otherspublic2010-10-14 12:422011-05-19 16:11
rmorley 
eduardo_Argal 
highmajoralways
closedfixed 
20Community Appliance
2.50 
2.50 
Advanced Payables and Receivables Mngmt
No
0014874: "Standard" matching algorithm requirement for date to be removed
The "Standard" matching algorithm requirement for a match on date should be removed.
The "Standard" matching algorithm currently requires a match on date for both a soft match and a hard match to be achieved.
The problem with this is that the date in the system is the "Deposited" or "Withdrawn" date, whereas the date on the bank statement is the date the bank actually clears the transaction.
For example, I receive a cheque from a customer and I deposit it today.
That results in today's date being captured for the "Deposited Date" in Openbravo.
The bank receives the cheque from me today, but then has to wait a couple of days for the cheque to be cleared by the issuing bank. When the cheque clears it then appears on my bank statement. The date on the bank statement is the date the cheque cleared, not the date the cheque was originally deposited.
There is then no match between the deposited date in Openbravo and the cleared date on the bank statement.

Similarly, when making payment today, the "Withdrawn Date" in Openbravo is today's date. I then send the cheque to my supplier. The supplier has up to six months to present the cheque to their own bank for payment. Their bank then requests that my bank clear the cheque. When this happens it is the date that the cheque cleared that appears on the statement from my bank, so again there is no relationship between the "Withdrawn Date" in Openbravo and the Cleared Date on the statement from my bank.
The match on date in the "Standard" matching algorithm must be removed because users will never get a match in reality.
No tags attached.
Issue History
2010-10-14 12:42rmorleyNew Issue
2010-10-14 12:42rmorleyAssigned To => eduardo_Argal
2010-10-14 18:34eduardo_ArgalStatusnew => scheduled
2010-10-14 18:34eduardo_Argalfix_in_branch => pi
2010-10-14 23:53hgbotCheckin
2010-10-14 23:53hgbotNote Added: 0031868
2010-10-14 23:53hgbotStatusscheduled => resolved
2010-10-14 23:53hgbotResolutionopen => fixed
2010-10-14 23:53hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.advpaymentmngt/rev/f4b3bd4d873615f3fa9357d010e21d3077812096 [^]
2011-05-19 16:11miruritaStatusresolved => closed

Notes
(0031868)
hgbot   
2010-10-14 23:53   
Repository: erp/pmods/org.openbravo.advpaymentmngt
Changeset: f4b3bd4d873615f3fa9357d010e21d3077812096
Author: Eduardo Argal Guibert <eduardo.argal <at> openbravo.com>
Date: Thu Oct 14 23:49:49 2010 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.advpaymentmngt/rev/f4b3bd4d873615f3fa9357d010e21d3077812096 [^]

Fixes issue 0014874.Changes API for Matching Algorithm

---
M src/org/openbravo/advpaymentmngt/ad_actionbutton/MatchTransaction.java
M src/org/openbravo/advpaymentmngt/algorithm/StandardMatchingAlgorithm.java
M src/org/openbravo/advpaymentmngt/dao/MatchTransactionDao.java
M src/org/openbravo/advpaymentmngt/utility/FIN_MatchingAlgorithm.java
M src/org/openbravo/advpaymentmngt/utility/FIN_MatchingTransaction.java
---