GAEB file rejected: the exchange phase makes the difference.
Transfer bills of quantities and tender data between existing construction systems. Investigate import errors using clear examples.
Read the German originalThe extension is an initial clue
GAEB organises construction data exchange into phases. X83 denotes an invitation to tender; X84 denotes tender submission. Before investigating an error, establish whether both applications support the same phase and a compatible version.
Record the file extension, generating application, application version and exact message. This is more useful than initially converting files at random. Different generations of the format may represent information differently.
Check schema and content separately
The GAEB XML checker validates a file against a schema. This does not establish whether quantities, line items and business relationships are correct for your transaction. Even a formally valid file may produce unexpected results in the target application.
Use a small bill of quantities to compare item identifiers, units and, where relevant, prices before and after import. A reproducible error involving a few line items is easier to investigate with software vendors than an unwieldy complete project dataset.
Repair the exchange traceably
Keep the original file and document every change made to a copy. A correction should retain the agreed information. Silently removing fields just to make an import work pushes the error into a later stage of the project.
A limited analysis package clarifies one transaction between two applications. If the same cause recurs, it can lead to a validated import process. Specialist approval of the tender remains with the responsible people in the construction project.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Check GAEB data and connect construction systems · Packages