Automate Loan Agreements
Generate loan agreements from your own .docx templates — upload a template with placeholders, map each token to an application field, and produce a completed document from any application review page.
Instead of retyping applicant details into a Word document for every approval, upload your loan agreement as a template once, map its placeholders to application fields, and generate a completed agreement from any application's review page.
Everything lives under Settings → Automations, which has two cards: Document Templates and Automations.
Step 1 — Upload a Document Template#
In the Document Templates card:
- Give the template a name (and optional description) and select Add template.
- Select Upload file on the new template row and choose your .docx file (up to 10MB — only .docx is supported).
Your document should contain placeholders wherever applicant data belongs, written as {TOKEN} or {{TOKEN}} — for example {APPLICANT_FULL_NAME} or {LOAN_AMOUNT}. The system scans the file and lists every token it detects.
Step 2 — Map the Tokens#
Each detected token gets a row in the Token mappings table:
- Source — pick the application field that fills the token, from a searchable list grouped by section (applicant, employer, bank, and so on). Choose ✎ Custom text… to insert a fixed literal instead.
- Format — how the value is rendered: UPPERCASE, lowercase, Title Case, Currency (cents → 0.00), Yes/No, or one of several date and datetime formats.
The card badges your progress — "✅ All mapped" or a warning with the count of unmapped tokens. Select Save mappings when done.
Use the Currency format for any amount token — application amounts are stored in cents, and this renders them as proper rand values.
Step 3 — Create the Automation#
In the Automations card, give the automation a name (for example "Loan Agreement Document Population"), pick the template it should use, and select Add automation.
Each automation row lets you change the linked template, toggle it Active, save changes, or delete it. Automations are manually triggered — nothing generates without a staff member asking for it.
Step 4 — Generate from an Application#
Open any application in the review queue. The Generate documents card lists every active automation with a Run button:
- Select the Run button next to the automation's name.
- If any tokens are still unmapped, you're warned and can choose Generate anyway — unmapped tokens stay as-is in the output.
- On success, a Download link appears for the completed document.
The generated agreement is populated with that application's data, formatted exactly as you mapped it.
A run button is disabled if the automation has no linked template or the template has no uploaded file — the card tells you which it is.