mifos-developer — mifos developers discussion

Re: [Mifos-developer] Improvements in Teller Module

[Ed C. <ed...@mi...>]

That time is fine by me as well. I will send out an invite.

Ed

On Thu, Aug 14, 2025 at 10:47 AM Jamal Inkoom <ji...@gm...> wrote:

> Hi Barath,
>
> Time works for me. If it's okay with Ed, then we are good to go.
>
> Regards,
>
> Jamal
>
> On Wed, Aug 13, 2025, 6:44 PM Bharath Gowda <bg...@mi...> wrote:
>
>> Hi Jamal,Ed
>>
>> Does Monday 18th August 3PM GMT  work for you for the discussion?
>>
>>
>>
>> Regards,
>> Bharath
>> Lead Implementation Analyst | Mifos Initiative
>> PMC Member | Apache Fineract
>> Mobile: +91.7019635592
>> http://mifos.org  <http://facebook.com/mifos>
>> <http://www.twitter.com/mifos>
>>
>> On Fri, Aug 8, 2025, 12:54 PM Jamal Inkoom <ji...@gm...> wrote:
>>
>>> Many Thanks Ed,
>>>
>>> I'm available for further discussions on this. Just let me know when and
>>> I will create the time.
>>>
>>> regards,
>>>
>>> On Thu, Aug 7, 2025 at 10:49 PM Ed Cable <ed...@mi...> wrote:
>>>
>>>> Hello Jamal,
>>>>
>>>> Thank you for suggesting these improvements. Bharath and myself would
>>>> be happy to discuss these further with you as we've had others in the
>>>> ecosystem express a willingness to share contributions regarding the teller
>>>> module back with the community.
>>>>
>>>> Ed
>>>>
>>>>
>>>>
>>>> On Thu, Aug 7, 2025 at 1:26 PM Jamal Inkoom <ji...@gm...> wrote:
>>>>
>>>>> Hello Team,
>>>>>
>>>>>
>>>>>
>>>>> I’d like to propose significant improvements to the Teller module in
>>>>> alignment with FINERACT-204
>>>>> <https://issues.apache.org/jira/browse/FINERACT-204>.
>>>>>
>>>>> While global financial services are increasingly shifting toward
>>>>> cashless transactions — with account-to-account transfers becoming the norm
>>>>> — the reality remains that branch banking is still widely practiced,
>>>>> especially in emerging markets. As such, cash handling and teller
>>>>> operations continue to be critical components of day-to-day banking.
>>>>>
>>>>> Most mature core banking platforms offer robust teller modules that
>>>>> support cash management, reconciliation, and audit trails. By strengthening
>>>>> Fineract’s teller capabilities, we can:
>>>>>
>>>>>    - Better support institutions operating in cash-heavy environments
>>>>>    - Improve adoption rates by offering parity with commercial systems
>>>>>    - Increase conversion from legacy platforms to Fineract
>>>>>
>>>>> I believe this enhancement aligns with the broader goal of making
>>>>> Fineract more versatile and enterprise-ready. If the community supports
>>>>> this direction, I’m committed to contributing the necessary improvements to
>>>>> deliver a more mature and feature-complete Teller module.
>>>>>
>>>>>
>>>>>
>>>>> The following outlines the backend enhancement plan for the Teller
>>>>> Module
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>    1. We maintain the m_tellers entity in the code base and christen
>>>>>    it as branch vaults, then modify it to have attached to it a dedicated GL
>>>>>    cash account - users can set it up as a multi-branch GL like all other GLs
>>>>>    or a dedicated Vault  Cash GL per branch
>>>>>    2. We Maintain the m_cashiers entity and christen it as Teller
>>>>>    Tills, then modify it to have attached to it dedicated GL cash account -
>>>>>    this means that each teller can have a dedicated GL account
>>>>>    3. At the moment, there's a setup in the accounting module to link
>>>>>    Teller and Cashier to GL accounts but the associated transactions in the
>>>>>    journal entries entity cannot be directly linked to cash allocation and
>>>>>    settlement transactions performed by cashiers making tracking of branch
>>>>>    cash balances and overages/shortages impossible
>>>>>    4. The platform also doesn't even provide for other cash
>>>>>    transactions other than movement and settlement of cash between cashier and
>>>>>    teller.
>>>>>    5. We will include the transaction types to enable us to perform
>>>>>    cash deposit and cash withdrawal at the branches.
>>>>>    6. The m_cashier_transaction entity will be modified to include
>>>>>    debit_account and credit_account to capture a cash deposit or withdrawal
>>>>>    transaction
>>>>>    7. For cash deposit, accounting entry will be - CREDIT the
>>>>>    customer account and DEBIT the GL associated with the Till performing the
>>>>>    transaction
>>>>>    8. For cash withdrawal, the accounting entry will be - DEBIT the
>>>>>    customer account and CREDIT the GL associated with the Till performing the
>>>>>    transaction
>>>>>    9. Each branch will have one vault (which means one GL for the
>>>>>    branch vault) but multiple tills can be created and associated with this
>>>>>    vault for the branch - this means multiple Cash GLs, one for each cashier
>>>>>    in the branch
>>>>>    10. A till with its associated GL account can either be for a
>>>>>    human teller or an ATM machine
>>>>>    11. Cash should be transferred into the tills (the associated GL
>>>>>    account should have a positive balance) before withdrawals are performed
>>>>>    against the tills - this will be simpler if we maintain balances for these
>>>>>    GL accounts (more on balance maintenance in another proposal)
>>>>>    12. Balance update for both the tills, vault, customer accounts
>>>>>    are going to be online
>>>>>    13. Till cash can be transferred back to the vault after the day's
>>>>>    transactions
>>>>>    14. At any point, the total cash in the branch will reflect the
>>>>>    sum of balances on all cashier tills in the branch and the balance on the
>>>>>    branch vault account - this is essential to cash position management and
>>>>>    therefore risk management at the branches
>>>>>    15. Branch cash position management implies we have to introduce
>>>>>    the concept of interbranch entries - at any point in time the sum of all
>>>>>    inter branch balances must be zero
>>>>>    16. We can also enable denomination management to enhance cashier
>>>>>    cash balancing procedures for those working with denominations
>>>>>    17. There will be overage/shortage accounts in the branch that
>>>>>    will hold cash in the branch that would have been recorded in the system
>>>>>    but cannot be accounted for
>>>>>    18. With this, financial institutions can ensure some controls by
>>>>>    requiring that all cashier till balances are zero at the close of each
>>>>>    working day
>>>>>    19. We will also introduce mandates on accounts. Mandate is a
>>>>>    regulatory requirement in many countries. Introduction of mandates will
>>>>>    make it easier to support joint accounts
>>>>>    20. At the moment, we could use the groups feature to handle joint
>>>>>    accounts once mandates are available
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Front-end Changes
>>>>>
>>>>>    1. We'll rework the teller management screens within the
>>>>>    *Organization* setup menu to reflect the changes
>>>>>    2. We'll have a dedicated screen for teller transactions -
>>>>>    precisely, cash deposit and cash withdrawal - cheques will come in later
>>>>>    3. The dedicated screen will have a lazy list of all accounts with
>>>>>    search criteria to enable tellers search for specific accounts
>>>>>    4. The details displayed on the account should include the
>>>>>    available balance on the account, the status of the account, the last few
>>>>>    transactions on the account, and most importantly the mandate on the account
>>>>>    5. We will also include an option to verify the identity of the
>>>>>    originator of the transaction. In here, we can show the image of the
>>>>>    account owner, their signature or do biometric verification if there is an
>>>>>    integration into an external verification service or all of the above
>>>>>    6. A withdrawal transaction without corresponding balance on the
>>>>>    cashier till account will fail
>>>>>    7. Each cashier can print their call over report at any point in
>>>>>    time
>>>>>    8. This dedicated cashier screen will only show up in the menus of
>>>>>    users who have been designated and setup as cashiers
>>>>>
>>>>>
>>>>> Please let me know what you think.
>>>>>
>>>>> regards,
>>>>>
>>>>> Jamal
>>>>>
>>>>
>>>>
>>>> --
>>>> *Ed Cable*
>>>> President/CEO, Mifos Initiative
>>>> ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649
>>>>
>>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>>>
>>>> Mifos-developer mailing list
>>>> mif...@li...
>>>> Unsubscribe or change settings at:
>>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>>
>>> Mifos-developer mailing list
>>> mif...@li...
>>> Unsubscribe or change settings at:
>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer



-- 
*Ed Cable*
President/CEO, Mifos Initiative
ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Re: [Mifos-developer] Improvements in Teller Module

[Jamal I. <ji...@gm...>]

Hi Barath,

Time works for me. If it's okay with Ed, then we are good to go.

Regards,

Jamal

On Wed, Aug 13, 2025, 6:44 PM Bharath Gowda <bg...@mi...> wrote:

> Hi Jamal,Ed
>
> Does Monday 18th August 3PM GMT  work for you for the discussion?
>
>
>
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> PMC Member | Apache Fineract
> Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
> On Fri, Aug 8, 2025, 12:54 PM Jamal Inkoom <ji...@gm...> wrote:
>
>> Many Thanks Ed,
>>
>> I'm available for further discussions on this. Just let me know when and
>> I will create the time.
>>
>> regards,
>>
>> On Thu, Aug 7, 2025 at 10:49 PM Ed Cable <ed...@mi...> wrote:
>>
>>> Hello Jamal,
>>>
>>> Thank you for suggesting these improvements. Bharath and myself would be
>>> happy to discuss these further with you as we've had others in the
>>> ecosystem express a willingness to share contributions regarding the teller
>>> module back with the community.
>>>
>>> Ed
>>>
>>>
>>>
>>> On Thu, Aug 7, 2025 at 1:26 PM Jamal Inkoom <ji...@gm...> wrote:
>>>
>>>> Hello Team,
>>>>
>>>>
>>>>
>>>> I’d like to propose significant improvements to the Teller module in
>>>> alignment with FINERACT-204
>>>> <https://issues.apache.org/jira/browse/FINERACT-204>.
>>>>
>>>> While global financial services are increasingly shifting toward
>>>> cashless transactions — with account-to-account transfers becoming the norm
>>>> — the reality remains that branch banking is still widely practiced,
>>>> especially in emerging markets. As such, cash handling and teller
>>>> operations continue to be critical components of day-to-day banking.
>>>>
>>>> Most mature core banking platforms offer robust teller modules that
>>>> support cash management, reconciliation, and audit trails. By strengthening
>>>> Fineract’s teller capabilities, we can:
>>>>
>>>>    - Better support institutions operating in cash-heavy environments
>>>>    - Improve adoption rates by offering parity with commercial systems
>>>>    - Increase conversion from legacy platforms to Fineract
>>>>
>>>> I believe this enhancement aligns with the broader goal of making
>>>> Fineract more versatile and enterprise-ready. If the community supports
>>>> this direction, I’m committed to contributing the necessary improvements to
>>>> deliver a more mature and feature-complete Teller module.
>>>>
>>>>
>>>>
>>>> The following outlines the backend enhancement plan for the Teller
>>>> Module
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>    1. We maintain the m_tellers entity in the code base and christen
>>>>    it as branch vaults, then modify it to have attached to it a dedicated GL
>>>>    cash account - users can set it up as a multi-branch GL like all other GLs
>>>>    or a dedicated Vault  Cash GL per branch
>>>>    2. We Maintain the m_cashiers entity and christen it as Teller
>>>>    Tills, then modify it to have attached to it dedicated GL cash account -
>>>>    this means that each teller can have a dedicated GL account
>>>>    3. At the moment, there's a setup in the accounting module to link
>>>>    Teller and Cashier to GL accounts but the associated transactions in the
>>>>    journal entries entity cannot be directly linked to cash allocation and
>>>>    settlement transactions performed by cashiers making tracking of branch
>>>>    cash balances and overages/shortages impossible
>>>>    4. The platform also doesn't even provide for other cash
>>>>    transactions other than movement and settlement of cash between cashier and
>>>>    teller.
>>>>    5. We will include the transaction types to enable us to perform
>>>>    cash deposit and cash withdrawal at the branches.
>>>>    6. The m_cashier_transaction entity will be modified to include
>>>>    debit_account and credit_account to capture a cash deposit or withdrawal
>>>>    transaction
>>>>    7. For cash deposit, accounting entry will be - CREDIT the customer
>>>>    account and DEBIT the GL associated with the Till performing the transaction
>>>>    8. For cash withdrawal, the accounting entry will be - DEBIT the
>>>>    customer account and CREDIT the GL associated with the Till performing the
>>>>    transaction
>>>>    9. Each branch will have one vault (which means one GL for the
>>>>    branch vault) but multiple tills can be created and associated with this
>>>>    vault for the branch - this means multiple Cash GLs, one for each cashier
>>>>    in the branch
>>>>    10. A till with its associated GL account can either be for a human
>>>>    teller or an ATM machine
>>>>    11. Cash should be transferred into the tills (the associated GL
>>>>    account should have a positive balance) before withdrawals are performed
>>>>    against the tills - this will be simpler if we maintain balances for these
>>>>    GL accounts (more on balance maintenance in another proposal)
>>>>    12. Balance update for both the tills, vault, customer accounts are
>>>>    going to be online
>>>>    13. Till cash can be transferred back to the vault after the day's
>>>>    transactions
>>>>    14. At any point, the total cash in the branch will reflect the sum
>>>>    of balances on all cashier tills in the branch and the balance on the
>>>>    branch vault account - this is essential to cash position management and
>>>>    therefore risk management at the branches
>>>>    15. Branch cash position management implies we have to introduce
>>>>    the concept of interbranch entries - at any point in time the sum of all
>>>>    inter branch balances must be zero
>>>>    16. We can also enable denomination management to enhance cashier
>>>>    cash balancing procedures for those working with denominations
>>>>    17. There will be overage/shortage accounts in the branch that will
>>>>    hold cash in the branch that would have been recorded in the system but
>>>>    cannot be accounted for
>>>>    18. With this, financial institutions can ensure some controls by
>>>>    requiring that all cashier till balances are zero at the close of each
>>>>    working day
>>>>    19. We will also introduce mandates on accounts. Mandate is a
>>>>    regulatory requirement in many countries. Introduction of mandates will
>>>>    make it easier to support joint accounts
>>>>    20. At the moment, we could use the groups feature to handle joint
>>>>    accounts once mandates are available
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Front-end Changes
>>>>
>>>>    1. We'll rework the teller management screens within the
>>>>    *Organization* setup menu to reflect the changes
>>>>    2. We'll have a dedicated screen for teller transactions -
>>>>    precisely, cash deposit and cash withdrawal - cheques will come in later
>>>>    3. The dedicated screen will have a lazy list of all accounts with
>>>>    search criteria to enable tellers search for specific accounts
>>>>    4. The details displayed on the account should include the
>>>>    available balance on the account, the status of the account, the last few
>>>>    transactions on the account, and most importantly the mandate on the account
>>>>    5. We will also include an option to verify the identity of the
>>>>    originator of the transaction. In here, we can show the image of the
>>>>    account owner, their signature or do biometric verification if there is an
>>>>    integration into an external verification service or all of the above
>>>>    6. A withdrawal transaction without corresponding balance on the
>>>>    cashier till account will fail
>>>>    7. Each cashier can print their call over report at any point in
>>>>    time
>>>>    8. This dedicated cashier screen will only show up in the menus of  users
>>>>    who have been designated and setup as cashiers
>>>>
>>>>
>>>> Please let me know what you think.
>>>>
>>>> regards,
>>>>
>>>> Jamal
>>>>
>>>
>>>
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649
>>>
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>>
>>> Mifos-developer mailing list
>>> mif...@li...
>>> Unsubscribe or change settings at:
>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Improvements in Teller Module

[Bharath G. <bg...@mi...>]

Hi Jamal,Ed

Does Monday 18th August 3PM GMT  work for you for the discussion?



Regards,
Bharath
Lead Implementation Analyst | Mifos Initiative
PMC Member | Apache Fineract
Mobile: +91.7019635592
http://mifos.org  <http://facebook.com/mifos>
<http://www.twitter.com/mifos>

On Fri, Aug 8, 2025, 12:54 PM Jamal Inkoom <ji...@gm...> wrote:

> Many Thanks Ed,
>
> I'm available for further discussions on this. Just let me know when and I
> will create the time.
>
> regards,
>
> On Thu, Aug 7, 2025 at 10:49 PM Ed Cable <ed...@mi...> wrote:
>
>> Hello Jamal,
>>
>> Thank you for suggesting these improvements. Bharath and myself would be
>> happy to discuss these further with you as we've had others in the
>> ecosystem express a willingness to share contributions regarding the teller
>> module back with the community.
>>
>> Ed
>>
>>
>>
>> On Thu, Aug 7, 2025 at 1:26 PM Jamal Inkoom <ji...@gm...> wrote:
>>
>>> Hello Team,
>>>
>>>
>>>
>>> I’d like to propose significant improvements to the Teller module in
>>> alignment with FINERACT-204
>>> <https://issues.apache.org/jira/browse/FINERACT-204>.
>>>
>>> While global financial services are increasingly shifting toward
>>> cashless transactions — with account-to-account transfers becoming the norm
>>> — the reality remains that branch banking is still widely practiced,
>>> especially in emerging markets. As such, cash handling and teller
>>> operations continue to be critical components of day-to-day banking.
>>>
>>> Most mature core banking platforms offer robust teller modules that
>>> support cash management, reconciliation, and audit trails. By strengthening
>>> Fineract’s teller capabilities, we can:
>>>
>>>    - Better support institutions operating in cash-heavy environments
>>>    - Improve adoption rates by offering parity with commercial systems
>>>    - Increase conversion from legacy platforms to Fineract
>>>
>>> I believe this enhancement aligns with the broader goal of making
>>> Fineract more versatile and enterprise-ready. If the community supports
>>> this direction, I’m committed to contributing the necessary improvements to
>>> deliver a more mature and feature-complete Teller module.
>>>
>>>
>>>
>>> The following outlines the backend enhancement plan for the Teller Module
>>>
>>>
>>>
>>>
>>>
>>>    1. We maintain the m_tellers entity in the code base and christen it
>>>    as branch vaults, then modify it to have attached to it a dedicated GL cash
>>>    account - users can set it up as a multi-branch GL like all other GLs or a
>>>    dedicated Vault  Cash GL per branch
>>>    2. We Maintain the m_cashiers entity and christen it as Teller
>>>    Tills, then modify it to have attached to it dedicated GL cash account -
>>>    this means that each teller can have a dedicated GL account
>>>    3. At the moment, there's a setup in the accounting module to link
>>>    Teller and Cashier to GL accounts but the associated transactions in the
>>>    journal entries entity cannot be directly linked to cash allocation and
>>>    settlement transactions performed by cashiers making tracking of branch
>>>    cash balances and overages/shortages impossible
>>>    4. The platform also doesn't even provide for other cash
>>>    transactions other than movement and settlement of cash between cashier and
>>>    teller.
>>>    5. We will include the transaction types to enable us to perform
>>>    cash deposit and cash withdrawal at the branches.
>>>    6. The m_cashier_transaction entity will be modified to include
>>>    debit_account and credit_account to capture a cash deposit or withdrawal
>>>    transaction
>>>    7. For cash deposit, accounting entry will be - CREDIT the customer
>>>    account and DEBIT the GL associated with the Till performing the transaction
>>>    8. For cash withdrawal, the accounting entry will be - DEBIT the
>>>    customer account and CREDIT the GL associated with the Till performing the
>>>    transaction
>>>    9. Each branch will have one vault (which means one GL for the
>>>    branch vault) but multiple tills can be created and associated with this
>>>    vault for the branch - this means multiple Cash GLs, one for each cashier
>>>    in the branch
>>>    10. A till with its associated GL account can either be for a human
>>>    teller or an ATM machine
>>>    11. Cash should be transferred into the tills (the associated GL
>>>    account should have a positive balance) before withdrawals are performed
>>>    against the tills - this will be simpler if we maintain balances for these
>>>    GL accounts (more on balance maintenance in another proposal)
>>>    12. Balance update for both the tills, vault, customer accounts are
>>>    going to be online
>>>    13. Till cash can be transferred back to the vault after the day's
>>>    transactions
>>>    14. At any point, the total cash in the branch will reflect the sum
>>>    of balances on all cashier tills in the branch and the balance on the
>>>    branch vault account - this is essential to cash position management and
>>>    therefore risk management at the branches
>>>    15. Branch cash position management implies we have to introduce the
>>>    concept of interbranch entries - at any point in time the sum of all inter
>>>    branch balances must be zero
>>>    16. We can also enable denomination management to enhance cashier
>>>    cash balancing procedures for those working with denominations
>>>    17. There will be overage/shortage accounts in the branch that will
>>>    hold cash in the branch that would have been recorded in the system but
>>>    cannot be accounted for
>>>    18. With this, financial institutions can ensure some controls by
>>>    requiring that all cashier till balances are zero at the close of each
>>>    working day
>>>    19. We will also introduce mandates on accounts. Mandate is a
>>>    regulatory requirement in many countries. Introduction of mandates will
>>>    make it easier to support joint accounts
>>>    20. At the moment, we could use the groups feature to handle joint
>>>    accounts once mandates are available
>>>
>>>
>>>
>>>
>>>
>>> Front-end Changes
>>>
>>>    1. We'll rework the teller management screens within the
>>>    *Organization* setup menu to reflect the changes
>>>    2. We'll have a dedicated screen for teller transactions -
>>>    precisely, cash deposit and cash withdrawal - cheques will come in later
>>>    3. The dedicated screen will have a lazy list of all accounts with
>>>    search criteria to enable tellers search for specific accounts
>>>    4. The details displayed on the account should include the available
>>>    balance on the account, the status of the account, the last few
>>>    transactions on the account, and most importantly the mandate on the account
>>>    5. We will also include an option to verify the identity of the
>>>    originator of the transaction. In here, we can show the image of the
>>>    account owner, their signature or do biometric verification if there is an
>>>    integration into an external verification service or all of the above
>>>    6. A withdrawal transaction without corresponding balance on the
>>>    cashier till account will fail
>>>    7. Each cashier can print their call over report at any point in time
>>>    8. This dedicated cashier screen will only show up in the menus of  users
>>>    who have been designated and setup as cashiers
>>>
>>>
>>> Please let me know what you think.
>>>
>>> regards,
>>>
>>> Jamal
>>>
>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>>
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Improvements in Teller Module

[Jamal I. <ji...@gm...>]

Many Thanks Ed,

I'm available for further discussions on this. Just let me know when and I
will create the time.

regards,

On Thu, Aug 7, 2025 at 10:49 PM Ed Cable <ed...@mi...> wrote:

> Hello Jamal,
>
> Thank you for suggesting these improvements. Bharath and myself would be
> happy to discuss these further with you as we've had others in the
> ecosystem express a willingness to share contributions regarding the teller
> module back with the community.
>
> Ed
>
>
>
> On Thu, Aug 7, 2025 at 1:26 PM Jamal Inkoom <ji...@gm...> wrote:
>
>> Hello Team,
>>
>>
>>
>> I’d like to propose significant improvements to the Teller module in
>> alignment with FINERACT-204
>> <https://issues.apache.org/jira/browse/FINERACT-204>.
>>
>> While global financial services are increasingly shifting toward cashless
>> transactions — with account-to-account transfers becoming the norm — the
>> reality remains that branch banking is still widely practiced, especially
>> in emerging markets. As such, cash handling and teller operations continue
>> to be critical components of day-to-day banking.
>>
>> Most mature core banking platforms offer robust teller modules that
>> support cash management, reconciliation, and audit trails. By strengthening
>> Fineract’s teller capabilities, we can:
>>
>>    - Better support institutions operating in cash-heavy environments
>>    - Improve adoption rates by offering parity with commercial systems
>>    - Increase conversion from legacy platforms to Fineract
>>
>> I believe this enhancement aligns with the broader goal of making
>> Fineract more versatile and enterprise-ready. If the community supports
>> this direction, I’m committed to contributing the necessary improvements to
>> deliver a more mature and feature-complete Teller module.
>>
>>
>>
>> The following outlines the backend enhancement plan for the Teller Module
>>
>>
>>
>>
>>
>>    1. We maintain the m_tellers entity in the code base and christen it
>>    as branch vaults, then modify it to have attached to it a dedicated GL cash
>>    account - users can set it up as a multi-branch GL like all other GLs or a
>>    dedicated Vault  Cash GL per branch
>>    2. We Maintain the m_cashiers entity and christen it as Teller Tills,
>>    then modify it to have attached to it dedicated GL cash account - this
>>    means that each teller can have a dedicated GL account
>>    3. At the moment, there's a setup in the accounting module to link
>>    Teller and Cashier to GL accounts but the associated transactions in the
>>    journal entries entity cannot be directly linked to cash allocation and
>>    settlement transactions performed by cashiers making tracking of branch
>>    cash balances and overages/shortages impossible
>>    4. The platform also doesn't even provide for other cash transactions
>>    other than movement and settlement of cash between cashier and teller.
>>    5. We will include the transaction types to enable us to perform cash
>>    deposit and cash withdrawal at the branches.
>>    6. The m_cashier_transaction entity will be modified to include
>>    debit_account and credit_account to capture a cash deposit or withdrawal
>>    transaction
>>    7. For cash deposit, accounting entry will be - CREDIT the customer
>>    account and DEBIT the GL associated with the Till performing the transaction
>>    8. For cash withdrawal, the accounting entry will be - DEBIT the
>>    customer account and CREDIT the GL associated with the Till performing the
>>    transaction
>>    9. Each branch will have one vault (which means one GL for the branch
>>    vault) but multiple tills can be created and associated with this vault for
>>    the branch - this means multiple Cash GLs, one for each cashier in the
>>    branch
>>    10. A till with its associated GL account can either be for a human
>>    teller or an ATM machine
>>    11. Cash should be transferred into the tills (the associated GL
>>    account should have a positive balance) before withdrawals are performed
>>    against the tills - this will be simpler if we maintain balances for these
>>    GL accounts (more on balance maintenance in another proposal)
>>    12. Balance update for both the tills, vault, customer accounts are
>>    going to be online
>>    13. Till cash can be transferred back to the vault after the day's
>>    transactions
>>    14. At any point, the total cash in the branch will reflect the sum
>>    of balances on all cashier tills in the branch and the balance on the
>>    branch vault account - this is essential to cash position management and
>>    therefore risk management at the branches
>>    15. Branch cash position management implies we have to introduce the
>>    concept of interbranch entries - at any point in time the sum of all inter
>>    branch balances must be zero
>>    16. We can also enable denomination management to enhance cashier
>>    cash balancing procedures for those working with denominations
>>    17. There will be overage/shortage accounts in the branch that will
>>    hold cash in the branch that would have been recorded in the system but
>>    cannot be accounted for
>>    18. With this, financial institutions can ensure some controls by
>>    requiring that all cashier till balances are zero at the close of each
>>    working day
>>    19. We will also introduce mandates on accounts. Mandate is a
>>    regulatory requirement in many countries. Introduction of mandates will
>>    make it easier to support joint accounts
>>    20. At the moment, we could use the groups feature to handle joint
>>    accounts once mandates are available
>>
>>
>>
>>
>>
>> Front-end Changes
>>
>>    1. We'll rework the teller management screens within the
>>    *Organization* setup menu to reflect the changes
>>    2. We'll have a dedicated screen for teller transactions - precisely,
>>    cash deposit and cash withdrawal - cheques will come in later
>>    3. The dedicated screen will have a lazy list of all accounts with
>>    search criteria to enable tellers search for specific accounts
>>    4. The details displayed on the account should include the available
>>    balance on the account, the status of the account, the last few
>>    transactions on the account, and most importantly the mandate on the account
>>    5. We will also include an option to verify the identity of the
>>    originator of the transaction. In here, we can show the image of the
>>    account owner, their signature or do biometric verification if there is an
>>    integration into an external verification service or all of the above
>>    6. A withdrawal transaction without corresponding balance on the
>>    cashier till account will fail
>>    7. Each cashier can print their call over report at any point in time
>>    8. This dedicated cashier screen will only show up in the menus of  users
>>    who have been designated and setup as cashiers
>>
>>
>> Please let me know what you think.
>>
>> regards,
>>
>> Jamal
>>
>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Improvements in Teller Module

[Ed C. <ed...@mi...>]

Hello Jamal,

Thank you for suggesting these improvements. Bharath and myself would be
happy to discuss these further with you as we've had others in the
ecosystem express a willingness to share contributions regarding the teller
module back with the community.

Ed



On Thu, Aug 7, 2025 at 1:26 PM Jamal Inkoom <ji...@gm...> wrote:

> Hello Team,
>
>
>
> I’d like to propose significant improvements to the Teller module in
> alignment with FINERACT-204
> <https://issues.apache.org/jira/browse/FINERACT-204>.
>
> While global financial services are increasingly shifting toward cashless
> transactions — with account-to-account transfers becoming the norm — the
> reality remains that branch banking is still widely practiced, especially
> in emerging markets. As such, cash handling and teller operations continue
> to be critical components of day-to-day banking.
>
> Most mature core banking platforms offer robust teller modules that
> support cash management, reconciliation, and audit trails. By strengthening
> Fineract’s teller capabilities, we can:
>
>    - Better support institutions operating in cash-heavy environments
>    - Improve adoption rates by offering parity with commercial systems
>    - Increase conversion from legacy platforms to Fineract
>
> I believe this enhancement aligns with the broader goal of making Fineract
> more versatile and enterprise-ready. If the community supports this
> direction, I’m committed to contributing the necessary improvements to
> deliver a more mature and feature-complete Teller module.
>
>
>
> The following outlines the backend enhancement plan for the Teller Module
>
>
>
>
>
>    1. We maintain the m_tellers entity in the code base and christen it
>    as branch vaults, then modify it to have attached to it a dedicated GL cash
>    account - users can set it up as a multi-branch GL like all other GLs or a
>    dedicated Vault  Cash GL per branch
>    2. We Maintain the m_cashiers entity and christen it as Teller Tills,
>    then modify it to have attached to it dedicated GL cash account - this
>    means that each teller can have a dedicated GL account
>    3. At the moment, there's a setup in the accounting module to link
>    Teller and Cashier to GL accounts but the associated transactions in the
>    journal entries entity cannot be directly linked to cash allocation and
>    settlement transactions performed by cashiers making tracking of branch
>    cash balances and overages/shortages impossible
>    4. The platform also doesn't even provide for other cash transactions
>    other than movement and settlement of cash between cashier and teller.
>    5. We will include the transaction types to enable us to perform cash
>    deposit and cash withdrawal at the branches.
>    6. The m_cashier_transaction entity will be modified to include
>    debit_account and credit_account to capture a cash deposit or withdrawal
>    transaction
>    7. For cash deposit, accounting entry will be - CREDIT the customer
>    account and DEBIT the GL associated with the Till performing the transaction
>    8. For cash withdrawal, the accounting entry will be - DEBIT the
>    customer account and CREDIT the GL associated with the Till performing the
>    transaction
>    9. Each branch will have one vault (which means one GL for the branch
>    vault) but multiple tills can be created and associated with this vault for
>    the branch - this means multiple Cash GLs, one for each cashier in the
>    branch
>    10. A till with its associated GL account can either be for a human
>    teller or an ATM machine
>    11. Cash should be transferred into the tills (the associated GL
>    account should have a positive balance) before withdrawals are performed
>    against the tills - this will be simpler if we maintain balances for these
>    GL accounts (more on balance maintenance in another proposal)
>    12. Balance update for both the tills, vault, customer accounts are
>    going to be online
>    13. Till cash can be transferred back to the vault after the day's
>    transactions
>    14. At any point, the total cash in the branch will reflect the sum of
>    balances on all cashier tills in the branch and the balance on the branch
>    vault account - this is essential to cash position management and therefore
>    risk management at the branches
>    15. Branch cash position management implies we have to introduce the
>    concept of interbranch entries - at any point in time the sum of all inter
>    branch balances must be zero
>    16. We can also enable denomination management to enhance cashier cash
>    balancing procedures for those working with denominations
>    17. There will be overage/shortage accounts in the branch that will
>    hold cash in the branch that would have been recorded in the system but
>    cannot be accounted for
>    18. With this, financial institutions can ensure some controls by
>    requiring that all cashier till balances are zero at the close of each
>    working day
>    19. We will also introduce mandates on accounts. Mandate is a
>    regulatory requirement in many countries. Introduction of mandates will
>    make it easier to support joint accounts
>    20. At the moment, we could use the groups feature to handle joint
>    accounts once mandates are available
>
>
>
>
>
> Front-end Changes
>
>    1. We'll rework the teller management screens within the *Organization*
>    setup menu to reflect the changes
>    2. We'll have a dedicated screen for teller transactions - precisely,
>    cash deposit and cash withdrawal - cheques will come in later
>    3. The dedicated screen will have a lazy list of all accounts with
>    search criteria to enable tellers search for specific accounts
>    4. The details displayed on the account should include the available
>    balance on the account, the status of the account, the last few
>    transactions on the account, and most importantly the mandate on the account
>    5. We will also include an option to verify the identity of the
>    originator of the transaction. In here, we can show the image of the
>    account owner, their signature or do biometric verification if there is an
>    integration into an external verification service or all of the above
>    6. A withdrawal transaction without corresponding balance on the
>    cashier till account will fail
>    7. Each cashier can print their call over report at any point in time
>    8. This dedicated cashier screen will only show up in the menus of  users
>    who have been designated and setup as cashiers
>
>
> Please let me know what you think.
>
> regards,
>
> Jamal
>


-- 
*Ed Cable*
President/CEO, Mifos Initiative
ed...@mi... | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

[Mifos-developer] Improvements in Teller Module

[Jamal I. <ji...@gm...>]

Hello Team,



I’d like to propose significant improvements to the Teller module in
alignment with FINERACT-204
<https://issues.apache.org/jira/browse/FINERACT-204>.

While global financial services are increasingly shifting toward cashless
transactions — with account-to-account transfers becoming the norm — the
reality remains that branch banking is still widely practiced, especially
in emerging markets. As such, cash handling and teller operations continue
to be critical components of day-to-day banking.

Most mature core banking platforms offer robust teller modules that support
cash management, reconciliation, and audit trails. By strengthening
Fineract’s teller capabilities, we can:

   - Better support institutions operating in cash-heavy environments
   - Improve adoption rates by offering parity with commercial systems
   - Increase conversion from legacy platforms to Fineract

I believe this enhancement aligns with the broader goal of making Fineract
more versatile and enterprise-ready. If the community supports this
direction, I’m committed to contributing the necessary improvements to
deliver a more mature and feature-complete Teller module.



The following outlines the backend enhancement plan for the Teller Module





   1. We maintain the m_tellers entity in the code base and christen it as
   branch vaults, then modify it to have attached to it a dedicated GL cash
   account - users can set it up as a multi-branch GL like all other GLs or a
   dedicated Vault  Cash GL per branch
   2. We Maintain the m_cashiers entity and christen it as Teller Tills,
   then modify it to have attached to it dedicated GL cash account - this
   means that each teller can have a dedicated GL account
   3. At the moment, there's a setup in the accounting module to link
   Teller and Cashier to GL accounts but the associated transactions in the
   journal entries entity cannot be directly linked to cash allocation and
   settlement transactions performed by cashiers making tracking of branch
   cash balances and overages/shortages impossible
   4. The platform also doesn't even provide for other cash transactions
   other than movement and settlement of cash between cashier and teller.
   5. We will include the transaction types to enable us to perform cash
   deposit and cash withdrawal at the branches.
   6. The m_cashier_transaction entity will be modified to include
   debit_account and credit_account to capture a cash deposit or withdrawal
   transaction
   7. For cash deposit, accounting entry will be - CREDIT the customer
   account and DEBIT the GL associated with the Till performing the transaction
   8. For cash withdrawal, the accounting entry will be - DEBIT the
   customer account and CREDIT the GL associated with the Till performing the
   transaction
   9. Each branch will have one vault (which means one GL for the branch
   vault) but multiple tills can be created and associated with this vault for
   the branch - this means multiple Cash GLs, one for each cashier in the
   branch
   10. A till with its associated GL account can either be for a human
   teller or an ATM machine
   11. Cash should be transferred into the tills (the associated GL account
   should have a positive balance) before withdrawals are performed against
   the tills - this will be simpler if we maintain balances for these GL
   accounts (more on balance maintenance in another proposal)
   12. Balance update for both the tills, vault, customer accounts are
   going to be online
   13. Till cash can be transferred back to the vault after the day's
   transactions
   14. At any point, the total cash in the branch will reflect the sum of
   balances on all cashier tills in the branch and the balance on the branch
   vault account - this is essential to cash position management and therefore
   risk management at the branches
   15. Branch cash position management implies we have to introduce the
   concept of interbranch entries - at any point in time the sum of all inter
   branch balances must be zero
   16. We can also enable denomination management to enhance cashier cash
   balancing procedures for those working with denominations
   17. There will be overage/shortage accounts in the branch that will hold
   cash in the branch that would have been recorded in the system but cannot
   be accounted for
   18. With this, financial institutions can ensure some controls by
   requiring that all cashier till balances are zero at the close of each
   working day
   19. We will also introduce mandates on accounts. Mandate is a regulatory
   requirement in many countries. Introduction of mandates will make it easier
   to support joint accounts
   20. At the moment, we could use the groups feature to handle joint
   accounts once mandates are available





Front-end Changes

   1. We'll rework the teller management screens within the *Organization*
   setup menu to reflect the changes
   2. We'll have a dedicated screen for teller transactions - precisely,
   cash deposit and cash withdrawal - cheques will come in later
   3. The dedicated screen will have a lazy list of all accounts with
   search criteria to enable tellers search for specific accounts
   4. The details displayed on the account should include the available
   balance on the account, the status of the account, the last few
   transactions on the account, and most importantly the mandate on the account
   5. We will also include an option to verify the identity of the
   originator of the transaction. In here, we can show the image of the
   account owner, their signature or do biometric verification if there is an
   integration into an external verification service or all of the above
   6. A withdrawal transaction without corresponding balance on the cashier
   till account will fail
   7. Each cashier can print their call over report at any point in time
   8. This dedicated cashier screen will only show up in the menus of  users
   who have been designated and setup as cashiers


Please let me know what you think.

regards,

Jamal

[Mifos-developer] Upcoming Q2 Community Call Webinar & Summer Intern Midterm Showcases

[Ed C. <ed...@mi...>]

Hi community,

If you haven't seen the posts via Linkedin, our e-newsletter, or Slack,
please register for the upcoming events

Q2 2025 Community Call - Tuesday July 29 at 1500 GMT -
https://us02web.zoom.us/webinar/register/4817458629823/WN_C_RXzjEYSGGZkfPIIXEnLA

Summer Intern Midterm Showcase Part 1 - July 31 at 1500 GMT -
https://us02web.zoom.us/webinar/register/6717537835742/WN_CQqtSFNuSSmjoFjJdeOWLA

Summer Intern Midterm Showcase Part 2 - Aug 1 at 1500 GMT - -
https://us02web.zoom.us/webinar/register/5217537836095/WN_ASIZSwVhRm6tsuG0-P0c1Qf

Thanks,

Ed

[Mifos-developer] Summary of My Contributions as an aspiring GSoC Contributor

[Disha O. <doz...@gm...>]

Dear Maintainers

I hope you're doing well.

I'm Disha Oza, an aspiring Google Summer of Code (GSoC) contributor, and I
wanted to take a moment to share my contributions to the *AnimateItNow* ,
InfantCareCompass ,Codecov projects so far. I've been actively exploring
the codebase and contributing them in terms of community standards and new
feature ideas.
 Merged Contributions:

   -

   *Added CONTRIBUTING.md* – I created a detailed guide to help newcomers
   understand how to set up the project locally, raise issues and PRs, and
   follow contribution norms.
   -

   *Added CODE_OF_CONDUCT.md* – I included a standard and inclusive code of
   conduct to foster a welcoming environment for all contributors.

Contributions Made (Pending Merge):

   -

   *Feature: Bookmark / To-Do Section* – I proposed and began building a
   personal “To-Do” or Bookmark feature that allows users to save DSA
   questions locally for focused revision. This includes:
   -

      UI implementation using Tailwind CSS
      -

      localStorage integration for persistence
      -

      A separate section in the UI to manage bookmarked items
      -

   *Enhancements to README* (Local Dev Setup, GitHub Basics) – I suggested
   additions like:
   -

      How to clone a repo and raise a PR
      -

      Branch naming conventions
      -

      Contribution flow visuals for beginners

I'm passionate about open-source and have enjoyed working on *AnimateItNow*
as part of GSSoC. I'm constantly exploring areas to improve and simplify
the experience for other contributors as well. I'd love to take on more
issues or assist in prioritizing upcoming tasks.

Please feel free to share any feedback or suggestions that would help me
improve and contribute more effectively.

Looking forward to continuing my journey with the project!

Warm regards,
*Disha Oza*
GitHub: github.com/DishaA06
Email: dis...@gm...

[Mifos-developer] Introduction - Aspiring GSoC 2026 Contributor

[Priyansh S. <sin...@gm...>]

Hello Mifos Team,

I’m Priyansh Singh, a first-year BTech student from India with a strong
interest in backend systems, financial technology, and open-source
development. I'm aspiring to participate in GSoC 2026 and have chosen Mifos
as my primary focus due to its impactful mission and rich Java-based
backend architecture.

My current goal is to develop my skills in Java full stack (Spring Boot,
REST APIs, MySQL) and begin contributing meaningfully to the Mifos/Fineract
ecosystem. I’ve started exploring the Fineract repository and will soon
begin setting up the development environment.

As I’m just getting started, I’d be grateful for any guidance on:
- Good beginner issues I can look into
- Recommended sub-projects or areas to focus on for Java contributors
- Any best practices while contributing to Fineract or related modules

I’m excited to be a part of this community and look forward to learning
from you all while contributing!

Warm regards,
Priyansh Singh
Location: India

[Mifos-developer] Use of AI in Jira Tickets

[VICTOR M. R. R. <vic...@fi...>]

Hello Mifos Community,

I would like to know your opinion about using AI in Jira Tickets

This is an example:

https://mifosforge.jira.com/browse/WEB-233?atlOrigin=eyJpIjoiNmQ0YjFjYmYyZGRjNDc0MDgxNWQ4MDQxM2U2NWJhMmEiLCJwIjoiaiJ9

Please let me know your thoughts.

Regards

Victor Romero

Re: [Mifos-developer] Loan Disbursal Error

[Peter o. <pet...@gm...>]

No, it is not a custom query. It's the same logic for loan disbursements
process.



On Sun, Jun 29, 2025 at 4:56 PM José Alberto Hernández
<al...@ar...lutions> wrote:

> Hello!
>
> Is this query part of a custom development? There are around 45 tables
> used in this select
>
> Thanks
> Best regards
> Alberto
>
> On Thu, Jun 26, 2025 at 5:54 AM Peter oliver <pet...@gm...>
> wrote:
>
>> Hello @all, I am getting too many columns error when doing a loan
>> disbursal and it's only affecting one client.
>>
>> What are the possible solutions to fix this issue?
>>
>> Find the attached txt doc for the error logs.
>>
>> Regards.
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Loan Disbursal Error

[José A. H. <al...@ar...>]

Hello!

Is this query part of a custom development? There are around 45 tables used
in this select

Thanks
Best regards
Alberto

On Thu, Jun 26, 2025 at 5:54 AM Peter oliver <pet...@gm...>
wrote:

> Hello @all, I am getting too many columns error when doing a loan
> disbursal and it's only affecting one client.
>
> What are the possible solutions to fix this issue?
>
> Find the attached txt doc for the error logs.
>
> Regards.
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Loan Disbursal Error

[Peter o. <pet...@gm...>]

The Fineract version is 1.4.0

You can specify the specific detail inquiry needed of the database.

Regards.


On Fri, Jun 27, 2025 at 3:47 AM VICTOR MANUEL ROMERO RODRIGUEZ <
vic...@fi...> wrote:

> Hello,
>
> Could you please more information about the Apache Fineract version used
> for this setup.
>
> Also please provide information about your database.
>
> El El jue, 26 de jun de 2025 a la(s) 5:47 a.m., Peter oliver <
> pet...@gm...> escribió:
>
>> Hello @all, I am getting too many columns error when doing a loan
>> disbursal and it's only affecting one client.
>>
>> What are the possible solutions to fix this issue?
>>
>> Find the attached txt doc for the error logs.
>>
>> Regards.
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] Loan Disbursal Error

[VICTOR M. R. R. <vic...@fi...>]

Hello,

Could you please more information about the Apache Fineract version used
for this setup.

Also please provide information about your database.

El El jue, 26 de jun de 2025 a la(s) 5:47 a.m., Peter oliver <
pet...@gm...> escribió:

> Hello @all, I am getting too many columns error when doing a loan
> disbursal and it's only affecting one client.
>
> What are the possible solutions to fix this issue?
>
> Find the attached txt doc for the error logs.
>
> Regards.
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

[Mifos-developer] Loan Disbursal Error

[Peter o. <pet...@gm...>]

Hello @all, I am getting too many columns error when doing a loan disbursal
and it's only affecting one client.

What are the possible solutions to fix this issue?

Find the attached txt doc for the error logs.

Regards.

[Mifos-developer] Mifos Setting Configuration

[Timothy. O O. <tim...@ou...>]

Dear All,

Please, how can I save the User setting   configuration shown in the attached images as there is no attached image.

Also is it a system wide or per user base configuration.

Timothy O. Olawuyi
[cid:e656d347-6327-48d2-8746-d4c4f9f15754]
[cid:6b18f651-255a-428f-ae57-2d1529003c52]
+2348052612001

[Mifos-developer] OFF TOPIC

[Ahmed A. <a7m...@gm...>]

Hello mentors,
Is there any opportunity can I target like GSoC ?

Regards,
Ahmed Adel

[Mifos-developer] WebApp: Default branch is now dev

[VICTOR M. R. R. <vic...@fi...>]

Hello WebApp developers,

The default branch is now dev, this branch contains all the changes made to
the WebApp application.

Regards

Victor

Re: [Mifos-developer] REPORT FETCHING INCOMPLETE DATA

[Peter o. <pet...@gm...>]

Hello,

The version i am currently using is mapped to several organizations and
several integration processes.

What would be the outcome?
What do i need to do/consider in the refactor process of my fineract
project (1.4) to the current fineract version?


Regards.



On Fri, Apr 11, 2025 at 10:17 PM Adam Monsen <am...@mi...> wrote:

> On Fri, Apr 11, 2025 at 7:25 AM Peter oliver <pet...@gm...>
> wrote:
>
>> The fineract version i am using is 1.4.0.
>
>
> Peter, will you say more about this? Why not upgrade Fineract?
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] REPORT FETCHING INCOMPLETE DATA

[Adam M. <am...@mi...>]

On Fri, Apr 11, 2025 at 7:25 AM Peter oliver <pet...@gm...>
wrote:

> The fineract version i am using is 1.4.0.


Peter, will you say more about this? Why not upgrade Fineract?

[Mifos-developer] REPORT FETCHING INCOMPLETE DATA

[Peter o. <pet...@gm...>]

Hello @all, I am experiencing inadequate data fetched in comparison to the
"Member saving summary" and the specific "detail ledger report" linked to
the Member deposit product.

Below is the member saving summary report that populates the data as at at
the month of 1 jan 2024 -31 jan 2024.
It populates all the transactions for the month:
 [image: mifos.jpg]

Below is the Detail ledger report of the member deposit which after product
linking is done should ideally pull the same data but pulls only 6 details
of the deposits done:

[image: mifos 2.jpg]

What leads to the above inconsistencies and how can i rectify it as i am
experiencing it in several detail ledger report and trial balance figures?

The fineract version i am using is 1.4.0.

Regards.

Re: [Mifos-developer] CLIENT CREATION ERROR

[Peter o. <pet...@gm...>]

Hello,


Thanks for the assistance. I've been able to sort out the issue though.

Problem was on the new_initialize_db.py file that was to be executed via
API but wasn't due to change in valid Auth Token for the deployed system
and otp.

How to go about it:
 Authenticate the API which send a POST request to the auth endpoint using
the defined credentials (username and password) in the json body.
The function constructs the http request using urllib.request.Request and
sends it using urllib.request.urlopen.
Retrieve the Basic authentication token from the system: inspect:network
precise body preferred.
Hard code the token on the py.file and execute to create the table and
relevant data tables.

Regards.

On Fri, Apr 11, 2025 at 4:38 PM Felix van Hove via Mifos-developer <
mif...@li...> wrote:

> Hi Peter,
>
> If you don't refer to the latest code of the web app and of Fineract,
> please add version information to your questions and bug reports.
> Developers are trying help you tracking down your error. If you use
> Fineract 1.4 and an 8 years old version of the community app, developers
> need to search your bug in the source code that you use. Everything else
> is wasting their time. Or are you referring to newly released code?
>
> Kind Regards,
> Felix
>
>
> On 10/04/2025 10:05, Peter oliver wrote:
> > Hello,
> >
> > I get the error when creating the member in the UI as after indicating
> > the mandatory field and the needed optional fields. After am not able to
> > submit the creation.
> > Find attached snip.
> >
> >
> >       image.png
> >
> >
> > On Thu, Apr 10, 2025 at 10:41 AM Bharath Gowda <bg...@mi...
> > <mailto:bg...@mi...>> wrote:
> >
> >     Hi Peter,
> >
> >     Are you getting this error message while you are creating the client
> >     from the UI or when you are trying to save some data in a datatable
> >     that belongs to a client?
> >     A screenshot would be more helpful
> >
> >     Regards,
> >     Bharath
> >     Lead Implementation Analyst | Mifos Initiative
> >     Skype: live:cbharath4| Mobile: +91.7019635592
> >     http://mifos.org <http://mifos.org/><http://facebook.com/mifos>//
> >     <http://www.twitter.com/mifos>
> >
> >
> >     On Wed, Apr 9, 2025 at 6:43 PM Peter oliver
> >     <pet...@gm... <mailto:pet...@gm...>> wrote:
> >
> >         Hello @all,
> >
> >         Getting an error of "client extra info" does not exist in
> >         attempt to create the clients data in the system.
> >
> >         This is after deployment without the python file
> >         "new_db_initialize.py" being executed which should create the
> >         client extra info fields via the datatable apis.
> >
> >         Opted to attempt to create the client extra info table manually
> >         in the db but still not able to create/import a client data.
> >
> >         How can i fix this error?
> >
> >         Below is the attached error log:
> >
> >         client creation err.jpg
> >         Screenshot 2025-04-09 102129.png
> >
> >         Regards.
> >         Mifos-developer mailing list
> >         mif...@li... <mailto:mifos-
> >         dev...@li...>
> >         Unsubscribe or change settings at:
> >         https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >         <https://lists.sourceforge.net/lists/listinfo/mifos-developer>
> >
> >     Mifos-developer mailing list
> >     mif...@li... <mailto:mifos-
> >     dev...@li...>
> >     Unsubscribe or change settings at:
> >     https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >     <https://lists.sourceforge.net/lists/listinfo/mifos-developer>
> >
> >
> >
> > Mifos-developer mailing list
> > mif...@li...
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
>
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] CLIENT CREATION ERROR

[Felix v. H. <fva...@gm...>]

Hi Peter,

If you don't refer to the latest code of the web app and of Fineract,
please add version information to your questions and bug reports.
Developers are trying help you tracking down your error. If you use
Fineract 1.4 and an 8 years old version of the community app, developers
need to search your bug in the source code that you use. Everything else
is wasting their time. Or are you referring to newly released code?

Kind Regards,
Felix


On 10/04/2025 10:05, Peter oliver wrote:
> Hello,
>
> I get the error when creating the member in the UI as after indicating
> the mandatory field and the needed optional fields. After am not able to
> submit the creation.
> Find attached snip.
>
>
>       image.png
>
>
> On Thu, Apr 10, 2025 at 10:41 AM Bharath Gowda <bg...@mi...
> <mailto:bg...@mi...>> wrote:
>
>     Hi Peter,
>
>     Are you getting this error message while you are creating the client
>     from the UI or when you are trying to save some data in a datatable
>     that belongs to a client?
>     A screenshot would be more helpful
>
>     Regards,
>     Bharath
>     Lead Implementation Analyst | Mifos Initiative
>     Skype: live:cbharath4| Mobile: +91.7019635592
>     http://mifos.org <http://mifos.org/><http://facebook.com/mifos>//
>     <http://www.twitter.com/mifos>
>
>
>     On Wed, Apr 9, 2025 at 6:43 PM Peter oliver
>     <pet...@gm... <mailto:pet...@gm...>> wrote:
>
>         Hello @all,
>
>         Getting an error of "client extra info" does not exist in
>         attempt to create the clients data in the system.
>
>         This is after deployment without the python file
>         "new_db_initialize.py" being executed which should create the
>         client extra info fields via the datatable apis.
>
>         Opted to attempt to create the client extra info table manually
>         in the db but still not able to create/import a client data.
>
>         How can i fix this error?
>
>         Below is the attached error log:
>
>         client creation err.jpg
>         Screenshot 2025-04-09 102129.png
>
>         Regards.
>         Mifos-developer mailing list
>         mif...@li... <mailto:mifos-
>         dev...@li...>
>         Unsubscribe or change settings at:
>         https://lists.sourceforge.net/lists/listinfo/mifos-developer
>         <https://lists.sourceforge.net/lists/listinfo/mifos-developer>
>
>     Mifos-developer mailing list
>     mif...@li... <mailto:mifos-
>     dev...@li...>
>     Unsubscribe or change settings at:
>     https://lists.sourceforge.net/lists/listinfo/mifos-developer
>     <https://lists.sourceforge.net/lists/listinfo/mifos-developer>
>
>
>
> Mifos-developer mailing list
> mif...@li...
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Re: [Mifos-developer] CLIENT CREATION ERROR

[Peter o. <pet...@gm...>]

Hello,

At the moment there is no entity datatable check:
[image: image.png]

Deleted the manually created data table in system: manage data table and
still cannot create a client:
[image: image.png]

The fineract version is 1.4.0

Regards.


On Thu, Apr 10, 2025 at 11:13 AM Bharath Gowda <bg...@mi...> wrote:

> Hi Peter,
>
> Then I guess you'll need to check if there is a entity data mapping under
> admin->organization->entity data table checks
>
> remove if there are any entries here, and I believe this should solve the
> problem.
>
> Also, could you please let me know which version of UI and Fineract that
> you are using?
> The UI doesn't look like the latest, hence the question
>
>
> example screenshot
> [image: image.png]
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019635592
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
>
>
> On Thu, Apr 10, 2025 at 1:36 PM Peter oliver <pet...@gm...>
> wrote:
>
>> Hello,
>>
>> I get the error when creating the member in the UI as after indicating
>> the mandatory field and the needed optional fields. After am not able to
>> submit the creation.
>> Find attached snip.
>>
>> [image: image.png]
>>
>> On Thu, Apr 10, 2025 at 10:41 AM Bharath Gowda <bg...@mi...> wrote:
>>
>>> Hi Peter,
>>>
>>> Are you getting this error message while you are creating the client
>>> from the UI or when you are trying to save some data in a datatable that
>>> belongs to a client?
>>> A screenshot would be more helpful
>>>
>>> Regards,
>>> Bharath
>>> Lead Implementation Analyst | Mifos Initiative
>>> Skype: live:cbharath4| Mobile: +91.7019635592
>>> http://mifos.org  <http://facebook.com/mifos>
>>> <http://www.twitter.com/mifos>
>>>
>>>
>>> On Wed, Apr 9, 2025 at 6:43 PM Peter oliver <pet...@gm...>
>>> wrote:
>>>
>>>> Hello @all,
>>>>
>>>> Getting an error of "client extra info" does not exist in attempt to
>>>> create the clients data in the system.
>>>>
>>>> This is after deployment without the python file "new_db_initialize.py"
>>>> being executed which should create the client extra info fields via the
>>>> datatable apis.
>>>>
>>>> Opted to attempt to create the client extra info table manually in the
>>>> db but still not able to create/import a client data.
>>>>
>>>> How can i fix this error?
>>>>
>>>> Below is the attached error log:
>>>>
>>>> [image: client creation err.jpg]
>>>> [image: Screenshot 2025-04-09 102129.png]
>>>>
>>>> Regards.
>>>> Mifos-developer mailing list
>>>> mif...@li...
>>>> Unsubscribe or change settings at:
>>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>>
>>> Mifos-developer mailing list
>>> mif...@li...
>>> Unsubscribe or change settings at:
>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>
>>

Re: [Mifos-developer] CLIENT CREATION ERROR

[Bharath G. <bg...@mi...>]

Hi Peter,

Then I guess you'll need to check if there is a entity data mapping under
admin->organization->entity data table checks

remove if there are any entries here, and I believe this should solve the
problem.

Also, could you please let me know which version of UI and Fineract that
you are using?
The UI doesn't look like the latest, hence the question


example screenshot
[image: image.png]
Regards,
Bharath
Lead Implementation Analyst | Mifos Initiative
Skype: live:cbharath4| Mobile: +91.7019635592
http://mifos.org  <http://facebook.com/mifos>
<http://www.twitter.com/mifos>


On Thu, Apr 10, 2025 at 1:36 PM Peter oliver <pet...@gm...>
wrote:

> Hello,
>
> I get the error when creating the member in the UI as after indicating the
> mandatory field and the needed optional fields. After am not able to submit
> the creation.
> Find attached snip.
>
> [image: image.png]
>
> On Thu, Apr 10, 2025 at 10:41 AM Bharath Gowda <bg...@mi...> wrote:
>
>> Hi Peter,
>>
>> Are you getting this error message while you are creating the client from
>> the UI or when you are trying to save some data in a datatable that belongs
>> to a client?
>> A screenshot would be more helpful
>>
>> Regards,
>> Bharath
>> Lead Implementation Analyst | Mifos Initiative
>> Skype: live:cbharath4| Mobile: +91.7019635592
>> http://mifos.org  <http://facebook.com/mifos>
>> <http://www.twitter.com/mifos>
>>
>>
>> On Wed, Apr 9, 2025 at 6:43 PM Peter oliver <pet...@gm...>
>> wrote:
>>
>>> Hello @all,
>>>
>>> Getting an error of "client extra info" does not exist in attempt to
>>> create the clients data in the system.
>>>
>>> This is after deployment without the python file "new_db_initialize.py"
>>> being executed which should create the client extra info fields via the
>>> datatable apis.
>>>
>>> Opted to attempt to create the client extra info table manually in the
>>> db but still not able to create/import a client data.
>>>
>>> How can i fix this error?
>>>
>>> Below is the attached error log:
>>>
>>> [image: client creation err.jpg]
>>> [image: Screenshot 2025-04-09 102129.png]
>>>
>>> Regards.
>>> Mifos-developer mailing list
>>> mif...@li...
>>> Unsubscribe or change settings at:
>>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>
>> Mifos-developer mailing list
>> mif...@li...
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
>