ERP Comparison 2026 for SMEs in Austria: weclapp, BMD, Odoo, Business Central and SAP Business One

Transparency note: We at EA Digital Solutions in Graz do not sell licences for any of the vendors compared here and are not a reseller for any of them. We develop interfaces, extensions and custom software around ERP systems. All information comes from the vendors' own websites and from official Austrian bodies, as of 28 October 2026. Prices change, so please check them with the vendor before making a decision.

In short: which ERP suits whom?

None of these systems is "the best". What matters are your processes, your tax adviser, your existing systems (shop, CRM, till) and how much you need to customise.

Comparison table

weclapp

Type and hosting: weclapp is a cloud ERP. According to the FAQ on its pricing page, data is stored "exclusively in Germany" across several data centres, and contracts are governed by German law. Anyone who wants to self-host is referred to the private cloud variant weclappOn.

Austrian fit: weclapp supports the Austrian standard chart of accounts (Einheitskontenrahmen) and offers its own BMD export, which hands posted documents over to the tax adviser on a journal basis for a chosen period. This requires BMD-compliant personal account numbers that must not overlap with general ledger accounts. The help articles on the VAT pre-return refer to ELSTER, i.e. the German procedure. We did not find anything on the vendor's pages about whether a VAT pre-return (UVA) can be submitted directly to FinanzOnline – ask about this before deciding. For e-invoicing, weclapp generates ZUGFeRD in the EN 16931 profile and reads XRechnung; ebInterface is not mentioned. Austrian payroll is not listed as a module on the pricing page.

Prices (according to weclapp.com): ERP Starter €39 per user per month (monthly only, cannot be combined), ERP Dienstleistung (services) €86 or €95, ERP Handel (trade) €163 or €179, each net per user per month. The lower figure applies depending on the billing type (annual or monthly); the page does not clearly assign the figures. For more than 10 licences there is an "Enterprise" package with price on request. Add-ons such as Helpdesk or weclapp POS cost €55 each per user per month; the tax adviser licence is free.

API: API access is included from ERP Dienstleistung upwards (not in the Starter package). There is a REST API with a user-specific API token and webhooks for creating, changing and deleting records.

Strengths: quick start, transparent prices, trade and shop connections in the "Handel" package, BMD export for working with Austrian tax advisers. Limitations: hosting in Germany rather than Austria, strong focus on German procedures (ELSTER, DATEV), no integrated Austrian payroll.

BMD

Type and hosting: BMD is an Austrian software vendor based in Steyr. Its ERP solution runs on-premise or in the BMD Cloud. According to BMD, cloud data is stored in a Telekom Austria data centre in Linz; the cloud and the data centre are ISO 27001 certified.

Austrian fit: This is BMD's core competence. BMD describes itself as the Austrian market leader and cites more than 30,000 customers in the DACH region (vendor figure, not an independent market statistic). The ERP combines accounting, inventory management, time recording, payroll, CRM, DMS and controlling. Payroll offers ELDA submission directly from the program, around 900 collective agreements via an HGKV interface, and data exchange with the tax office, ÖGK, BUAK and banks. The Kassa till is described as RKSV-compliant. For e-invoices, BMD creates and reads ebInterface and XRechnung, and processes incoming ZUGFeRD (BMD article of 22 October 2024; check the current status with the vendor).

Prices: Price on request. BMD does not publish ERP prices; quotes are requested via an enquiry form.

API: BMD's documentation describes a BMD web service as a separate IIS web application, and the Hardening Guide mentions a REST interface of the BMD web applications. We did not find a public API reference for developers. For projects this means: agree on interfaces early with BMD or your BMD account manager.

Strengths: Austrian legal and tax environment from a single source, payroll with collective agreements, hosting in Austria, joint work with the tax adviser. Limitations: no published prices, interface documentation not public, web shop connections often run via partner solutions.

Odoo

Type and hosting: Odoo is available as SaaS (Odoo Online), on the Odoo.sh platform or self-hosted. The Community Edition is licensed under LGPLv3 and is open source; the Enterprise Edition has its own licence. According to the privacy policy, databases for the Europe region are located in France and Belgium, with backups in France, the Netherlands and Sweden. For existing customers, Odoo says there is still an additional backup in Canada until the migration is complete (planned for Q4 2026); new customers from Odoo 19 onwards have EU-only backups.

Austrian fit: The Austrian localisation includes the chart of accounts (l10n_at), balance sheet under § 224 UGB and P&L under § 231 UGB (l10n_at_reports), a SAF-T export (l10n_at_saft) and a POS module for the RKSV with signed receipts via fiskaly, DEP7 export and monthly and annual receipts (l10n_at_pos). For e-invoicing, Odoo itself is a PEPPOL access point; Austria is enabled for PEPPOL registration, with formats including BIS Billing 3.0. ebInterface and UVA submission to FinanzOnline are not mentioned on the Austria page of the documentation. An Austrian payroll localisation is not listed in the Odoo documentation.

Prices (according to odoo.com): "One App Free" €0 (one app, unlimited users). "Standard" €19.90 per user per month billed annually, €24.90 billed monthly. "Custom" €35.90 or €44.90. According to the footnote, these prices are discounted for 12 months and for the users ordered initially; the struck-through list prices are €31.10 (Standard) and €56.90 (Custom). Odoo.sh hosting and implementation are not included.

API: Important for integrations: the external API (access to Odoo from outside) is only available in the "Custom" plan, not in the "Standard" plan. Since Odoo 19, the External JSON-2 API with an API key in the bearer header is the intended route; XML-RPC and JSON-RPC are deprecated. Custom modules are developed in Python.

Strengths: modular, large choice of apps, open-source base, free choice of hosting, highly extensible. Limitations: external API only in the more expensive plan, no Austrian payroll as standard, version upgrades need to be planned for custom developments.

Microsoft Dynamics 365 Business Central

Type and hosting: Business Central is primarily a cloud ERP. Since 1 April 2025, new customers can only license on-premise on a subscription basis. In the cloud, the environment's localisation determines the Azure location; according to Microsoft, environments with an EU localisation remain within the EU Data Boundary. Microsoft does not explicitly say whether Austrian environments are located in the Azure region "Austria East" (Vienna).

Austrian fit: Microsoft offers a dedicated Austrian version including a VAT Statement, VAT reporting, delivery reminders and Intrastat. SAF-T reporting for Austria is under consideration for "2026 release wave 2". Austrian payroll is not included in this list; clarify with your partner how payroll will be connected. E-invoices run via the E-Documents module with PEPPOL BIS 3.0; ebInterface is not mentioned in the documentation.

Prices (according to microsoft.com/de-at, excl. VAT, annual commitment): Essentials €69.30 per user per month, Premium €95.30, Team Members €6.90. Microsoft points out that the prices are for information only and that purchases usually go through partners.

API: REST API v2.0 (enabled by default for Online), OpenAPI specification, custom APIs and extensions in the AL language. Standard APIs cannot be extended with additional fields; for that you build a custom API.

Strengths: tight integration with Microsoft 365, Power BI and Copilot; large partner and app ecosystem; well-documented APIs. Limitations: no Austrian payroll as standard, implementation usually via a partner, restricted licensing model for on-premise.

SAP Business One

Type and hosting: According to SAP, SAP Business One is aimed at small and medium-sized businesses with no minimum size, especially in wholesale, light manufacturing, retail and services. SAP cites more than 85,000 customers (vendor figure). It can run in the cloud or on-premise, technically on Microsoft SQL Server or SAP HANA. Where the data is stored in the cloud depends on the operator.

Austrian fit: SAP lists Austria as a localised version for HANA and SQL Server (demo databases, as of August 2026). We did not find details on UVA, ebInterface, RKSV or payroll on SAP's pages; clarify these points with your SAP partner.

Prices: Price on request. SAP does not publish prices on the product page and refers to quotes and partners.

API: The Service Layer exposes Business One objects over the web; there is also an SDK with DI API and UI API.

Strengths: proven in trade and light manufacturing, large partner network, clear growth path within the SAP environment. Limitations: no public prices, Austrian specifics must be clarified with the partner, implementation usually more extensive than with pure SaaS solutions.

What Austrian SMEs should look out for

1. Interface to the tax adviser (BMD): Ask your tax adviser first which system they work with and in which format they want to receive data. weclapp has a built-in BMD export; with BMD itself there is no handover at all. With other systems you should have the BMD handover tested in practice before you sign.

2. E-invoicing: Since 1 January 2014, contractual partners of the federal government have had to submit invoices in structured electronic form; federal agencies no longer accept paper invoices. Submission is via the Business Service Portal (USP) or PEPPOL (legal basis: § 5 IKTKonG). There is currently no obligation for federal states and municipalities. The Austrian XML format is ebInterface. Check whether your ERP supports PEPPOL or ebInterface if you have public-sector clients. We did not find a general B2B e-invoicing obligation in Austria on the official pages; keep an eye on the EU plans for digital VAT (ViDA).

3. Cash register obligation (RKSV): It applies when a business has annual turnover of more than €15,000 and cash sales of more than €7,500; both thresholds must be exceeded, and card payments count as cash sales. Every till needs a security device. New since 1 October 2026: receipts may also be issued electronically, but customers can still ask for a paper receipt. If you sell on site, your till solution must be RKSV-compliant and work together with the ERP.

4. Payroll: In this comparison, only BMD includes Austrian payroll with collective agreements and ELDA. With the other systems, payroll usually runs separately, for example at the tax adviser or in a dedicated payroll program. Clarify how payroll postings get back into the ERP.

5. Hosting and GDPR: The GDPR does not require hosting in Austria. However, the rules in Chapter V apply to transfers to third countries (adequacy decision or safeguards such as standard contractual clauses). The Austrian Data Protection Authority has ruled US transfers unlawful in several cases. So pay attention to the data centre location, backup location and sub-processors. BMD hosts in Linz, weclapp in Germany, Odoo in France and Belgium, Business Central within the EU Data Boundary.

6. Interfaces to shop, CRM and till: An ERP rarely stands alone. Check whether your web shop (e.g. Shopify, WooCommerce, Shopware), your CRM and your till can be connected via a documented API, and whether API access is included in the chosen plan. With weclapp it is missing in the Starter package, with Odoo in the Standard plan.

Standard ERP, extend it, or build your own?

In our projects we see three routes:

• Use the standard: If your processes match the industry standard, a standard ERP is almost always the cheapest and safest choice. Adapt your processes to the software rather than the other way round.
• Extend the standard: If most things fit and the rest is your competitive advantage, we extend the ERP via its API: for example a shop connection, a customer portal, automatic data handover to the tax adviser, or a custom module in Odoo or an AL extension in Business Central.
• Develop your own ERP: If your core processes are very specific and standard systems only work with a lot of workarounds, a custom solution can make sense. It usually complements accounting and payroll from a standard system such as BMD rather than replacing them.

We are happy to work out which route suits you in a no-obligation conversation, independently of any vendor. You can find out more on our ERP development page. We work from Graz and remotely.

Sources (accessed 28 October 2026)

Vendors

• weclapp pricing
• weclapp standard charts of accounts
• weclapp BMD export
• weclapp VAT pre-return (ELSTER)
• weclapp ZUGFeRD
• weclapp API
• weclapp webhooks
• BMD home page
• BMD ERP
• BMD Cloud
• BMD payroll
• BMD Kassa
• BMD e-invoicing (22 October 2024)
• BMD Web / web service
• BMD Hardening Guide
• Odoo pricing
• Odoo Austrian localisation (19.0)
• Odoo e-invoicing/PEPPOL
• Odoo payroll localisations
• Odoo External JSON-2 API
• Odoo licences
• Odoo privacy policy (hosting locations)
• Business Central pricing
• Business Central Austria
• Business Central data residency/sovereignty
• Business Central e-invoicing FAQ
• Business Central API v2.0
• Business Central on-premise licensing (announcement)
• SAP Business One
• SAP Business One help (Service Layer, SDK)
• SAP Business One localised demo databases (August 2026)

Official Austrian bodies

• USP – e-invoicing to public administration
• USP – cash register obligation
• Data Protection Authority – international data transfers