Häufig gestellte Fragen
What must an ERP for the construction industry cover that a standard ERP does not?
Construction companies work on a project basis with long durations, many subcontractors and a high share of change orders, which is why industry-neutral systems are often not sufficient. A construction ERP must additionally cover project costing based on bills of quantities, GAEB-compliant data exchange for tendering and contract awarding, site measurement (Aufmass) as well as progress and final invoicing in accordance with VOB. Change order management with version control, construction-capable payroll (Baulohn) with a SOKA-BAU connection and equipment management with scheduling are also part of the typical scope of functions. These construction specifics are the main reason why many firms use specialised industry solutions instead of generic ERP systems.
What is the GAEB interface and why is it important for construction ERP?
GAEB stands for the Gemeinsamer Ausschuss Elektronik im Bauwesen (Joint Committee for Electronics in Construction), which has been a main committee of the German Committee for Construction Contract Procedures (Deutscher Vergabe- und Vertragsausschuss für Bauleistungen) since 2005 and defines the standard format for the electronic exchange of bills of quantities, bids and invoices. The current standard is GAEB DA XML with phase-dependent file extensions, for example .X81 for the tendered bill of quantities, .X83 for the bid and .X89 for the invoice, which has largely replaced older formats such as GAEB 90. For public contracts, GAEB is practically indispensable, as the federal procurement manual (Vergabehandbuch des Bundes) builds on GAEB standards and GAEB DA XML data exchange is de facto a prerequisite in public construction. A construction ERP with a GAEB interface can import tendered bills of quantities directly, cost them and return the bid in the appropriate format.
How does a construction ERP support change order management under VOB?
In construction, change orders frequently arise from modified or additional services as well as from disrupted construction sequences, for example when the client issues instructions or duties to cooperate are breached. Under VOB/B, a claim for additional remuneration generally requires an instruction from the client and a new price determination based on the original costing, and for additional services the claim must be announced before execution, which is why seamless documentation and verifiable calculation are crucial. A construction ERP supports this by managing change orders with version control, linking them to the original costing and documenting the construction sequence traceably via a site diary and hours reporting. This allows claims to be notified promptly and substantiated to the client in comprehensible change order proposals.
What special rules apply to payroll in construction (Baulohn) and SOKA-BAU?
Payroll in the construction industry is more complex than in other sectors because, in addition to the usual wage components, contributions to the social funds of the construction industry (SOKA-BAU) for the holiday fund, supplementary pension and vocational training are due. Added to this are seasonal rules such as seasonal short-time working compensation (Saison-Kurzarbeitergeld) and the winter employment levy during the bad-weather period from 1 December to 31 March, as well as collectively agreed wage groups under the BRTV. An ERP solution capable of construction payroll therefore needs modules for SOKA-BAU reporting, winter construction settlement as well as construction bonuses and allowances. Important obligations include the timely monthly report to SOKA-BAU, which is why an integrated interface reduces sources of error and duplicate data entry.
Cloud or on-premise - what suits a construction company?
Both operating models are widespread in the construction industry, and the choice depends heavily on company size and the need for customisation. Cloud solutions are gaining importance among smaller and mid-sized firms because mobile site data capture, measurement via app and location-independent access are possible without in-house server infrastructure. On-premise, by contrast, often remains the first choice when highly individual adaptations, deep integrations or special data storage requirements are the priority. A detailed comparison including cost and risk aspects can be found at Cloud vs On-Premise.
What does a construction ERP cost and how long does implementation take?
Realistic total costs for a construction ERP in the mid-market range roughly between 180,000 and 850,000 euros over the first three to five years, depending on user numbers and depth of customising, with solutions featuring a GAEB interface, site measurement and change order management at the upper end. Added to this are annual maintenance fees of an industry-standard 18 to 22 percent of the licence sum for on-premise models, or a cloud subscription that is typically billed per user per month. Implementation usually takes 8 to 18 months for mid-market projects, with larger multi-site initiatives taking considerably longer, and seasonal project peaks in spring and summer can delay the roll-out. Details can be found in our guides ERP costs and ERP implementation checklist.