Countersign
Countersign is four-eyes approval over the actions a tenant chooses. A clerk captures the change; it does not take effect until the required approvers sign it. Nobody can approve their own capture.
What can be countersigned
Every mutating action in LedgerTM resolves to an action id — operations.give-notice,
credit-limit.increase, and so on. That id is the unit approval rules key off, and
it is the same id access control keys off, so one vocabulary covers both.
An action is eligible for countersign unless it is one the system runs on its own behalf (day-end, seeding, a cascade), or one of the countersign control actions themselves. Approving an approval would need its own approval, so those are excluded by construction.
How much a new tenant countersigns
You choose how much countersigning a tenant does when you create it, not later in a settings screen. The choice sets the rules the tenant starts with, and you can change those rules afterwards like any others.
| Posture | What the tenant starts with | When to choose it |
|---|---|---|
| Curated | One rule for every action a person can be asked to sign, each needing one approver, apart from the departures the package names. | The default, and the right answer for a bank. |
| Off | No rules at all. Every change is recorded and takes effect at once. | A development or demonstration system where one person works alone. |
| All | A single rule covering everything, including actions added in a later release. | The strictest setting, and the only one that also covers actions that did not exist when you created the tenant. |
Curated and All differ in how a new action is covered. Curated writes out the actions that exist today. Each release then adds one rule, needing one approver, for every new action no rule names yet. All is a single catch-all, so it covers whatever arrives the moment it arrives. Curated is easier to read and to tune.
The tenant remembers the posture you chose. A tenant created before the posture was recorded has it worked out once, from the rules it holds. Any catch-all rule means All. Rules naming at least half of today’s actions mean Curated. Anything else means Off. The release log prints the posture each such tenant was given.
Off needs no second person; the other two do. On a Curated or All tenant, almost everything a clerk does waits for an approver, so the tenant needs at least two people before anyone can get work done.
A package may name departures — actions it sets differently from the posture. Woodgrove Bank’s retail package marks the triage decisions inside a payment batch as needing nobody, because the batch itself is signed once as a whole. Signing each of forty items separately would stall the batch without adding a control.
Keeping a Curated action unsigned
If a Curated tenant wants an action to go straight through, keep its rule and empty its quorum. A rule with no approvers still names the action, so a release leaves it alone.
Do not delete the rule. A deleted rule is a gap, and the next release fills it with the default rule needing one approver.
| What the tenant did to the rule for admitting a user | After the next release |
|---|---|
| Emptied its quorum | Admitting a user still applies at once. |
| Deleted the rule | Admitting a user needs one approver again. |
A release never edits or removes a rule. It only adds the ones that are missing. Off and All tenants are left exactly as they are.
Worked example
You create a tenant for Woodgrove Bank’s retail book and choose Curated. Increasing a facility needs one approver. So does rescheduling a standing order. Approving an individual payment inside a batch does not, because the package names it as a departure — the batch is signed once, when it is released.
Had you chosen Off, the facility increase would take effect the moment the clerk saved it, and the change would still be on the record.
Changes nobody has to sign
A change no rule asks anyone to sign still goes on the record. It takes effect the moment the clerk saves it, and the change history shows it as approved automatically. Nobody’s queue lists it, because nobody has anything to do.
This is the same record a signed change leaves. An auditor reads one history, whether or not a second person was involved.
Batches signed once
Some work is decided item by item and released together: a day’s outgoing payments, a day’s suspense items. You decide each item, then release the batch. One approver signs the release, and every decision in it takes effect together.
flowchart LR
A[Decide each item] --> B[Release the batch]
B --> C{Approver signs?}
C -->|Signed| D[Every decision applies]
C -->|Rejected| E[Nothing applies]
A batch belongs to one operating entity, one kind of work and one trading day.
| While the batch is | What happens when you decide another item for it |
|---|---|
| Being built | The decision joins the batch. |
| Released, awaiting its signature | The decision is refused, naming the pending release. |
| Signed or rejected | The decision starts a new batch. |
Until the approver signs, each decided item shows its decision as staged. Nothing on the item itself has changed yet.
Worked example
A clerk at Woodgrove Bank works through today’s outgoing direct credits for one operating entity. They approve forty and reject two. The forty are paid from two different funding accounts.
| Step | What you see |
|---|---|
| The clerk decides 42 items | Each shows its decision as staged. No payment has moved. |
| The clerk releases the batch | One request appears in an approver’s queue. |
| An approver signs | All 42 decisions apply, and two payment files are built, one per funding account. |
If a second clerk approves another of that entity’s direct credits for the same day while the release waits, the approval is refused. Once the approver signs, the next approval starts a fresh batch.
Approval rules
A rule matches an action id, optionally narrowed by a predicate over the action’s own facts, and states the quorum it requires:
| Part of the rule | What it says |
|---|---|
| Action | Which action this rule governs |
| Predicate | An optional condition over the action’s facts, such as amount > 500000 |
| Thresholds | Per-currency amounts, so a limit means the same thing in each currency |
| Require | The quorum: one or more groups, each with a count |
A single require entry means “N approvals from this group” — the common case. Two
or more entries express separation of duties: one from Credit Risk and one from
Treasury, which no single team can satisfy alone.
The action has to be one this system recognises. If you name an action that does not exist, the rule is refused when you save it. Pick the action from the list the rule editor offers rather than typing it. A misspelled action would match nothing, so the rule would sit in your settings looking like a control while the action it named went unsigned.
Acts a client user makes
A client user’s act in the client portal follows the client’s own rules, not yours. Each agreement carries the client’s rules, and the client’s own signers approve from their own portal queue. Your approval rules never apply to a client’s act, and no one at the bank can sign it or force it through. For how a client sets its rules, see a client’s own approval rules.
If a signing officer makes a contractual act, such as appointing an administrator, the act waits for the co-signer the agreement’s mandate asks for. It is not refused. The second officer signs from their own queue, and the act applies citing both.
A client’s payment works the same way. It waits for the client’s signatories, and your queue shows how many have signed, such as 1 of 2. Your approvers cannot sign it, and the bank’s approval rules never add a signature to it.
Worked example
A tenant wants rate changes above half a percent of movement to need a second pair of eyes from Treasury, and everything else to go straight through.
| Action | operations.change-rate |
| Predicate | spread > 0.5 |
| Require | 1 from Treasury |
A clerk changes a rate by 0.25 — no rule matches, the change applies. A clerk changes a rate by 0.75 — the change is captured, a Treasury approver sees it in their queue, and the rate moves when they sign. If nobody signs, nothing happened: the account is untouched and the capture is on the record.
Rules for one account type
If a change is made on an account, the rule can also read the account’s type. The
type is a fact called accountType, and it holds the type’s name, such as
PersonalLoan. So one rule can treat a personal loan differently from a mortgage bond.
The system reads the type from the account itself. A clerk cannot supply it. If an
operation has an input that happens to be called accountType, the account’s own type
still decides.
The fact applies to every change made on an account, not only to operations. Discarding an account draft, for example, can be gated on the type too.
Names in a predicate are written in single quotes, and they match exactly, including upper and lower case.
Worked example
Woodgrove Bank wants rate changes on personal loans to need a second signature. Rate changes on mortgage bonds go straight through.
| Action | operations.change-rate |
| Predicate | accountType == 'PersonalLoan' |
| Require | 1 from Approvers |
| The clerk changes the spread from 2.5% to 3.25% on | What happens |
|---|---|
| A personal loan | The change waits for an approver. The spread stays at 2.5%. |
| A mortgage bond | The change applies at once. The spread is 3.25%. |
Settings changes
A settings change is signed as one action, settings.publish, whatever the settings
cover. On a Curated tenant that action has a rule needing one approver. So a change to
the bank registry waits for an approver, and so does a change to the approval rules
themselves.
The rule can read which settings are changing. The fact is called settingsType, and
it holds the settings’ name, such as BankSettings or AccountLayoutSettings.
If you want one kind of settings to go straight through, narrow the one
settings.publish rule. Do not add a second rule that needs nobody. A second rule sits
beside the first, and the stricter one still applies.
Worked example
Woodgrove Bank wants screen layout changes to go straight through. Every other settings change keeps its approver.
| Action | settings.publish |
| Predicate | settingsType != 'AccountLayoutSettings' |
| Require | 1 from Approvers |
| The operator publishes a change to | What happens |
|---|---|
| The account layout settings | The change applies at once. |
| The bank registry | The change waits for an approver. The new bank is not live yet. |
Saving a produced document is signed the same way. Every package’s rule asks for an approver on a loan agreement only, so a statement still saves at once.
What the clerk and approver see
The captured change appears on the Staged Changes panel of whatever it affects, showing the full before-and-after the change carries. An approver sees the same list the clerk captured, not a summary of it, so the thing being approved is the thing that will run.
Every change shows the values it sets. A change that nobody wrote a tailored summary for still lists what it carries, field by field, so the panel is never empty for a change that is really there.
A capture that is never approved never takes effect. It stays visible as a capture, which is the audit answer to “who asked for this and who refused it”.
You need permission to open the approval queue. Without it you cannot list what is waiting, read a captured change, or see who is required to sign it. Approvers hold that permission, so an approver can always read what they are being asked to sign.
What the old value tells you
Each row shows the new value on the right. What appears on the left depends on what the system was able to record at the moment of capture.
| On the left | What it means |
|---|---|
| The old value | The value being replaced was recorded when the change was captured. |
| prior value not captured | Nothing recorded what this field held beforehand. |
| newly set (on the card) | The change creates the record, so there was nothing to replace. |
Prior value not captured is neither a warning nor a blank. It says the system did not record the old value, rather than claiming there was none. Read it as: you are approving this new value, and this screen cannot show you what it replaces. If you need the old value, open the record itself before you sign.
Newly set marks a card that creates something. That card stays on its own, and never merges with later changes to the same record.
Worked example
A clerk corrects a counterparty’s tax residency from the United Kingdom to South Africa. The approver opens Staged Changes and sees one card, Correct tax residency:
| Field | Old | New |
|---|---|---|
| Country code | GB | ZA |
The old country was recorded when the correction was captured, so the approver reads the change rather than only its result. Fields the correction leaves alone are not listed — the card shows what moves.
If the clerk captures a second correction to the same residency before anyone signs, the two appear as one card showing the latest value, labelled with how many captures it nets.
What the change does to money
If a change moves an account’s money, the approver sees a Money effect box. It is worked out once, when the clerk submits, and it never changes after that. It is marked as at the trading date of submission.
| Line | What it shows |
|---|---|
| A forward line, such as Next instalment | The figure before and after the change, from the trading date forward, and the difference. |
| Back-dated transaction type | The adjustment to accrual already booked, from the date shown on the second line. |
| Back-dated adjustment — could not be computed | The system could not work out the back-dated figure. The forward lines still show. |
A change dated after the account was last processed has no back-dated line. Nothing was booked on those days yet.
You do not need permission to view accounts to see this box. It shows what was stored, and it reads nothing live.
Why the posting can differ from the figure you signed
You approve the correction, not an amount. If end of day runs between submission and your signature, the posting includes those extra days. The posting, not the box, is what reaches the ledger.
For example, a clerk submits a back-dated rate correction on Friday. You sign it on Tuesday. The posting then covers up to four more days than the box shows.
Worked example
A clerk corrects an interest rate back to 1 March 2026. The trading date is 1 June 2026. You see:
| Line | Before | After | Change |
|---|---|---|---|
| Back-dated Interest, from 2026-03-01 | −412.37 | ||
| Next instalment | R 1 812.40 | R 1 766.05 | −46.35 |
The box reads as at 2026-06-01. The back-dated line is the accrual already booked since 1 March, restated at the new rate. The forward line is the next instalment.
When the request switches a feature off
If the request switches a feature off, the approver sees an Affected by switching this off box. It counts what uses the feature now, at the moment you open the request.
The box lists every check that ran, with its own count. The total in the heading is the sum of those counts.
| The box says | What it means |
|---|---|
| A list of checks, each with a count | Those checks ran. A count above zero is work that stops when you approve. |
| No accounts, products or settings use this feature. | Every check ran and found nothing. |
| No usage checks exist for this feature. | Nothing is checked for this feature. The system cannot tell you what stops. |
| Could not check what uses the feature | The count failed to load. Approving still switches the feature off for everyone. |
If the count moved since the request was raised, the box states both figures. You sign against the count shown now.
Worked example
A clerk asks to switch off loan provisioning. No account uses it. You see:
| Check | Count |
|---|---|
| Accounts provisioned | 0 |
| Provisioning runs | 0 |
The box reads No accounts, products or settings use this feature. Two checks ran, so “nothing” is an answer, not a gap.
When the request runs an operation
If the request runs an operation on an account, such as a rate change, the approver sees the same preview the clerk saw. The back-dated lines match line for line, including the day count your organisation configured for the account.
If the clerk gave no effective date, the change takes effect on the trading date. A change dated after the account was last processed has no back-dated line.
When a request is refused instead of approved
A capture is a promise made on the day it was staged. Approval can come days later, and the world moves in between. So the rules that read the world are asked again at the moment of approval, not only at capture.
If one of them refuses, nothing in the request applies — not the failing row, and not the rows either side of it. The request stays where it is, still awaiting approval, and your own approval stays recorded against it. You are told which row refused and which rule refused it.
A clerk stages a ten-row onboarding request on Tuesday. Row 6 moves an account to
cost centre CC-204. Someone closes CC-204 on Wednesday. On Friday the approver
signs:
| What | Before | Now |
|---|---|---|
| Rows 1–5, 7–10 | applied | not applied |
| Row 6 | applied against a closed cost centre | refused, naming the row and the rule |
| The request | Granted | still awaiting approval |
| Your approval | recorded | recorded |
The approver reads “You approved this. The change was refused:” followed by the reason in words. The queue shows the request as Refused, with the same reason under it. The clerk who raised the request sees Refused and the reason on the record itself.
Refused is different from Not applied, which you will also see. Not applied means the request was approved and applied, and one trailing step afterwards did not. Refused means nothing happened at all.
When the system could not apply the change
A refusal is a rule saying no. Sometimes the system itself fails instead. Then the approver reads “The system could not apply this change. Nothing was changed.” with a reference.
| What you see | What it means | What to do |
|---|---|---|
| Refused, with a reason | A rule said no. Your approval stays recorded. | Resolve the cause and approve again, or reject. |
| Could not apply, with a reference | The system failed. Nothing changed, and your approval was not recorded. | Approve again later. If it fails again, give the reference to support. |
A system failure never names a rule, and it never says someone else changed the record. The reference lets support find exactly what went wrong.
The request itself is not editable once submitted. The way back is to resolve the cause — here, reopen the cost centre — and approve the same request again, which re-runs it against the world as it then stands. If the cause will never be resolved, reject the request and stage a new one.
When something else is in the way
Sometimes a change cannot go ahead because of something else happening at the same moment. The message tells you what is in the way and what to do. The same messages show to a clerk saving a change and to an approver pressing approve. None of them is recorded as a refusal.
| You see | What it means | What to do |
|---|---|---|
| Day-end is running. Try again shortly. | End of day is running, and the system is read-only until it finishes. | Select Try again once end of day has finished. |
| Someone else is changing this record. Try again shortly. | Another change to this record is in progress, or waiting for an approver. The message names who, when it can. | Select Try again once their change has gone through. |
| This record is already in another change set, raised by a named person | That person has unsaved changes open on this record. | Ask them to submit or discard their change set. |
| A record in your change set changed since you staged it. | A record your change set relies on moved after you staged it. Each one that moved is listed. | Check what moved, then stage your change again. |
| Not enough approvers are left to sign this. | Everyone who could approve has worked on this change themselves. | Ask a colleague who has not worked on it to submit it. Trying again will not help. |
| This record changed while you were editing it. | Someone saved a change to this record after you opened it. The latest version loads for you. | Check the record, then make your change again. |
| The number of records still using a feature | You asked to switch off a feature that is still in use. | Confirm to switch it off anyway, or leave it on. |
If end of day has already finished when you try to start it, you are told the trading date it moved to instead.
Worked example
Sam asks to switch off withholding tax while 14 accounts still use it. Sam reads Withholding tax is in use on 14 accounts. Confirm to switch it off. Nothing changes until Sam confirms.
Changing your approval rules
The rules are the controls, so changing them is itself controlled. You edit them on the Approval Rules settings screen, which keeps your edits in a staged copy. Nothing you do there reaches the live rules until you publish the staged copy.
- Open the Approval Rules settings screen.
- Add, edit, or remove rules. Each change lands in the staged copy.
- Select Publish.
Publishing is an action like any other, so your organisation can require a second pair of eyes for it. Where it does, the live rules move only once an approver signs.
A change sent to the live rules without going through the staged copy is refused, and the refusal says the change has to be staged first. There is no way to edit the live rules in one step.
Working through the queue
The queue opens on Pending requests, oldest first, so the request waiting longest is at the top. The count beside the title is every request that matches your chips, not the rows on the page. Move through the queue with Previous and Next.
- Select Mine to approve to see only the open requests you may approve. A request you submitted, or added a change to, never appears there, and the count leaves it out too.
- Select a status chip, such as Approved, to see closed requests. All shows every status.
- Search finds a request by the requester’s email, the record type or the change.
For example, Woodgrove Bank has 240 open requests. Sam opens the queue. The count shows 240, and the first page shows the 100 oldest requests.
Who can see the queue
Reading the whole queue needs the list authorisations permission. It covers the list, each request’s detail, its timeline, and the approver’s feasibility and quorum checks. Approving needs the approve permission as well.
If a person lacks it, they still see the requests they submitted themselves. Their queue lists only those, and the pending-request banner still shows on their own changes. Anyone else’s request is refused.
Verifying a phone-passkey signature needs the verify signed decision permission. If a person lacks it, the timeline still marks a signed decision, without the verify button.
What your organisation configures
- Which actions need approval, and the quorum each one requires.
- Which account types a rule applies to.
- Whether a batch’s item decisions need a signature of their own, or only the release.
- Whether publishing a change to the approval rules itself needs an approver.
- Which groups approvers belong to, and who is in them.
- Which groups may read the queue and verify signatures.
A client’s own rules for its portal acts are the client’s to set, not yours.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.