Studio
Change it, see what it does, and sign it. Studio is a workbench where you try a change, see its effect, and then discard it or keep it, and nothing reaches the ledger until you say so.
Not sure what a change will do? Try it.
Stage it, look at the before-and-after, run the forecast with it applied, and read the effect on the book. If it isn't what you meant, discard it, and the account is exactly as it was with nothing recorded. If it is, save it or send it for countersign. That's the whole idea of the workbench, so an operator can follow a restructuring, a repricing or a correction all the way through before committing to any of it.
Pressing Apply on an operation writes nothing.
It stages the change into Studio, and you can stage as many as the job needs, say a rate change and a revised instalment plan on an account, a new bank account and an address on the counterparty, or five facilities on a customer. Each one shows its full before-and-after on the Staged Changes panel. Then you save the set, or submit it for approval where a rule says a second person must sign. We once built an engine so configurable that resetting a rate meant adding an accrual rule, which is how we learnt that "reset the rate" should be a button.
The forecast includes what you have staged.
Stage a deposit of 100,000 on an account holding nothing and the forecast's starting balance reads 100,000, while the plain forecast beside it still reads zero, because nothing is committed. Stage a rate change and the projected accruals move. That's how a change gets shaped and checked before anyone signs it, and the approver sees the same projected effect.
Before and after
Every staged card carries the prior value and the new one. A corrected tax residency, for instance, shows the old country beside the new one.
Value dates respected
A change dated next month sits pending on the panel and takes effect when the day walk reaches it. Until then it can be cancelled or re-dated.
One authorisation, not seven
A set that crosses accounts, counterparties and settings is reviewed and signed once, as the combined change it is.
Countersign is something you configure rather than something built in.
Your organisation decides which actions need approval, who may approve them, how many signatures each needs, and under what conditions. A rule names an action, an optional condition over the action's own facts, amount thresholds per currency, and the quorum: one or more approver groups, each with a count. Put two groups in one rule and you have separation of duties that no single team can satisfy alone. Whoever initiated or contributed to the change can never sign it.
The rules are settings themselves, edited in a staged copy and then published, and publishing can need a signature of its own.
| Rule | Reads as |
|---|---|
| change-rate · spread > 0.5 · 1 from Treasury | A rate change by more than half a percent needs a Treasury approver. Smaller changes apply at once. |
| advance · amount > 500,000 · 1 from Credit Risk and 1 from Treasury | A loan drawdown above the threshold needs two signatures from two different teams. |
| change-limit · 2 from Credit Committee | Any limit change needs two committee members, whatever the amount. |
| correct-tax-residency · 1 from Compliance | A compliance fact needs a compliance approver. |
The first row is the guide's worked example, and the others show the shape. Thresholds are set per currency, so a limit means the same thing in each.
Approval rules, rate cards and the other settings screens keep your edits in a staged copy. Nothing reaches the live rules until you publish it, and publishing is an action your organisation can put behind a second signature. There is no way to edit a live rule in one step.
A clerk can try a restructuring, see exactly what it will do to the book, and then throw it away or hand it to the right approvers as one thing. Who those approvers are, and how many of them, is your rule, and what they sign is the change that will run rather than a description of it.