A new way Wakandi collects its fees, and a run of loan and import fixes

Amawulire Amaggya Kyakyusibwa

Released: 24 September 2026

Summary

Eighteen items shipped. Wakandi's own fees now use a new collection method: instead of an institution topping up its Wakandi Business Account before a fee is charged, the fee is collected from the institution's connected bank account once the transaction has gone through. A credit report or ID verification that fails is no longer charged to the member, and a run of loan, accounting and import fixes rounds out the release.

What's new

  • Wakandi's own transaction fees are now collected directly from an institution's connected bank or mobile-money account once a transaction has gone through, instead of requiring the institution to pre-fund its Wakandi Business Account, alongside related fee-accuracy fixes.
  • A credit report or national ID verification order that fails is no longer charged to the member. These orders used to be marked complete, and the fee billed, even when the check itself failed; the fee is now reversed whenever that happens.
  • Loan repayment file imports no longer reject a valid loan product as invalid after the product's name changed through a policy resubmission, at an institution in Kenya.
  • Loan repayment file imports no longer wrongly reject a correct loan product, and removing a repayment no longer fails with a false overpayment error.
  • Loan repayments no longer get stuck at "Created" status when an installment's due date falls in a prior financial year, at an institution in Tanzania.
  • A fully paid loan installment no longer continues to show as overdue on the repayment schedule, at an institution in Uganda.
  • Member imports that update a Quick Loan credit limit no longer fail with a false "user does not exist" error for members already visible in the client list.
  • Transactions no longer get stuck in Submitted status with a false financial-year-locked error when the current year is actually open, at an institution in Kenya.
  • Correcting an unusually large fund-allotment transaction no longer fails because the reversing entry could not accept amounts over 10 digits, at an institution in Uganda.
  • Newly created institutions no longer get stuck showing as "in progress" after setup has actually finished, which had also caused a false "user does not exist" error when editing a brand-new user's roles, at an institution in Kenya.
  • The Statement of Financial Position now reflects the correct owner's equity balances from the chart of accounts, fixing a mismatch that had left assets and liabilities-plus-equity out of balance, at an institution in Tanzania.
  • The Owner Equity edit screen in Accounting reports now responds correctly when values are entered, at an institution in Tanzania.
  • Staff can now open and edit a member's details from within a group's Members tab, fixing newly added group members that previously could not be opened, at an institution in Kenya.
  • A group's Members tab now reliably lists its members instead of sometimes showing an empty list, at an institution in Uganda.
  • The Chart of Accounts ledger drill-down now correctly shows its transaction listing instead of appearing empty.
  • Transaction and fee data now loads correctly in the Collections & Disbursement and Expenditure tabs, instead of appearing empty.
  • Staff can now rename an existing savings product from Settings, instead of the name being locked permanently after creation.
  • Inviting a new administrator no longer fails with a server error.

What this means for you

If your institution tops up a Wakandi Business Account so that fees can be charged, that step is no longer needed for online transactions: fees are now collected directly from your connected account instead.