Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0028683
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] 09. Financial managementmajoralways2015-01-20 02:232015-07-14 04:09
ReporterrjapoovaView Statuspublic 
Assigned ToTriage Omni OMS 
PriorityhighResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0PR14Q4SCM revision 
Review Assigned To
Web browserGoogle Chrome
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0028683: You should be able to view reconciliation balance before confirming reconciliation

DescriptionThe purpose of a bank statement reconciliation is to ensure that the records in the systems and the records as reported by the bank are in agreement.

This involves two aspects:
1) Confirming that the transactions known in the system are the same as the ones known by the bank (i.e. no transaction in the bank is missed in the system and vice versa)
2) Confirming that the balance of the account matches the balance as reported by the bank.

Openbravo is very effective in achieving the first objective thanks to the Match Statement window.

The second objective however is not quite as well supported.

Once you complete the match statement process and you click Done in the Match Statement window, all transactions are marked as Cleared and you are then asked to confirm the reconciliation. If you accept (press Done), all cleared transactions are set as reconciled and the balance as of the last reconciled transaction is stored as the "Last Reconciliation Balance" amount on the financial account.

The problem is that when you are asked to confirm, you are not told what that amount is going to be so you have no way to know whether it is correct or not.

Unless you want to blindly trust the system (in which case, why bother with a reconciliation?), the correct user procedure is to:
1) Do not confirm reconciliation (press Cancel)
2) Review the financial account balance
3) Using a calculator, subtract any uncleared transaction, if any
4) Match that amount (which is going to be the last reconciliation balance) with the amount reported by the bank (typically, you can find that in the online banking app for your bank account)
5) If they are in agreement, you can safely reconcile.
6) To do so, you need to restart the Match Statement process (there is not going to be any new transaction), press Done and access the Confirm reconciliation window. At this point you can safely press Done.

As you can see this process is unnecessarily convoluted.

When the Confirm Reconciliation window is presented to the user, the system is already able to calculate what the "Last Reconciliation Balance" is going to be.

It would be enough for that window to present that amount and the user would not need to go through this painful process.
Steps To ReproduceSee above
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0028669 closedTriage Omni OMS Language in Confim Process Reconciliation window is very confusing 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2015-01-20 02:23 rjapoova New Issue
2015-01-20 02:23 rjapoova Assigned To => dmiguelez
2015-01-20 02:23 rjapoova Web browser => Google Chrome
2015-01-20 02:23 rjapoova Modules => Core
2015-01-20 02:23 rjapoova Triggers an Emergency Pack => No
2015-04-27 13:48 dmitry_mezentsev Relationship added related to 0028669
2015-04-27 13:52 dmitry_mezentsev Assigned To dmiguelez => Triage Finance
2015-04-27 13:52 dmitry_mezentsev Status new => acknowledged
2015-04-27 13:55 dmitry_mezentsev Web browser Google Chrome => Google Chrome
2015-04-27 13:55 dmitry_mezentsev Priority normal => high
2015-07-14 04:09 eintelau Issue Monitored: eintelau


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker