1. Micro-finance System
  2. Features
  3. Group collection runs
Feature · Group collection runs

Group collection runs

Prepare a collection run and retain its review and provider outcome.

OverviewSubmitted Collection Runs
Micro-finance System · Group collection runs

Submitted Collection Runs

Approval conditions

New
StatusRevisionCollectorSubmitted atCollected USDParent
Submitted700CLL-60007 Oct40LA-91425
Submitted610CLL-52325 Oct240LA-50124
Submitted50CLL-19106 Oct140LA-40031
Submitted740CLL-49720 Oct100LA-45585
Submitted890CLL-54404 Oct860LA-24281
6 of 6 records
CLL-600Group collection runs · GCR-86016
Submitted
Revision700
Submitted at07 Oct
Collected USD40
ParentLA-91425
Example screen with sample data

What you can do

Give the run a parent and a reviewer

A group collection run belongs to an application and an organization. The Collector prepares its amount, collector identity and submission details, then sends a revision for review. The run’s status distinguishes a draft from a submitted, approved, rejected or completed run. Completion is a separate outcome from approval: the provider’s authority and supporting evidence decide whether the run has actually completed.

The Independent Credit Approver checks the frozen run revision against the application and evidence. A review decision is recorded on the parent application with the relevant revision. The decision needs a reason, reviewer and time, so a later dispute can be investigated. A collection total by itself is not evidence that money moved. Keep the provider application identity and verified event with the run’s progression.

How the work is organized

  • Preparation. Collector records the proposed collected amount and the parent application.
  • Independent decision. The reviewer checks evidence and records an approve or reject decision for the submitted revision.
  • Completion. Staff compare the provider authority and recorded effect before considering the run complete.

What to agree during setup

Agree which organization may submit a run for a given application, who may act as Collector and which reviewer has independent authority. Define what supports the collected amount and how a correction changes the revision. The team should know whether a revised run needs a new decision and how to retain the rejected one. Decide how a provider application identity is obtained, checked and attached to the run.

The run has both submission and decision dates. Agree which team supplies each date and how late provider evidence is handled. A run may be approved while provider completion is still outstanding. Keep that position visible to operations rather than treating approval as proof of a completed collection. The Auditor needs a route from the run to the parent application, decision and evidence.

Check the handoff on an actual case

A Collector prepares a run against an existing application. The reported collected amount is changed before review, so the Collector updates the revision and supporting evidence. The Independent Credit Approver reviews that revision and records a reasoned decision. When the provider later issues an authority, the Credit Officer checks the identity and evidence before treating the run as completed. If the provider outcome differs, the run remains in its reviewable position while staff investigate; the original submitted amount and decision remain traceable.

What your team sees

  • Submitted Collection Runs — Runs awaiting an independent review, with collector, amount and parent application visible.
  • Collection Run Board — Draft, submitted, approved, rejected and completed work grouped by status.

Follow the work through

What it keeps track of

Data model
Group collection runs
Group collection runs submitted for review and completed against verified collection evidence.
Loan applications
Loan applications moving through authorization, submission and confirmation.
Review decisions
Independent approver decisions recorded against a frozen application revision.
Application evidence
Provider evidence supporting a loan application revision, with validity and verification.
Operation receipts
Idempotent operation receipts with stable operation keys and actual effect references.
Organizations
Banking organizations whose treasury operations are run in this app.

Who uses it

Permissions
Collector
Prepares and submits the run.
Independent Credit Approver
Decides on the submitted revision.
Credit Officer
Follows the provider outcome.
Auditor
Reads the connected evidence.
App Administrator
Maintains organization and member scope.

Set up Micro-finance System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started