BOSA vs FOSA: How a Unified System Helps
5 min read
Defining the Two Sides
Back Office Service Activities (BOSA) cover a SACCO's traditional savings and lending business: member shares, savings accounts, and loans. Front Office Service Activities (FOSA) cover banking-style services members interact with directly, such as current accounts, withdrawals and over-the-counter transactions.
Where Separate Systems Cause Friction
When BOSA and FOSA run on different systems, staff often have to key the same member details twice, reconcile two ledgers at month-end, and reassure members why their balances differ between the two service points. It also complicates audit, since transaction history is split across systems.
What Changes with a Unified Platform
On a single platform, a member's savings, loan and FOSA transactions post to the same account structure and the same general ledger. Front-desk and back-office staff see the same live balances. Audit trails cover both sides of the business in one continuous record, which also simplifies SASRA-aligned reporting.
A Practical Example
Consider a member repaying a loan at the FOSA counter. On a unified system, that repayment updates the loan account, the member's savings-linked collateral if applicable, and the general ledger, all in the same transaction. On separate systems, that same repayment might require a second manual entry in the BOSA system later the same day.
See the Platform Behind This Article
Book a free walkthrough tailored to your organisation.