October 20, 2026 · 3 min read
The chart of accounts in Fineract: what to create before configuring the first product
A cash-based loan product requires 19 GL account mappings; on accrual, 25. Which ones they are, which ones always get forgotten, and why the order matters.
The usual sequence in an implementation is: create the product, test it, and find out on the first attempt that Fineract will not save it because accounts are missing. Somebody then improvises a chart of accounts to get moving, and that improvised chart stays for five years.
The right order is the opposite: the chart of accounts is designed before anyone opens the product screen. For that you need to know exactly how many accounts Fineract asks for and what each one is for.
First, the decision that sets the number
Fineract offers four accounting rules per product, and the choice changes how many accounts you need:
NONE, no accounting. Testing only.CASH_BASED: the journal entry is generated when money moves.ACCRUAL_PERIODIC: income is recognised as it accrues, through a daily process.ACCRUAL_UPFRONT: income is recognised in full at disbursement.
A cash-based loan product requires 19 account mappings. The same product on accrual requires 25. Those six extra are not optional, and they are precisely the ones missing from every inherited chart of accounts.
The ones that exist only on accrual
Seven accounts appear only when you choose accrual, and they are worth knowing because they are what forces the conversation with accounting to happen early rather than late:
Interest receivable, fees receivable and penalties receivable. These are the bridge accounts where recognised-but-uncollected income lives. If your chart does not have them, you were not really doing accrual.
Deferred income liability, for income collected that does not yet belong to the period.
And three more for specific scenarios: income from capitalisation, and the expense and income pair for buy-down.
On the deposits side the gap is smaller but just as real: a savings account maps 10 accounts on cash and 14 on accrual, adding interest payable, interest receivable and the two receivables.
The ones everybody forgets
One group never appears in a traditional chart of accounts, because it does not correspond to a classic accounting concept but to a system state:
Overpayment. When a client pays more than due, that money is not income: it is a liability until applied or refunded. Fineract requires the account and uses it on its own.
Transfers suspense. The temporary contra account for movements between branches or between accounts. Without it, a transfer leaves the entry open.
Charge-off, with its variants. Fineract separates charge-off expense from fraud charge-off expense, and income from interest, fees and penalties recovered after charge-off each goes to its own account. That is six accounts almost nobody anticipates, and they surface on the day of the first charge-off.
Recovery. Income from an already charged-off loan does not go back to the interest account: it goes to its own recovery account.
What gets mapped once
Beyond the per-product accounts, there are seven organisation-level mappings configured once and used everywhere: asset transfer, liability transfer, cash at main vault, cash at teller, opening balances transfer contra, asset fund source and payable dividends.
The two cash ones are what make teller operations possible. If you are going to have tellers, those mappings are not optional, and they are best decided when you design the office hierarchy rather than when you open the first till.
The order I would follow
Decide the accounting rule first, because it determines whether you need 19 accounts or 25, and because changing it once you have a live portfolio is not a reconfiguration but a migration.
List the accounts per product, not per institution. Two loan products with different treatments — one consumer, one commercial — may need separate accounts so that management reporting comes out without manual work later.
And validate that list with accounting before opening Fineract. Every missing account will surface anyway, but at the worst moment: during testing, under time pressure, and the decision will be taken by whoever is configuring rather than by whoever answers for the balance sheet.