$ 117.57
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 142 |
| Technical Name |
limit_cash_control |
| License | OPL-1 |
| Website | https://youtu.be/qjOuFaAxWNE |
| Versions | 17.0 15.0 16.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 142 |
| Technical Name |
limit_cash_control |
| License | OPL-1 |
| Website | https://youtu.be/qjOuFaAxWNE |
| Versions | 17.0 15.0 16.0 |
Ewetoye Ibrahim
Community
Enterprise
Limit Cash Control in Odoo Point of Sale
Customize Cash Control Mechanism in Point of Sales
About
The problem and solution
Problem 1:
The point of sale module assumes a cashier will always open the day with the previous closing cash and as such sets the opening cash as the previous session closing cash. Although this can always be changed manually, Cashiers typically forget to change the value which eventually leads to accounting issues, especially with the profit/loss statement.
Solution 1:
In some business cases, it will be more rational to be allow the manger set a fixed default opening amount which may be zero or not for each pos.
Problem 2:
By default, Cashiers get to see the session payments values in each account by clicking on the "Close" button, this may not be desired in some organizations that consider them confidential.
Solution 2:
It will be great to selectively choose whether a point os sale session should have access to the closing payment summary or not.
The point of sale module assumes a cashier will always open the day with the previous closing cash and as such sets the opening cash as the previous session closing cash. Although this can always be changed manually, Cashiers typically forget to change the value which eventually leads to accounting issues, especially with the profit/loss statement.
Solution 1:
In some business cases, it will be more rational to be allow the manger set a fixed default opening amount which may be zero or not for each pos.
Problem 2:
By default, Cashiers get to see the session payments values in each account by clicking on the "Close" button, this may not be desired in some organizations that consider them confidential.
Solution 2:
It will be great to selectively choose whether a point os sale session should have access to the closing payment summary or not.
Features
What this module does
Choose whether to set a default opening value or not
Choose whether to hide closing payment summary or not
Configuration
How to set things up
-
After installation, go to the "Limit Cash Control" section of a point of sales settings; if needed, set the default opening cash; and whether to show closing summary or not.
-
When opening cash has a default value (e.g. 0), the opening control looks like the image below
-
When the "Hide Closing Stat is checked, the hidden control looks like the image below"
CONTACT FOR YOUR BUSINESS NEEDS
(i.ewetoye@gmail.com)
(i.ewetoye@gmail.com)
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module