Pierre Smits created OFBIZ-12445:
------------------------------------

             Summary: InvoiceRole handling
                 Key: OFBIZ-12445
                 URL: https://issues.apache.org/jira/browse/OFBIZ-12445
             Project: OFBiz
          Issue Type: Improvement
          Components: accounting
    Affects Versions: Trunk
            Reporter: Pierre Smits
            Assignee: Pierre Smits


Based on page regarding EntityNameRole page in Confluence (see link) and the 
discussions on dev ml, the way the InvoiceRole entity is defined and how the 
functionalities in OFBiz work with this needs improvement.

An invoice role record tells something about the object (the invoice) and which 
parties (apart from the two identified on the header) are associated with the 
object and in which capacity (the role).

In the case of an invoice, we can identify following roles:
 * invoice creator,
 * invoice editor,
 * invoice reviewer,
 * invoice approver.

h3. Invoice Creator

The party with the role of creator is the user that works with OFBiz for the 
(primary) internal company, most likely someone from the accounting department 
in the case of manually generated/registered sales or purchase invoices).
h3. Invoice Editor

The party with the role of invoice editor is the user that works with OFBiz for 
the (primary) internal organisation, most likely a co-worker of the party with 
the invoice creator role, and who can edit/update the invoice generated by 
someone else.
h3. Invoice Reviewer

The party with the role of invoice reviewer is the user, that works with OFBiz 
for the (primary) internal organisation, most likely in the department from 
where the root-cause of the invoice originated (sales department for sales 
invoices, purchase department for purchase invoices, etc.), but neither has the 
permission to update or approve an invoice.
h3. Invoice Approver

The party with the role of invoice approver is the user, that works with OFBiz 
for the (primary) internal organisation, most likely in the department from 
where the root-cause of the invoice originated (sales department for sales 
invoices, purchase department for purchase invoices, etc.), and has the proxy 
to approve an invoice.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to