Community mailing list archives
Re: Chart of accountsby
On 2014-12-12 13:32, Jordi Ballester Alomar wrote:<blockquote cite="mid:CALVkZEd0ReA=WvDc+DX7U84rPC9vNT1K=2Ym7iCPmuywQWS0Vw@mail.gmail.com" type="cite">
Cost Centers in Odoo are analytic accounts.
please keep in mind that cost centers are not mandatory for P&L in standard odoo
a solution can be found here
Allows to define analytic accounts and their usage for accounts. It is especially IMPORTANT to assign default analytic accounts to all P&L accounts which are created automatically. *init* will set all P&L accounts to have mandatory analytic accounts and all other accounts to not allowed. checks implemented: * main - will check/prohibit everything what comes in wrong from other modules * ./account/account_move_line.py * other checks implemented * ./account/account_bank_statement.py * ./account/invoice.py potentially important * ./purchase/purchase.py * ./sale/sale.py
<blockquote cite="mid:CALVkZEd0ReA=WvDc+DX7U84rPC9vNT1K=2Ym7iCPmuywQWS0Vw@mail.gmail.com" type="cite">
For every transaction that is going to impact on the GL the user should enter the analytic account.First activate the analytic accounting under settings > Configuration > Accounting:
Then in transactions such as PO you are able to enter the analytic account that should receive the cost:
The analytic account is finally entered in the Account Journal Items.
The report "Analytic Entries Analysis" provides a basic report of costs and revenues allocated to your analytic account:
On Fri, Dec 12, 2014 at 12:39 PM, John Pia Jr <email@example.com> wrote:
I am seeking some feed back as to how other businesses go about managing a very large chart of accounts.
Let me first explain what we have been doing for years (I Dont necessarily think that this method is still the best choice being as we are operating on a very outdated set of software platforms)
Basically we have a list of a couple hundred different types of GL codes. Each of those GL codes must be related to a cost center(locations). Currently we create 1 gl code location. For example let's take the GL code for repair and maintenance, within that code there are 5 sub codes, each one of those 5 sub codes need to be related to a location.
GL = x
Sub gl = Y
Sub gl 2 = z
Location 2 = L2
Locations 3 = L3
Here are a list of gl codes that are created as a result from the above.
The entire purpose of creating a separate GL code for each location is only for reporting purposes. My accounting department likes to be able to see on a trial balance report all of me codes broken down by location. To me this is a very old way of doing things
What I would like to do is I would like to be able to give my accountant that same break down of transactional information based on location, but rather than use the GL code to represent the location I want to know if it is possible to use the location being the source or destination location within any transaction to create that relationship between GL code and location. By doing this it will allow me to expedient really decrease the amount of GL codes we currently have.
Finally I would like to ask the community if anybody would be willing to share with me some of the basic accounting reports offered by odoo that are of much larger companies. For example we are a 200 million dollar organization with 8 locations and 3800 GL codes. I would like to have a better understanding as to how others among our size handle the above question.
What I'm looking to do is get rid of the need to have to identify a location within a GL code.
If I have not been clear please let me know, and thank you in advance for any help
Jordi Ballester Alomar
Tel: (+34) 629530707
Twitter: @jbeficent_erp | Skype: jordi.ballester
Este email contiene información confidencial. El contenido de la misma se encuentra protegido por Ley. Cualquier persona distinta a su destinatario tiene prohibida su reproducción, uso, divulgación o impresión total o parcial. Si ha recibido este mensaje por error, notifíquelo de inmediato al remitente y borre el mensaje original junto con los ficheros anexos.
This message contains confidential information and it is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete it from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.