Hello Cedric,
thank you for taking the time to read and answer my blatant feature
request. I gather that a cash management module is currently not
planned. Please note that I would be very interested in an EBICS
implementation. Also if other companies are interested in sponsoring
such a thing. The company I am in touch with is doing property
management. As such they have one to two bank accounts for each
individual unit they manage. Some of them are single appartments, some
are rental houses, some are condos. A couple hundred bank accounts
across twenty or so banks. With a lot of money coming in (rent,
utlities, ...) and going out (utlities, services, repairs, ...).
Whichever ERP they end up using, it has to be able to do cash management
of some sort. And while I am talking about feature requests, some
intelligent matching would be nice. For example, if you have an
outstanding invoice and an incoming money transfer that matches the
invoice number and amount it could consider the invoice paid.
Lastly I would love to see some nifty security features in a cash
management module. I did some data entry myself and one thing that
really bugs me is the checking of the bank account number. Because
it has to be 100% right. Otherwise the money is going someplace
else. And it can be very difficult to get it back. We will have much
longer bank account numbers (IBAN) in Germany soon and this task
will get harder. Anything to make that task easier and safer against
errors would be much appreciated. Wikipedia says [3] that IBAN will
be mandatory from 2014 for all EU countries.
Yes of course, a library like ibanlib[1] could be used.
But more over, the account numbers should be stored on the Party to
prevent typing it multiple times.
[1] http://pypi.python.org/pypi/ibanlib
Storing the bank account numbers on the Party is pretty much a given
IMHO. I was thinking of more "advanced" features. For example: Every
single account number used for transfers is saved into a list. And every
time someone initiates a transfer, this list is checked. If the account
number is not on the list already, a popup (optional feature that can be
turned off) would then warn the user, that he is transferring to a brand
new account and should check again. EBICS has some built in security
features, where transfers could require two signatures, one party could
sign the transfers, upload them and then have the other party read them
(perhaps in a different location) and sign them with their key for
approval. Since cash management is so sensitive, Tryton could/should
make use of the role model to be able to subtly adjust who can do what
and impose volume limits (a certain user can only transfer up to a
certain sum, or needs approval from another user for sums greater than x
amount) approved bank accounts (a user can only transfer money to a
number of accounts) or limits on actions, such as being able to only
touch certain accounts, or only see bank statements from certain
accounts and not being able to transfer money. Especially the approval
stage (like EBICS) is vital for any cash management. One or several
users could be allowed to enter transfers and then one or several users
would need to sign off on them. This could/should be independant of the
method of transfer, be it Paypal, bank transfer or other.
Thank you,
Malte
--
[email protected] mailing list
