Correspondence sent to a client

The Correspondence panel lists everything sent to a client — statements, notices, certificates, advices — and how each one went. It answers the question an auditor asks: did the client get it, and if not, why?

An account has its own Correspondence panel. It lists what was sent about that account: its statements, notices, payment advices and letters.

On the client’s panel, the Account column names the account each item was about. It is blank for correspondence about the client alone, such as a welcome letter.

Both panels list newest first, 50 at a time; select Load older for earlier items. Search matches the title and the address each item went to. There is no list of everything sent across the bank: correspondence is always read for one client or one account.

Sending a letter

  1. Select Send document above the list.
  2. Pick the document, such as a welcome letter.
  3. Preview it, then select Save and send.

This is the same screen as Produce document on the Documents panel. The client’s delivery choices pick the channel. The new row appears here once it is sent.

What each row shows

Each row is one piece of correspondence. The Channels column shows each channel it was meant to go by, and what happened on it.

Channel outcome What it means
Sent The gateway accepted it, on the date shown, to the address shown
Not used The channel was not used, with the reason
Failed The gateway refused it, or retries ran out
Returned It was sent, and later came back — the send stays on record
Waiting It is still being sent, or a clerk is still to post it

A despatched channel reads by its despatch label. An email sent by a Simulator gateway reads Email (simulated), and an SMS reads Sms (simulated).

Not used always gives the reason:

Reason What it means
client opted out The client chose no channel for this kind of correspondence
no email address The client has no primary email
no mobile number The client has no mobile number
channel not configured Your organisation has not set up this channel
channel cannot carry a document A document cannot go by this channel, such as SMS

Select View on a row to see what each channel sent — the email as the client saw it, its plain-text part, and the SMS text. The email shows in a frame that cannot run anything, exactly as it was rendered at the time.

The outcome

Once every channel has finished, the correspondence has one outcome.

stateDiagram-v2
    [*] --> InProgress
    InProgress --> Delivered: at least one channel sent
    InProgress --> NotSent: the client opted out
    InProgress --> Undeliverable: nothing was sent
    Undeliverable --> Delivered: a resend succeeds
Outcome What it means
Delivered At least one channel sent it
Not sent The client opted out of this kind of correspondence
Undeliverable No channel could send it

A temporary gateway problem, such as a timeout, is retried automatically. The channel stays Waiting while it retries.

When correspondence cannot be delivered

Some correspondence must be delivered, such as a legal notice. If none of its channels reaches the client, it goes by the fallback channel your organisation has set, if any. If there is none, or it fails too, a follow-up task is raised on the client, naming the correspondence and the reasons.

A must-deliver item that is returned — post that comes back — also raises a task, unless another channel’s send still stands. The return never cancels the original send date.

Resending a failed channel

  1. Find the row with a Failed channel.
  2. Select Resend beside it.

The resend goes to the address recorded when it was first sent, even if the client has changed their address since. Only a failed channel can be resent.

Forwarding a copy

  1. Select Forward on the row.
  2. Enter the email address.
  3. Select Forward.

The copy has the same title and document. It goes only to the address you type — the client’s choices and copies do not apply. The original row is unchanged, and the copy is marked as a forwarded copy. If your organisation asks for a second person to approve, the forward waits for a checker.

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.