You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "James Dailey (Jira)" <ji...@apache.org> on 2020/05/03 03:01: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=17098194#comment-17098194 ]
James Dailey commented on FINERACT-871:
---------------------------------------
Henry -
So, I understand that what you are asking for. You need the overall solution to generate the proper NUBAN (account number with built in check sums) and that this number has reference to the static Bank number.
I think you should reach out to the listserv with a request to help you with this. You may need to engage $$ someone to code this and then have that contributed back to the core. Or you may find a volunteer.
Since this is a custom numbering scheme for account numbers, it has a couple of different pieces (I believe). Since I may be wrong, please comment and clarify.
1)Generating a new account number. This could be done partly via a front end which takes a known fixed BankID and then checks the storage of existing account for the next in sequence and then does the modulo calculations in the regulatory circular you attached above.
2) The backend storage of the number (trivial and already supported I believe, via custom fields)
3) Modifying the APIs to support this exchange of data - if necessary? I think it may be possible to use existing APIs in a sequence.
If you can put the requirements more in a kind of developer requirement, that would help.
> 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)