How it works
Ikibina encodes the rules most groups already know: a rotating share, a savings pot, and loans that should never be informal. This page is the operator’s version of that story.
The group starts as a draft. Admins set the name, appoint at least one manager, and send invitations. Members and managers accept the invite and choose a password. Until a manager is in place, the group is not ready to run a month.
Every active member owes the configured monthly share and the smaller savings amount. They can attach a proof file (image or PDF). Status moves from not paid → pending → confirmed, or rejected with a reason the member can see.
Managers review proofs, mark payments, and wait until every active member is confirmed. Recipients for the rotating payout are selected and locked. The month cannot be processed while a member is still outstanding or a recipient list is open.
Processing the month splits the share pool among the locked recipients. Group savings accumulate separately and remain visible on the dashboard. Historical months stay in contribution history and reports.
A member may request a loan up to the group cap. Interest, term, grace days, and overdue penalties come from group settings (themselves bounded by platform configuration). Managers approve, reject, and follow outstanding balances on the active-loans view.