Transcript Maker and Concept “A Role feature is required In Mifos”:AMIT Definition • The maker-checker principle states that important tasks should be completed by two.

Maker and Concept
“A Role feature is required In Mifos”:AMIT
Definition
• The maker-checker principle states that important tasks
should be completed by two people, not just one, to reduce
the risk of errors and misuse. One person initiates the
process, and the other person completes it. In practice, some
higher-risk processes require a third person acting as a
checker.
• A maker-checker system has been put in place to de-risk the
process of sensitive data maintenance because allowing just
one individual to have full control of what records can be
added or updated or how this is done can pose substantial
risks to a system.
Maker and Checker is a Role
•
•
This facility will ensure that a higher authority will always be able to keep tabs on
changes or additions in records. For instance, if a Client is registered in the system
by a user with Maker privileges, the record will be pending for approval with a
user with Checker authority at the HO end, and will be activated in the Clients
master only after approval.
This facility can be activated / deactivated according to users’ requirement.
In Application
•
•
•
What you can do is define roles in system and add users to them.
You would have to have a sort of "Inbox" for "makers" and "checkers". All
items for an individual maker would come into his inbox. The maker can
then work on it and "approve" it. Approving it would take this item to the
"checkers" inbox. The checker can then work on it and approve. If checker
"rejects" then it again goes to the "makers" inbox for his work.
There are other workflow tools from other vendors like IBM FileNet,
Documentum, OpenText that would provide you out of the box
functionality. There are many Open Source vendor's too like Alfresco,
Drupal etc.
PS: Inbox would be like a queue of items to be worked upon. You can have a table in
database that would behave as a Inbox wherein you can have items assigned to individual
users. And the ones assigned to users would appear in an individual's inbox.
“M & C” in our daily life
Situation
If not
Result
Effect
Movie for above 18
year to view
No ticket checker
Easy access to
unauthorized person
You all Knows
Fill your warehouse
with articles
No instructor is there
for proper placing
Important articles are
mixed with other article
Requires energy and
time to relocate them
Tea filter
No Filter
Tea particles comes into
your mouth
It will destroy your
taste
Dish prepared for
GUESTS
To pre taste checking
done
Salt is in excess
Useless dish, wasting
of time and money
Effects in Application
Situation related to making of an application
Movie situation
Unauthorized user
Warehouse situation
Integrity of Database
Tea situation
Slow performance
Guest situation
Useless application
If we have a maker and checker concept in our daily life they
why don’t we have in “Mifos”.
This application must based on senses.
Where it can be used?
It can be use for every process in Mifos.
For example: Making of user in Mifos
Admin rights has been given to any user mistakenly,
results unauthorized access.
If checker is there
The mistake has been captured and rectified.
Like this we can use every process has been checked by
the authorizer before going to database.
It is present in Mifos.
• Yes it is
• Where??
• While approving the Center, Group, User and
Opening of loan accounts.
Maker And Checker Workflow
Before it role must assign like
A filed officer
:
Always have a maker role.
A branch Manager:
Always have a checker Role
OR we will decide it in different-2 roles who will be
maker and checker.
A checker always have an inbox where he can trace
the checking required items.
Transaction has been made by maker
Posted to higher for approval (it having
some Txn ID)
Checker Inbox
Click the request and approves or reject it as per the
policy of company.
After approval the txn will save in the database.
Otherwise it rejects do not save in database because of
the garbage or defected entry.
Maker Checker Concept:
1.1
Multiple level of makers (based on a pre-defined number)
1.2
Multiple level of checkers (based on a pre-defined number)
1.3
Maker cannot be checker and vice versa
1.4
Allow Maker checker concept to be mandatory for all transactions
including to master and parameter files.
Provide for maker and checker concept allowing, for entry, verification, and
authorization and post commit verification and audit by different users based on:
2.1
Product type
2.2
Account Type
2.3
Transaction type
2.4
Transaction amount
2.5
Authorization levels
Your questions if any
Thank you
,