banking-addons-drivers team mailing list archive

[Luc De Meyer <luc.demeyer@xxxxxxxxx>]

Joel,

 

I don’t think that it is required to create new objects and hence make the data model more complex in order to bypass performance issues. 

 

We have one customer (still running V6.0) with a single bank statement exceeding sometimes 5000 lines (mostly card payments) and we could get it running by adding a flag into the context when importing the statements and bypassing a good amount of the standard ORM methods when this specific flag is in the context. Net result is that we process those statements in less than 2 minutes. We haven’t done any in depth analysis in this particular case to figure out exactly which of the ORM methods take up the most of the processing power but if you eliminate the account.voucher object and create the accounting moves and reconciliations while bypassing some of the constraints (which have to be there for data entry via the UI but make no sense in a batch import) than you’ll see major performance improvements.

 

The logic that we tend to use:

-          Import card payment statements into a bank statement (in some cases we need to add some logic in order to split the ‘amount paid’ and ‘bank expenses’ over 2 separate lines)

-          Create an accounting move per statement line (with reconciled moves for the account receivables and regular moves for the bank expenses)

-          Create an ‘internal transfer account’ move for the total amount 

 

On the bank statement where the amount paid by e.g. VISA is present, we book this amount also on that same ‘internal transfer account’ so that this can be reconciled with its counterpart in the ‘VISA import’ bank statement.

 

Kind Regards,

Luc

 

 

 <http://www.noviat.com/> www.noviat.com

Rusatiralaan 1, 1083 Brussel

+32 2 808 86 38

 



 

From: Banking-addons-drivers [mailto:banking-addons-drivers-bounces+luc.demeyer=noviat.be@xxxxxxxxxxxxxxxxxxx] On Behalf Of Joël Grand-Guillaume
Sent: maandag 13 oktober 2014 8:28
To: Bidoul, Stéphane
Cc: banking-addons-drivers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Banking-addons-drivers] Banking addons guidelines for 8.0 - a proposal

 

Hi Stéphane,



Thanks for this summary. I completely agree with this vision and the way you suggest to split the various repo:

- Payment

- Import

- Completion & Reconciliation

 

On our side, we're thinking about how we gonna move our work to v8. Our biggest trouble for us is about the volume of transaction we need to deal with. 

Currently we use the bank statement object to import not only the bank, but also the payment confirmation from other financial institution (such as VISA, Mast Card, Atos, ...). This lead to the creation of thousands of move today in v 7. 

So it may happened that we start a new module to cover this needs, basically :

 * importing the payment confirmation in a new object "Batch Line"(no account move generated this time)
 * matching the concerned SO/Invoice to run the completion (mostly the partner) on Batch Line

 * on bank importation of the amount paid by the financial institute (e.g. VISA), we'll have to match the N batch lines of payment confirmation concerned by the amount received. We'll override the standard mechanism so a bank statement line will be able to generate various move lines (in our case one by batch line). 
* finally, we'll create reconciliations with the moves of the concerned invoices.

Don't know if it's clear, but well, we'll post something more detailed about that. I just wanted to inform you.

In any case, I'm 100% with Stéphane's suggestion.

Best regards,

Joël

 

 

 







 

 

On Fri, Oct 10, 2014 at 6:15 PM, Bidoul, Stéphane <stephane.bidoul@xxxxxxxxx <mailto:stephane.bidoul@xxxxxxxxx> > wrote:

Hi,

 

Following the thread about the future of banking addons [1] and the comparison between the various frameworks [2], I would like to summarize the conclusions and lay out a proposal.

 

Three distinct and independent areas clearly emerge in banking addons:

1.	payment orders (credit transfer and direct debit)
2.	import of bank statements
3.	bank statement completion (enrichment) and reconciliation

Regarding payments, a clear majority voted to abandon OCA/account-payment in favor of the payment part of OCA/banking, and adding the eventual missing features there.

 

Regarding the import of bank statements, there was no clear vote, although there is a tendency to deprecate the bank statement part of OCA/banking. 

 

My understanding and opinion from [2] is that the most promising and future-proof track consists in using and extending in 8.0 a backport of the Odoo master branch (account_bank_statement_import).

 

If the community agrees on these conclusions, I would suggest the following as guidelines for managing the ports to 8.0:

*	deprecate OCA/account-payment (ie no 8.0 branch)
*	OCA/banking becomes the repository for payment interfaces

*	possibly renamed to OCA/bank-payment
*	only the payment part gets ported to the 8.0 branch (in progress [3] [4])

*	OCA/bank-statement-reconcile becomes the repository for statement completion and reconciliation

*	the statement import features in it are not ported to the 8.0 branch

*	a new repository named OCA/bank-statement-import is created

*	it hosts a backport of odoo master branch account_bank_statement_import 
*	as well as parsers and additional import features modules inspired by OCA/banking and OCA/bank-statement-reconcile 7.0

Looking forward to reading your feedback,

 

-sbi

 

[1] https://lists.launchpad.net/banking-addons-drivers/msg00096.html

[2] https://docs.google.com/spreadsheets/d/1R77W6xFFexM247mUen3N9uFacX-OZYtGcyP6HGgRjjU/edit?usp=sharing

[3] https://github.com/OCA/banking/pull/35

[4] https://github.com/acsone/banking/tree/8.0-refactor-account_banking_payment-sbi

 

Stéphane Bidoul |  <https://twitter.com/SBidoul> @SBidoul

Acsone sa/nv |  <http://acsone.eu/> http://acsone.eu/ | +32 2 888 3120 <tel:%2B32%202%20888%203120> 

 


--
Mailing list: https://launchpad.net/~banking-addons-drivers
Post to     : banking-addons-drivers@xxxxxxxxxxxxxxxxxxx <mailto:banking-addons-drivers@xxxxxxxxxxxxxxxxxxx> 
Unsubscribe : https://launchpad.net/~banking-addons-drivers
More help   : https://help.launchpad.net/ListHelp




-- 

 

camptocamp

INNOVATIVE SOLUTIONS

BY OPEN SOURCE EXPERTS

 

Joël Grand-Guillaume

Division Manager

Business Solutions

 

+41 21 619 10 28

 <http://www.camptocamp.com/> www.camptocamp.com