Is Act of Remuneration intended to cover acts of compensating contractors? #727
Replies: 3 comments
-
@gregfowlerphd Contractors are party to an Agreement and are compensated based upon the terms of the Agreement alone. In the real world, it is handled as a business-to-business (or party-to-party) interaction. Some tax regulations, contractual terms or grant stipulations require the contractor to handle payments to Person/Humans for "Acts of Human Labor" in a specified manner. So a Contractor seems to not be a "Person" at all, but is a business organization which is paid according to a contract and then carries out its own payment of Persons. As an aside... I am a little concerned about the term "purchasing" because employment is an internal activity within an organization. Purchasing is usually a business activity that is external to an organization. Very different for accounting purposes... And - I personally feel that employees are compensated (paid) for services rendered and not purchased....🤔 Investopedia UN - International Labour Organization 1951 |
Beta Was this translation helpful? Give feedback.
-
@BrendaBraitling: Thanks for the reply, Brenda! A few thoughts:
|
Beta Was this translation helpful? Give feedback.
-
@gregfowlerphd You bring up two very good points. Sources should be authoritative and we need to be cautious regarding details at midlevel. As you state above, the definition source is probably being handled. However the logic and semantic meaning need to be carefully considered in light of being universally useful to various domain ontologies and task ontologies as they link up to CCO. CCO branches need to be logically clear in their relations to one another and up to BFO. Perhaps there is too much detail. It is my understanding that applied ontologies on this level need to 'be specific enough' to 'be useful' - and , ideally, provide a means for many domains to link up... Perhaps this delineation is too specific because it is getting into the domain of employment law terms and tasks of business accounting and operations. Perhaps CCO should terminate at the level of business expense which allows a more specific Business Domain ontology or Business Task ontology to split the fine hairs... At level of 'business income' and 'business expense,' CCO allows all types of business practices and tasks and all type of business organizations to link up to it - from multinational corporations and governments to nonprofit organizations and lemonade stands. It also allows for localization to various cultures around the world regarding how business is done. This 'pruning' allows the CCO to BFO links and logic to be clear and the the link-up and logical connections to be clean from any intricate business domain ontology. It is also expeditious in getting a robust, unified CCO to standardization. I am inclined to think that there are several CCO issues that may be resolved by carefully contemplating the terminal elements of CCO's reach. @johnbeve |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I hope so, because I'd like to use it that way. (I'd also assume so, since that fits the standard use of "remuneration".) However, if it is, I think there's a problem with the current definition:
The problem is that the definition restricts acts of remuneration to acts occurring in the context of an employment relationship, and CCO elsewhere distinguishes sharply between employment relationships and contractee/contractor relationships (see the scope note for Contractor Role).
Beta Was this translation helpful? Give feedback.
All reactions