Low-code was sold for years on a line that sounds good and is half the truth: build your processes without depending on IT.
Half true, because it genuinely works — for the form, for the two-tier approval, for the flow you can draw in a morning. And it stops working exactly where the business gets interesting and complex. Closing that gap is what AI-assisted low-code development is for.
When the logic has exceptions. When there is an integration with another system in the middle. When the rule depends on a table that changes in January. At that point the work goes back to whoever can write code, and that is where projects stall — not for want of a platform, but for want of time from the people who know it. Anyone who has bought low-code recognises the backlog that never moves. They are always there.
Release 7 «Touring» of the Uniksystem platform, succeeding R6 «Trinity», goes after those challenges: it brings AI-assisted low-code development inside the cycle itself.
AI-assisted low-code development: what actually changes
Describing this as developer productivity is a mistake. Nobody buys a platform to write fewer lines.
What changes is the timeline. A process approved in September that used to go live in February now goes live in October. And when the timeline changes, the decision changes: it becomes worth automating things that never justified a project before — the middling process, the one that occupies three people half a day a week and never reached the top of the list because something more urgent always did.
For decision-makers the gain takes three shapes. A process in production in weeks rather than months. Less dependence on scarce resources, internal or supplier-side. And the ability to change a rule when the business changes, instead of queueing it.
The third one matters most, and gets discussed least. A platform where changing a rule costs three weeks of waiting is not an agility platform — it is a new legacy system.
Three obligations, and they all land in the same place
The release arrives in an unusual year for European organisations, because three requirements are converging on one point: the path a document and an approval take.
NIS2, transposed in Portugal as the Legal Regime for Cybersecurity and in force since April 2026, requires documented risk management, incident notification within 24 hours, and holds management bodies personally accountable. What it asks for in practice is the ability to state, with evidence, who saw and changed what. A security purchase does not answer the question. Where data lives in shared files, that question has no answer.
The EU Pay Transparency Directive requires the first report in June 2027, and builds it on 2026 data — the data being generated now, in every payroll run. The action it demands is this year: information has to be classified on the way in. Organisations that only sort this out in 2027 will be building the report on twelve months of records that were never structured for the question they are about to be asked.
And ViDA, the VAT in the Digital Age package. Directive (EU) 2025/516 and Regulations 2025/517 and 2025/518 were adopted on 11 March 2025 and in force since 14 April; digital reporting under EN 16931 applies from 1 July 2030, and alignment of all national systems from 1 January 2035. What ViDA already did was let member states mandate e-invoicing without a derogation, which is why national deadlines are falling now rather than later — France’s obligation took effect on 2 September 2026, and Slovakia is preparing for 2027.
None of the three is solved by an application. They are solved by auditable workflow that leaves a trail: who approved, when, on what basis, and where the document sits. That is what a BPM engine does — which is why three regulatory obligations belong in a piece about a platform release.
What stalls any of these changes is rarely the law or the technology: it is the sheer size of what has to be rebuilt, because the supplier invoice circuit and the mailbox through which work arrives are, in any company, the two oldest and least documented parts of the process, and touching them is usually a multi-year project. That is what the platform’s ready-built vertical solutions are for, InvoiceRouter for qualifying and approving the supplier invoice and InboxRouter for turning the mailbox into a work queue with an owner and a deadline, and that is the difference between a delivery cycle measured in years and one measured in weeks.
For the finance director the challenge is arithmetic. Qualifying a supplier invoice takes four to six minutes for a known supplier and around fifteen for a new one, and with ten thousand invoices a year that is roughly 830 hours: half a full-time post spent deciding cost centre, accounting account and tax code. And that is not the larger cost. A wrong cost centre is corrected in the next report; a wrong tax code is a VAT problem that surfaces months later, in a reconciliation or an audit.
For the operations director the criterion is measured in days. Work arriving by email has no owner and no deadline until somebody assigns it by hand, which is why the month-end close depends on two or three people remembering what is outstanding. When one of them is away, more than time is lost: what goes with them is the ability to know the state of each process.
And for whoever owns IT there is a fourth problem, and it is neither compliance nor running cost: end-of-life software. An ageing application nobody wants to touch, whose author has left and whose technology is out of support, can now be migrated with AI assistance in weeks rather than years, and our own public-sector accounting ERP under SNC-AP was built that way, which means we can say it with a concrete case rather than as a promise.
Part of this is about us rather than about the product, and it is worth disclosing because it explains the rest: our DevOps cycle runs on Master → Deploy Agents, with AI, and that is what lets us ship more than ten releases a day per application. What normally throttles that cadence is not development, it is what comes after: systems administration, infrastructure, maintenance windows and the request waiting for the right person. With agents carrying the path from master to deployment, that load drops to zero for IT Admin teams, and it is the reason we can promise weeks where the industry counts in quarters.
The part that is calendar, not compliance
There is a fourth date, and this one comes from no legislation. It comes from how these systems work.
Payroll and ERP change at the boundary of the financial year. On 1 January new tax tables, new social security thresholds, new opening balances and a new accounting period come into force. Switching mid-year means running two systems in parallel and explaining to your auditors why they disagree. Almost nobody does it.
Work backwards: a migration with historical data, mapping of pay elements, parallel runs and training the people who will use it needs a few months. It is September. Organisations that want to enter 2027 with the trail in order decide this quarter; those that do not will keep what they have for another twelve months — including the year of data the Pay Transparency report will use.
One caveat: three months may not be enough. In that case what gets decided now is the January 2028 go-live, and it is better to know that in September than in February.
Two questions that are not about software
For anyone who has to decide, two questions separate those who manage it from those who do not, and neither involves choosing technology.
How many people in the organisation know, today, where every payroll record and every supplier invoice sits? If the answer is one or two, and those two overlap on August holidays, the problem already exists — the year boundary is merely the date it becomes visible.
And the second: what happens to the month-end close when those people are away? The usual answer is «it slips». What the answer hides is that the information exists, all of it, and depends on human memory rather than on a system or a process.
Release 7 «Touring» answers neither question. It changes the cost of answering them, which is a different thing — and it reflects the sheer advantage of deciding this quarter over postponing for a year.
Jorge Gamito Pereira
CEO | Uniksystem