On 26 juin, 15:50, Cédric Krier <[email protected]> wrote: > On 26/06/12 15:03 +0200, Rom1 wrote: > > > On Tue, Jun 26, 2012 at 2:41 PM, Cédric Krier <[email protected]> wrote: > > > > On 26/06/12 14:25 +0200, Rom1 wrote: > > > > On Tue, Jun 26, 2012 at 12:32 PM, Cédric Krier <[email protected] > > > >wrote: > > > > > I mean the "Bank Account" Model must contains a list of "Account > > > Number" > > > > > with a type and the corresponding required fields. > > > I'm not sure, I understood correctly. What do you have in the O2M ? > > account > > ->RIB > > ->IBAN > > ->any account number > > This one. > > > > I think a "Bank account" should have an address but it should be > > > investigated to know what is the common form for it. > > > > I don't know for other countries, but in France, you have a repos for each > > bank code/branch code with the address, you don't specify the address each > > time you enter a new RIB, as it is the same for all the customer of the > > branch. I suppose it's the same wherever you have a branch code. But you'll > > need the country first the restrict the search, because branch code are > > only unique per country. > > Indeed, I think the best is to just link the bank account to the bank (a > party) and to an address of the party. >
I did something here: https://github.com/sampaccoud/tryton-bank So if we want to allow storing different numbers for a same bank account I can refactor to make a separate object for the bank number. Then we can add several account numbers to a bank account. But I don't think it is necessary because a given bank account only works with a given number. RIB and IBAN are just the same thing with a different checksum... The way I did the account number is very generic and we can write as many methods to validate and split the account number depending on the country case... Looking forward to your comments / pull requests. -- -- [email protected] mailing list
