Templates for email and SMS

The Templates page sets what your organisation’s emails and SMS say. Every statement, notice and advice starts from built-in wording, so nothing needs writing before the first send. You change the wording here, in each language your clients use.

What the page shows

Tab What you edit
Templates The subject, body and SMS text of each kind of correspondence
Layouts The HTML page every email is framed in — logo, colours, footer
Snippets Clauses many templates share, such as the complaints wording
Images Pictures a template or layout can show, such as a banner

Writing a template

  1. Choose the Template, the Channel and the Language.
  2. Click where the text should go.
  3. Select a field from Placeholders. It appears as a chip in the text.
  4. Select Save draft. The preview shows the draft inside the email layout, filled with sample values.

The body uses simple formatting: bold, italic and bulleted lists. Select the code button to see the text as written. Text that uses formatting the visual view cannot show always opens that way.

For example, a rate-change email that shows the account balance reads R 412 380.00 for account LA-100231 as at 1 October 2026. The amount is formatted for English as used in South Africa: a non-breaking space groups the thousands.

Sensitive fields

A field marked sensitive, such as a date of birth, can go in an email or a letter. It never goes in an SMS or a WhatsApp message. Publishing refuses an SMS that uses one, and names the field.

From draft to published

A saved draft changes nothing a client receives. Publish makes it the text every new send uses. If your organisation requires a second person, publishing waits for their approval, and they see the published and draft text side by side.

Correspondence already sent keeps the text it was sent with. A later change never rewrites it.

Languages

A client receives the template in their preferred language. If there is none in that language, they receive the default language. Dates and amounts are formatted for the template’s language.

The languages you can choose are set on the Languages page.

Language An instalment of 3812.50 reads
English R 3 812.50
Afrikaans R 3 812,50

When publishing is refused

Message names What to do
A field the template does not offer Pick the field from Placeholders instead of typing it
Text that does not parse Close the {{ }} or {% %} the message points at
A required block, such as the complaints clause Put the block back — the law requires it on that correspondence
A layout that breaks an email Keep the content placeholder in the layout

Word templates and producing documents

A Word template is a .docx whose placeholders are tagged content controls. Download the starter document from a document type: every field it offers is already a tagged control. A repeating section tagged account.schedule repeats once per instalment.

Uploads are refused when they carry tracked changes, a font that is neither embedded nor standard, or a tag the type does not offer. A loan agreement must name the lender’s registration number (entity.registrationNumber).

Produce a document from the Documents tab on a client, an account, or another record that offers documents. Preview it first; nothing is stored until you save. Save keeps the PDF. Save and send also sends it by the client’s delivery preferences, in the language it was produced in.

If the record names one branch or business, the document is issued under it, and you are not asked to choose. If it names several, choose one under Issue as.

If the document concerns no client, only Save is offered. Download or print the PDF from the Documents tab. A back-office slip about a cash lodgement is an example: no client receives it.

If the bank’s approval rules say so, saving waits for an Approver. Retail banks require one for loan agreements (documentType == 'loan-agreement'). The approver opens the pending file, which is the file the clerk produced. If the approver rejects, the document stays on the tab marked rejected and is sent to no one.

Worked example (fixture demo-loan-agreement.docx, test LoanAgreementTests): LA-100231’s agreement is produced on 2026-10-05 from version 1. Version 2 is published on 2026-10-06. A manager approves on 2026-10-07. The saved agreement is the 2026-10-05 file, from version 1.

What your organisation configures

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.