MicroZen
Platform Roles Field Customers Blog
New Connected microfinance operations

One platform. Every role. Smarter microfinance.

Microfinance operations, finance and people on one record — from member enrolment and the samity collection sheet through to the branch ledger and the regulatory return.

See how it works
app.microzen.com/fis/overview
MicroZen FIS dashboard: cash position, daily inflow and outflow, and ledger integrity
MicroZen mobile app: loan applications by status and the applications list
Built for institutions that answer to a regulator and an apex funder.
Microcredit Regulatory Authority Palli Karma-Sahayak Foundation Padakhep Manabik Unnayan Kendra BASIS
Operating at scale

One platform, wherever the last mile is.

Every branch writes to one record — one member file, one set of entries, one classification applied the same way everywhere.

1.8Mmembers managed

Every cycle, instalment, and credit rating held in one file, from enrolment to closure.

$2.1Bdisbursed to date

USD equivalent tracked end to end, reconciled against the branch ledger each night.

94%collection rate

Recorded where officers work the route-ordered daily sheet instead of a paper register.

MicroZen Field App

11,400field officers

Working offline in the field, syncing the moment a signal returns.

Product ecosystem

Four modules, one operational spine.

Each module is usable on its own and stronger connected.

MZ-01

MF Ops

Microfinance operations end to end: member enrolment and verification, income-based credit assessment, disbursement controls, collection sheets built from the samity calendar, and a day-end that will not close on an unreconciled taka.

Member lifecycle Credit assessment Disbursement controls Collections Savings Classification Field app
Explore MF Ops
MF Ops screen: list of disbursed loans with payment method, FIS postings, and member verification
MZ-02

FIS

Finance and accounts for a multi-branch institution: twelve voucher types, independent books for every office, shared cost allocated down to programme level, and a period close under controls no role can waive.

Chart of accounts Vouchers Cost allocation Consolidation Period close Fund transfers Audit trail
Explore FIS
FIS financial reporting screen: cash position, daily inflow and outflow, ledger integrity, and voucher register
MZ-03

Reporting

Ledgers, statutory formats, and branch consolidation generated from the same entries, so head office reads one set of numbers.

Ledger Statutory formats Consolidation Drill-down Scheduled export
Explore Reporting
Reporting and analytics screen: disbursed loan totals, portfolio at risk, self-sufficiency, and collection efficiency
MZ-04

HRIS

The employee lifecycle on one record: onboarding and the employee master, attendance merged from the biometric feed, leave and exchange leave, transfers with handover, and payroll through to settlement.

Onboarding Employee master Attendance Leave Payroll Separation Field self-service
Explore HRIS
HRIS screen: active employees, pending approvals, and employee separation requests
Built for every role

The same platform, framed around the work each person does.

Field officers, branch managers, and head office each see the view their day needs.

{{ role.label }}

{{ role.headline }}

{{ role.blurb }}

{{ b }}
{{ role.screen }} {{ role.scope }}
{{ k.label }} {{ k.value }}
{{ row.id }} {{ row.text }} {{ row.status }}
MicroZen Field App

The work happens at the samity, not at a desk.

Verification at the point of enrolment, geo-tagged evidence from the field, and the member’s full history on hand at the meeting.

Mobile loan applications screen: application counts by status, filters, and the applications list
Member verificationIdentity, repayment, and savings history checked at the doorstep.
NA Nasrin Akter#MZ-2041 · Savar centre 12 Rating A–
Outstanding৳ 28,400
On time98%
Cycle3 of 3
Last 12 instalments
National ID matched
Home visit geotagged
Guarantor signaturePending
New loan applicationRaised at the centre meeting and sent for verification.
MemberRokeya Begum · #MZ-1987
Loan productMicro-enterprise · 12% flat
Amount৳ 40,000
Instalments46 weeks
Loan purposePoultry
Weekly instalment৳ 974 Submit
{{ t.label }}

Scheduled to the samity calendar

Instalment dates are generated from the samity’s own collection calendar, so every due date is by construction a meeting day. No holiday-shift rule is needed because no date ever lands off-calendar.

Evidence captured in the field

Locality surveys, member enrolment and IGA site visits capture geo-tagged evidence, queue on the device when there is no signal, and sync when the connection returns.

A day that closes on a reconciliation

Eleven mandatory day-end items across five categories, with no partial completion and no override of the completion gate. A single taka of variance blocks the day.

The whole member file, not a summary

Prior cycles, arrears, consent record and both current classifications sit on the member record, so a question at a samity meeting does not need a call to the branch.

Identity verified at enrolment

Government ID verification with OCR auto-population and mismatch flags, OTP confirmation on the member’s own mobile, and fingerprint verification where the product requires it.

Scoped access, permanent record

An officer sees only their own portfolio, and every action is written to an append-only trail carrying the actor, the timestamp and the state before and after.

Why MicroZen

What changes after the first cycle.

The difference shows up in the numbers your branch managers already track.

Spreadsheets and ledgers
With MicroZen
{{ w.bLead }} {{ w.bRest }}
{{ w.aLead }} {{ w.aRest }}
Each line describes how the platform is specified to behave.
Customers & trust

Run by the people who close the day.

Institutions running their branch network on MicroZen.

{{ quote.text }}

{{ quote.initials }}
{{ quote.name }} {{ quote.role }}
Verified customer
Year: 2025 FinTech Innovation of the Year Award by: Bangladesh FinTech Award
Year: 2019 BASIS National ICT Awards Award by: BASIS
Blog

What is happening at MicroZen

Notes from the field on running a microfinance operation.

Ready to build a smarter microfinance operation?

See how MicroZen can transform the way your teams manage, operate, and grow.

45-minute walkthrough · no commitment
MZ-01Microfinance operations

Microzen MF Operations

The complete microfinance lifecycle on one record — prospecting and member admission, income-based credit assessment, disbursement, collection and savings, delinquency recovery, and the branch day close. Lending policy is configured by the institution, not written into the code.

app.microzen.com/mf-ops
Microzen MF Ops screen
Product tour

Inside MF Ops

Screens from MicroZen MF Ops. Choose a feature to zoom into the part of the screen that handles it.

app.microzen.com/mf-ops/disbursements
MicroZen MF Ops screen
{{ m_mfops.counter }}{{ m_mfops.cap }}
What sets it apart

Where it stops being a generic lender

Scoring is built around the borrower’s own income-generating activity, classification runs two taxonomies at once, and the branch day will not close on a rounding difference.

  1. 01 / 07

    Credit assessment on the member’s own income-generating activity, capped by the lowest of eight limits

  2. 02 / 07

    Regulatory and institutional classification evaluated in parallel on every loan

  3. 03 / 07

    Member Welfare Fund adjustment with dual rule sets and a mandatory residual deposit

  4. 04 / 07

    Instalment dates drawn from the samity calendar — every due date is a meeting day

  5. 05 / 07

    Fifteen codified blocking rules: hard blocks, wait states and overridable conditions

  6. 06 / 07

    An eleven-item Day-End whose overridden close stays distinguishable from a clean one

  7. 07 / 07

    Chain of custody from lead to loan, with a provenance hash recomputed at each step

Industry standard

What a multi-branch lender now expects

Configurable chains, identity verified against the government register, classification that runs daily, and a period that closes on a checklist rather than a conversation.

app.microzen.com/mf-ops

Approval workflow

Approval chains configured from the front end, with escalation, vacancy skip and same-user blocking.

Identity checks

Government NID verification with OCR auto-population and mismatch flags.

Transaction authentication

OTP at onboarding, disbursement and withdrawal, with optional fingerprint per operation.

Field evidence

Geo-tagged capture for surveys, enrolment and IGA sites, synced on reconnect.

Loan classification

Automatic regulatory classification with configurable provision rates and daily provisioning.

Payment channels

Disbursement and collection by cash, bank, cheque or mobile financial services.

Period close

Day-End, Month-End and Year-End close, each gated by its own mandatory checklist.

Foundations

The floor a lender is judged on

Every configuration change passes an approval chain, every user sees only their own slice of the hierarchy, and every action lands in a trail that cannot be edited or erased.

  1. 01

    Approval-gated configuration

    Every configuration entity approval-gated — units, programmes, loan and savings products

  2. 02

    Hierarchy-bound visibility

    Data visibility bounded by hierarchy position, on every screen and every report

  3. 03

    Append-only audit trail

    Append-only audit trail: actor, role, state before and after, timestamp

  4. 04

    Enforced status transitions

    Enforced status transitions; an unauthorised change is blocked and recorded

MZ-01 Core record
Microzen MF Ops
  1. 01Approval-gated configuration
  2. 02Hierarchy-bound visibility
  3. 03Append-only audit trail
  4. 04Enforced status transitions
  5. 05Validated data and documents
  6. 06Member SMS notifications
  7. 07Logged report exports
  1. 05

    Validated data and documents

    Mandatory-field validation and document upload under format, size and verification status

  2. 06

    Member SMS notifications

    SMS notification to the member on every material state change

  3. 07

    Logged report exports

    Operational reporting exported to Excel, PDF or CSV, with every export logged

Ready to build a smarter microfinance operation?

See how MicroZen can transform the way your teams manage, operate, and grow.

45-minute walkthrough · no commitment
MZ-02Financial information system

Microzen FIS

The finance and accounts backbone of a multi-branch institution — the chart of accounts, the vouchers and the books, fund movement between head office and the branches, shared cost allocated down to programme level, and the day, month and year close.

app.microzen.com/fis
Microzen FIS screen
Product tour

Inside FIS

Screens from MicroZen FIS. Choose a feature to zoom into the part of the screen that handles it.

app.microzen.com/fis/overview
MicroZen FIS screen
{{ m_fis.counter }}{{ m_fis.cap }}
What sets it apart

Integrity that is structural, not procedural

Shared cost is allocated to zero rather than estimated, both legs of a transfer post as one, and nothing is ever physically deleted from the system.

  1. 01 / 07

    A Common Items unit at every office level, allocated monthly until it reads zero

  2. 02 / 07

    Balance-sheet items allocate once in their month of origin, never drifting afterwards

  3. 03 / 07

    Through the month the books hold the unsplit balance; the split is shown, never posted

  4. 04 / 07

    Allocations must equal the originating pool to the cent, programme leg by programme leg

  5. 05 / 07

    Fund cost, the single documented exception, allocated on average daily inter-office borrowing

  6. 06 / 07

    Every inter-office movement posts both legs as one transaction and reverses as one

  7. 07 / 07

    No interface or privileged role removes a voucher, an audit entry or an attachment

Industry standard

The integration and control layer

Upstream events post themselves against a locked mapping set, failures queue for a named owner, and each period closes through the same defined sequence at day, month and year.

app.microzen.com/fis

Automated postings

Field and payroll events post automatically against a versioned, locked mapping set.

Posting schedules

Posting timing configured per transaction class: immediate, gated, or period-end batch.

Failure handling

An exception queue separating transient from terminal failure, with retry and escalation.

Consolidation and eliminations

Balances consolidate up the hierarchy, with eliminations recorded as named entries.

Period close

Soft close admits only flagged adjustments; hard close is immutable to every role.

Alerting

Configurable alerts with per-alert thresholds, schedules and four delivery channels.

Traceable figures

Drill-down from any monetary figure to the voucher and the transaction behind it.

Foundations

The structure and the complete record

Twelve voucher types route themselves to the right books, every office keeps its own full set, and no voucher reaches approval without a document and three different people.

  1. 01

    Chart of accounts

    Chart of accounts across five categories, with hierarchical codes and posting rules

  2. 02

    Twelve voucher types

    Twelve manual voucher types, each routed to its books by a fixed rule

  3. 03

    Books per financial unit

    Independent cash book, bank book, sub-ledger and general ledger per financial unit

  4. 04

    Three-user approval

    Maker, verifier and approver must be three different users, on configuration as on vouchers

MZ-02 Core record
Microzen FIS
  1. 01Chart of accounts
  2. 02Twelve voucher types
  3. 03Books per financial unit
  4. 04Three-user approval
  5. 05Gapless numbering
  6. 06Document before approval
  7. 07Immutable audit record
  1. 05

    Gapless numbering

    Gapless voucher numbering per type, branch and fiscal year, never reused

  2. 06

    Document before approval

    No voucher reaches approval without a supporting document attached

  3. 07

    Immutable audit record

    Immutable audit record of actor, state before and after, and reason, retained seven years

Ready to build a smarter microfinance operation?

See how MicroZen can transform the way your teams manage, operate, and grow.

45-minute walkthrough · no commitment
MZ-03Reporting and analytics

Microzen Reporting

Microzen Reporting is the analytics and reporting layer that sits across MF Operations, FIS and HRIS.

app.microzen.com/reporting
Microzen Reporting screen
Product tour

Inside Reporting

Screens from MicroZen Reporting. Choose a feature to zoom into the part of the screen that handles it.

app.microzen.com/reports/overview
MicroZen Reporting screen
{{ m_reporting.counter }}{{ m_reporting.cap }}
What sets it apart

What distinguishes Microzen Reporting is that it reports the state of the record rather than a reconstruction of it.

For an institution whose numbers are read by a regulator, an apex funder and a board, the point is that the same figure means the same thing on every screen, in every export and in every pack.

  1. 01 / 06

    One platform, linked records

    Because MF Operations, FIS and HRIS share one platform, a report never reconciles three systems after the fact: the loan, the voucher it produced and the officer who disbursed it are already linked, and the report follows those links instead of matching extracts by hand.

  2. 02 / 06

    Period status from the close

    Every report states the status of each period it covers, taken from the close itself rather than entered by the person running it, and a report spanning any period that is not hard closed cannot be marked or exported as final.

  3. 03 / 06

    Overridden closes stay marked

    A day closed under override in operations or in finance carries that mark into every report that includes it, so an overridden close is never presented as a clean one.

  4. 04 / 06

    Classifications as recorded

    Classifications are reported exactly as the system recorded them: a loan reaches a terminal recovery state in a report only when the event that produced it has been recorded, so a portfolio can never appear resolved by the passage of time.

  5. 05 / 06

    A labelled notional split

    For a running month, programme and consolidated figures show the notional split as FIS presents it, annotated on the face of the report and never written back to any ledger, and suppressed rather than estimated where no prior month exists.

  6. 06 / 06

    Insights with their evidence

    AI insights summarise what has moved and where, but every insight links to the figures it was drawn from and none is shown without them.

Industry standard

The platform meets what a multi-branch institution now expects of its reporting.

app.microzen.com/reporting

Computed, not submitted

Indicators are computed from the transaction record rather than from returns submitted by branches, so a branch figure and the consolidated figure are the same calculation read at different levels of the hierarchy, and a branch cannot report a number the system does not hold.

Both loan classifications

Portfolio reporting follows both classifications a loan carries — the regulatory bands used for provisioning and statutory reporting, and the institution's own post-tenure taxonomy used for recovery governance — so one portfolio is read by the regulator and by the recovery team without a second extract.

Trend and branch views

Trend views compare week against week and period against period, and branch views set portfolio, borrowers and risk side by side so an outlying branch is visible without a request to head office.

Governed report builder

The report builder lets an authorised user assemble a report from approved data sources, fields and filters without a release, and a built report enters the shared catalogue only once it has been approved, so the catalogue never carries an unreviewed definition.

Scheduled delivery

Scheduled reports run on a configured frequency to named recipients, with each delivery recorded.

Alerts

Alerts carry a threshold, a comparison basis and recipient rules, and bring a movement — a rise in portfolio at risk, a fall in collection efficiency, a branch moving outside its usual range — to the manager responsible rather than leaving it to be found in the monthly pack.

Drill-down

Drill-down runs from any figure on a dashboard to the branch, the member and the voucher behind it.

Workforce indicators

Workforce figures come from HRIS, so productivity indicators are measured against where staff are actually posted rather than against a headcount kept apart from the payroll.

Foundations

Microzen Reporting holds the institution's standard reporting set in a single catalogue.

  1. 01

    Dashboards

    Dashboards for the overview, loan portfolio, collections and member growth open on the headline totals — loans disbursed, loan amount and active members — and on the portfolio indicators an institution is judged by: portfolio at risk at thirty days, operational self-sufficiency and collection efficiency.

  2. 02

    Find any report

    Reports are organised by category and found by report name, dashboard or data source, and every report names the data source it reads.

  3. 03

    Standard reporting set

    The standard set covers collections, overdue and classification, recovery actions, restructuring and settlements, rebates and write-offs, the ledgers and statements of FIS, attendance and payroll from HRIS, and a management summary.

MZ-03 Core record
Microzen Reporting
  1. 01Dashboards
  2. 02Find any report
  3. 03Standard reporting set
  4. 04Shared controls and export
  5. 05Scoped access
  6. 06Local conventions
  1. 04

    Shared controls and export

    Every report runs on the same controls — a hierarchy filter from institution to branch, an independent programme filter and a period selector — and exports to spreadsheet and document format, with every export itself recorded against the user who made it.

  2. 05

    Scoped access

    Access is scoped to the user's position in the hierarchy, so a branch manager sees their branch and an area manager their area, and no report parameter can widen it; auditors receive read-only access with no permission to build, schedule or alter a report.

  3. 06

    Local conventions

    Amounts follow the institution's own conventions, in taka with lakh and crore grouping, and dates are shown as day, month and year.

Ready to build a smarter microfinance operation?

See how MicroZen can transform the way your teams manage, operate, and grow.

45-minute walkthrough · no commitment
MZ-04Human resource information system

Microzen HRIS

The employee lifecycle on one record — requisition and onboarding, the employee master and self-service, attendance and leave, transfers, separation and settlement, payroll, and HR policy. Rules are configured by HR rather than written into the code.

app.microzen.com/hris
Microzen HRIS screen
Product tour

Inside HRIS

Screens from MicroZen HRIS. Choose a feature to zoom into the part of the screen that handles it.

app.microzen.com/hris/overview
MicroZen HRIS screen
{{ m_hris.counter }}{{ m_hris.cap }}
What sets it apart

Two org models, and gates that hold

A corporate hierarchy and a field hierarchy run side by side as equals, and the control points cannot be talked around — eligibility the system proves, custody that gates settlement.

  1. 01 / 07

    A corporate hierarchy and a field hierarchy, both first-class, chosen per transaction

  2. 02 / 07

    Exchange leave eligibility proved by recorded attendance, never asserted by the employee

  3. 03 / 07

    One redemption per eligible day, never deducted from casual, sick or earned balance

  4. 04 / 07

    Handover checklists covering portfolio, cash, devices and members gate the transfer letter

  5. 05 / 07

    Separation configured as eleven scenarios, where a contract ending can become an extension

  6. 06 / 07

    Late attendance taken from leave balance first, reaching salary only when none remains

  7. 07 / 07

    Policies issued to a defined scope and visible only to the employees inside it

Industry standard

Approvals, self-service and the finance handoff

Head office and field run their own approval chains, employees serve themselves end to end, and payroll reaches finance only on a finalised, fully approved run.

app.microzen.com/hris

Approval structure

Separate approval chains for head office and field, changed without redevelopment.

Escalation

SLA timers, reminders and automatic escalation past an inactive approver.

Review and resubmission

A review reopens only permitted fields; resubmission restarts the chain from the first approver.

Employee requests

Self-service for documents, expenses, advances, leave, remote activity and payslips.

Shift planning

Duty planned on a roster, with approved leave recording the next duty date.

Statutory compliance

Statutory contributions and tax slabs configured as percentages, effective-dated with full history.

Finance handoff

Payroll reaches finance with its full breakdown, or disbursement is blocked outright.

Foundations

One record, built in sequence

Onboarding is step-gated through to a system-generated ID, identity is enforced unique, and attendance arrives from the device rather than a typed sheet.

  1. 01

    System-generated employee ID

    A pre-joining checklist and a system-generated employee ID that cannot be typed in

  2. 02

    Single employee master

    One employee master carrying identity, education, experience, nominee and guarantor records

  3. 03

    Unique identity

    National ID and tax ID enforced unique, so a duplicate record cannot be created

  4. 04

    Configured leave rules

    Leave types, balances, carry-forward rules and approval hierarchies configured rather than coded

MZ-04 Core record
Microzen HRIS
  1. 01System-generated employee ID
  2. 02Single employee master
  3. 03Unique identity
  4. 04Configured leave rules
  5. 05Merged attendance
  6. 06Approved holiday calendar
  7. 07Logged reporting
  1. 05

    Merged attendance

    Attendance merged from the biometric feed and approved remote activity into one dataset

  2. 06

    Approved holiday calendar

    A holiday calendar approved before publication, then applied to timesheet and leave alike

  3. 07

    Logged reporting

    Reporting by branch, samity and employee, with every report download logged

Ready to build a smarter microfinance operation?

See how MicroZen can transform the way your teams manage, operate, and grow.

45-minute walkthrough · no commitment
Request a demo 45-minute walkthrough with an implementation lead.
Request received An implementation lead will reply within one working day to schedule the walkthrough.
No commitment