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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0047063
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] POScriticalalways2021-06-11 11:112021-06-29 16:52
ReporterjmelinView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0047063: JIRA 2078 - Safebox/Counting - Intial count in BO

DescriptionThe data entered on POS when performing counting (cashup or safebox) must be available in BO.

Currently, in the cashup history tab, we store the "starting amount" of each payment method, that corresponds to the "amount to keep" of the last cashup.

However, for some payment methods, depending on the configuration, an "initial count" operation may be performed by the cashier. Depending on the result of this operation, the available amount may be lower or greater than the theoretical starting amount.

This is currently properly reflected by a transaction for differences that is created in the corresponding financial account. However, this is not reflected in the Cashup History, and it would be very useful to keep track of this.

So, the proposal is to add a new column, "Initlally counted amount", besides the "Starting amount" on each payment method on the Cashup History tab. This amount will be equal to the "Starting amount" in case the payment method is not counted. If it is counted, then it will be the amount provided by the user when he counts.
Steps To ReproduceThe data entered on POS when performing counting (cashup or safebox) must be available in BO.

Currently, in the cashup history tab, we store the "starting amount" of each payment method, that corresponds to the "amount to keep" of the last cashup.

However, for some payment methods, depending on the configuration, an "initial count" operation may be performed by the cashier. Depending on the result of this operation, the available amount may be lower or greater than the theoretical starting amount.

This is currently properly reflected by a transaction for differences that is created in the corresponding financial account. However, this is not reflected in the Cashup History, and it would be very useful to keep track of this.

So, the proposal is to add a new column, "Initlally counted amount", besides the "Starting amount" on each payment method on the Cashup History tab. This amount will be equal to the "Starting amount" in case the payment method is not counted. If it is counted, then it will be the amount provided by the user when he counts.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2021-06-11 11:11 jmelin New Issue
2021-06-11 11:11 jmelin Assigned To => Retail
2021-06-11 11:11 jmelin Triggers an Emergency Pack => No
2021-06-14 10:35 marvintm Severity critical => minor
2021-06-14 10:46 marvintm Note Added: 0129451
2021-06-14 10:46 marvintm Assigned To Retail => jmelin
2021-06-14 10:46 marvintm Status new => feedback
2021-06-17 12:53 marvintm Description Updated View Revisions
2021-06-17 12:53 marvintm Steps to Reproduce Updated View Revisions
2021-06-17 12:53 marvintm Status feedback => scheduled
2021-06-17 12:53 marvintm Assigned To jmelin => Retail
2021-06-17 12:54 marvintm Status scheduled => acknowledged
2021-06-21 16:23 dmiguelez Severity minor => critical
2021-06-22 11:18 guilleaer Note Deleted: 0129451
2021-06-23 12:04 dmiguelez Status acknowledged => scheduled
2021-06-23 12:04 dmiguelez Status scheduled => acknowledged
2021-06-23 12:05 dmiguelez Status acknowledged => scheduled
2021-06-23 12:05 dmiguelez Steps to Reproduce Updated View Revisions
2021-06-23 12:05 dmiguelez Status scheduled => acknowledged
2021-06-23 12:05 dmiguelez Status acknowledged => scheduled
2021-06-23 12:05 dmiguelez Assigned To Retail => pablobessone
2021-06-24 11:36 dmiguelez Status scheduled => acknowledged
2021-06-29 16:52 guilleaer Assigned To pablobessone => Retail


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker