Technical Guide

Understanding and Applying GAEB

GAEB is the standard for data exchange in construction tenders in Germany. This guide explains the formats, shows common problems, and provides practical tips for processing.

What is GAEB?

GAEB stands for 'Gemeinsamer Ausschuss Elektronik im Bauwesen' (Joint Committee for Electronics in Construction). It's a standardized data exchange format for bills of quantities and proposals in construction. The standard enables electronic exchange of tender, offer, and billing data between clients, planners, and contractors. For over 30 years, GAEB has been the de facto standard for construction procurement in Germany.

Standardized Data Exchange

Unified format for bills of quantities, offers, and invoices.

Vendor Independent

Compatibility between different AVA software solutions.

Legal Certainty

Recognized standard in public procurement and with private clients.

GAEB Formats Overview

GAEB distinguishes different exchange phases, identified by format numbers. Each format has a specific purpose in the procurement and execution process.

X81 – Bill of Quantities (BoQ)

Contains the bill of quantities without prices – the BoQ handover with line items, quantities, and descriptions.

X82 – Cost Quotation

A priced BoQ used before the formal bidding phase – not to be confused with the bid submission (X84).

X83 – Bid Request

The unpriced BoQ the contracting authority issues to bidders – the basis for your bid.

X84 – Bid Submission

Your priced response to the authority. Contains unit prices and totals for each line item.

X85 – Side Offer

Alternative proposals that can be submitted in addition to the main bid – where the tender documents permit them.

X86 – Contract Award

Documents the commissioning after the award decision – based on the winning bid (X84).

Structure of a GAEB File

GAEB files since version GAEB XML 3.x are based on the XML format. The structure is hierarchical: header data contains project information, followed by service areas (BoQCtgy) with individual line items (LVItem). Each item has a reference number, quantity with unit, and service description.

GAEBInfo

Header section with file metadata, version, and creation information.

BoQ (Bill of Quantities)

The actual bill of quantities with all positions and structural information.

LVItem (Line Item)

Individual item with quantity (Qty), unit (QU), unit price (UP), and description.

Hierarchical Structure

Titles, lots, and service areas organize the bill of quantities clearly.

Common GAEB Processing Problems

Practice shows typical stumbling blocks when working with GAEB files. Many of these problems can be avoided through validation tools and careful checking.

Encoding Errors

GAEB requires UTF-8 encoding. Wrong character sets lead to unreadable umlauts and special characters.

Missing Required Fields

Invalid or missing mandatory information can lead to bid exclusion.

Version Incompatibilities

Differences between GAEB DA81 (old) and GAEB XML 3.2 (current) can cause problems.

Rounding Differences

Discrepancies in totals due to different rounding rules in software.

Software for GAEB Processing

Various software solutions are available for working with GAEB files – from comprehensive AVA programs for large construction companies to lightweight tools for occasional users. Support for relevant GAEB versions for import and export is important.

Full AVA Software

Programs like ORCA, California, RIB iTWO for comprehensive tendering, awarding, and billing.

GAEB Converters

Specialized tools for converting between GAEB versions and other formats.

Validation Tools

Programs for checking GAEB files for errors and completeness.

AI-Powered Solutions

Modern tools with automatic analysis and intelligent support for proposal processing.

GAEB in Practice: Best Practices

Successful GAEB processing requires established processes and regular quality checks. These best practices help avoid errors and work efficiently.

Validate Files Before Processing

Always check incoming GAEB files for errors and completeness.

Keep Software Updated

Regular updates ensure compatibility with current GAEB versions.

Test Export Before Submission

Export your own offers before submission and check in different software.

Read Item Texts Carefully

Fully understand service descriptions – also recognize implicit requirements.

Frequently Asked Questions

What's the difference between GAEB DA81 and GAEB XML?

GAEB DA81 is the older ASCII format, while GAEB XML 3.x is the modern XML-based format. GAEB XML offers more structure, better validation capabilities, and is the current standard. Most modern software solutions support both formats.

Which GAEB format do I need for my offer?

For bid submission, you use the X84 format. You receive the bid request as an X83 file (or the bill of quantities as an X81) from the contracting authority, add your prices, and return the result as an X84 file.

Can I open GAEB files without special software?

GAEB XML files can be opened in any text editor since it's XML. However, AVA software is recommended for structured viewing and editing, which displays the data clearly and performs calculations automatically.

What happens if my GAEB file contains errors?

Faulty GAEB files can cause various problems depending on error severity: from display errors to incorrect calculations to complete bid exclusion. Therefore, validation before submission is strongly recommended.

Simplify GAEB Processing

Learn how BlackSwanAI supports you in efficiently processing GAEB tenders.

Request a demo
GAEB Guide: Understanding the German Construction Standard | BlackSwanAI