Actions39
- Client Actions
- Loan Actions
Overview
This node integrates with the Fineract API to manage loans and clients. Specifically, the "Charge Off" operation under the "Loan" resource allows users to mark a loan as charged off by submitting a transaction that records the charge off event. This is useful in financial workflows where loans need to be written off due to non-payment or other reasons.
Practical examples include:
- Automatically charging off delinquent loans at the end of a reporting period.
- Recording charge off transactions with relevant metadata such as date, amount, and notes for audit purposes.
- Integrating loan management systems with Fineract to keep loan statuses up to date.
Properties
| Name | Meaning |
|---|---|
| Loan ID | The unique identifier of the loan to be charged off. |
| Transaction Date | The date when the charge off transaction occurs, formatted as YYYY-MM-DD. |
| Transaction Amount | The monetary amount to charge off on the loan. |
| External ID | An optional external identifier for the charge off transaction (e.g., from another system). |
| Note | An optional note or comment describing the charge off transaction. |
Output
The node outputs JSON data representing the response from the Fineract API after performing the charge off operation. This typically includes details about the created charge off transaction, confirmation of the loan status update, and any related metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Fineract API instance.
- Needs configuration of credentials including:
- Base URL of the Fineract API.
- Tenant ID for multi-tenant environments.
- An API key or authentication token to authorize requests.
- The node sends HTTP requests with JSON payloads to the Fineract API endpoint
/fineract-provider/api/v1.
Troubleshooting
- Invalid Loan ID: If the provided Loan ID does not exist or is incorrect, the API will return an error. Verify the Loan ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure credentials are correctly configured.
- Date Format Issues: The Transaction Date must be in
YYYY-MM-DDformat. Incorrect formats may lead to request rejection. - Amount Validation: The Transaction Amount should be a positive number. Negative or zero values might cause errors.
- API Endpoint Unreachable: Network issues or incorrect base URL settings can prevent communication with the Fineract API.
