You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Airsay (Jira)" <ji...@apache.org> on 2020/04/29 21:58:00 UTC
[jira] [Commented] (FINERACT-871) NUBAN Account Format is Required
[ https://issues.apache.org/jira/browse/FINERACT-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095912#comment-17095912 ]
Airsay commented on FINERACT-871:
---------------------------------
Is this to do with how Fineract Generates Account Numbers? I understand the NUBAN coding scheme but I need to understand what your request is about
> NUBAN Account Format is Required
> --------------------------------
>
> Key: FINERACT-871
> URL: https://issues.apache.org/jira/browse/FINERACT-871
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Accounting, Client
> Affects Versions: 1.3.0
> Reporter: Henry
> Priority: Blocker
> Attachments: Exposure Circular for NUBAN.pdf
>
>
> Hello mentors,
>
> We are starting an implementation for one of our MfB in Nigeria. While Mifos is the preferred option we are stuck with a regulatory requirement account client account format.
> Nigeria operates a Unified client account format: Nigeria Unified Bank Account Number (NUBAN) system which we have observed cannot be achieved in Mifos at the moment.
> I have attached the guide on how to generate the NUBAN compliant account numbers for your review and assistance to proceed with our project.
> We are available for further clarifications.
>
> Best regards,
> Henry.[^Exposure Circular for NUBAN.pdf]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)