Pages on specific platform features that change how a Fineract implementation is designed and controlled: approvals, logical business dates, restructuring, delinquency, authentication and custom data.
Designing four-eyes control in Fineract: which state-changing APIs to put under maker-checker, roles and fine-grained permissions, the approval queue, and the command audit trail auditors and regulators ask to see.
Running Fineract on a logical business date: cutoff times before or after midnight, how COB date and business date interact, catching up missed days after an outage, and testing loan lifecycles by moving the date.
Restructuring loans for borrowers in difficulty: re-amortization spreading overdue principal over existing installments versus re-aging with a new schedule, interest handling options, eligibility rules and reversal behavior on progressive loans.
Tracking arrears in Fineract: delinquency buckets and ranges, how COB tags loans, pausing and resuming delinquency for payment holidays or disputes, emitted events and reporting to collections teams.
Turning on Fineract 2FA for staff: the configuration flag, OTP request, validation and delivery methods, token invalidation, and how 2FA fits with OAuth2 and an external identity provider.
Extending Fineract clients, loans and other entities with data tables: registering tables against application tables, one-to-one and one-to-many data, entity data table checks, and keeping extensions upgrade-safe.
Defining account number formats for clients, loans and savings: prefix types, choosing formats before migration so legacy account numbers survive, and external IDs for integration keys.
Configuring the drop-down lists behind Fineract forms: codes and code values for identifier types, closure and rejection reasons, genders and custom fields, and keeping them consistent across tenants.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.