openerp-brazil-team team mailing list archive

[Raphaël Valyi <rvalyi@xxxxxxxxx>]

Segue aqui um email para lidar melhor com os boletos.

Atts.

---------- Forwarded message ----------
From: Raphaël Valyi <rvalyi@xxxxxxxxx>
Date: 2010/8/31
Subject: account_payment, account_payment_extension: are you using it,
refactoring?
To: openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
Cc: Fabien Pinckaers <fp@xxxxxxxxxxx>, Renato Lima <
renato.lima@xxxxxxxxxxxxxxx>, Jordi Esteve <jesteve@xxxxxxxxxxxxxxx>


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.br/>