View Source

Target release	Release name or number
Epic	Link to related JIRA epic or feature
Document status
Document owner	DaynaH (Deactivated)
Designer	Lead designer
Developers	Lead developer
QA	Lead tester

Goals

Mifos X currently has a basic teller module that is awkward for the end user and limited by basic. Given that the current accounting and general ledger system is not made for a real teller service, we will implement all enhancements and additional requirement in the new Mifos framework, allowing more flexibility than we experience today.
The goal of this document is to clearly define required system enhancements.

Background and strategic fit

More and more Mifos users are implementing and supporting complex organizations. A complex organization must have clear cash management systems in place to ensure proper audits, internal controls and quality customer service.

Assumptions

Assume that every organization uses cash in their operation.
Assume that every organization must reconcile cash.
Assume that every organization must be able to audit cash.

Requirements

#	Title	User Story	Importance	Notes
1	Create Tellers	Need page to create tellers (cashiers) and assign permissions	must have	Additional considerations or noteworthy references (links, issues)
2	general ledger posting	Tellers must have the ability to post transactions from a general ledger to a customer account and vice versa	must have
3	post transactions	tellers must be able to post savings, loans and gl transactions.	must have
4	Transfer	tellers must have the ability to transfer funds from one account to another in a single transactions	must have
5	Daily Report	At any time during the day, a teller should be able to pull a reporting with options for cash totals, transaction lists, transfers	must have	See https://issues.apache.org/jira/browse/FINERACT-203

User interaction and design

Mifos X > Teller Module Enhancment > Teller Cash Flow.png

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome
(e.g. How we make users more aware of this feature?)	Communicate the decision reached

Not Doing

List the features discussed which are out of scope or might be revisited in a later release.