Going live, in four steps.
Moving a lender onto a new core system is mostly about getting the configuration right and proving the data before it is written. This is how that works on Fused.
Step 1
Configure
We set Fused up to look like your institution before anything is loaded into it.
- The office tree: head office, regions and branches, which every figure is scoped to.
- The business calendar: your working week, the year’s Poya days and other holidays, for every branch or a few.
- The chart of accounts, provisioned from a finance-company starter with leasing, pawning, hire purchase and factoring accounts, then adjusted to yours.
- Your loan and savings products, their rate charts and fees, released as dated versions.
- Roles, office scope and the approval flows your controls require.
Step 2
Load
Your clients and balances come across, with nothing written until the file is proven.
- Clients import from a CSV file through the same enrolment rules as the form, whole or not at all.
- A dry run checks the whole file first and names every row that would be refused.
- Opening balances post one entry per branch and currency, with the contra amount computed rather than typed.
- How your existing loan book moves across is planned with you during scoping.
Step 3
Rehearse
Your team works through its own day on its own numbers.
- A disbursement, a repayment at the counter and a collection sheet, each checked against the entry it posts.
- Approval flows exercised by the people who will approve.
- The reports your management and board read, run and compared with what you use today.
Step 4
Go live
Branch by branch, with the ledger balancing from the first day.
- Tills opened and counted by denomination.
- The trial balance footing to zero in every office from the first posting.
- Month-end worked through the closing checklist.
Plan your move with the team that builds Fused.
A walkthrough with the team that builds Fused: your loan products, your branches, your month-end.