Uniksystem releases 7 «Touring»: building on the platform now comes with AI assistance

The Portuguese technology firm’s Low-Code BPM platform now embeds AI-assisted development. What changes is how long it takes to put a process into production, not the feature list, in a year when three regulatory obligations land on the same document trail.

Lisbon, 9 September 2026 — Uniksystem has announced Release 7 «Touring» of its Low-Code BPM/AI platform, succeeding R6 «Trinity». The release embeds artificial intelligence assistance into the development cycle itself.

The problem it addresses is familiar to anyone who has already bought low-code, and it rarely appears in the brochures. For years the promise was building processes without depending on IT. It works — until the hard case. When the logic gets complex, when an integration sits in the middle, when the business rule has exceptions, the work goes back to whoever can write code. That is where projects stall: not for want of a platform, but for want of time from the people who know it.

That is the part 7 changes. With AI assistance in the development cycle, the hard case no longer requires a queue. The benefit is not writing less code; it is the process going live in the quarter it was approved, rather than the one after.

For decision-makers this translates into three concrete outcomes: 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 adding it to a backlog. The last one usually matters most, because it is the difference between a platform that serves the business and one that slows it down.

Three obligations, one document trail

The release arrives in a year when European organisations face three requirements converging on the same place: 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 demands is the ability to state, with evidence, who saw and changed what. A security purchase does not answer the question.

The EU Pay Transparency Directive (2023/970) requires the first report in June 2027 — built on 2026 data. The action it demands is this year: information has to be classified on the way in, because reconstructing it in 2027 means auditing a full year of records that were never structured for the question.

And ViDA, the VAT in the Digital Age package — Directive (EU) 2025/516 and Regulations 2025/517 and 2025/518, adopted on 11 March 2025 — sets digital reporting under EN 16931 for 1 July 2030 and alignment of all national systems for 1 January 2035. National mandates are already falling in line: France’s obligation took effect on 2 September 2026, and Slovakia is preparing for 2027.

None of the three is solved by a new application. They are solved by auditable workflow that leaves a trail: who approved, when, on what basis, and where the document is.

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.

What is at stake before the year closes

Part of this calendar is a management matter rather than a compliance one, and it decides what is possible in 2027.

Payroll and ERP systems change at the boundary of the financial year. On 1 January new tables, new thresholds and new opening balances come into force. A migration involving historical data, mapping of pay elements and parallel testing needs a few months. Organisations that want to enter 2027 with the trail in order have to decide this quarter — and those that do not will keep what they have for another twelve months, including the year of data the Pay Transparency report will use.

That is why Uniksystem is presenting 7 as a calendar decision rather than a technical novelty.

«Low-code was sold for years as the way to build without depending on IT. What got left out was who writes the logic when the case is hard. That is the part 7 changes — and anyone who has to switch systems to enter 2027 compliant has three months, not a year.»

Jorge Gamito Pereira, CEO, Uniksystem

One caveat: three months may not be enough. In those cases what gets decided now is the January 2028 go-live. What makes no sense is reaching January without a decision and finding out in February.

Decision-makers have two questions to ask this week, and neither is about software: how many people in the organisation know, today, where every payroll record and every supplier invoice sits — and what happens to the month-end close when those people are on holiday. If the answers are uncomfortable, the problem already exists; the year boundary is merely the date it becomes visible.

Release 7 «Touring» is available from 9 September 2026. Details on demonstrations and the upgrade path are available from Uniksystem.

About Uniksystem

Uniksystem is a Portuguese company specialising in low-code BPM platforms and AI-powered automation. With over 15 years of activity, it serves organisations including Banco de Portugal, Edenred, Equifax, ANEPC and IHG Hotels, managing over 7,000 employees on the UnikPeople platform and processing EUR 8 million in monthly payroll. More at www.uniksystem.com.