> ## Documentation Index
> Fetch the complete documentation index at: https://docs.compuzign.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Release approved loan funds in Disbursement
> Enter payee details, verify fees, and execute funds release for approved loans. An overview of the Disbursement queue and its detail topics.
The **Disbursement** queue holds approved loans that are ready for funds release. With the **Disbursement** role, you enter payee details, verify the fee calculations, and execute the disbursement. A loan is only marked **DISBURSED** once you confirm. No funds are scheduled or released until you act.
## What you need
You need the **Disbursement** role, which carries the `loans.disburse` capability. If you can view the queue but cannot act on applications, ask your Administrator to verify your role.
## How a disbursement works
Open **Disbursement** under the **Review queue** group in the sidebar. The queue's **Pending** tab shows loans in **DISBURSEMENT** status that are ready for scheduling or execution; the **Completed** tab shows disbursed and filed loans. The **All / My queue / Unassigned** tabs filter to your files or unclaimed work.
Click a row to open the disbursement detail page. You'll see the approved loan amount, the fee schedule pre-populated from your credit union's configuration, and the calculated net-to-member amount.
The form shows the gross approved amount, the fee and tax breakdown, and the live **Net to member** figure. This is the amount you must distribute in full across all payees.
Add one or more payees, each with a payee type, name, payment method, account and routing details, amount, and purpose. The sum of all payee amounts must equal the net-to-member figure exactly before you can schedule.
Pick a scheduled date of today or later, then click **Schedule disbursement**. This creates the disbursement instruction with all its payees and fee lines. The loan stays in **DISBURSEMENT** status. The Disbursement team, or the file's assignee if one is set, is notified that the disbursement is scheduled.
Scheduling is refused if an instruction already exists on the loan (re-scheduling means reverting the file back to Securities first), or if the deductions would push the net to member below zero.
Return to the instruction and click **Mark disbursed** to release the funds. Only then does the loan move to **DISBURSED**. The Credit Officer is notified, and the member is notified too if member email delivery has been switched on for the platform (the `ILOAN_MEMBER_EMAILS_ENABLED` environment setting, off by default). Scheduling and execution are two separate actions, so a file can be scheduled by one officer and released by another.
Dual control is off until your credit union sets a threshold, so existing workspaces are never blocked by it. When it applies, the platform refuses to release the funds while approval is still pending. The block is enforced server-side, not by graying out the button: a net at or above your credit union's dual-control threshold sets the instruction to await a second approver, and a **different** user holding `disbursements.approve` must sign off before the release goes through (the maker cannot be the checker). Until they do, **Mark disbursed** is turned away with an "awaiting a maker-checker approval" message.
There is one exception to the two-step flow: when auto-disbursement is enabled and the net to member is at or below the configured threshold, scheduling executes the release immediately. Auto-disbursement also requires that no dual-control approval is pending, that the officer is within their personal limit, and that your credit union does not require AML screening.
With the loan in **DISBURSED**, the **File loan** card shows a **File loan (terminal)** button. Clicking it fires the **DISBURSED → FILED** transition (gated by `loans.disburse`) and closes the file at its terminal **FILED** state. Filing always lands on **FILED**; it never routes the loan anywhere else. Filing is a manual step, not automatic.
## What the detail page shows
The disbursement detail page is also a read-only recap of the whole file, so you can sanity-check it before releasing funds without leaving the page. Alongside the approved amount and the payee form, you'll see:
* **Risk assessment.** The latest risk band, score, engine version, and the same factor breakdown the Adjudicator saw.
* **Collateral summary.** The most recent collateral record for secured loans, with valued amount and valuation source.
* **Decision history.** Every adjudication decision in order, each with its rationale, the decider's name, and their role.
* **KYC status.** The member's identity-verification state, with a link to their documents.
* **Agreement.** The signed loan agreement to view or download. If the agreement PDF failed to generate, the page surfaces the last generation error so you know why it's missing.
## Pre-execution checklist
Before you can schedule or release a disbursement, the loan has to clear three prerequisites. The detail page shows them as a **Pre-execution checklist** and disables the **Mark disbursed** button until all three pass:
* **Member identity verification (KYC) is VERIFIED.**
* **Zero outstanding security requests.** No request on the loan is in PENDING or SUBMITTED.
* **A loan agreement has been generated.**
This is a hard rule, not just a UI gate. The platform re-checks all three inside both scheduling and execution and refuses the action if any is open, even from a stale page or a direct call. If something regresses between scheduling and release, for example a security request reopens or the agreement is revoked, execution is blocked until it clears again.
## Disbursement topics
Disbursement has several detail areas, each covered on its own page.
Choose a payment rail for each payee: ACH, RTGS, Internal Transfer, Cheque, Manager's Cheque, or Wire/SWIFT. ACH cannot carry more than J\$1,000,000 per payee. Use RTGS for larger amounts.
Review, edit, waive, or add fee lines, set how each is treated, and adjust the GCT rate. The net-to-member figure updates as you go.
Save frequently used payees such as attorneys, insurers, and dealer accounts to the payee directory, then reuse them without re-entering details.
Dual control sign-off, AML and sanctions screening, per-officer limits, and auto-disburse settings that govern who can release funds and when.
Track each disbursement through its lifecycle as the payment moves on the rail: sent, cleared, returned, failed, or reversed.
## Multi-payee disbursements
Many loans pay more than one party. An auto loan might split between the car dealer and the member. A mortgage might include a portion to an attorney for title transfer fees. Add payees with **Add another payee**, and the sum of all payee amounts must equal the net-to-member figure exactly before you can schedule.
A single instruction holds between 1 and 20 payees, and the payee sequence numbers must run as a contiguous 1-to-N list with no gaps or duplicates.
The total of all payee amounts must equal the net-to-member amount exactly. The form will not allow scheduling if there is any shortfall or excess. Watch the **Payees total vs net** panel for the current total, the required net, and the difference.
## After disbursement
Marking a loan **DISBURSED** stamps the bank reference number on the instruction and emits the `disbursement.executed` event, which notifies the Credit Officer (and the member, when member emails are enabled). The loan does not file itself. Filing is the separate manual step described above: someone on the Disbursement team clicks **File loan** to mark it **FILED**, and that always lands the loan on **FILED**.
### Post-disbursement securities re-check
A few credit unions require a security check *after* funds have gone out, for example to confirm vehicle insurance was activated or a lien was filed. That re-check is a distinct **DISBURSED → SECURITIES** transition, gated by `loans.adjudicate`, that someone holding that capability initiates with a post-disbursement security request. It is not part of the **File loan** button, and clicking **File loan** never triggers it.
When that transition fires, the workflow opens a new security request and moves the file back to the Securities queue for review, while the loan's status stays **DISBURSED**. The platform only allows it when your credit union's `securitiesFinalCheckRequired` configuration flag is on (a setting on `TenantWorkflowOverride`, defaulting off; there is no screen that toggles it). Once the new request is resolved, the file returns through Disbursement and can be filed.
**FILED** is the terminal state. Once a loan is filed, the record is locked from further editing and the audit trail is complete. Any future lending for the same member requires a new application.
## Disbursement dashboard
The **Disbursement dashboard** lives under the **Dashboards** group in the sidebar (**Dashboards → Disbursement**). It shows four tiles plus a throughput sparkline over fixed windows: **Awaiting disbursement** (a single count), **Disbursed this week**, **Total disbursed** (net of fees, last 7 days), and **Avg approval to fund** (last 7 days), with a **Disbursements per day** sparkline over the last 14 days. Reaching it needs `loans.disburse` or `reports.view`.