An end-of-day run is more than a date change. It is the process that confirms portfolio balances, risk, and accounting reflect a complete and consistent operation before the next business day begins.
In MicrofinCloud, the end-of-day run turns the day’s transactions into reliable information for operations, accounting, and internal control. Each stage follows rules configured by the institution and leaves evidence of the outcome.
1. VALIDATING PENDING OPERATIONS
Before closing, MicrofinCloud checks for incomplete transactions, unapplied collections, in-progress movements, or inconsistencies that could affect balances. This helps prevent partially recorded events from carrying into the next day.
2. UPDATING THE LOAN PORTFOLIO
The system processes the events that affect loans: disbursements, payments, charges, interest, penalties, maturities, restructurings, and other configured movements. It then updates principal, interest, penalty, and other loan components.
3. CALCULATING RISK AND PROVISIONS
Based on the institution’s policies, portfolio classification, and delinquency rules, MicrofinCloud evaluates the applicable risk. When required, it updates provisions and prepares the effects that must be reflected in financial information.
4. GENERATING ACCOUNTING ENTRIES
Every portfolio event with an accounting impact is translated into the entries configured for the product, currency, loan status, and transaction. Portfolio and accounting are therefore updated from the same transaction, without depending on a later manual upload.
5. CONTROLS, TRACEABILITY, AND EXCEPTIONS
The run identifies situations that need review: missing configurations, differences, unavailable accounts, or conditions that must be resolved before the process is complete. The institution retains evidence of what happened, when it happened, and which user or process performed it.
6. CONFIRMING THE NEXT OPERATING DAY
Once validations and processes complete correctly, the system prepares operations for the following day. Teams begin with updated balances and a consistent base for collections, disbursements, portfolio analysis, and decision-making.
WHY DOES IT MATTER?
A reliable end-of-day run prevents the institution from accumulating differences between portfolio and accounting. It also improves report timeliness, reduces rework, and strengthens traceability for audits, internal reviews, and regulatory requirements.
MicrofinCloud integrates this process into the same platform used to manage loans. The result is a more orderly operation: every movement matters, every balance has support, and every day starts with reliable information.
WHEN AN END-OF-DAY RUN NEEDS ATTENTION
The operating day should move forward only after the previous business date has been fully closed. If a holiday, interruption, or exception leaves a day pending, MicrofinCloud should process the outstanding dates in sequence, applying the rules configured by the institution and preserving the traceability of each step.
If an exception occurs, the appropriate response is to review the status of the process, identify the last completed operating date, resolve the underlying cause, and then resume. Repeating a process without verifying its status can create avoidable inconsistencies.
Idempotent controls are essential in this context: a transaction that has already been processed for a specific business date must not create duplicate accruals, charges, or accounting entries when the process is resumed.
BEFORE OPERATIONS OPEN
Before teams begin collections, disbursements, or other daily activities, the institution should confirm that:
• The scheduled end-of-day process completed successfully.
• The operating date is current.
• There are no failed processes or unresolved exceptions.
This discipline turns the end-of-day run into a reliable operational control, not merely an automated task.
