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.
Each generated PDF records its template name and version, the approved principal, term, rate, and approval date, the member’s name and address, and the full monthly payment breakdown. The template version is 4 today; it shows as Version on the agreement card and in the download filename (
loan-agreement-<id>-v4.pdf). The figures come from the approved decision and its rate computation, so the agreement always reflects what was actually approved. The agreement is signed by the member, any guarantors, the Loan Officer, and the Branch Manager, each with a date. The Adjudicator who recorded the decision is not a signatory.
What the agreement contains
The agreement follows the credit union’s own legal review. A few things are worth knowing about what a member reads and signs. The full monthly payment, itemised. Rather than a single number, the agreement breaks the monthly payment into its parts: principal and interest, the compulsory savings paid alongside the loan, and the creditor-life premium where it applies. It then shows the total the member pays each month. Creditor-life is not charged on a cash-secured loan, so its line is zero there. The total matches the affordability figure the officer sees at capture. The security, stated plainly. On a secured loan, the agreement leads with the type of security, Cash Secured, Motor Vehicle, or Real Property, and the details of what is pledged, before the legal clause that grants it. When the first payment is due. A cash-secured loan carries an Effective Date and the first payment falls one month after it. The other loan types are not disbursed on the day the agreement is drawn up, so they state instead that the first payment is due thirty days after the loan is disbursed. The Effective Date line appears only on the cash-secured agreement. The clauses your members expect. The agreement includes a credit-bureau consent, under the Credit Reporting Act, 2010, and a change-in-circumstances clause asking the member to tell the credit union promptly of any material change during the term of the loan. The signature page. The required signatories are the member, any guarantor where applicable, the Loan Officer, and the Branch Manager, each with a place to date their signature. Each page also carries the member’s initials. The page closes with an acknowledgement by the member, and each guarantor where applicable, that they have read and understood the agreement.The name the agreement uses for the credit union as the legal party, in the opening sentence and on the signature lines, is configurable per credit union and is set to the credit union’s registered name. It can differ from the display brand shown on the letterhead.
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.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.”
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:
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.