TechnologyOne

TechnologyOne 2026A and Plus: what Australian councils and universities should test

A practical buyer guide to TechnologyOne 2026A, Plus, Guide, and SaaS+ for Australian councils, universities, government, and asset-intensive teams.

TechnologyOne is no longer only a finance, property, asset, and student-management ERP discussion for Australian public-sector and education buyers. With 2026A, Plus, Guide, and SaaS+, the shortlist question now includes how much conversational AI, managed delivery, and vendor-owned operating support should sit inside the ERP relationship.

That can be useful for councils, universities, government agencies, health and community organisations, and asset-intensive businesses, but it also changes the due-diligence work. Buyers should test the release claims against their own data, permissions, service model, implementation boundary, and long-term commercial exposure before treating the new capability as a simple productivity add-on.

What TechnologyOne says is new in 2026A

• TechnologyOne describes 2026A as a release with AI-enabled enhancements, automation, and deeper insights across the ERP suite.
• The 2026A release page says Plus is introduced in this release and is available across Australia, New Zealand, and the United Kingdom for customers on CiA.
• TechnologyOne describes Plus as an agentic AI interface that can surface insights from enterprise data through natural-language requests and manage work through one interface.
• The same release material names examples such as ECM Natural Language Search, Intelligent Field Defect Capture, an AI-powered Policy Configuration Tool, development-application eligibility checking, supplier invoice scanning, and predictive budgeting.
• TechnologyOne separately describes SaaS+ as an all-inclusive offer where implementation, upgrades, security, and ongoing support are included in one annual fee, with TechnologyOne taking accountability for the solution experience rather than only the software.

Why this matters for Australian public-sector ERP buyers

• Councils and universities often run ERP programmes where finance, rating, assets, property, student services, documents, budgeting, customer portals, and reporting all depend on shared data and consistent process ownership.
• If Plus works as described, the business case may shift from screen-by-screen efficiency to faster search, guided action, field capture, policy interpretation, supplier invoice handling, and management insight.
• The risk is that teams validate a polished conversational interface without checking role permissions, auditability, exception handling, records management, model governance, and how the annual SaaS+ relationship changes future operating choices.
• For Australian buyers, the practical decision is not whether AI sounds modern. It is whether TechnologyOne can prove fit against local service delivery, privacy, cyber, record-keeping, procurement, and support obligations.

Priority 1: prove the CiA and release-readiness path

• TechnologyOne says Plus requires the 26A release and CiA. That makes current estate readiness a first-order question for any customer still planning release timing, migration work, or process clean-up.
• Ask which products, modules, environments, integrations, reports, customisations, and user groups must be ready before Plus can be enabled usefully.
• Do not treat feature-flag enablement as business readiness. The buyer still needs clean roles, tested data access, trained process owners, and agreed boundaries for what users are allowed to ask the system to do.
• If the organisation is moving from legacy arrangements to SaaS+ at the same time, separate the release plan from the operating-model plan so scope, responsibilities, and timing stay clear.

Priority 2: test AI against real council and university workflows

• For councils, useful proof scenarios may include a resident enquiry, a defect photo, an asset work request, a property or rating assessment rule, a document search, a receipting query, or a budget forecast adjustment.
• For universities, useful proof scenarios may include student support enquiries, course or enrolment information, staff workflow queries, document retrieval, budgeting, and controlled hand-off between service teams.
• Each scenario should show source data, user permissions, generated answer or action, human review point, exception path, and audit evidence.
• Ask TechnologyOne or the implementation team to demonstrate what happens when information is incomplete, ambiguous, confidential, outside the user role, or inconsistent across source records.

Priority 3: keep privacy, security, and records controls visible

• TechnologyOne says Plus uses human-in-the-loop principles and is underpinned by ISO 42001:2023 certification for AI management systems. That is useful evidence, but buyers still need their own control design.
• Map which personal information, student information, resident information, employee records, supplier records, and operational documents the AI-enabled workflows can access.
• The Office of the Australian Information Commissioner expects organisations using commercial AI products to consider intended use, personal-information handling, privacy and security risks, testing, human oversight, and accountability.
• The Australian Cyber Security Centre recommends clear security responsibilities across procurement, operation, maintenance, and supplier relationships. Apply that discipline to AI features, integrations, support access, incident handling, and subcontractors.

Priority 4: understand what SaaS+ changes commercially

• TechnologyOne positions SaaS+ as more than a subscription because implementation, upgrades, support, and security are part of the annual arrangement.
• That model can simplify accountability, especially for public-sector and education teams with limited internal ERP capacity, but it should still be compared against the organisation’s procurement, governance, and exit requirements.
• Ask what is included in the annual fee, what is separately charged, how Plus or Guide usage is priced, how scope changes are handled, and what happens when the organisation needs integrations, reporting, data migration, or process changes outside the standard path.
• Review data ownership, transition assistance, service levels, release obligations, security responsibilities, and long-term renewal exposure before treating the model as lower-risk by default.

Priority 5: treat Guide as a service-design decision

• TechnologyOne announced Guide in February 2026 as an AI-powered product for residents and students to access public services and higher-education support through voice or text.
• The ASX release material says Guide is intended to reduce friction in complex council and higher-education systems and put enterprise AI into the hands of communities and students.
• That makes Guide a customer-experience and service-governance decision, not only an ERP feature. The organisation needs to decide which services are suitable, what information can be exposed, how escalation works, and who owns answer quality.
• Before rollout, test accessibility, multilingual needs, vulnerable-user handling, incorrect-answer recovery, privacy notices, consent, record capture, complaint handling, and fallback to human service channels.

Questions to ask before shortlisting TechnologyOne

1. Which current products, modules, environments, integrations, and data sets must be on 26A and CiA before Plus is viable?
2. Which Plus and 2026A use cases are standard, which require configuration, and which depend on future roadmap or separate commercial terms?
3. How are role permissions, data access, human review, logs, and exception queues enforced when users interact through natural language?
4. How does SaaS+ separate included implementation and support from project-specific data migration, integrations, reporting, change management, and optimisation work?
5. If Guide is in scope, what resident or student journeys will be exposed first, and how will privacy, accessibility, service quality, and escalation be governed?

Where projects can go wrong

• Teams assume agentic AI reduces the need for process ownership when it actually increases the need for clear permissions, data quality, and exception design.
• Buyers treat SaaS+ as a simple managed-service label without testing what happens when requirements move outside standard inclusions.
• Councils or universities pilot resident-facing or student-facing AI before service teams agree answer ownership, complaints handling, escalation, and record capture.
• The shortlist focuses on the latest release features but underweights procurement obligations, cyber responsibility, privacy impact, integration support, and exit planning.

What Australian buyers should conclude now

• TechnologyOne 2026A makes AI, SaaS+, and service-experience design part of the ERP evaluation conversation for councils, universities, government, and asset-intensive organisations.
• The strongest first step is a controlled proof workshop: pick three high-value workflows, run them through real permissions and real data boundaries, and document what is standard, what needs configuration, and what remains unproven.
• If TechnologyOne is on the shortlist, compare product fit and SaaS+ accountability beside implementation evidence, commercial boundaries, privacy controls, cyber ownership, and long-term support obligations.

FAQ

• Is TechnologyOne Plus available in Australia? TechnologyOne says Plus is available in its 26A release across Australia, New Zealand, and the United Kingdom for customers on CiA.
• Does Plus require implementation? TechnologyOne says Plus can be enabled by feature flag once licensed, but buyers should still treat roles, data access, controls, and workflow readiness as implementation work.
• What is SaaS+? TechnologyOne describes SaaS+ as an all-inclusive offering where implementation, upgrades, security, and ongoing support are included in one annual fee.
• Is Guide the same as Plus? TechnologyOne describes Guide as a separate AI-powered product that is powered by Plus and aimed at resident and student access to services and support.

Sources used

• TechnologyOne 2026A software-release page for Plus availability, release features, and named AI-enabled enhancements.
• TechnologyOne article "What is Plus and How Does it Work?" for Plus requirements, example use cases, security positioning, and SaaS+ description.
• TechnologyOne ASX release dated 25 February 2026 for Guide, resident and student service positioning, and SaaS+ company context.
• Office of the Australian Information Commissioner guidance on commercially available AI products.
• Australian Cyber Security Centre procurement and outsourcing guidance for supplier responsibility and cyber-risk controls.