What's new

12 features landed in the last week and 41 in the last thirty days, each on the day it landed, with the guide article that explains it.

Most of us have waited a year for a vendor's next release, and then found the one thing we asked for in the notes as "under consideration". We'd rather show you the work as it lands. Every entry below is a feature that went through a decision record, a plan and the full test suite and landed on main, and the time beside it runs from the day it was proposed to the day it was released, nights included. Some of it is on main but not yet in a numbered release, and we say so beside it, along with how long it took to land. Fixes and small changes are left out, so this is the floor, not the ceiling.

11 November 2026
Corporate banking

Invest the surplus overnight

A liquidity structure can invest its header account's surplus at day-end and keep a cash buffer you choose, with call deposits coming back when funding is needed and external instruments settled through notional accounts.

on main, not yet released2 days from proposal to landingNotional investment accounts →
Corporate banking

See a sweep before any money moves

A treasurer previews a structure's sweep in the client app or the bank's Liquidity panel, every account's balance before and after and a sentence on why each leg moved what it did, for today, a past day-end or a change still waiting for approval.

on main, not yet released47 hours from proposal to landingSimulating a sweep →
10 November 2026
Corporate banking

Sweep on a schedule

Each pair says on which business days and at what times it sweeps, a slot too late for its payment cut-off is refused when it is set up, and day-end waits for the date's sweeps to settle.

on main, not yet released38 hours from proposal to landingLiquidity structures →
Corporate banking

Sweeps that run, and breaks that get worked

A sweep run moves the money leg by leg as book transfers coded CAMT/ACCB/SWEP, a leg that cannot finish breaks with a named reason while the rest carries on, and operations work the breaks on their own list.

on main, not yet released35 hours from proposal to landingSweep breaks →
Corporate banking

How a sweep concentrates cash

Each pair in a liquidity structure names its method, from zero balance and target to collar, range or a custom band, and one calculation turns the structure into proposed legs and names what limited each one.

on main, not yet released27 hours from proposal to landingLiquidity structures →
9 November 2026
Corporate banking

Liquidity structures both sides agree on

A client and the bank share one dated account tree with its full change history, the other side approves a change before it takes effect, and no account can sweep in two structures on the same date.

on main, not yet released10 hours from proposal to landingLiquidity structures →
8 November 2026
Corporate banking

Move money between a customer's currencies

Bank and client users raise, approve and release transfers between the same customer's accounts in different currencies, with a countdown on the booked price and the execution reference on both entries.

on main, not yet released27 hours from proposal to landingFX transfers →
Corporate banking

Incoming money finds its virtual account

A receipt to a trusted virtual number or an exact invoice reference routes itself, the rest wait on a list for a clerk to confirm, and a clerk can place and release holds on a virtual account's money.

on main, not yet released3 days from proposal to landingReconciling a bank account →
7 November 2026
Card acquiring

Settle under more than one sponsor bank

An acquirer can settle under several sponsor banks, ordered rules pick each merchant's sponsor at boarding, and scheme settlement, positions and payouts run per sponsor.

on main, not yet released22 hours from proposal to landingSponsor banks and sponsor rules →
Corporate banking

Statements for virtual accounts

A statement can cover one virtual account, a grouping or everything a client holds, exported as camt.053 or issued as a PDF, and a client can subscribe to have it delivered by email or host-to-host once the period is final.

on main, not yet released43 hours from proposal to landingStatements →
6 November 2026
Card acquiring

Merchant groups of any shape, in any currency

A merchant is a node in a tree of any depth, with a settlement account per currency, one pricing plan, and pricing, settlement and reserve changes that are value-dated and can be cancelled before they take effect.

on main, not yet released2 days from proposal to landingOutlets →
5 November 2026
Platform

Price lists in many currencies

A price list holds any number of currencies, a fee prices from the row in the account's currency and rounds to its minor unit, and a pricing plan can belong to any owner and be shared by several accounts.

on main, not yet released30 hours from proposal to landingPricing plans →
4 November 2026
Card acquiring

The scheme's side of every card sale

Acquiring now books the scheme's leg of every sale as well as the merchant's, per settlement currency, so the scheme's totals show any break and the nostro receipt clears the account.

on main, not yet released29 hours from proposal to landingScheme settlement elections →
3 November 2026
Retail bankingLending

Retail and loan customers on the client app

An existing retail or lending customer registers themselves with an ID number, an account number and a code sent to their phone, then reads their transactions, loan balances and the instalments still to pay.

on main, not yet released35 days from proposal to landingThe payments area →
Card acquiring

A waiting agreement shows on its merchant

When opening a merchant agreement waits for a second person, the request sits on the merchant's agreements tab until it resolves, so a colleague sees it before opening the same agreement again.

on main, not yet released3 hours from proposal to landingMerchant agreements →
Corporate banking

A client adds its own beneficiaries

A client adds a beneficiary from the portal under its own approval rules, with a fresh passkey sign-in for each one, and the list marks every beneficiary as the client's own or bank approved.

on main, not yet released20 hours from proposal to landingApproved beneficiaries →
Corporate banking

The client portal, rebuilt for corporates

The client portal wears the bank app's shell, with accounts by type, cards by cardholder, one Authorisations page where people sign, and the client's own administrator managing entitlements and signing rules.

on main, not yet released20 hours from proposal to landingCorporate cards →
2 November 2026
Platform

Another bank's day, before it closes

Intraday reports from another bank, camt.052, MT942 and camt.054, are imported or pushed per account and held as a provisional day, which the close statement then replaces and confirms.

on main, not yet released15 days from proposal to landingImporting a bank statement →
1 November 2026
Corporate banking

A client signs and releases its own payments

A client's own people sign, release and reject payments in the portal under ceilings they set, and the bank no longer approves a client payment at all.

on main, not yet released31 days from proposal to landingReleasing a payment file →
31 October 2026
Corporate banking

A client's own signing rules

A client sets who must sign each act in the portal, and a client act follows the client's rules and never the bank's, so no bank operator can sign it or force it through.

on main, not yet released31 days from proposal to landingCountersign →
30 October 2026
Corporate banking

Follow a payment to settlement

The client portal's Payments page tells a client in plain words where each payment is, from with the bank to settled or returned with the bank's reason, and a clerk can raise a payment to someone the client has paid before.

on main, not yet released30 days from proposal to landingHow a payment picks its rail →
Platform

Money is never posted without a reason

The decision commits first and the money follows, so if an account refuses the money the refusal is written on the payment, fee or dispute that asked for it, and a day-end step that fails on one item still finishes the rest.

on main, not yet released30 hours from proposal to landingPayments on an account →
Platform

Switched off means off, everywhere

A feature that is switched off or not licensed is refused at every door, the API, the MCP door and an approval already waiting included, and switching one off names the settings that rely on it.

on main, not yet released3 days from proposal to landingSwitching features on and off →
27 October 2026
Platform

A tax register that adds up to the return

Pick a tax type, a currency and a period and the register lists every tax line in it with the total that goes on the return, and in the accounting currency it matches the VAT payable movement to the cent.

on main, not yet released5 hours from proposal to landingTax register →
26 October 2026
Platform

Tax on its own line, beside its charge

Tax now posts as its own transaction paired to the fee or interest it is levied on, shows as one row with a breakdown on the statement, the export and camt.053, and takes the VAT rate at the value date.

on main, not yet released3 days from proposal to landingTax types →
18 October 2026
Platform

Sold by some entities, in some currencies

A product can name the operating entities that sell it and the currencies it is sold in, and opening an account offers only those and refuses anything outside them.

2 days from proposal to releasebuilt in five stepsAnswers the system fills in when you open an account →
Platform

Variants that follow their parent

A staff or broker variant can be based on its parent product and follow it part by part, so one change to the parent reaches every variant that follows it, and each variant can still hold its own value for any part.

3 days from proposal to releasebuilt in five stepsProducts →
Platform

Change an account type on its own page

Positions, dates, transaction types and properties are added, edited and removed on the account type itself, every change goes to a second person, and each form says which products and how many open accounts it reaches before you save.

3 days from proposal to releasebuilt in four stepsChanging what an account type holds →
Platform

Ask the assistant to change a product

Where your organisation allows it, the assistant drafts a product change, or a new product copied from an existing one, into that product's change set, and nothing goes live until the clerk accepts it and the set is approved.

3 days from proposal to releasebuilt in six stepsProducts →
Platform

See what a product change reaches

Before you submit a product change you can see how many open accounts it changes, and forecast one of them under the new rules beside the rules in force today, with nothing saved while you look.

3 days from proposal to releasebuilt in four stepsWhat a product change reaches →
Platform

One change set per product

A product's edits to its collection, statement, deposit and collateral rules are approved together and apply all or nothing, two clerks on different products no longer lock each other out, and New from… copies a product with its rules.

3 days from proposal to releaseProducts →
Platform

Different views of the same account

An account type can carry named views beside Standard, so a collector and a credit analyst open the same loan on the panels their work needs, with a default view per role on each product.

2 days from proposal to releaseAccount views →
16 October 2026
Retail banking

Tills, vaults and suspense books are the system's own

The account types list now says which types are opened by the system itself, a till by Cashier or a suspense book by Suspense, and those are never offered when a clerk opens an account and cannot be sold as a product.

25 hours from proposal to releaseAccount types →
Platform

Move an account to another product

A running account can move to another product of its account type, a staff loan whose borrower has left the bank say, and it keeps its number, balances, schedule and history while the new product's rules apply from the day of the change, with a second person approving where your organisation requires one.

41 hours from proposal to releaseChanging an account's product →
Lending

One provision matrix, shared by every product that carries the risk

A provision matrix is now a named policy under Settings rather than a copy inside each account type, each loan product names the one it follows and two loans on the same account type can sit on different matrices, and a matrix's page lists the products using it before you change its bands.

36 hours from proposal to releaseBad debt provisioning →
15 October 2026
Platform

AI on your own contract, or not at all

Your organisation chooses whether AI is used at all and whether calls go on its own vendor key or the platform's, and customer details are masked before a statement line is sent for matching.

7 days from proposal to releasebuilt in six stepsReconciling a bank account →
Platform

One account type, several products

Personal Loan and Staff Personal Loan can now share an account type and still differ in price lists, posting groups and sale dates, every account is opened on a named product, and opening offers only what that product allows.

24 hours from proposal to releaseProducts →
Platform

Everything about an account type, on one page

The account type page now gathers the rules other parts of the system hold about it, from collections and statements to the posting group that books it, and a dot on each says whether it is set up yet.

24 hours from proposal to releaseProduct rules →
Platform

Agree a different term with one customer

A clerk can amend one account's term, a card's minimum payment say, from a date, a second person approves it, and anything worked out before that date keeps the old value.

35 hours from proposal to releasebuilt in six stepsChanging a product's term →
14 October 2026
Platform

Retire a product without deleting it

Retiring an account type stops anyone opening a new account of that type, and the accounts already on it carry on as before through day-end, statements and closure.

45 hours from proposal to releasebuilt in two stepsProducts →
Platform

No detail left without a place on the form

When a form's steps leave a detail out, it appears on an Other details step just before Review, so a required field can no longer stop a record being saved.

45 hours from proposal to releaseThe Other details step →
11 October 2026
Platform

Uploaded images checked for what they are

A logo uploaded for statements and emails is checked by reading the file itself, so a PDF renamed to logo.png is refused, and the approver sees the image rather than a file name.

23 hours from proposal to releasebuilt in four stepsChanging an entity's logo →
Platform

Help on every settings page

Every settings page and tab now has a guide article, and the help link opens the section you are working in rather than the top of the article.

29 hours from proposal to releasebuilt in nine stepsPayment collection minimums →
Lending

A debit order that pays the instalment

On a lending product that opts in, the customer's repeating debit order pays the instalment instead of a separate collection, any shortfall goes into arrears, and the dialog warns when the order is short or lands after the due date.

Card issuing

Credit cards collected and charged

A credit card is collected from the customer's own bank account under a debit order mandate, for the minimum, the statement balance or a fixed amount, and is charged its monthly service fee plus VAT on each statement day.

33 hours from proposal to releasebuilt in seven stepsCredit cards →
Platform

Forecasts that ask what if

The Forecast panel can assume every instalment is paid, or the arrears cleared today, or the customer stops paying altogether, and each row an assumption booked carries its name.

2 days from proposal to releasebuilt in five stepsForecasting an account →
Platform

A reference page for every account type

Help has a page for each account type showing what it holds, what each transaction does to each balance and what runs on its own, in your organisation's own labels.

2 days from proposal to releasebuilt in seven stepsReading an account type's reference page →
8 October 2026
Platform

Decades of daily history, one entry a month

When a book is imported, daily interest and revaluations from before the snapshot can come across as one entry a month, every month-end balance matches daily posting to the cent, and each summary row opens on the days it covers.

9 hours from proposal to releasebuilt in five stepsImporting a book →
Platform

Your own AI agent can read the ledger

Your organisation's own agent connects over MCP and reads the same lists a person with the same permissions sees, it cannot post or approve anything, and every call it makes is kept for a checker to review.

36 hours from proposal to releaseThe MCP door →
7 October 2026
Platform

Point your BI tool at the book

Power BI, Tableau, Excel or any SQL tool connects with a read-only login to tables shaped for reporting, and every query reads the book as it stands, with nothing copied overnight to go out of date.

21 hours from proposal to releasebuilt in five stepsReporting tables for BI tools →
Card issuing

Play the merchant in a demonstration

With simulation switched on, a card can be tapped, reversed, refunded and added to a phone as a merchant and cardholder would, and the card's real authorisation checks decide what happens.

2 days from proposal to releasebuilt in three stepsCard processor →
Platform

Limits on how fast anyone can ask

Each person and each connected system has a limit on how fast it can ask for things, so one runaway screen or script cannot slow everyone else down, and a clerk working normally never reaches it.

2 days from proposal to releaseWhen you see "Too many requests →
Payments

Open a payment file

Any payment file opens from the Submissions panel or the Releases list to show its dates and totals, every payment in it, and every payment that came back and why.

24 days from proposal to releasebuilt in six stepsOpening a payment file →
4 October 2026
Card acquiring

Cards: the merchant's rolling reserve

We hold back part of what a merchant is owed in case their customers charge back, chargebacks are paid from it oldest first, and the reserve is reviewed monthly.

32 hours from proposal to releasebuilt in six stepsMerchant reserve →
Card acquiring

Cards: merchant acquiring

The bank signs merchants under dated agreements, takes in the acquirer's daily file, prices each sale interchange++ or blended, holds the proceeds for the agreed days and pays the merchant out.

27 hours from proposal to releaseMerchant agreements →
Card issuing

Prices that read the card

A price can now depend on what it prices, the card's tier or an amount band, with a floor and a cap on a percentage fee, so currency conversion and cross-border ATM fees come off one price list.

30 hours from proposal to releasePrice lists →
Platform

Studio and Countersign, split

Changes to a live record are staged on the server in Studio and approved in Countersign, an open change locks nothing, and a change made on a stale copy is refused at save.

11 days from proposal to releaseChanging a rate →
3 October 2026
Platform

Documents about any record

A document can now be about anything in the system, not only a client, so a till's lodgement slip or a facility memo is produced and filed like a statement.

1 hour from proposal to releasebuilt in three stepsTemplates for email and SMS →
Retail banking

Cashier management

A branch's cash sits in a vault, a till per teller and the bag on its way to the bank, each its own account with its own books, and cash moves between them on the Cashier page.

18 hours from proposal to releasebuilt in four stepsThe cashier →
Card issuingCorporate banking

Cards: spend controls and the corporate card

Limits and rules by merchant category, country and channel, eight of them sharing one decline path, and a corporate card whose spend rolls up to the company that holds it.

23 hours from proposal to releasebuilt in five stepsCard spend controls →
Card issuing

Cards: disputes and chargebacks

A disputed purchase runs through the scheme's stages under its reason code, with the deadlines watched at day end and the cardholder credited back to the date of the purchase.

28 hours from proposal to releasebuilt in six stepsCard disputes →
Card issuing

Cards: renewal, replacement and fees

Cards renew themselves at day end before they expire, a lost or stolen card is reissued with a new number, and card fees are charged or waived from the price list.

20 hours from proposal to releasebuilt in three stepsCards →
Card issuing

Cards: the credit card

A revolving credit card on the retail template, with its statement cycle, payment allocation, the interest-free period and cash advances.

18 hours from proposal to releasebuilt in five stepsCredit cards →
Retail banking

Cards: the current account and overdraft

An everyday account with an arranged overdraft, which a debit card spends against, with interest on what's overdrawn accrued daily.

13 hours from proposal to releasebuilt in six stepsCurrent accounts and overdrafts →
Card issuing

Cards: authorising a card purchase

Every card purchase is approved or declined in the moment against the available balance, and the money is held until the purchase clears or the hold expires.

14 hours from proposal to releasebuilt in six stepsCard hold expiry →
2 October 2026
Platform

Document signing

A clerk sends a saved document for signature, the signers are invited by email, and the signed PDF and its certificate are filed on the record, with a page showing every agreement still unsigned.

2 days from proposal to releaseSigning documents electronically →
1 October 2026
Platform

Document production

Documents print to archival PDF from templates, and a bank can upload its own Word templates and have them filled from the same data, so the loan agreement looks like the one legal signed off.

21 hours from proposal to releasebuilt in seven stepsTemplates for email and SMS →
Platform

Email and SMS templates

Every email and SMS renders from the bank's own templates, per language, edited on a visual editor with a test send and published under four eyes.

18 hours from proposal to releasebuilt in seven stepsTemplates for email and SMS →
30 September 2026
Card issuing

Cards: connecting a card processor

A card processor plugs in as configuration, answering authorisations, reversals and token requests inside the scheme's time budget, with a Paymentology adapter and a simulator to test against.

29 hours from proposal to releasebuilt in seven stepsCard processor →
Platform

Letters by post

A letter that must go by post joins a post list, a clerk marks it posted with a tracking number, and a notice that can't be emailed falls back to post.

9 hours from proposal to releaseThe post list →
Platform

WhatsApp

Correspondence goes out on WhatsApp through the bank's own Twilio account, only to clients who opted in, with documents sent as expiring links.

2 hours from proposal to releaseWhatsApp gateways →
Platform

SMS

Text messages go out through the bank's own Twilio account, with numbers checked, segments counted and every failure classified.

18 hours from proposal to releaseSMS gateways →
Platform

Email

Email goes out through the bank's own SendGrid account, with sender rules per kind of message and each sending domain's status on the settings page.

23 hours from proposal to releaseEmail gateways and senders →
29 September 2026
Platform

Correspondence

Every statement, notice and certificate now goes through one correspondence service that picks the channel from the client's preferences and keeps a record of what was sent.

11 hours from proposal to releaseCorrespondence sent to a client →
28 September 2026
Platform

The Back Office hub

One page for the desks a back-office clerk works every day, and ten fewer links on the rail.

1 hour from proposal to releaseThe Back Office hub →
Platform

Staff profiles

Colleagues have a photo and a profile, so you can see who approved what and who to ask.

6 hours from proposal to releasebuilt in five stepsYour profile →
27 September 2026
Platform

Change it where you see it

A field on an account is changed from the pencil beside it, and the actions sit on the tab they belong to, so the Actions menu in the header has gone.

11 hours from proposal to releasebuilt in eight stepsChanging a value →
26 September 2026
23 September 2026
Payments

Bacs and Faster Payments files

UK payments go out as Bacs Standard 18 files and as Faster Payments, and when Bacs sends back an unpaid advice, each item is matched to the collection it names and its reason code read.

27 hours from proposal to releasebuilt in five stepsReturn files →
Payments

NACHA ACH files

US ACH payment files written to the NACHA layout, with the returns read back and matched to what we sent.

27 hours from proposal to releasebuilt in four stepsScheme participants →
Payments

SEPA files

SEPA credit transfers and direct debits written to the published pain.001 and pain.008 schemas, with the returns read back to the payment that went out.

18 hours from proposal to releasebuilt in four stepsReturn files →
16 September 2026
Platform

Exchange rates from your provider's file

End of day reads the rate file your provider sent and sets the day's rates from it, anything posted at the morning's provisional rate is restated to the final one, and if no file comes yesterday's rate carries over.

14 hours from proposal to releasebuilt in four stepsWhere today's exchange rates come from →
Platform

Market data feeds you set up yourself

How to read a bank's market data file is a setting you describe and try out before saving, so a bank changing its format is a change on a screen, and every file that arrived is there to see.

9 hours from proposal to releaseMarket data feeds →
14 September 2026
Platform

Tracing a ledger account

Trace shows what moved a general ledger account over a period, opening balance to closing with a running balance on each row, and several accounts side by side so a posting that hit three of them reads on one line.

17 hours from proposal to releasebuilt in seven stepsTracing a ledger account →
13 September 2026
Platform

A cost centre's own screen

A cost centre now has its own screen, with its ledger balances in the header, its details, and the accounts booked to it.

2 hours from proposal to releasebuilt in four stepsCost centres →
Platform

Every action in one menu

Everything you can do to a customer, a bank entity, an account or a structure sits in one Actions menu, and an action you may not take is greyed out with the reason instead of disappearing.

21 hours from proposal to releasebuilt in nine stepsSuspending or holding a customer →
Platform

Cost centres, kept apart from branches

The cost centre says which books the money lands in, chosen per account and dated, and it is kept apart from the branch that looks after the customer, so you can move a branch without moving a penny.

21 hours from proposal to releaseCost centres →
12 September 2026
Platform

Bringing your book across

Your existing accounts come across in an import you run yourself, seven steps that each show what is still to do, and you post the books when the result looks right.

21 hours from proposal to releasebuilt in eleven stepsImporting a book →
11 September 2026
Payments

Scheme participants

The identity a clearing scheme knows you by, a user code in South Africa or a Service User Number in the UK, is recorded once, and every payment file goes out under it and every return file comes back to it.

8 hours from proposal to releasebuilt in six stepsScheme participants →
9 September 2026
Payments

A payment file takes two people

A payment file is built, recorded exactly as built and then waits until one person releases it and a second approves, and where no approval rule is set the release is refused instead of going out on one pair of eyes.

18 hours from proposal to releasebuilt in four stepsReleasing a payment file →
Payments

Returns that find their payment

Every payment goes out carrying a trace number the scheme quotes back, so a return file is read line by line, each matched return reverses the collection it names, and no line goes unaccounted for.

29 hours from proposal to releaseReturn files →
Platform

Numbering schemes

Account, customer and entity numbers come from schemes you set up yourself, as many as you like, and the screen shows the next number a change will issue before you save it.

24 hours from proposal to releaseHow things are numbered →
Platform

Branches, regions and divisions

Below each book sits a tree of your own shape, accounts are serviced at a branch and moved between branches on a date, and a statement carries the servicing branch's address.

4 days from proposal to releaseOrganisational units →
8 September 2026
Platform

Settings pages for every list of types

Collateral, customer, branch, bank entity, role, relationship and security types each have a settings page where you add a type, rename it, retire it and choose what it captures, staged and then published.

47 hours from proposal to releasebuilt in six stepsCollateral types →
3 September 2026
Platform

Suspense, managed

Money nobody can place is parked in suspense as a case with an owner and an age counted from the day it reached the bank, it leaves by allocation, refund, write-off or transfer, and it cannot leave without arriving somewhere.

37 hours from proposal to releaseHanding out suspense cases →
1 September 2026
Corporate banking

Client administrators

A corporate client appoints its own administrators, each user reaches only the accounts their entitlement allows, and a client left with nobody to administer it can be rescued by the bank under its own four-eyes.

25 hours from proposal to releaseCorporate cards →
Platform

A new account page

The account page was redesigned, and notes, files and alerts sit on three tabs on an account and a customer, with an alert showing itself to everyone who opens the record.

26 days from proposal to releaseNotes, files and alerts →
31 August 2026
Platform

Transaction and position types in Settings

Transaction types and position types are kept in Settings beside account types, and removing one that something still uses is refused with the name of what uses it.

10 hours from proposal to releasebuilt in five stepsPosition types →
28 August 2026
Platform

Registrations for your own entities

Your own banking entities hold their registrations and licences on the same Identifications panel a customer's passport sits on.

18 hours from proposal to releasebuilt in seven stepsIdentifications →
Platform

Price types you add yourself

A new kind of charge is added on the Price types screen without waiting for a release, and every price list and account type picks it from there.

11 hours from proposal to releasebuilt in six stepsPrice types →
26 August 2026
Platform

Switch a feature off and it is gone

Switching a feature off removes it from every screen it appears on, its pages, settings, tabs, columns and menu entries, and nobody can reach it by typing its address.

10 hours from proposal to releasebuilt in nine stepsSwitching features on and off →
25 August 2026
Platform

A product guide built into the screens

Help opens a guide written for the people using the system, and links on the screens open the article for the page you are on.

14 hours from proposal to releasebuilt in five stepsChanging an entity's logo →
Platform

Former names, found or kept private

Search can find a customer by a former name, such as a married surname or a company's old name, and a switch turns that off where a former name is private, while duplicate checks still use it.

16 hours from proposal to releasebuilt in six stepsFormer names in counterparty search →
21 August 2026
Platform

A readable event history

A record's Events panel lists what happened one act per row, with who did it and who countersigned it, and each act opens to show every change underneath.

39 hours from proposal to releasebuilt in eight stepsReading a record's events →
20 August 2026
Platform

One positions panel

Balances roll up into groups you name, capital and arrears are worked out from those groups, and one positions panel shows them the same way on every screen.

16 hours from proposal to releasebuilt in 7 stepsPosition types →
Platform

Identifications

A customer's passport, identity card or company registration is kept with its issuer and dates, and one that was replaced or withdrawn stays on file, struck through.

25 hours from proposal to releasebuilt in nine stepsIdentifications →

The list is generated from the engine's release notes every time the site is built, the unreleased ones included, so it can't run ahead of what has actually been built.