Accounting integration

How the integration is wired

The integration is event-source, not batch. Each app has a thin GL bridge module that listens for the operational event (e.g. mfi.loan._post_repayment) and posts the journal in the same transaction. If the posting fails, the operational event is rolled back too — the suite never leaves the GL out of sync with the sub-ledger.

Wiring summary:

• Every loan + savings product has 3–4 GL accounts mapped on its form (principal receivable, interest income, fee income, write-off).
• Every channel (cash, M-Pesa float, Airtel float, sponsor-bank float) has a dedicated cash-equivalent account.
• Every MFI journal (MLOAN, MSAV, MMOB, MSHR, MTRS, MFEE) routes a specific class of entries.
• The company-level defaults (mfi_*_journal_id, share-related accounts) tie the products to the company's books.

The Odoo Apps store edition (MFI Accounting)

The MFI apps sold on apps.odoo.com do not use the GL bridge modules described on this page. MFI Accounting (aminitech_mfi_accounting) posts the entries itself, for any mix of MFI apps installed, with these accounts:

• The accounts are created from your chart of accounts when the app is installed (or found by name if they exist), and you can point each one at your own account in Settings → MFI Accounting → Journal entries for MFI transactions.
• Money that moves between two MFI apps (a loan instalment debited from savings, say) goes through MFI Cash and Clearing, so the two sides net out whichever apps you own.
• Transfers between two members’ savings or shares change no balance-sheet total and post nothing. Reversing a transaction reverses its entry.
• Transactions recorded before MFI Accounting was installed: press Post missing journal entries on the same settings page. It only posts what has no entry yet, so it is safe to press again.
• A posting never blocks the teller or loan officer. If an account is missing, the transaction goes through, the reason is noted on the record, and the button above catches it up once the account is set.
• All entries: Accounting → Journal Entries → MFI Journal Entries, each linked back to the loan, savings, share or member record it came from.

The full event → journal entry map

How to read the Profit and Loss

The MFI Suite posts Revenue under 240xxx (Interest Income, Fee & Commission Income) and Expenses under 25xxxx (Interest Expense, Loan Loss Provisioning, Bad-Debt Expense).

The Kenya P&L variant has been extended to include those code prefixes — on a live tenant with this guide's configuration, opening Accounting → Reporting → Profit and Loss (KE) at "All Time" shows the numbers below:

How to verify the Trial Balance

The trial balance is the production-readiness gate. Open Accounting → Reporting → Trial Balance with date filter "All Time".

Total Debits must equal Total Credits exactly. If not:

• Search Journal Entries for state = Draft. Each draft is missing from the TB and probably has a rounding gap.
• Open each draft and look for a 0.01–1.00 imbalance between the principal / interest / fee components.
• Post the draft (the suite's repayment-posting flow handles rounding by widening the largest line).

Where to wire a new module to the GL

If you build a new MFI module that moves money, follow these conventions:

1. Add a tiny <module>_gl_bridge shim module (or extend an existing bridge).
2. Listen on the operational event method (action_post / action_confirm).
3. Build the account.move with two or more lines that sum to zero.
4. Call move.action_post() in the same transaction.
5. On failure, let the exception bubble so the operational event rolls back too.