Hello guys, 2 comments on this : 1 - About Prepayment booking : Alexis Delattre did a great job here : lp:~akretion-team/account-closing/70-cutoff-modules. These modules adds dates (start/end) on invoice lines and compute/generate automatic cut-off entries (year-end or month-end). This also includes prepayements of course. And it works for continental accounting and anglo-saxon accounting.... so totally generic. The MP is under review and hope fully should be included into the account-closing community branch. 2 - E-commerce prepayment by credit/debit card is something totally different. Nothing to do with cut-off bookings. At Camptocamp we handle this through our connector (http://openerp-connector.com/) which make things easy to set. But in the end, we can handle any e-commerce payment method (cards, cheque, cash, multi-payment...) without specific workflow. Ex. : A credit card payment can generate a sale order with manual invoicing and invoice generated after delevery. So when the invoice is generated, the accounting booking is posted and through the connector we can decide if we generate immediately a payment accounting entry. If we so so, the invoice is paid (workflow) but we use an intermediate account for payment instead of a bank account.
Conclusion 2 different topics. Cordialement, *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Frédéric Clementi* Project Manager Business Solutions +41 21 619 10 41 www.camptocamp.com 2013/11/18 Guewen Baconnier <[email protected]> > Hi, > > > On 11/16/2013 09:28 AM, Eric Caudal wrote: > >> Hi, >> There is an aspect of OpenERP which seems to not very well implemented >> while it is wildly spread in accounting practices: prepayment treatment. >> In many countries (all?), prepayment accounts have to be different from >> the AR/AP general account for the mere reason that they are on the other >> side of the BS. This behavior is at least true in China, NZ, UK, AU and >> probably in any anglo-saxon accounting countries. >> >> We have created a simple module for this ( >> https://apps.openerp.com/apps/7.0/account_prepayment) to create a >> separate property for AR and AP prepayments. In every implementation I >> have in accounting, the prepayment strategy is a problem in standard >> implementation that we can solve with this very simple module (my point >> is that this module or similar should be actually a standard module). >> >> In ecommerce sales strategy where payment is made on website, we can >> rely on several modules such as sale_payment_method and >> sale_automatic_workflow to automate the payment. Nevertheless, they rely >> on the AR account to create the prepayment transaction which in my >> opinion is not correct. >> NB: This could probably be even more complex as for certain payment >> method, account should "Uncleared Payments". >> > > Not sure about that here... Frédéric's opinion is welcome :-) > > > >> I am thinking of adapting the sale_payment_method to make it dependent >> on the account_prepayment and add a tickbox "Use prepayment accounts" in >> payment method and automatic_payment method. >> > > I think that's not the correct way: you should rather create a third > module with 'auto_install' on "account_prepayment" and > "sale_payment_method", so when both are installed you get the tickbox "Use > prepayment accounts". > > > > -- > Guewen Baconnier > Business Solutions Software Developer > > Camptocamp SA > PSE A, CH-1015 Lausanne > Phone: +41 21 619 10 39 > Office: +41 21 619 10 10 > http://www.camptocamp.com/ >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-accounting Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-accounting More help : https://help.launchpad.net/ListHelp
