openerp-expert-accounting team mailing list archive
-
openerp-expert-accounting team
-
Mailing list archive
-
Message #00519
Bank Statements & bank transfers between two OpenERP bank accounts
Hi OpenERP Accounting Experts! :)
Today we have one question that we would want to discuss here (though
we'll be posting the question and the possible answers
<https://answers.launchpad.net/openobject-addons/+question/113211> to
the LaunchPad Answers tracker too)://
*How do you manage bank transfers between your own bank accounts (two
bank accounts of your company) with the **OpenERP **bank statements?
(same transaction on two bank statements, just one accounting move)
*
Ok, first of all, before anybody mentions it: yeah, we did RTFM
(http://doc.openerp.com/book/3/3_7/accounting_entries.html#managing-bank-statements)
and we didn't find anything useful about this. We also checked the
forums, the answers, the bugs..., and everything we could find was this
unreplied post about a transfer between two bank accounts with different
currency: http://openobject.com/forum/topic16650.html
<http://openobject.com/forum/topic16650.html?highlight=bank>
/Ferdinand @ Chricar: We wanted to try your ChriCar branch demo
(http://www.chricar.at/ChriCar/OpenERP.html) to check wether you had
an alternative to this problem, but the bank statement form view
fails (duplicated field or something like that)./
---------------------------------------------------
Context
What do we mean with "bank transfers between your own bank accounts"*?:
/ * By the way, Spanish banks even have a special name for this kind
of transfer between your own accounts, they call them "Traspaso", while
normal transfers to other partners are called "Transferencia" (lit.
transfer)./
* We have two (or more) bank accounts, for example A and B. /Or a
bank account A plus a (petty) cash account C./
* We move some money from A to B. /Or we withdraw some money from A
and deposit it into C./
//
On the bank account A statement we would have an entry like this:
Amount
Comment
-1000
Transfer to B (withdrawal)
On the bank account B statement we would have this:
Amount
Comment
+1000
Transfer from A (deposit)
On the accounting side, we would have just one move (with two lines)
like this:
Debit
Credit
Comment
57200001 Bank account A
1000
Transfer to B (withdrawal)
57200002 Bank account B 1000
Transfer from A (deposit)
(Note: I'm using account codes from the Spanish Chart of Accounts as
reference)
The problem
So, what's the problem here? Simple: _OpenERP generates a duplicated
account move if we reflect the same transaction on two bank statements_ :(
If we follow the manual, the users are encouraged to use the bank
statements tool ("/Open ERP provides a visual tool for managing bank
statements that simplifies data entry into accounts. As soon as a
statement entry is validated the corresponding accounting entries are
automatically generated by Open ERP/") to enter financial transactions:
* We would configure two financial journals in OpenERP "Journal A"
and "Journal B", and set the default debit/credit accounts in each
of the journals (for example the accounts"57200001" for Journal A,
"57200002" for Journal B).
* We would create a bank statement in OpenERP for the first bank
account:
o Create the statement and select the "Journal A".
o Set the initial balance, for example 2000, and the final
balance, for example 1000.
o Reflect the real bank statement lines into the OpenERP bank
statement: Either create the statement lines by hand, or
import them (on the Spanish localization we have a tool to
import the standard N43 format that Spanish banks use). In
the example we would create a "Transfer to B (withdrawal)
-1000" line.
o Confirm the statement (the final balance matches).
A ledger post is created by OpenERP, when we confirm the
bank statement, moving the amount from "57200001 Bank
account A" (credit) to "57200002 Bank account B" (debit).
* We would create a statement for the second bank account:
o Create the statement and select the "Journal B".
o Set the initial balance, for example 5000, and the final
balance, for example 6000.
o Reflect the real bank statement lines into the OpenERP bank
statement: In the example we would create a "Transfer from A
(deposit) +1000" line.
o Confirm the statement (the final balance matches).
A ledger post is created by OpenERP, when we confirm the
bank statement, moving the amount to "57200002 Bank
account B" (debit) from "57200001 Bank account A"
(credit). That is, a move with different line order, but
equal to the previous ledger post: _We just duplicated
the move in our accounting!
_
That's where we are stuck: We couldn't find a way to avoid this "double
ledger post problem" on bank transfers between own bank accounts.
The solution?
We think that we are missing either:
* A way to set that a bank statement line should not be reflected
into the accounting (no post should be created for this line when
the statement is confirmed).
* Or a way to set that a bank statement line is part of the same
transaction as other line in other bank statement (a one2many
reference to another bank statement line), and when any of the
bank statements is confirmed, create the ledger post either if:
o The counterpart bank statement is from another company (just
to avoid problems with multicompany setups).
o Or the account move hasn't been created for the counterpart
statement line (that is, we would check if the other
statement has been confirmed, and create the account move
only for the first statement being confirmed).
So... What do you think about this problem? Anybody got a way to
work-around it? What do you think about the proposed solutions?
--
Borja López Soilán
borjals@xxxxxxxxx
Pexego Sistemas Informáticos S.L.
Avenida de Magoi 66 - 27002 Lugo (España)
Tel./Fax 982801517
http://www.pexego.es
AVISO LEGAL - CLÁUSULA DE PRIVACIDAD
Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es usted el destinatario indicado, queda informado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
Follow ups