Skip to main content
The loan agreement is the signed PDF contract between your credit union and the borrower. The platform generates it automatically once a loan is approved, stores it with a fixed retention period, and requires it on file before any funds can be released. Every agreement is tied to the approved loan and to the exact figures that were approved.

​
The four agreement templates

The platform picks the template that matches the loan type. Each one carries the legal clauses and collateral section appropriate to that kind of loan.
Loan typeTemplateWhat it covers
Cash-Securedcash-securedThe loan secured against the member’s savings, including the hypothecation of the secured deposit.
UnsecuredunsecuredA personal loan with no collateral section.
AutoautoThe chattel mortgage over the vehicle, the registered lien, and the insurance requirement.
MortgagemortgageThe mortgage over the real property, the title custody terms, and the property insurance requirement.
Each generated PDF records its template name and version, the approved principal, term, rate, monthly payment, and approval date, the member’s name and address, and the approving officer. The template version is 3 today; it shows as Version on the agreement card and in the download filename (loan-agreement-<id>-v3.pdf). The approving officer is the Adjudicator who recorded the approval; the agreement shows their name with the title “Adjudicator”. The figures come from the approved decision and its rate computation, so the agreement always reflects what was actually approved.

​
When the agreement is generated

The agreement is generated as part of disbursement readiness. When a loan is approved, the platform queues a job that renders the PDF, uploads it to secure storage, and writes an agreement record against the loan. This happens in the background, so the agreement is ready by the time the loan reaches the Disbursement team.
A loan cannot be disbursed without a generated agreement. The disbursement readiness check refuses to schedule or execute a disbursement while the agreement is missing, with the reason “The signed loan agreement has not been generated yet.” The agreement is one of three readiness gates: the member’s KYC must be VERIFIED, every security request must be resolved, and the agreement must be on file. This is a server-side guard, not just a hidden button, so it holds even against a stale page.

​
Regenerating an agreement

If the agreement needs to be reissued, for example after a correction, you can regenerate it from the loan detail page. Regenerating queues a fresh PDF render and writes a new agreement record. The prior agreement is kept and the new one supersedes it, so the full history is preserved for audit. The newest agreement in the chain, the one nothing supersedes, is the canonical version. It is the one the download link serves. The readiness check requires at least one agreement on file for the loan, regardless of which version is canonical. Older versions stay on file and remain in the audit trail.
1

Open the loan

Go to the loan on the adjudication or disbursement detail page. The agreement card shows whether an agreement has been generated.
2

Regenerate

Click the regenerate action. The platform finds the loan’s latest approved decision, queues the render against it, and waits for the job to finish. A regeneration from an existing agreement supersedes that agreement; a first generation simply creates the first record.
3

Confirm the result

When the job completes, the page refreshes and the new agreement becomes the canonical version. If the render fails, the page shows the reason and the technical detail is captured in the audit log. Two failures are worth knowing: an agreement generates only against an APPROVED decision, and an Auto or Mortgage agreement needs a collateral record on file. If the collateral record is missing, the reason reads “The agreement could not be generated because the loan has no collateral record on file. Open the loan and capture the collateral details, then retry.”
Who can regenerate depends on the surface. Any oversight role that holds reports.view regenerates through that access: Administrator, Credit Manager, and Branch Manager. The Disbursement team can also retry generation (loans.disburse) when the post-approval job failed silently and is blocking their pre-execution checklist.

​
Downloading the agreement

The agreement download is capability-gated. Five capabilities can download it, so everyone working the loan in its pipeline can read the agreement that backs the file:
CapabilityWho holds it
reports.viewOversight roles: Administrator, Credit Manager, and Branch Manager
loans.read.ownThe officer who created the loan
loans.adjudicateAdjudicator
securities.reviewSecurities team
loans.disburseDisbursement team
The download serves the canonical agreement for the loan. You can open it inline in a new tab to read it first, or request it as an attachment to save it directly. If no agreement has been generated yet, the download returns a clear “not generated yet” response rather than an empty file. The agreement-download links on the Adjudicator, Securities, and Disbursement detail pages all point at this same endpoint.
The scoping of loans.read.own to the loan’s creator is a planned refinement; today any holder of the capability can download. Agreement PDFs are stored with a 7-year retention period, the Bank of Jamaica minimum for loan records, and cannot be altered or deleted within that window. Every download is logged.

​
Events recorded

The agreement lifecycle is logged. The generated and failed events are also written to the immutable audit trail; the start of a render is a log line only.
EventWhen it firesWhere it lands
loan_agreement.generation.startedA render job began for an approved loan.Log only
loan_agreement.generatedThe PDF was rendered, stored, and recorded against the loan.Audit trail and log
loan_agreement.generation.failedThe render or storage step failed. The reason is captured for investigation.Audit trail and log