These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Microfinance / SHG Management
- Features
- Account reconciliation
Account reconciliation
Compare source-identified provider movements with instructions and dated account snapshots.
OverviewAccount Movements to Match×
Microfinance / SHG Management · Account reconciliation
New
Account Movements to Match
Repayments
| Loan | Matched instruction | Provider event ID | Received at | Received USD | State | |
|---|---|---|---|---|---|---|
| LA-150 | LA-84938 | PEI-386 | 04 Oct | 180 | Unmatched | |
| LA-110 | LA-33542 | PEI-247 | 14 Oct | 20 | Exception | |
| LA-150 | LA-19221 | PEI-601 | 12 Oct | 10 | Unmatched | |
| LA-130 | LA-46376 | PEI-580 | 03 Oct | 160 | Exception | |
| LA-120 | LA-63100 | PEI-524 | 11 Oct | 10 | Unmatched |
6 of 6 records
PEI-386Repayments · RPY-21676
UnmatchedLoanLA-150
Matched instructionLA-84938
Received at04 Oct
Received USD180
What you can do
Account reconciliation in daily work
Compare source-identified provider movements with instructions and dated account snapshots. The record stays with the organization that owns the work. Each handoff has a named owner and a source record that the next person can inspect. This makes the decision and its provider outcome traceable to the same instruction.
How the work is organized
- Prepare. Record the operating context and source references before changing the status.
- Decide. Use the appropriate role to check the current revision and supporting evidence.
- Verify. Compare the recorded outcome with the provider event and retain exceptions.
Repayments records a provider event ID, received date, amount, state, account and matched instruction. Repayment schedules records dated provider snapshots with principal and interest amounts for a loan accounts record. The matching rule requires the same account, exact received amount and confirmed occurrence date. A differing amount or date stays unmatched or becomes an exception. This keeps the provider movement distinct from the instruction being checked and avoids creating a match merely because their totals look similar.
What to agree during setup
Agree which organization owns each account and counterparty, who may prepare an instruction and who may independently decide it. Define where provider references, confirmations and balance snapshots arrive. Give each person the minimum scope needed for their role, including what may be shared in attachments. Choose one real account movement for the first rehearsal and retain its provider source identifiers.
The team should also agree when a returned record needs a fresh revision. Provider events can arrive after an internal action, so an operational status should reflect the observed event. Keep the timing and reason for correction on the related record. This helps the next shift understand why an item is still waiting.
Check the handoff on an actual case
Suppose a provider movement and an instruction share an amount but differ by a day. Treasury Reconciler leaves the movement Unmatched or marks it Exception while investigating the provider event ID and snapshot date. The reconciler does not change the recorded date to manufacture a match. Once the provider record and confirmed instruction actually agree, the matched instruction reference provides a traceable link. Walk through the case with the preparer, reviewer and reconciler together. Ask each person to point to the record they used and the event that made the next state valid. Check the same case in an ordinary screen and in the exception list, then verify that an unauthorized actor cannot make the decision.
What your team sees
- Account Movements to Match — Follow the records that need the module’s next action.
- Provider Balance Dates — Check the subsequent state against its source information.
Follow the work through
See the related process and the data model for the record handoff.
What it keeps track of
Data model- Repayments
- Source-identified provider movements matched against banking instructions.
- Repayment schedules
- Dated provider balance snapshots for a financial account.
- Loan accounts
- Provider-held financial accounts owned by a counterparty.
- Loan applications
- Typed banking instructions moving through authorization, submission and confirmation.
Who uses it
Permissions- Treasury Reconciler
- Investigates account movements.
- Credit Officer
- Supplies instruction context.
- Auditor
- Reviews the retained source references.
Set up Microfinance / SHG Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.