Appearance
Welcome to Finecko Documentation
Finecko is a managed Core Banking System built on Apache Fineract - the open-source platform that powers financial services for banks, microfinance institutions, credit unions, and fintechs worldwide. Finecko handles the infrastructure, upgrades, and operations so your team can focus on running your institution.
This documentation covers both the Finecko platform and Apache Fineract itself.
New to Finecko?
If you have just received your Finecko credentials, start here:
- Getting Started - first login, initial configuration, and your first API call
What Is in These Docs
Apache Fineract Resources
Background and reference material on Apache Fineract as a platform.
- Apache Fineract Overview - what the platform is, how it is architected, and who it is designed for
- Product Features - detailed pages on every major feature: loan management, savings, clients, offices, accounting, reporting, multi-tenancy, datatables, business events, COB, and user management
- Datatables - real-world use cases for extending every entity type with custom fields
Guides
Step-by-step technical guides for developers and operators.
Setup & Configuration
- Getting Started - onboarding walkthrough for new environments
- Environment Variables Reference - complete reference for all configuration variables
- Instance Types & Deployment Modes - Read, Write, and Batch node architecture
- Global Configuration Reference - all system-wide feature flags
- Payment Types & System Codes - required before recording any transactions
- Accounting Setup - configuring the chart of accounts and GL mappings
Loans & Credit
- Progressive Loan Configuration - advanced payment allocation and interest recalculation
- Charges & Penalties - disbursement fees, overdue penalties, and savings charges
- Loan Collateral & Guarantors - securing loans with assets and guarantors
- Delinquency Bucketing - days-past-due classification and PAR reporting
- Collection Sheets - bulk group loan repayments
Savings & Deposits
- Fixed & Recurring Deposits - term deposits and recurring contribution products
- Standing Instructions - auto-debit and recurring transfers
Operations & Compliance
- Maker-Checker Approval - 4-eyes control for sensitive operations
- Holidays & Working Days - repayment rescheduling on non-working days
- Business Date - decoupling financial date from system clock
- Close of Business - configuring and operating the nightly batch processing job
- Teller & Cash Management - branch cash drawers and shift reconciliation
- Accounting Rules - reusable journal entry templates
- Bulk Data Import - Excel-based migration for clients, loans, and accounts
Integration & Infrastructure
- REST API Overview - authentication, pagination, error handling, and the Swagger UI
- Business Events - the event pipeline, Kafka and ActiveMQ connectors
- Webhooks & Lightweight Integration - polling and middleware bridges
- Multi-Tenancy Configuration - the two-database architecture and tenant provisioning
- Plugin JAR Extensibility - extending Fineract without forking the codebase
- Datatables Extensibility - adding custom fields via the datatable API
- Monitoring & Observability - health checks, metrics, and log patterns to watch
Development & Troubleshooting
- Local Development with Docker - run Fineract locally for testing and API exploration
- Troubleshooting & Common Issues - connection errors, auth issues, and COB failures
- UI Options & Mifos X Web App - community frontends and how to connect them
FAQ
Quick answers to common questions about Finecko as a managed service.
- Hosting - cloud providers, on-premises, and custom deployments
- Security - data encryption, backups, and disaster recovery
- Upgrades - how version updates are managed
- Plans - available tiers and features
- Unsubscription - data export and offboarding
Using the Search
Press Ctrl+K (or Cmd+K on Mac) to search across all documentation. Search works locally in the browser - no data is sent externally.
Questions and Support
For questions not covered in these docs, email [email protected]. The support team typically responds within 24 hours.