Fineract in production
Architecture, deployment, configuration, loan and deposit migration, and go-live with a contingency plan. Multi-tenant, highly available, with full accounting traceability.
Boutique consultancy · Apache Fineract
Open-source core banking. In production.
We implement Apache Fineract for banks, credit unions, fintechs, fund managers and microfinance institutions in Latin America: lending and deposits designed with accounting precision, multi-currency, multi-branch, integrated with your ecosystem and operating from day one.
20+years in financial systems
FineractApache platform, no license fees
LatAmplus projects in other regions
Services
Three things we do well, and only those.
A small firm with judgment: every implementation is led by the person who designed it. No management layers, no gap between what was promised and what gets built.
Lending and deposits, from rulebook to configuration
Loans, credit lines, demand savings, term and recurring deposits: schedules, rates, fees, taxes, withholdings and how each posts to the ledger, on accrual or cash basis. Local regulatory compliance by design.
A connected ecosystem, an untouched core
Extensions as modules, not as a fork. Origination, portal, payments, KYC, credit bureaus and regulatory reporting connected through API and events, so the core upgrades without rewriting the integration.
Products and use cases
Every product, with its journal entry solved.
What we configure and what we have extended on Fineract for real clients, on both sides of the balance sheet.
Lending
Progressive lending
Amounts that grow with the client's track record: tiers, graduation rules and automatic re-qualification.
Buy now, pay later
Interest-free installments for merchants, with partner fees, daily reconciliation and integrated collections.
Working capital
Revolving lines and credit limits for SMEs: drawdowns, partial repayments and real-time availability.
Multiple disbursement
Scheduled or milestone-based tranches on a single loan, each with its own schedule and accrual.
Fees and charges
Disbursement, servicing, late-payment and service charges: flat, percentage, event- or calendar-driven.
Taxes and withholdings
VAT, transaction taxes and withholdings applied to interest and fees, with their journal entry and per-jurisdiction reporting.
Deposits
Demand savings
Transactional accounts with interest on balance, withholdings, maintenance fees, holds and authorized overdraft.
Term deposits
Fixed deposits and CDs: rate by term and amount, auto-renewal, early redemption with penalty, interest paid out or capitalized.
Recurring deposits
Scheduled savings with installment and goal: auto-debit, missed installments, extensions and settlement at maturity.
Operations
Multiple currencies
Products and accounting per currency, dated exchange rates and balance restatement at period end.
Branches and agencies
Office hierarchy, tellers and cash drawers, inter-branch transfers and accounting per office or consolidated.
Accrual and cash accounting
Accounting rules per product and event, accounts per office or fund, daily close and reconciliation with the general ledger.
Reporting
Regulatory, management and portfolio reports from a read replica or data warehouse, without loading the core.
Loan and deposit migration
Loading clients, active loans, accounts and balances from the legacy system, reconciled to the cent against the cut-off balance sheet.
Daily close and jobs
Close of business (COB), accrual, arrears, provisioning and renewals as monitored jobs, with controlled reprocessing when something fails.
Platform
Loan origination
Application flow, documents, scoring and tiered approval, integrated with the Fineract API.
Customer portal
Balances, statements, payments and requests on web and mobile, on the same source of truth as the core.
Risk and compliance
KYC, watchlists, credit bureaus and portfolio analysis: provisioning, arrears and concentration.
Architecture and patterns
The core stays untouched. Everything else connects to it.
Fineract evolves with every Apache release. An implementation that modifies it from the inside freezes at the version it was modified in. These are the patterns we use to avoid that.
Extend by modules, not by fork
Custom logic lives in Spring modules loaded alongside the core, or in separate services. Upgrading Fineract is a version bump, not a months-long merge.
One entry point
An API Gateway with OIDC in front of Fineract and the custom services: authentication, quotas, audit and API versioning in one place.
Events with an outbox
Every business event (disbursement, repayment, account opening) leaves through an outbox table into the bus. No consumer misses an event when it goes down; no producer blocks the core.
Reads separated from writes
Reporting, BI and portals read from a replica or a warehouse fed by events. The core only serves transactions.
Multi-tenant by design
One deployment, several tenants with isolated data: useful for groups with several entities, for white-label fintechs, and for test environments identical to production.
Observable operations
Traces, metrics and logs correlated per transaction; alerts on the daily close (COB) and accrual jobs before accounting notices the difference.
Process
From rulebook to production in four stages.
Order matters: nothing gets configured that isn't written down and validated with accounting first.
- 01 · Diagnosis
Rulebooks and portfolio
We read the products the way the regulator sees them and the way the ledger sees them. Out come the gaps and the chart of accounts.
2 to 3 weeks - 02 · Design
Product and accounting model
Every product fully specified: schedule, rates, charges, taxes, arrears, event-based accounting. Signed off before the system is touched.
3 to 4 weeks - 03 · Build
Configuration and integration
Fineract configured, extensions built, integrations connected and tests run on real portfolio cases.
6 to 12 weeks - 04 · Go-live
Migration and production
Migration reconciled to the cent, supported operation for the first weeks and handover to the internal team.
3 to 6 weeks
Why Art3ch
Building solutions with technology is an art.
Doing it well, efficiently, powerfully and simply is not something anyone can do. That is the name, and that is the promise.
- Accounting firstEvery product is designed from the T-account. If the entry doesn't balance, the product doesn't ship.
- Open source, no lock-inApache Fineract charges no license and no per-seat fees. Your institution owns its core and its data.
- Twenty years in the sectorBanks, credit unions, fintechs and microfinance. We know what breaks in a migration before it starts.
- Latin America as a specialty, not a limitColombian and regional regulation solved; projects outside the region too.
“A core banking system isn't software: it is the executable version of your product rulebook. Our job is to make that version exact.”Alberto · Founder & CEO, Art3ch Solutions
Blog
Implementation notes.
What we learn configuring Fineract in production, written for the person who has to make the technical call.
September 27, 2026
Fineract without a fork: five patterns to extend it and keep upgrading
How to add custom logic, integrations and reporting to Apache Fineract without modifying the core, so that every new Apache release is a version bump and not a migration project.
Read →September 20, 2026OIDC in Fineract: stop managing passwords in the core
How to delegate Apache Fineract authentication to an identity provider (Keycloak, Entra ID, Google) with OpenID Connect, what changes in the API and what does not change in permissions.
Read →September 13, 2026Term loans in Fineract: the seven decisions that define the product
What each key parameter of a term loan product means in Apache Fineract, how it changes the installment and the journal entry, and which combinations produce results nobody can explain later.
Read →Contact
Tell us which product you want in production.
A 30-minute call to understand your portfolio, your regulation and your timeline. No sales deck: concrete questions and a first read on feasibility.