Fabien thanks for the explanations. I've look at account_voucher. But:
- it's not very clear to me what it does, especially the "post" button. I think this module could have a bit more of documentation. And as there are no demo data either here... - In account_payment we can select the payments of several different partners. In account_voucher we can select only one partner. We absolutely would need to deal with several payments in one record. Is that the "batch" feature you mention? If yes, that's something we need here in Brazil to develop the "boleto" support upon it. - An other blocker is: account_payment has bank account information. As soon as we emit XML/electronic payment orders, we would definitely need to be able to select a bank account with the required account information so we can export them in the XML (like owner of the account, codes of the account, agency etc, just like account_payment has). We would need that in account_voucher to be able to use it. - How account_voucher works with intermediary accounts? With "boletos" we don't need intermediary accounts, but a nice feature, of the yet complex bank statement/reconciliation of OpenERP is the ability to work with intermediary accounts. If you do ecommerce with Paypal fro instance, this is essential you can receive first on the intermediary account as the payment gateway tells the payment has been accepted and then you transfer the money on your account/reconcile after Paypall gives you the money. Will account_voucher works with those workflows? It seems important we don't multiply the payment user interfaces just because there is an intermediary account or not. So currently it's not clear at all if we can rely upon account_voucher. Could you please clarify, and give timeframe. We need to deliver that work by September 24th at most so we need to know in which direction we can go. Regards Raphaël Valyi Founder and ERP Consultant +55 21 3010 9965 http://www.akretion.com <http://www.akretion.com.br/> 2010/9/2 Fabien Pinckaers <[email protected]> > Hello, > > The account_voucher module in trunk is far better for handling customer > payments and vendor payments. The account_voucher has been made to > simplify the accounting of OpenERP which is too complex for most of the > people. To test it: > - do some customer invoices or sales recepit > - do some Sales Payment > > It's not decided yet, but it may replace the account_payment module in > trunk, with a very small improvement to allows him to work by batches > (or print/send batches). (group a list of payments) > > Moreover, this module will allow us to simplify the whole OpenERP > reconciliation processes: > - Pay wizard on an invoice: simply replaced by an act_window that > opens a Sales Payment with default values. > - Reconciliation on bank statement lines: simply replaced by a > many2one to a Sales Payment that will manage the generation of the > entries and the reconciliation. > In total, the review of the Sales Payment system allowed to remove 1000 > lines of code in the accounting and have a simpler and better way to > manage payments and reconciliations. > > The Sales Payment is very good to manage: > - partial payments > - complex reconciliations > - credits and outstanding payments > > The vendor payment is the same, but I did not had the time to validate > the new developments yet. We still have a few work on it, in order to > validate these new developments but it's already useable. > > All those are based on one single object: account.voucher > > Thanks, > > Raphaël Valyi wrote: > > Hello accounting expert, > > > > For the Brazilian localization of OpenERP, we need to make it easier for > > companies to register the B2B bank payment they should emit and receive. > > It seems we better reuse the account_payment module (official addons) > > for that. > > > > But we can't exactly reuse it directly because account_payment is only > > meant for payables (at least when filtering invoice entries to make > > payment order lines). > > However, in Brazil at least, when a company expects B2B payments, a > > popular method is to register them at the bank, this makes > > reconciliation easier and banks > > will reclaim your money in time for you, so it's used in both ways. > > See http://pt.wikipedia.org/wiki/Bloqueto_de_cobran%C3%A7a > > > > So we would need a change in account_payment to use it also for > receivables. > > > > Actually this is what is done in the account_payment_extension from > > stable extra addons 5.0 (by Zikzakmedia). A payment order has now a type > > payable/receivable + dedicated menu. > > > > However, we are a bit cautious about making the Brazilian localization > > depend upon that account_payment_extension module. > > Indeed: > > - account_payment_extension seems to do a lot more than we need > > immediately at least, it also does it in a sub-optimal way wherever > > account_payment lacks extension points. > > - how reliable is it? Who uses it here for which countries? > > - it has been done for v5, we are assuming a Brazilian localization for > > OpenERP v6+ essentially, we can't really afford to port the module to v6 > > alone for features we won't use. > > - has it has been done for v6, are there features that would be better > > refactored for v6 given the changes in v6? > > - may be it has been done for v5 because v5 was frozen as it was and > > unusable, but the situation with v6 might be different, may be we have a > > chance to contrib a minimal refactoring in v6 account_payment before a > > freeze? > > > > > > At the end, I'm proposing we move the receivable/payable two ways > > feature of account_payment_extension to account_payment in v6, what do > > you think about that? > > Would like to hear OpenERP S.A. view on that as they are the one > > making/blocking merges at the end. > > > > > > Regards, > > > > > > Raphaël Valyi > > Founder and ERP Consultant > > +55 21 3010 9965 > > http://www.akretion.com <http://www.akretion.com/> > > > > <http://www.akretion.com.br/> > > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 > > > -- > Fabien Pinckaers > CEO OpenERP > Chaussée de Namur 40 > B-1367 Grand-Rosière > Belgium > Phone: +32.81.81.37.00 > Fax: +32.81.73.35.01 > Web: http://openerp.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
