banking-addons-drivers team mailing list archive

[Stefan Rijnhart <stefan@xxxxxxxx>]

On 28-07-13 15:02, Bidoul, Stéphane wrote:
> Hi list,
>
> I'm getting more and more interested in the banking addons and, more 
> important, we will hopefully soon have customers with similar 
> requirements and therefore the possibility to contribute some features 
> or enhancements.
>
> Now I'm trying to find my way and I thought you might help me choose 
> the right path. Would you mind looking into a few questions?
>
> When I tried to use the sepa credit transfer module last month (using 
> lp:~therp-nl/banking-addons/ba7.0-future), I noticed it pulled 
> dependencies which modified the behaviour of bank statements. In my 
> case, it was a show stopper, since I was using other bank statement 
> related modules which were incompatible.
>
> So my first question is: is there any particular reason that payment 
> and bank statements are tied together? Would it be a good idea to 
> somehow split  the account_banking module in two parts: one for 
> payment and one for bank statements?

Hi Stéphane,

we are trying to split up functionality into separate models with each 
new release. For 7.0, we split off the payment module so that if you 
only use banks statement imports, you do not get the payment part. Now 
the payment part in 7.0 does the following:

1 generate the payment export files. The formats are split off into 
various modules already
2 reconcile the invoices from the payment order with a move on a 
clearing account. Payment order goes into state 'Sent'
3 add an option in the bank statement reconciliation wizard to match a 
payment order. In some cases the bank statement import matches the 
payment order automatically. When the bank mutation is confirmed, the 
move on the clearing account is reconciled and the payment order 
workflow is triggered to go into state 'Done'.

Splitting off [1] should be easy and addresses your current need.
Splitting up [2] from [3] is a little harder as there is no base 
abstraction for performing additional actions when a bank statement is 
confirmed. This is provided by the account_banking module and that is 
why you get all this dependent functionality when you install the 
payment module. We are open to refactoring but I do not have a clear 
idea of what it could look like yet.

> My second question is related to bank statements. We are considering 
> implementing Belgium CODA bank statement support in banking-addons to 
> benefit from advanced reconciliation features for e-commerce (at this 
> stage, both banking-addons-70 and bank-statement-reconcile-70 are 
> apparently incompatible with the official l10n_be_coda).
>
> To implement such a CODA parser, I have difficulties to chose between 
> the banking-addons approach and the bank-statement-reconcile way. I 
> understand both approaches are incompatible? Is that correct? I also 
> understand there are also longer terms goals of merging them. Are 
> there already any concrete plan in this regard?

The modules are currently incompatible. The long term goal is to merge 
but it is not concrete yet. All I can say is that I did a large 
refactoring and cleanup for 7.0, hoping that it will allow us to proceed 
in the direction of compatibility in future releases.

Maybe this is a good opportunity to confess that I am not that familiar 
with the bank-statement-reconcile aproach yet. To get me started, maybe 
someone from Camptocamp can take my use case of payment order 
reconciliation and indicate if this could fit into their framework at all?

> Finally, I saw in OpenDays slides that OpenERP SA has plans to improve 
> banking support in v8. Is there any relationship with the 
> banking-addons efforts, and does one influence the other?

There is no relationship. From what I saw, the changes are mainly 
cosmetic (expanding a bank mutation to show the voucher lines that it 
reconciles). It will not affect the banking addons much if we choose the 
simple option just to replace it with the current reconciliation wizard. 
Maybe the new interface development that is driven by this change will 
allow for a more subtle integration of the banking addons with standard 
voucher functionality but I have not had the opportunity to look at the 
code.

Cheers,
Stefan.

--
Therp - Maatwerk in open ontwikkeling

Stefan Rijnhart - Ontwerp en implementatie

mail: stefan@xxxxxxxx
tel: +31 (0) 614478606
http://therp.nl
https://twitter.com/therp_stefan