Objective vendor comparison

Units-Master vs. CONTHAUS

Modular Austrian ERP with CONTBUCH accounting and CONTWEB portal.

Architecture type: Legacy ERPs (Desktop)Target group: AT PMs & real estate trusteesOfficial website: conthaus.at

Executive Summary

CONTHAUS is a modular Austrian ERP suite for property managers and real estate trustees. Its CONTBUCH accounting module and CONTWEB portal deliver solid BAO-compliant bookkeeping and EBICS banking, but there is no visual workflow builder, no AI layer and no auditor portal.

Feature comparison in detail

Feature⚡ Units-MasterCONTHAUS
Process TicketingBuilt-inPartial
Visual Workflow EngineBuilt-inNot available
Voice AI (Phone)Built-inNot available
In-App AI ChatBuilt-inNot available
In-App Team ChatBuilt-inPartial
Owner / Tenant PortalIn developmentPartial
Auditor PortalIn developmentNot available
Accounting & ReportsIn developmentBuilt-in
GoBD / BAO ArchivingBuilt-inBuilt-in
Service DirectoryBuilt-inNot available
Banking / SEPA & EBICSNot availableBuilt-in
WEG Voting & AssemblyNot availableNot available
Meter & Heating DBNot availableBuilt-in

Legend

Built-in
Fully part of the vendor's own product, developed and maintained in-house. No extra contract, no data sync, one support line.
In development
Not yet usable, but on the active engineering roadmap with a confirmed release window. Relevant for multi-month rollouts that can plan around it.
External vendor
Delivered by a separate vendor via integration, add-on or sync. Expect additional licence fees, a second support relationship, and data flowing across two systems.
Partial
The feature technically exists, but only at checkbox level: enough to tick the requirement, rarely enough to solve the underlying day-to-day workflow.
Not available
Not part of the product. No integration, no roadmap commitment — the workflow has to happen outside the platform.

Strengths of CONTHAUS

  • Native CONTBUCH accounting with BAO-compliant archiving
  • Native EBICS banking and meter/heating cost database
  • CONTWEB portal for owner and tenant self-service

Weaknesses of CONTHAUS

  • Only basic ticketing via CONTMANAGER task notes
  • No AI layer — neither voice agent nor in-app copilot
  • No auditor portal, no service directory, no WEG voting engine

Operational differences

  • 01

    Process-driven workflows instead of static inboxes

    Every ticket in Units-Master triggers an executable, multi-step Standard Operating Procedure (SOP) — no manual tag assignment, no ping-pong between staff members.

  • 02

    Native voice AI agent, not a third-party tool

    Inbound phone calls are handled entirely by the native voice AI agent: emergency dispatch, intake and ticket creation — autonomously, 24/7.

  • 03

    In-app copilot Werner AI: contextual and action-capable

    Werner AI is not a generic chatbot. It knows property history, summarises units, prepares accounting data and executes actions directly.

  • 04

    Embedded service directory, wired into workflows

    The /directory connects local tradespeople, plumbers, HVAC technicians and auditors directly to the automated ticket workflows — no media breaks, no manual coordination.

When each fits

Choose Units-Master when…

  • You want executable SOP-driven workflows instead of task lists
  • AI-assisted telephony and native service directory are strategic priorities

Choose CONTHAUS when…

  • You need a modular Austrian ERP with proven BAO accounting
  • Your team already runs the CONTHAUS module stack (CONTBUCH, CONTMANAGER, CONTWEB)

See Units-Master in action

30-minute demo, live on your portfolio.

Last reviewed and updated: 15 August 2026

All information without guarantee. Feature scope may change through product updates from the vendors listed.