diff options
| author | Quentin (OpenERP) <qdp-launchpad@openerp.com> | 2012-02-23 16:56:12 +0100 |
|---|---|---|
| committer | Quentin (OpenERP) <qdp-launchpad@openerp.com> | 2012-02-23 16:56:12 +0100 |
| commit | 0889435d6fa569a14fc6160b0c44f4bdcd2b714d (patch) | |
| tree | 54eb50cb7e77d509c3f3563362ad30268da71f91 | |
| parent | 69c4a6aa341b3b68b8c3c079c48c9533c6be7018 (diff) | |
[IMP] account_payment: improved the module description to tackle the most common pitfall linked to this module
bzr revid: qdp-launchpad@openerp.com-20120223155612-lncs24euy3yubdmq
| -rw-r--r-- | addons/account_payment/__openerp__.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/account_payment/__openerp__.py b/addons/account_payment/__openerp__.py index 82eff66d7d0..83c179801ab 100644 --- a/addons/account_payment/__openerp__.py +++ b/addons/account_payment/__openerp__.py @@ -35,7 +35,7 @@ This module allows you to create and manage your payment orders, with purposes t Warning: -------- -This module does _not_ create accounting entries, it just records your payment order. The booking of your order must be encoded as usual through a bank statement. Indeed, it's only when you get the confirmation from your bank that your order has been accepted that you can book it in your accounting. To help you with that operation, you have a new option to import payment orders as bank statement lines. +The confirmation of a payment order does _not_ create accounting entries, it just records the fact that you gave your payment order to your bank. The booking of your order must be encoded as usual through a bank statement. Indeed, it's only when you get the confirmation from your bank that your order has been accepted that you can book it in your accounting. To help you with that operation, you have a new option to import payment orders as bank statement lines. """, 'images': ['images/payment_mode.jpeg','images/payment_order.jpeg'], 'depends': ['account','account_voucher'], |