Accounting

1 Initial Problem

• Currently if an educational provider wants to have price tags for courses, they have to use custom metadata. 
• Custom metadata do not carry business logic. 
• Custom metadata is a poor choice if you want to allow for educational budgets and internal accounting.

2 Conceptual Summary

A new Accounting Service is introduced. By default it is not activated. Administrators can activate it in Administration > Organisational Units. 
Activating the Acounting Service invokes: 

1. Administrators have to select a currency. 
2. In the Settings-tabs of all Organisational Units  an input field is shown to assign a Cost Centre number. 
3. In all User-Accounts   an input field is shown to assign a Cost Centre number. 
4. Upon Activation all courses will get a new required input field "Price" in the Settings-tab in the "Additional Features" section. There is no way of option courses out of the accounting service. Course can only be set to 0,00 EUR to be free. 

3 User Interface Modifications

3.1 List of Affected Views

• Administration > Organisational Units > Settings
• Actuatual Settings-tabs of individual organisational units

3.2 User Interface Details

3.3 New User Interface Concepts

None.

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: Studer, Martin [mstuder]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.