If your sales team receives tender documents from architects, general contractors, or public procurement offices in Germany, Austria, or Switzerland, a significant portion of them arrive as GAEB files. The .x83 file in the inbox is a bidding order: a structured request for your prices against a defined specification, formatted according to the GAEB DA XML standard that governs electronic construction tendering across the DACH region.
For suppliers in building materials distribution, technical installation, or construction-related manufacturing, handling these files efficiently is a direct competitive variable. The contractor who submitted the GAEB has a tender deadline. They sent it to multiple suppliers simultaneously. Your response time and the completeness of your pricing determine whether you are on the shortlist.
The standard
GAEB stands for Gemeinsamer Ausschuss Elektronik im Bauwesen, the joint committee that developed and maintains the standard. The format has existed since the 1980s and has been continually updated, with the current XML-based standard now used in virtually all building projects in Germany. Most governmental contracts require its use.
The GAEB DA XML standard uses exchange phases marked with file extension codes. The phases most relevant for suppliers are:
| Extension | Phase | Direction | What it contains |
|---|---|---|---|
| .X81 | Bill of quantities transfer | Architect or engineer to project owner | BoQ data prepared by the design team, passed to the owner for procurement |
| .X83 Incoming | Bidding order | Project owner to supplier | BoQ requesting prices from the supplier. This is what arrives in your inbox. |
| .X84 Outgoing | Bidding offer | Supplier to project owner | The supplier's priced response, with unit rates filled in for each position. This is what you send back. |
| .D83 | Bidding order (legacy) | Project owner to supplier | GAEB 90 format equivalent of X83. Still in use in older systems. |
| .D84 | Bidding offer (legacy) | Supplier to project owner | GAEB 90 format equivalent of X84. |
Regardless of the format variant, a GAEB file replicates the structure of a classic paper specification. It contains tender texts, quantity specifications, and quantity units organized according to the GAEB classification structure. For a supplier, the incoming file is almost always an X83 or D83. The expected response is an X84 or D84 with unit rates filled in for each position.
Why it matters
The OZ position numbers in a GAEB file are the reference system for the entire tender. Your priced X84 must match the same position numbers from the X83, line by line, for the project owner to compare your response against competitors.
The structure
A GAEB file is not a flat list of line items. It is a hierarchical document with a defined structure that carries meaning at every level.
Element
LOS and LV structure
Leistungsbereich / Leistungsverzeichnis
Element
OZ position numbers
Ordnungszahlen
Element
Long text and short text
Langtext / Kurztext
Element
Quantity and unit
Menge / Einheit
Element
Provisional and alternative positions
Bedarfs- / Alternativpositionen
Common processing error
Provisional and alternative positions are a frequent source of manual processing errors when teams process GAEB files without automation. Pricing them incorrectly or omitting them creates discrepancies in the returned X84 that the project owner has to reconcile manually.Where tools fall short
A document extraction tool that has not been built for GAEB will attempt to parse the file as if it were a structured document: extracting text strings and looking for patterns. It may extract some content correctly. It will fail in predictable ways.
Failure point
The hierarchy is lost
Failure point
Position type handling breaks
Failure point
Long text is ignored or treated as prose
Failure point
No valid X84 output
The key distinction
Generic extraction tools stop at reading. A GAEB-aware system writes prices back into the structure and exports a valid X84 response file, ready for review and submission.
What good looks like
A system built for construction supply tendering approaches GAEB files differently from a generic document processor.
Capability
Schema-aware parsing
Capability
Long text interpretation
Capability
Scope filtering
Capability
Variant configuration resolution
Capability
Valid X84 output
The detail that catches teams out
These two position types are worth addressing directly because they appear in most GAEB files and are consistently mishandled in manual processing.
Provisional Sums
Bedarfspositionen
Items the project owner may order, optionally. They are included in the BoQ for pricing purposes but may not appear in the final order. Some suppliers price them at their standard rate; others apply a different margin given the uncertain demand.
Alternative Positions
Alternativpositionen
A specification alternative: a standard valve and a higher-pressure alternative for the same installation point, for example. The project owner selects one; both are priced in the tender. The system needs to identify which positions are alternatives to which, price them separately, and present them correctly in the X84 response.
ERP integration
Construction supply companies typically use one of several ERP and quoting systems: SAP (Business One or S/4HANA), Microsoft Dynamics 365, Infor, ProAlpha, or sector-specific systems like Navision-based solutions common in building materials distribution.
The connection between BoQ automation and the ERP needs to cover two directions.
On intake
The system reads from the ERP
To validate and price the BoQ positions, the system reads:
On output
The system writes to the ERP
Once positions are priced and confirmed:
GAEB-specific output step
For GAEB workflows, the output step also includes generating the X84 response file: a requirement that has no equivalent in standard order intake automation, and that requires the BoQ automation layer to understand the GAEB format well enough to write it correctly.Turian's BoQ automation agent handles GAEB files as a native format: parsing the full schema, preserving the OZ hierarchy, interpreting long text specifications, filtering by supplier scope, resolving variant configurations, and generating valid X84 response files. It connects bidirectionally to the ERPs used in construction supply.
The right question to ask
For construction supply companies receiving GAEB files as a standard part of their tendering workflow, the question to ask any automation vendor is not "do you support GAEB?" Most will say yes. The question is:
"Show me how your system handles a 400-position X83 file with multiple trade sections, provisional sums, and alternative positions. Walk me through what the inside sales team sees and what the X84 output looks like."
The answer will tell you whether the vendor has built for GAEB or is claiming GAEB support based on basic XML parsing. There is a significant difference between the two.
See how turian handles GAEB BoQ automation end-to-end
From X83 intake to priced X84 output, via your ERP.
By clicking "Accept", you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
