[ 
https://issues.apache.org/jira/browse/OFBIZ-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872548#comment-13872548
 ] 

Pierre Smits commented on OFBIZ-5476:
-------------------------------------

I disagree.

This is not about that it should go where existing services and functions are 
based, solely on the word 'expense'. If that were the case everything would be 
in accounting as everything is related to expense, cost or income and. Even 
domain specific functions as goods transfer, execution of production run tasks, 
or time registration.

This is about where the ownership of the business processes lie and the cost of 
ownership are borne. In that domain this should be covered. 

A good example explaining this is the following. Suppose accounting (the 
department) is owner of the solution and pays for its maintenance and support. 
As soon as e.g. HR decides that due to changed circumstances  (whatever they 
may be) changes must be effected in the solution, accounting will have to bear 
those expenses and will dictate the changes. Irrespective of whether this is in 
line with the requirements and wishes of HR. But HR will be expected to pay for 
the implementation, support and maintenance.. And the one who pays owns. 

Moreover,  accounting doesn't care about how the business processes regarding 
expense declarations and approval are executed as long as the output of these 
processes are in line with general and company specific accounting principles, 
legislation and that that output can be processed with as minimal effort as 
possible with regards to debt registration and mitigation (payment) ,gl 
transactions and cost accounting. And the reporting thereof.



> Create component in OFBiz JIRA
> ------------------------------
>
>                 Key: OFBIZ-5476
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5476
>             Project: OFBiz
>          Issue Type: Sub-task
>            Reporter: Pierre Smits
>
> Create a new component in JIRA to:
> 1. capture requirements (at first)
> 2. capture other issues pertaining bugs and improvements (a.o.)
> related to the Expense solution.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to