Loan Booking and Disbursement: From Approval to Funds in the Account

How an approved workplace-banking loan is booked in the core banking system and disbursed — limit marking, the Finacle booking fields, the one-month moratorium, break-period interest, fee recovery and partial/final disbursements.

By the time a check-off loan reaches credit approval, the hard analytical work is done — affordability has been verified, compliance checks have cleared, and a credit approver has signed off. What follows is the part borrowers actually feel: the loan being booked in the core banking system and the money landing in an account. This is where small mechanical errors become expensive. A repayment schedule that does not match the check-off booking, a fee that is not recovered, or a disbursement that bypasses dual control can each turn a clean approval into an operational dispute. In Creodata's Workplace Banking platform, this final mile is handled by the Disbursement service, which orchestrates account creation, loan booking against Finacle, the financial rules that govern timing and interest, and the disbursement itself. This article walks through that booking-to-disbursement sequence in detail. For the wider end-to-end picture, see the complete guide to workplace banking.

Creating the account before the money moves

A workplace-banking applicant may already bank with the institution, or may be entirely new to it. Where the customer is new to the bank — or existing but without an active transactional account — a Customer Information File (CIF) and a transactional account are created automatically through the core banking API. This does not wait until the end of the workflow. Account opening runs in parallel with the loan workflow, so that by the time the loan is ready to disburse, there is a live account to receive the funds.

Two points are worth drawing out:

• When it happens. The CIF and account are auto-created on confirmation of check-offs or on approval, so the account exists before disbursement rather than being scrambled together afterwards.
• What kind of account. The account type is determined by the customer's income level, so the product opened is appropriate to the salary band rather than a one-size-fits-all default.

This parallel-track approach is the natural handover point between origination and onboarding. The deeper account-creation mechanics — the CIF, the operative account, and the data captured at onboarding — are covered in our business account opening guide and the account opening product page. For workplace banking, the relevant fact is simply that there is always a destination account ready, and its creation never blocks the loan.

Booking the loan in Finacle

Loan booking is the act of registering the approved facility in the core banking system. In WPB this is done through the Finacle loan-booking API, and it captures a specific, complete set of fields so that the loan, its repayment instrument and its accounting are all internally consistent from day one.

Alongside booking, the platform performs limit marking through a core-banking API call, reserving the facility limit so the loan is properly recognised against the customer before funds move.

The employer code deserves a note of its own. The scheme code and employer code are what tie a loan to the right payroll deduction; without a valid employer code, the check-off cannot be set up correctly. Where an employer code is missing at booking time, the platform does not silently proceed — Credit Admin liaises with the Scheme Loan Administrator (SLAD) or the Scheme Relationship Manager to resolve it before disbursement. Getting the scheme right at this point matters because it governs the parameters the whole loan was built on; the relationship between schemes and their parameters is set out in our guide to employer scheme onboarding. Finacle is one of several systems the platform talks to through its adapter-based integration layer, alongside IPPD for government payroll booking; the full picture is in our overview of workplace-banking system integrations.

The financial rules: moratorium and break-period interest

Two timing rules shape how a check-off loan behaves in its first weeks, and both exist to keep the repayment schedule and the payroll deduction perfectly aligned.

The first is the one-month moratorium. A new loan carries a one-month moratorium, after which the first instalment falls due on the 10th of the month following the moratorium's expiry. Anchoring the first due date to the 10th aligns repayment with the typical payroll cycle, so the check-off deduction and the instalment date line up rather than drifting against each other.

The second rule handles what happens in the gap. Where the first repayment date is more than one month after the booking date, there is a stretch of time during which principal is outstanding but no instalment has yet fallen due. For that gap the platform applies break-period interest: interest is calculated daily and paid monthly across the break. Critically, the EMI calculation itself factors in both the booking date and the first-repayment date so that every instalment is equated and the check-off booking is never less than the repayment schedule.

That last clause is the operationally important one. In a check-off arrangement the employer remits a fixed deduction; if the booked deduction were ever smaller than what the repayment schedule actually requires, the loan would quietly fall into arrears through no fault of the borrower. By equating the instalments around the real booking and first-repayment dates, the system ensures the payroll deduction always covers the schedule. The arithmetic that produces these instalments — and how affordability is established before the loan is ever booked — is explored in our pieces on forward and reverse loan calculators and the payslip affordability check.

Disbursement: full, partial and final

Once the loan is booked, the Disbursement service moves the money. Disbursement is not a single mode — it supports full, partial and final disbursements, which matters because not every facility is paid out in one tranche.

Where the funds go depends on the loan type:

• New loans and top-ups are disbursed to the customer's transactional account — the operative account created or confirmed earlier.
• Take-overs (buy-offs) do not go straight to the customer. The funds go to a suspense account first, because the money is destined to settle a facility at another institution rather than to be spent by the borrower. Settlement to another bank is done by RTGS, routed and approved through the document workflow system; settlement to a SACCO credits a branch suspense account and a bankers cheque is issued to the branch, with the system auto-emailing the branch. The full mechanics of taking over an external facility are set out in our loan buy-off and take-over guide.

At disbursement the platform also handles money owed to the bank itself. Bank commissions and insurance are automatically recovered and credited to the relevant general-ledger (GL) accounts. This removes a manual reconciliation step and ensures fee income and insurance premiums are captured at the same moment the principal leaves the bank, rather than being chased afterwards.

The methods available for moving funds — RTGS/TT transfers and bankers cheque issuance — reflect the different counterparties involved, from a customer's own account to another bank's settlement instructions.

Dual control and what happens after the money leaves

None of this runs on a single person's say-so. Booking and disbursement are subject to maker-checker dual approval, enforced not as a policy reminder but as a database constraint: the inputter and the verifier must be different users, so the system physically cannot record a self-approved disbursement. This is the control that turns "money movement" into "controlled money movement", and it sits alongside the platform's immutable audit trail. The reasoning behind enforcing separation of duties at the database layer — and why a UI check alone is not enough — is the subject of our dedicated piece on maker-checker in loan disbursement, with the broader access-control picture in audit trail and RBAC.

Disbursement is also not always the end of the story. The post-disbursement stage covers the loose ends and ongoing obligations:

1. Confirm and recover processing fees, completing any fee recovery not settled at the point of disbursement.
2. Amend the repayment schedule for partial disbursements, so the schedule reflects what was actually paid out rather than the original full approval.
3. Remit Credit Life Assurance premiums to Banc Assurance, ensuring the cover that protects the facility is funded.
4. Handle internal transfers and take-over settlement, including cross-currency transfers at the prevailing exchange rate and RTGS/TT for loan take-over routed through the document workflow system with verifier approval.

For take-overs specifically, the final disbursement is gated: it proceeds only on a certified loan statement showing a nil balance or a clearance letter from the other institution, together with confirmation that the external check-off has been stopped. That gate prevents the bank funding a take-over while the borrower is still being deducted elsewhere.

This booking-to-disbursement sequence is one stage of a thirteen-stage workflow; to see how an approval arrives here in the first place, read the workplace-banking loan workflow and the broader check-off loans in Kenya overview.

Frequently asked questions

What is break-period interest and why does it matter?

Break-period interest covers the gap between the loan's booking date and its first repayment date when that gap is longer than a month. During this window the principal is outstanding but no instalment has yet fallen due, so the platform calculates interest daily and collects it monthly across the break. More importantly, the EMI calculation factors in both the booking date and the first-repayment date so that every instalment is equated and the check-off booking is never less than the repayment schedule. This alignment matters because, in a payroll-deduction loan, the employer remits a fixed amount — if the booked deduction were ever short of the schedule, the loan would slip into arrears through no fault of the borrower.

When does the first loan instalment fall due?

A new workplace-banking loan carries a one-month moratorium. After that moratorium expires, the first instalment falls due on the 10th of the following month. Anchoring the first due date to the 10th aligns the instalment with a typical payroll cycle, so the check-off deduction the employer remits and the loan instalment date line up rather than drifting apart. Where the resulting gap between booking and the first repayment is longer than a month, break-period interest covers the interim, and the EMI is calculated around the actual booking and first-repayment dates so all instalments remain equal and the deduction always covers the schedule.

How are bank fees and insurance recovered at disbursement?

Bank commissions and insurance are recovered automatically as part of the disbursement process and credited to the relevant general-ledger accounts, rather than being reconciled or chased after the fact. This means fee income and insurance premiums are captured at the same moment the principal is paid out. Some elements continue into the post-disbursement stage: processing fees are confirmed and recovered there, and Credit Life Assurance premiums are remitted to Banc Assurance to fund the cover that protects the facility. Because these steps move money, they fall under the platform's maker-checker dual control, with the inputter and verifier required to be different users.

To see how this booking-to-disbursement engine fits the full origination lifecycle, explore the Workplace Banking product page or request a walkthrough via our demo.