Table of contents
The 3 Major Site Risks
- Financial / Margin: A rounding discrepancy or truncation on unit prices during file transfers under standard SIA 451 can generate a distortion on the order of 0,5 % to 2 % of the total awarded amount, representing an illustrative loss of 15 000,00 CHF to 60 000,00 CHF borne by the successful tenderer bound by the lump-sum price under art. 373 CO.
- Legal / Joint body / SUVA: XML tag corruption or non-compliance with the CAN structure exposes the tenderer to exclusion from the procedure under art. 44 LMP for formal defects, or to requests for clarification on abnormally low prices under art. 38 LMP.
- Administrative / Acceptance: Altering standard item identifiers prevents rigorous matching of contractual quantity take-offs defined for the contract for work governed by art. 363 CO and complicates verification of payment claims under standard SIA 118.
The digital transmission of construction tenders in Switzerland relies on the data exchange standard defined by standard SIA 451, structured jointly with CRB catalogues. For company directors, technical managers, and estimators responding to public calls for tenders or private procedures governed by the LMP, mastering file import and export mechanisms is essential. Inaccurate software handling, altered character sets, or unverified markup schemas frequently trigger the technical rejection of the priced bill of quantities even before the contracting authority evaluates the award criteria.
Among recurring failures observed on procurement platforms are arithmetic calculation discrepancies caused by the Swiss rule of rounding to the nearest multiple of 0,05 CHF. Incorrectly applying this rounding at the gross unit prices level instead of line totals, or vice versa, produces chapter totals that diverge from those generated by the site management software. The contracting authority applying art. 38 LMP rectifies obvious calculation errors ex officio, or may exclude the tender if it contains substantive formal defects under art. 44 LMP. Ensuring the absolute integrity of your digital data flows protects your company's margin and validates the contract for work.
Calculation mechanisms and management of 5-cent rounding under SIA 451
The electronic data exchange standard defined by standard SIA 451 requires absolute mathematical precision when converting data between a contractor's estimating software and the contracting authority's bid opening system. In Switzerland, standard accounting practices require settlement to the nearest multiple of 0,05 CHF. However, within a bill of quantities structured according to the Standard Item Catalogue (CAN) established by CRB, calculations operate at multiple levels: unit prices, item line total amounts, subtotals by Building Cost Classification (CFC) chapters, and the overall summary total.
The primary source of encoding anomalies lies in the precise moment rounding is applied. If an application applies commercial rounding to each intermediate multiplication between the measured quantity and the unit price before summing, the final result inevitably diverges from a method that sums raw floating-point values and only rounds the chapter total. When the file exported under standard SIA 451 is re-imported by the site management, the client's verification algorithm recalculates each line. A cumulative variance of just a few centimes is thus flagged as an arithmetic inconsistency. In contracts governed by the LMP, the contracting authority examines tenders pursuant to art. 38 LMP, which mandates checking formal requirements and rectifying obvious calculation errors ex officio.
To prevent these discrepancies, price entry into standardised structures must separate internal price breakdown calculations from exported figures. Unit prices can be entered with extended decimal places in measurement tools, but the standard SIA 451 exchange schema strictly sets the numerical data format transmitted for tender evaluation. Each position in the quote must therefore feature a unit price and a total value that match up seamlessly, ensuring the verification software detects no summation errors.
Common import, export, and XML encoding errors
The interoperability of tenders depends on strict compliance with file schemas. Technical failures encountered when submitting files stem from three main categories of software or human errors:
- Character set alteration (encoding): Using incompatible encodings when generating the file leads to corruption of Swiss accented characters or specific symbols. When imported by the contracting authority, these errors corrupt CAN descriptions or crash the reading tool's XML parsers.
- Unauthorised alteration of standardised texts: Closed CAN descriptions tolerate no modification by the tenderer. Attempting to edit the text of a pre-established item instead of merely completing open variables triggers immediate rejection of the tender file during validation by the contracting authority's system.
- Inconsistent value added tax handling: The contracting authority expects net unit prices excluding tax, with Swiss VAT at 8,1 % added only in the final summary of the tender. Incorrectly applying a tax rate directly to unit positions creates partial double counting or distorts objective tender comparisons.
- Disruption of CFC chapter hierarchy: Item positions must remain attached to their original structure. Inserting free lines outside designated chapters invalidates the tree hierarchy during automated file parsing.
- Misinterpretation of negative quantities or deductions: Global rebates or discounts placed in inappropriate fields within the transmission file disrupt automated tender validation and may be disregarded during the comparative analysis.
Comparison table of rounding and import processing methods
| Method or setting | Calculation process | Standard SIA 451 compliance | Consequence for the tenderer |
|---|---|---|---|
| Systematic line-by-line rounding (0,05 CHF) | Each quantity x unit price product is immediately rounded to the nearest multiple of 5 centimes. | Compliant if the software recalculates chapter totals using simple arithmetic summation. | Avoids any addition discrepancies in subtotals during formal verification. |
| Untruncated floating-point rounding | Retention of multiple internal decimal places with rounding applied only to the grand summary. | Non-compliant during tender opening if displayed item totals do not equal the grand total. | Risk of formal challenge or ex officio rectification pursuant to art. 38 LMP. |
| Entering unit prices with fractional centimes | Unit prices transmitted with 3 or 4 decimal places in a standard export format. | Rejected by most tender opening software packages, which require two decimal places for unit prices. | Automatic truncation by the importer, creating a financial deficit borne by the contractor. |
| Exporting without prior schema validation | Direct generation of the data container without checking tags and character encoding. | Non-compliant whenever corrupted special characters or inverted fields are present. | Outright rejection of the tender for formal defects under the screening criteria of art. 44 LMP. |
| Direct manual editing inside the export file | Raw text editing of the file to force roundings before electronic tender submission. | Critical: almost certain corruption of the validation structure or checksums. | Inability of the client to import the file, resulting in exclusion from the procedure. |
Legal and financial consequences of calculation discrepancies
When a construction contract is awarded at a fixed lump-sum price, the consequences of a rounding discrepancy or software transmission error fall heavily on the successful tenderer. Under art. 373 CO, where the price has been fixed as a lump sum, the contractor is bound to complete the work for that exact agreed amount and cannot claim any increase, even if the work required more labour or expenditure. If an encoding error led to an understated unit price or omitted centimes across a large volume of standard items, the contractor has no automatic legal mechanism to recover the difference during project execution.
Within a public call for tenders, the contracting authority applies the bid evaluation criteria defined in art. 29 LMP. Inconsistencies in the priced bill of quantities undermine both the profitability and credibility of the submission. Furthermore, under art. 44 LMP, the contracting authority has the power to exclude from the procedure any tenderer that submits an offer marred by significant formal defects. An unreadable, corrupted data file or one exhibiting logical discrepancies in basic calculations provides grounds for immediate formal exclusion, without the company's technical proposal or references even being evaluated.
Illustrative practical cases (typical scenarios on Swiss construction sites)
The following scenarios are illustrative examples designed to examine the technical and legal dispute mechanisms encountered on Swiss construction sites.
Scenario 1: Tender for a school complex in the canton of Vaud
A masonry and reinforced concrete firm of 35 employees prepares its tender for a cantonal public procurement contract with an estimated value of around 4 800 000,00 CHF. The call for tenders includes over 600 items across multiple structural work CFC chapters. When transferring the quantity take-offs into the export software compliant with standard SIA 451, the estimator lets the calculation module run internal computations to three decimal places without line-level rounding to 0,05 CHF. The exported file shows a total net amount of 4 440 250,12 CHF. During import into the tender opening platform by the site management, the official software rounds each line to the nearest 0,05 CHF and recalculates the CFC chapter sums. The line-by-line total reaches 4 435 120,40 CHF, generating a cumulative variance of 5 129,72 CHF. Pursuant to art. 38 LMP, the contracting authority rectifies this obvious calculation error ex officio by applying the lower recalculated figure. The firm is ultimately awarded the contract, but must execute the works based on the lower corrected sum, absorbing the entire margin deficit.
Scenario 2: Renovation of an office complex in the canton of Geneva
For a finishing work installation contract valued at roughly 850 000,00 CHF, a general contractor with 12 employees submits an electronic tender. Wanting to make a last-minute adjustment by applying a 2 % discount to the plastering CFC chapter, the manager directly edits the export file using a raw text editor. This manual change corrupts the tag encoding and truncates the Swiss VAT calculation at 8,1 %. When the client loads the tender into its evaluation software, the system flags the file as invalid and rejects the bill of quantities. Based on art. 44 LMP, the contracting authority excludes the tender due to a substantive formal defect. The firm loses the contract solely because of a digital data error, despite having submitted a competitive initial price.
Calls for tenders: free tools
Direct public procurement tenders, AIMP thresholds by canton, converting SIA 451 to Excel, quantity takeoff from an IFC model.
Frequently asked questions
How does the contracting authority handle a rounding discrepancy during formal review?
Under art. 38 LMP, the contracting authority verifies formal requirements and corrects obvious calculation errors ex officio. A minor 5-cent rounding discrepancy, such as 0,05 CHF on a total of 184 250,30 CHF, is adjusted based on official rules without leading to the rejection of the tender.
Does a cumulative discrepancy in a data file justify excluding the tender?
No, a mere discrepancy of cents does not justify exclusion under art. 44 LMP. The contracting authority asks for technical clarifications. Conversely, refusing to confirm the arithmetic source or altering the unit price without explanation exposes the contractor to rejection for an offer tainted by a substantive formal defect.
Why do tender software packages apply commercial rounding to each item?
To ensure CRB data interoperability, each product of unit price by quantity is rounded immediately to two decimal places, and then to the commercial 5 cents in Swiss currency. This standardised method prevents award disputes during the final reconciliation between the tenderer and the site management.
At what stage does legal rounding to the nearest 5-cent multiple apply?
Swiss commercial practice calculates line items to the exact cent, then applies rounding to the nearest 0,05 CHF multiple on chapter subtotals and the final net amount. This principle ensures complete alignment with VAT at 8,1 % and the tendered total.
What should you do if the structure of the descriptive quote is corrupted upon export?
You must stop sending the file and verify the source file using a certified tool. Under SIA 118, the contractor submits a tender strictly compliant with the tender specifications. Manually modifying standardised item codes irrevocably invalidates automated tender processing by the contracting authority.
Can you challenge an arithmetic adjustment made by the contracting authority?
Yes, the tenderer has formal legal remedies. Pursuant to art. 56 LMP, a substantiated appeal may be lodged in writing within 20 days of notification of the decision, particularly if the contracting authority distorted the calculation of a contractual unit price.
Thorough mastery of electronic data interchange and commercial 5-cent rounding rules is a vital prerequisite for safeguarding your tenders in Switzerland. Flawless technical handling protects your margin and prevents any dispute during the formal vetting of bids. To explore the structure of public procurement and private contracts in depth, view our specialised analyses:
