← Back to team overview

openerp-expert-accounting team mailing list archive

Re: anglo-saxon stock accounting in v6

 

I believe Anglo-saxon module is imperative to realtime inventory costing
around the world.
The problem though is the anglo-saxon module has bugs for standard and for
average costing, and does not do the correct journals in several senarios.
I have not heard of Prescriptive or Descriptive accounting, but use the
nearly globally accepted IFRS and the older GAAP standards.
Read this link:
http://feedback.openerp.com/forums/77459-general-improvements/suggestions/1944011-make-openerp-inventory-valuation-ifrs-compliant
Not only does the anglo-saxon module not work in multi-company but neither
does it do the correct journals in a single environment.
I agree that the field labels are confusing and also mixed up. The
anglo-saxon module needs some serious work.
Hope this helps.
Let me know if you are able to solve the issues with anglo-saxon.
kind regards,
Michael
openrevolution.co.za




On Wed, Oct 26, 2011 at 12:01 PM, Vadim Chobanu <vadim@xxxxxxxxxxxxxxx>wrote:

> Yes, I agree that module is redundant now with v6. And even if it was
> still needed the naming (Anglo-Saxon Accounting) is misleading – most
> modern books on accounting would refer this as  Prescriptive (France etc)
>  or Descriptive accounting (UK etc).****
>
> ** **
>
> Prescriptive accounting stock rules: Some countries ( Madagascar for one i
> have seen this summer) have in their fiscal legislation that stock
> purchases should show as a purchase that is to hit the PNL and then do the
> stock variation at the month end or realtime if the system allows) Probably
> this is the same for France as this is where most of Madagascar laws are
> derived from.****
>
> Descriptive accounting: No-one is prescribing your COA or through what
> account you record you moves as long as your statements represent a true
> and fair view. So conventionally in the UK we do record the stock purchase
> directly on the balance sheet in the stock account and then when you sell
> goods, you will do the CR stock, DR COS****
>
> ** **
>
> For this matter, in OpenERP, a correctly configured product can post the
> correct journal entries using both principles – prescriptive or descriptive
> and you don’t need the anglo-saxon module for that – it is just introducing
> confusion.****
>
> ** **
>
> ** **
>
> Regards,****
>
> ** **
>
> Vadim Chobanu
> M: +44 7939230959****
>
> ** **
>
> ** **
>
> [image: logo_email]****
>
> -------------------------------------------------------------------------
> Information in this email is confidential and may be privileged.
> It is intended for the addressee only. If you have received it in error,
> please notify the sender immediately and delete it from your system.
> You should not otherwise copy it, retransmit it or use or disclose its
> contents to anyone.
> Thank you for your co-operation.
> -------------------------------------------------------------------------*
> ***
>
> ** **
>
> ** **
>
> ** **
>
> *From:* openerp-expert-accounting-bounces+vadim=
> smartmode.co.uk@xxxxxxxxxxxxxxxxxxx [mailto:
> openerp-expert-accounting-bounces+vadim=
> smartmode.co.uk@xxxxxxxxxxxxxxxxxxx] *On Behalf Of *Frédéric Clementi
> *Sent:* 26 October 2011 10:34
> *To:* openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
> *Subject:* [Openerp-expert-accounting] anglo-saxon stock accounting in v6*
> ***
>
> ** **
>
> Hello,****
>
> ** **
>
> We are testing the anglo-saxon stock accounting entries in v6 with the
> dedicated module.****
>
> ** **
>
> First feeling, it is impossible to get correct entries.See below :****
>
> ** **
>
> ** **
>
> ** **
>
> *Flow :*****
>
> Puchases of 1 CPU1 at 120****
>
> Sales of 1 CPU1 at 190****
>
> CPU1 std cost 100****
>
> *Event*****
>
> *account_id*****
>
> *journal_id*****
>
> *debit*****
>
> *credit*****
>
> Sales invoice****
>
> DEBTORS****
>
> Sales Journal****
>
> 190****
>
> EXPENSES****
>
> Sales Journal****
>
> 100****
>
> ???****
>
> COGS****
>
> Sales Journal****
>
> 100****
>
> ???****
>
> SALES****
>
> Sales Journal****
>
> 190****
>
> stock out****
>
> INVENTORY****
>
> Stock Journal****
>
> 100****
>
> COGS****
>
> Stock Journal****
>
> 100****
>
> Purchases invoice****
>
> CREDITORS****
>
> Expenses Journal****
>
> 130****
>
> PRICE VARIANCE (Purchase Price – Std Price)****
>
> Expenses Journal****
>
> 30****
>
> GRNI****
>
> Expenses Journal****
>
> 100****
>
> stock in****
>
> GRNI****
>
> Stock Journal****
>
> 120****
>
> Valued at PO price ! Instead of Std price****
>
> INVENTORY****
>
> Stock Journal****
>
> 120****
>
> Does anyone knows about this issue ?****
>
> - Stock in entry is valuated at PO price....which is wrong ****
>
> ** **
>
> ** **
>
> - I do not understand what the module anglo saxon accounting modify the sales invoices entry****
>
> - There is a name mix-up in the account properties : stock variation is in fact the inventory and stock is teh stock valuation...****
>
> Many thanks for you help****
>
> ** **
>
> Frédéric CLEMENTI
> Business Solutions
> Camptocamp SA
> Tel : + 41 (0)21 619 1041
>
> ****
>
> ** **
>
> http://www.camptocamp.com
>
> ****
>
>
>  <frederic.clementi@xxxxxxxxxxxxxx>****
>
> ** **
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-accounting
> Post to     : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-accounting
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References