Contributors mailing list archives
Re: The Concept of "Charge"by
- At the time of Budget Planning, it is for "End Users", so things must make sense for them, and accounting code is not. User wants to plan with "Activity based" (i.e., traveling by land, traveling by air, training inhouse, training aborad, etc., which they map with an account code)
- At the time of PR, the "Product" is not even chosen yet, and the user will be using "Activity" to make purchase request,
- Only at the time of PO and Invoice that, "Product" and "Accounting Code" is viable. Still the "Activity" matrix need to be there too.
If you consider odoo accounting alone, using products is a perfectly fine solution.Problem is when you create an invoice from a sales order. You can't just swap the products for accounting purposes. (You don't have the choice for the product)Then if you need to change the account, or the tax, unless you want the accountant to review each invoice line (and you can end with 30 lines each time), you need some sort of automation. As of today, the default mechanism is the "fiscal position"...Cheers,On Mon, 15 Jun 2020 at 10:57, Richard deMeester <email@example.com> wrote:
In the Accounting package I was previously involved in writing, they used the concept of a "dissection" to hide the account number complexities - it had account numbers, default descriptions, linked tax codes, etc, and could be used directly in invoices. The idea was to bridge the gap between those encoding the information from the knowledge required to accurately map it to the General Ledger.
In Odoo, if the information is not coming from a Sales Order or Purchase Order, then just using a (dummy or otherwise) product on a customer invoice line is a solution - and could be unticked for can be sold / can be purchased. Otherwise, it could be set up as a service.
I like the "cleanliness" of a separate concept to bring in the information which avoids the need for dummy products, but most clients don't mind lumping them in to their products, and don't want different areas to maintain it all...
Senior Development Analyst
WilldooIT Pty Ltd
M: +61 403 76 76 76
P: +61 3 9135 1900
A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
Making growth through technology easy
DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
From: Kitti Upariphutthiphong <firstname.lastname@example.org>
Sent: Friday, 12 June 2020 8:21 PM
To: Contributors <email@example.com>
Subject: The Concept of "Charge"Dear contributors,
Coming from other ERPs, there is a concept of Charge, which is very useful. You can read it here,
From time to time, we will face situations where only "Charge" is suitable (compared to using product or direct account selection).Note: some time it is called "Activity".
Anyone heard about the "Charge" concept before?