Activate the MFI Suite

The MFI Suite is sold as a fully managed SaaS. There is nothing to install. When you complete checkout, your tenant is provisioned automatically, a welcome email lands in your inbox with sign-in credentials, and you can be onboarding your first member inside an hour.

BridgeERP backend home
The first screen after sign-in — your MFI Suite tenant, ready to use.

How activation works

  1. Pick your plan on mybridgeerp.com and complete checkout.
  2. Tenant provisioning runs in the background — typically 5–15 minutes from purchase to ready. You will see a status page while it works.
  3. Welcome email lands with your tenant URL (your-name.mybridgeerp.com), the administrator login, and a one-time link to set your password.
  4. Sign in and run the welcome wizard — branch, country profile, default currency, first operator. Five minutes.
  5. You are live. Start onboarding members and capturing transactions.

What is included out of the box

  • Latest version of the MFI Suite — all 38 modules, automatically updated as releases ship.
  • A managed PostgreSQL database with daily backups (30-day retention) on the Starter plan, and point-in-time recovery on Pro / Enterprise.
  • HTTPS / TLS, custom subdomain, optional custom domain.
  • Pre-seeded chart of accounts, sample loan + savings products, sample roles — every record tagged DEMO_ so you can wipe them in one click when you are ready for production data.
  • Two-factor authentication on every operator login (mandatory).
  • SOC 2 evidence collection running from day one.

What to do in the first hour

Once you are signed in, follow this order — it matches how a real operator learns the suite, and every step has a tutorial below.

  1. Core — rename your branch, create operators, set country profile.
  2. Members — onboard your first member, capture KYC.
  3. Savings — open a savings account and post a deposit at the teller.
  4. Loans — capture a loan application and run the disbursement.
  5. Accounting integration — verify the journal entries the suite has already posted for you.

Enabling optional features

Most advanced features (Term Deposits, Group Lending, IFRS 9, Pesalink, RTGS, Open Banking, USSD, WhatsApp) are hidden by default. Turn them on as your team grows into them — no upgrade ticket needed.

  1. Open Configuration → Settings → MFI Suite.
  2. Find the feature block (Savings, Loans, Channels, Compliance, etc.).
  3. Toggle the feature on. Save.
  4. The new menus appear instantly. See Feature Gates for the full list of toggles.
MFI Suite settings page
Configuration → Settings → MFI Suite — every optional feature is a toggle on this page.

Adding a custom domain

Out of the box your tenant is at your-name.mybridgeerp.com. If you own a domain (e.g. sacco.example.co.ke) and want your members to use it for iBANK and the public website:

  1. Open Configuration → Settings → Website → Custom domain and enter the domain you control.
  2. The wizard tells you the DNS records to add at your registrar (one CNAME for the tenant, one for the iBANK subdomain).
  3. Save. The platform provisions a TLS certificate automatically within ~5 minutes of the DNS pointing at us.

Adding more operators

The first administrator user is created by checkout. Adding teammates takes about 30 seconds:

  1. Open Settings → Users & Companies → Users → New.
  2. Enter the operator's name, email, branch.
  3. Assign them their role groups (Front Office, Credit, Operations, Finance, Compliance, HR, Branch Manager, Executive) — see the Core page for what each role unlocks.
  4. Save + send invite. The operator receives a welcome email with a link to set their password and enrol their 2FA device.

Self-hosted / one-time licence buyers

If you purchased a one-time (perpetual) licence and chose to run the suite on your own infrastructure, you receive a dedicated installation runbook bundled with the licence delivery (PDF + scripts in your customer portal). That runbook covers Docker / VM provisioning, secret management, TLS, backup, monitoring and the upgrade procedure.

The user-facing documentation in this site assumes a managed tenant — the menus, workflows and screenshots are identical, only the operations layer differs.

Next steps

Was this page helpful?