Listing of API Resources

During the deployment, you must list the API resources into active and inactive in order to segregate them into complete or restrictive usage.

Following url can be used for reference API resource documentation:

Apache Fineract API Documentation

END CLIENT:

A standard classification is based on the premise that Fineract Platform has limited/restrictive usage for End Client Relationship Management except in the case of MFIs, where borrower management is a strong use case. Therefore, account holder management can be orchestrated via service layer approach. Thus Client Resources APIs will have restricted use.

CLIENT

Clients are people and businesses(end customer) that have applied (or may apply) for loans or other financial products.

CLIENT CHARGES

Client Charges are client specific instances of Charges(FEES).

CLIENT TXNS

Client level Transactions refer to transactions made directly againt a Client's internal account. Currently, these transactions are only created as a result of charge payments/waivers.

ACCOUNT TRANSFER

Ability to be able to transfer monetary funds from one account to another.

CLIENT ADDRESS

In order to activate optional Address module, we need to enable the configuration, enable-address by setting its value to true.

Accounting

Fineract platform provides a robust and granular level of accounting, accounting bulk reporting and sequential JL entry publishing methods. Following are the listed API resources, you must classify as active if you are planning to use Fineract as an accounting engine.

The following Accounting resources are applicable for all types of financial products.

GENERAL LEDGER ACCOUNT

Ledger accounts represent an Individual account within an Organizations Chart Of Accounts(COA) and are assigned a name and unique number (GL code) by which they can be identified.

The CoAs can have manual or automated postings of JL entries enabled.

The CoAs can have parent-daughter relationships in the form of sub ledger accounts.

The CoAs can be either Header or detail. Detail type CoAs are hit with txn entries.

Accounting Closure

An accounting closure indicates that no more journal entries may be logged (or reversed) in the system, either manually or via the portfolio with an entry date prior to the defined closure date

JOURNAL ENTRIES

A journal entry directly changes the account balances on the general ledger. JL entries are double posted with two cr/db entries and can be automated or manual.

ACCOUNTING RULES

Enter accounting rules, an abstraction on top of manual Journal entires for enabling simpler data entry. An accounting rule can define many of the abstractions. Frequent Postings are a direct consequence of confugured accounting rules.

Financial Account Activity

Organization Level Financial Activities like Asset and Liability Transfer can be mapped to GL Account. Integrated accounting takes these accounts into consideration when an Account transfer is made between a savings to loan/savings account and vice-versa

The following API resources are only specific to Loan Product types.

Periodic Acrual Accounting

Periodic Accrual is to accrue the loan income till the specific date or till batch job scheduled time.

Provisioning Entries

Defines the Provisioning Entries for all active loan products

Loans

Loan

The API concept of loans models the loan application process and the loan contract/monitoring process.

LOAN TXNS

Capabilities include loan repayment's, interest waivers and the ability to 'adjust' an existing transaction.

LOAN PRODUCT MIX	LOAN PRODUCTS
Create a mix of Loan products so as to restrict loan products office and client specific	A Loan product is a template that is used when creating a loan. Much of the template definition can be overridden during loan creation.

PROVISIONING CRITERIA:

Provisioning criterias to bulk loans to check delinquencies.

LOAN TERMS VARIATION

Loan Term Variations provides the ability to change due dates, amounts and number of instalments before loan approval.

STANDING INSTRUCTIONS

At present only savings account to savings account and savings account to Loan account transfers are permitted

LOAN CHARGES

Loan Charges are instances of Charges and represent either fees and penalties for loan products.

LOAN GUARANTORS

A person who guarantees to pay for someone else's debt if he or she should default on a loan obligation. A guarantor can act as a co-signor too.

LOAN COLLATERAL

In lending agreements, collateral is a borrower's pledge of specific property to a lender, to secure repayment of a loan.

LOAN RESCHEDULING

Loan rescheduling provides the ability to give clients extra grace periods, extend loan term by adding extra installments and adjust the interest rate of a loan.

ORG

Title	Description
ENTITY DATATABLE CHECKS:	To restrict datatable usage across different type of lending and permissions workflow.
FUNDS:	Create, read, delete and manage funds
STAFF:	Staff associated with the Org.
CHARGES:	Charges such as fees, penalty at a system defined level.
HOLIDAYS:	Pre defined set of holidays controlling the lending schedules.
WORKING DAYS:	Pre defined set of working days controlling the lending schedules and repayment frameworks.
USER GENERATED REPORTS:	Templates
INTEREST RATE CHART:	Interest Grid
INTEREST RATE SLABS:	Interest Grid
PAYMENT TYPE:	Different types & modes of payments
TAX COMPONENT:	Defining and managing the tax rates.
TAX GROUPS:	Defining and managing the tax groups
RATES:

Following API resources are financial instrument(FI product type) agnostic and can be used by all FIs whether offering only checking or lending or share products.

USER

ALL RESOURCES

SELF SERVICE

ALL RESOURCES

REPORT

ALL RESOURCES

SYSTEM

ALL RESOURCES

NON CORE

ALL RESOURCES

If your use case involves Checking type Products:

SAVINGS	SAVINGS TRANSACTION
ALL RESOURCES	ALL RESOURCES

If your use case involves share type Products:

SHARES

ALL RESOURCES

If your use case involves micro-finance savings and loan products:

GROUPS	CENTERS
ALL RESOURCES	ALL RESOURCES

Following are the inactive resources:

The APIs which are not listed in the above section are not part of a standard deployment. Thus keeping the implementation independent and reliant on external services such as CRM. While the service layer may have these services built, it may not have a communication basis with Fineract. The source of truth to these data points will lie with any stated and defined external service.

E.g are:

CLIENT IDENTIFIER

Restrictive Current API and capability of Fineract to seamlessly connect to external KYC service.

CLIENT IMAGES

Restrictive Current API and capability of Fineract to seamlessly connect to external KYC service.

TEMPLATE

ALL RESOURCES

SPM

ALL RESOURCES