Switching features on and off
Your organisation licenses a set of features. The Features screen shows what you hold and lets you switch each one on or off. Switching a feature off removes it from the screen everywhere it appears.
Off means invisible. You do not have to hide the screens yourself, and nobody can reach a switched-off feature by typing its address.
What “off” removes
When a feature is off, everyone in your organisation stops seeing all of it:
| Surface | What disappears |
|---|---|
| Navigation | The icon in the left rail, and the entries behind it |
| Pages | The page itself, even when opened from a saved link |
| Settings | The feature’s settings pages, and its tile when nothing else is left on it |
| Record tabs | The tabs on an account, counterparty, operating entity or external account |
| Table columns | Columns that only make sense with the feature — in the table and in its exports |
| Views | The named views above a list, such as the ones for a specific product |
| Actions | The feature’s entries in an action menu |
An entry that is not part of any feature is always shown. Switching everything off still leaves you a working system.
If your configuration requires a record, the place to capture it stays visible. An account type that needs a credit limit before activation keeps the credit limit tab, even while that feature is off. The feature hides its optional screens; it never hides the field that satisfies a requirement you have configured.
A feature switch is not a behaviour switch
The switch controls what people see, sell, and newly capture. Your configuration — account types, rails, compliance rules — controls what the running system does.
Switching a feature off does not stop the work your configuration drives. Arrears are still tracked, statements still produced, postings still made. That history is kept, so the day you switch the feature on, its screens open with the record complete.
The exception is work one feature does in response to another. If that feature is off, it does not respond:
- If suspense is off, unmatched statement lines are not parked. They stay unmatched.
- If collateral is off, activating a secured account records no security against it.
If you want a behaviour to stop, change the configuration that drives it — remove the rail, the statement cycle, or the rule — rather than switching the feature off.
Licensed, and switched on, are two different things
Two separate answers decide what you see.
- Licensed — your organisation bought the feature.
- Switched on — you are using it today.
You can hold a licence and keep the feature off. Its help articles and release notes stay readable while it is off, so you can read up on a feature before deciding to switch it on.
Every feature can be switched off. There is no feature you are obliged to keep.
When a request is refused
The switch is enforced wherever a request arrives, not only on screen. A saved link, a script, or another system calling in gets the same answer as the screen.
You see one of two messages. Each tells you who can fix it.
| Message | What it means | What you do |
|---|---|---|
| “Collections Desk is switched off for this bank.” | Your organisation holds the licence, but the feature is off today. | Ask an administrator. They can switch it on in Settings → Features. |
| “Collections Desk is not part of this bank’s licence.” | Your organisation has not bought the feature. | Contact whoever manages your agreement. No setting here changes it. |
The feature named in the message is the one your request needed. Collections Desk is an example.
What still works while a feature is off
If a feature is licensed but switched off, you can still look things up. A record made while it was on stays readable.
You can also finish work already started. Closing a collection case, or lifting a hold on one, still goes through. What stops is new work: a new promise to pay, a new case.
If a feature is not licensed, nothing in it is available, including looking things up.
The client portal
Clients reach you through the client portal. It is a feature of its own, listed as Client Channel on the Features screen. If the client portal is switched off, every client request is refused, including finishing work already started.
If the client portal is on, each client request also needs the feature it uses. A client setting up a debit order needs debit orders switched on too.
Changes waiting for approval
A change captured for a second person to approve is checked again when they approve it. If the feature it needs was switched off in between, the approval is refused and nothing is applied.
The approver sees who switched the feature off, and when:
This change can no longer be applied. Collections Desk was switched off on 30 Oct 2026 by Alex.
If the licence was removed instead, the message says the feature was removed from this bank’s licence. If the system has no record of the switch, the message leaves out the date and the name.
The change stays in the approval queue. If the feature is switched back on, the same change can be approved again. Finishing work already started, such as closing a collection case, still approves while the feature is off.
Features that contain other features
Some features sit inside a larger one. Multi-currency contains exchange rates and foreign-exchange revaluation, for example.
Switching off the larger feature switches off everything inside it. Switching off one of the smaller ones leaves the rest alone.
flowchart TD
A["Multi-currency: ON"] --> B["Exchange rates: ON"]
A --> C["FX revaluation: OFF"]
B --> D["Rates screens visible"]
C --> E["Revaluation screens hidden"]
A feature can also depend on another one. If something it depends on is off, it is off too, even where its own switch says on.
Switching a feature off does not delete anything
Records made while a feature was on stay exactly as they are. Balances do not move and history is not rewritten.
Switching the feature back on brings its screens back with the records still there.
Some features warn you when you switch them off, because work is in flight — an unexpired notice, or an open settlement quote. Read the warning before confirming; it tells you how many records are affected.
If switching a feature off needs a second person to approve it, the approver also sees how many changes that need the feature are waiting for approval. Once the feature is off, approving any of them is refused.
If your configuration still requires the feature, the warning also names what requires it — the account types, compliance rules, or rails involved. You can then change that configuration first, or confirm and switch the feature off anyway.
Settings that need a licence
Some settings only make sense with a feature. A document type that requires a signature needs Document Signing. A posting group on an account type needs General Ledger.
If your organisation does not license the feature, you cannot save a setting that needs it. You see a message such as “Document Signing is not part of this bank’s licence.” You can still remove a setting like that, so an old row never blocks you.
If the feature is licensed but switched off, the setting saves normally. The switch controls what people see. It never decides which settings you may keep.
| Feature | Licensed and on | Licensed and off | Not licensed |
|---|---|---|---|
| Document Signing | The setting saves. Documents of that type go out for signature. | The setting saves. Sending a document of that type is refused, never sent unsigned. | The setting is refused. |
| General Ledger | The posting group saves. Postings are made. | The posting group saves. Postings are still made. | The posting group is refused. |
A document that needs a signature is never sent without one
If a document type requires a signature and Document Signing is off, saving and sending that document is refused. The message names Document Signing. The document is not sent unsigned.
Finding settings that rely on a missing licence
A licence can change after a setting is saved. Your administrator can list every setting that relies on a feature your organisation no longer licenses. Each entry names the setting and the feature it needs.
What your organisation configures
- Which features you license. This comes from your agreement and is not changed on this screen.
- Which licensed features are switched on today.
- Who may change the switches. Changing one can require a second person to approve it, depending on how your organisation has set approvals up.
Related
- Countersign — when a change needs a second person to approve it.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.