Fineract icon

Fineract

Interact with Fineract API to manage clients and loans
Join our community

Actions39

Overview

This node integrates with the Fineract API to create new loan records for clients. It is designed to facilitate loan management by allowing users to specify detailed loan parameters such as principal amount, loan term, repayment schedule, and interest rate. This node is beneficial in financial automation workflows where loans need to be programmatically created and managed, such as in lending platforms or financial service applications.

Practical examples include:

  • Automatically creating a loan when a client is approved in a CRM system.
  • Batch processing loan creation from a spreadsheet of client data.
  • Integrating loan origination into a broader financial workflow that includes client onboarding and credit checks.

Properties

Name Meaning
Client ID The unique identifier of the client for whom the loan is being created.
Product ID Identifier of the loan product to apply (e.g., type of loan).
Principal Amount The principal amount of the loan (numeric value).
Loan Term Frequency Duration of the loan term expressed as a number (e.g., 12).
Loan Term Frequency Type Unit of time for the loan term frequency; options: Days, Weeks, Months, Years.
Repayment Every Frequency of repayments expressed as a number (e.g., every 1 period).
Repayment Frequency Type Unit of time for repayment frequency; options: Days, Weeks, Months, Years.
Interest Rate Per Period Interest rate applied per period, expressed as a percentage (numeric).
Expected Disbursement Date Date when the loan funds are expected to be disbursed (format: YYYY-MM-DD).
Submitted On Date Date when the loan application was submitted (format: YYYY-MM-DD).
External ID Optional external identifier for the loan, useful for cross-referencing systems.

Output

The node outputs JSON data representing the newly created loan record as returned by the Fineract API. This typically includes details such as loan ID, status, terms, client association, and timestamps. The output can be used downstream in workflows for further processing, reporting, or notifications.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Fineract API.
  • Needs configuration of the base URL and tenant ID for the Fineract instance.
  • The node sends requests to the /fineract-provider/api/v1 endpoint of the configured Fineract server.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect date formats for expectedDisbursementDate or submittedOnDate may result in validation errors.
    • Providing invalid IDs for client or product may lead to "not found" errors.
    • Network connectivity issues with the Fineract server can cause request timeouts.

  • Error messages:

    • Authentication errors: Check API key and tenant ID correctness.
    • Validation errors: Ensure all required fields are provided and dates are in YYYY-MM-DD format.
    • Resource not found: Verify that the client and product IDs exist in the Fineract system.
    • Server errors: Review server logs or contact the Fineract administrator if unexpected errors occur.

Links and References

Discussion