Templates

The Templates page allows you to create and manage document and communication templates used across the platform.

Navigation: Administration → General Setup → Templates

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Templates	Administration -> General Setup -> Templates	Create and maintain document, communication, receipt, and report output templates, including layout rules.
Branding	Administration -> General Setup -> Branding	Confirm logos, colours, and identity blocks used by generated outputs.
Organisation Details	Administration -> General Setup -> Organisation Details	Maintain the tenant legal/contact identity used by default headers and footers.
Communication	Communication service workspaces	Send messages or documents using approved templates.
Service Workspaces	Loans, Deposits, Billing, POS, Shares, Production, Driving, and other services	Generate agreements, invoices, receipts, certificates, letters, and notifications from operational records.

What Are Templates?

Templates are reusable document formats that can be populated with dynamic data. They are used for:

• Loan agreements — Pre-formatted contracts populated with client and loan details
• Deposit account opening letters — Welcome letters with account information
• Receipt templates — Transaction receipts with amounts and dates
• Notification templates — Email and SMS message templates
• Report headers/footers — Standardised branding on generated reports

Template Types

Type	Description	Format
Document	Formal documents like agreements, contracts, letters	Rich text (CKEditor)
Communication	Email and SMS notification templates	Rich text / plain text
Receipt	Transaction receipts and vouchers	Rich text

Creating a Template

1. Click Create New Template
2. Fill in the form:

Field	Description
Template Name	A descriptive name (e.g., "Loan Agreement — Standard")
Template Type	Document, Communication, or Receipt
Entity	The entity this template applies to (e.g., Loan Account, Deposit Account, Client)
Subject	For communication templates — the email subject line
Body	The template content with placeholders

3. Use the rich text editor (CKEditor) to format the body
4. Insert placeholders using the syntax
5. Review the Layout settings for identity scope, header, and footer behavior

Available Placeholders

Placeholders are replaced with actual values when the template is rendered. Common placeholders include:

Placeholder	Description
	Full name of the client
	Account number
	Transaction or loan amount
	Current date
	Your company name
	Branch or office name
	Currency code

TIP

The exact placeholders available depend on the entity the template is associated with. The template editor will show available placeholders for the selected entity.

Managing Templates

• Edit — Modify an existing template's content or settings
• Delete — Remove a template (requires confirmation)
• Preview — See how the template will look with sample data
• Duplicate — Create a copy of an existing template as a starting point

Layout Settings

Templates now include a layout section so users can control how the generated document is wrapped, not just what the body says.

Identity Scope

• Tenant — Uses the tenant-wide document identity from Organisation Details
• Business Unit — Reserved for templates that should later use branch-specific letterhead logic

Header And Footer Modes

• Use default header — Builds a standard organisation header from the saved document identity
• Use default footer — Builds a standard compliance/footer block from saved registration, tax, VAT, and disclaimer details
• Custom header HTML — Lets advanced users replace the default header block
• Custom footer HTML — Lets advanced users replace the default footer block

Good Practice

• Keep the default header/footer for standard letters, invoices, notices, and internal forms unless there is a strong legal or operational reason to replace them.
• Maintain organisation legal/contact details in Organisation Details instead of hardcoding them into every template body.
• Use custom header/footer HTML only when the document really needs a different visual contract.

Next Steps

• Configurations — System-level configuration settings
• Organisation Details — Maintain the default identity used by generated documents