Contributors

• Re: The Concept of "Charge"

  
  

  Hi Kitti,

  
  

  with what you describe:

  - it seems you could use products. The products in the approval request may not be the same as the products in the PO, but can be in the same category, hence they will be mapped to the same GL account

  - to compare the actual amount and budget amount for an approval request, you could as Daniel mentioned, use analytic accounts.

  
  

  Or simply make sure that on all the purchase order/vendor bills, that they have the same reference number (budget number) so you can query and get the comparison budget/actual per product category

  
  

  Less developments...

  my 2 cents.

  Cheers

  
  

  On Mon, 15 Jun 2020 at 16:47, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
  

  Thank you to all for the opinion.

  
  

  I came across the "Charge" because I have the need to do comparing report between "planned budget" and "resulting expense" with "activity based".

  
  

  • 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.

  With that, we can compare "Plan" and "Result" in activity terms.

  
  

  I might have messed up my requirement with the "Charge" or "Product" concept. With you guys answer I think I am more cleared myself.

  
  

  I will have create the "Activity" matrix, and deploy them on both Plan and Resulting document. Will make it the PR to OCA, although I am not sure it will be generic enough.

  
  

  Thank you all!

  
  

  
  

  ---

  by dominique.k - 12:26 - 15 Jun 2020

• Re: The Concept of "Charge"

  Kitty,
  
  What you describe looks like Analytical Accounts.
  I could see those items as AAs, and each would have budgets and real expenses assigned.
  In case you need multidimension (example: expense type + department or segment), you need to use Analytic Tags.
  
  Consider if Analytic Account fit your use case before implementing Activities.
  And if you do implement Activities, consider building them on top of Analytic Accounts.
  
  Thanks
  Daniel
  
  
  

  On 15/06/2020 09:47, Kitti Upariphutthiphong wrote:
  

  Thank you to all for the opinion.

  
  

  I came across the "Charge" because I have the need to do comparing report between "planned budget" and "resulting expense" with "activity based".

  
  

  • 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.

  With that, we can compare "Plan" and "Result" in activity terms.

  
  

  I might have messed up my requirement with the "Charge" or "Product" concept. With you guys answer I think I am more cleared myself.

  
  

  I will have create the "Activity" matrix, and deploy them on both Plan and Resulting document. Will make it the PR to OCA, although I am not sure it will be generic enough.

  
  

  Thank you all!

  
  

  On Mon, Jun 15, 2020 at 10:26 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:
  

  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,

  
  

  Dominique KON-SUN-TACK  [Project Manager]
  

  Elico Solutions (Singapore/Shanghai/Shenzhen) 

  Odoo Gold Partner, best Odoo Partner 2014 for APAC

  
  

  Mobile: + 65 8502 2399

  Skype: dominique_elico

  Email: dominique.k@elico-corp.com.sg

  Website: www.elico-corp.com
  

  
  

  
  

  
  

  
  

  On Mon, 15 Jun 2020 at 10:57, Richard deMeester <richard.demeester@willdooit.com> wrote:
  

  Hi

  
  

  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...

  
  

  
  

  
  

  	Richard deMeester Senior Development Analyst WilldooIT Pty Ltd E: richard.demeester@willdooit.com 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 <kittiu@ecosoft.co.th>
  Sent: Friday, 12 June 2020 8:21 PM
  To: Contributors <contributors@odoo-community.org>
  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,

  https://www.chuckboecking.com/adempiere-open-source-erp-power-charge/

  
  

  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?

  
  

  Kitti

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  
  

  ---

  by Daniel Reis - 11:30 - 15 Jun 2020

• Re: The Concept of "Charge"

  Thank you to all for the opinion.

  
  

  I came across the "Charge" because I have the need to do comparing report between "planned budget" and "resulting expense" with "activity based".

  
  

  • 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.

  With that, we can compare "Plan" and "Result" in activity terms.

  
  

  I might have messed up my requirement with the "Charge" or "Product" concept. With you guys answer I think I am more cleared myself.

  
  

  I will have create the "Activity" matrix, and deploy them on both Plan and Resulting document. Will make it the PR to OCA, although I am not sure it will be generic enough.

  
  

  Thank you all!

  
  

  On Mon, Jun 15, 2020 at 10:26 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:
  

  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,

  
  

  Dominique KON-SUN-TACK  [Project Manager]
  

  Elico Solutions (Singapore/Shanghai/Shenzhen) 

  Odoo Gold Partner, best Odoo Partner 2014 for APAC

  
  

  Mobile: + 65 8502 2399

  Skype: dominique_elico

  Email: dominique.k@elico-corp.com.sg

  Website: www.elico-corp.com
  

  
  

  
  

  
  

  
  

  On Mon, 15 Jun 2020 at 10:57, Richard deMeester <richard.demeester@willdooit.com> wrote:
  

  Hi

  
  

  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...

  
  

  
  

  
  

  	Richard deMeester Senior Development Analyst WilldooIT Pty Ltd E: richard.demeester@willdooit.com 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 <kittiu@ecosoft.co.th>
  Sent: Friday, 12 June 2020 8:21 PM
  To: Contributors <contributors@odoo-community.org>
  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,

  https://www.chuckboecking.com/adempiere-open-source-erp-power-charge/

  
  

  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?

  
  

  Kitti

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  ---

  by Kitti Upariphutthiphong - 10:46 - 15 Jun 2020

• Re: The Concept of "Charge"

  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,

  
  

  Dominique KON-SUN-TACK  [Project Manager]
  

  Elico Solutions (Singapore/Shanghai/Shenzhen) 

  Odoo Gold Partner, best Odoo Partner 2014 for APAC

  
  

  Mobile: + 65 8502 2399

  Skype: dominique_elico

  Email: dominique.k@elico-corp.com.sg

  Website: www.elico-corp.com
  

  
  

  
  

  
  

  
  

  On Mon, 15 Jun 2020 at 10:57, Richard deMeester <richard.demeester@willdooit.com> wrote:
  

  Hi

  
  

  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...

  
  

  
  

  
  

  	Richard deMeester Senior Development Analyst WilldooIT Pty Ltd E: richard.demeester@willdooit.com 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 <kittiu@ecosoft.co.th>
  Sent: Friday, 12 June 2020 8:21 PM
  To: Contributors <contributors@odoo-community.org>
  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,

  https://www.chuckboecking.com/adempiere-open-source-erp-power-charge/

  
  

  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?

  
  

  Kitti

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  ---

  by dominique.k - 05:26 - 15 Jun 2020

• Re: The Concept of "Charge"

  Hi

  
  

  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...

  
  

  
  

  
  

  	Richard deMeester Senior Development Analyst WilldooIT Pty Ltd E: richard.demeester@willdooit.com 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 <kittiu@ecosoft.co.th>
  Sent: Friday, 12 June 2020 8:21 PM
  To: Contributors <contributors@odoo-community.org>
  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,

  https://www.chuckboecking.com/adempiere-open-source-erp-power-charge/

  
  

  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?

  
  

  Kitti

  _______________________________________________
  Mailing-List: https://odoo-community.org/groups/contributors-15
  Post to: mailto:contributors@odoo-community.org
  Unsubscribe: https://odoo-community.org/groups?unsubscribe
  

  ---

  by Richard deMeester <richard.demeester@willdooit.com> - 04:55 - 15 Jun 2020

  2 attachments 2 attachments

  Outlook-b5slv5yq.png

  Outlook-5r1dhd2r.jpg

2 more replies