Apache Fineract csv files for import to set up a basic credit union structure

Clone this repo:
  1. 3e9317c Delete travis.sh by aasaru · 1 year, 5 months ago develop
  2. 51dcb07 Delete .travis.yml by aasaru · 1 year, 5 months ago
  3. cd91828 Merge pull request #10 from Anh3h/develop by Courage Angeh · 4 years, 8 months ago spring_boot_2
  4. 20cceeb Fix bug in ledgers.csv file by Anh3h · 4 years, 8 months ago
  5. 5966920 Merge pull request #8 from Izakey/FINCN-155 by Isaac Kamga · 4 years, 10 months ago

Apache Fineract CN default setup Build Status

This project provides resources which can be used to create a default setup for microservices in Apache Fineract CN deployment. It is dependent on the apis and importers of those microservices.


Apache Fineract CN is an application framework for digital financial services, a system to support nationwide and cross-national financial transactions and help to level and speed the creation of an inclusive, interconnected digital economy for every nation in the world.

Steps needed to create a default setup for a new microservice

  1. Create a module with the same name as the microservice. Add it to settings.gradle, and build.gradle of the composite build.

  2. Place the csv files in subfolder of main/resources

  3. Change build.gradle of your module to reference the importer of your microservice in compileTest

  4. Write a test which checks the format of your csv files to prevent data corruption. See accounting/ImportTest for an example of how to do this.


The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • BUILD-SNAPSHOT - A release currently in development.
  • M - A milestone release include specific sets of functions and are released as soon as the functionality is complete.
  • RC - A release candidate is a version with potential to be a final product, considered code complete.
  • RELEASE - General availability indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:



See LICENSE file.