How are retention bonds different from performance bonds and bid bonds?

All three protect the developer, but at different stages. A bid bond guarantees the contractor will sign if awarded — typically 1-2% of the tender value, released right after award. A performance bond covers correct execution during the works — usually 5-10% of the contract, issued as a bank guarantee or insurance bond and released at provisional acceptance. A retention bond (or contractual retention) is a percentage withheld from each progress invoice — typically 5% — and released after the Defects Liability Period (DLP), usually 12 months after final acceptance. Retention bonds are the silent one: no formal expiry document, no bank reminder, just a quiet line on a balance sheet that someone has to remember to chase.

What's the typical retention period in Spain and EU construction?

In Spain, the contractual standard for private construction is 5% retention released 12 months after provisional acceptance, aligned with the LOE (Ley de Ordenación de la Edificación) one-year defects period for finishings. For structural defects, LOE extends liability to 3 and 10 years, but cash retention is rarely held that long — it's covered by ten-year insurance (seguro decenal). In public works, the standard is also typically 5% with a one-year guarantee period after acceptance, regulated by the Ley de Contratos del Sector Público. Across the EU it varies: UK construction often uses 3-5% with a 6-12 month DLP, German and French contracts commonly use 5% with 12 months, sometimes substituted by a bank-issued retention bond.

How does dvretencionesgarantia handle bankrupt developer scenarios?

The extension does not magically recover money from an insolvent developer — nothing can. What it does is give you the documentation you need to file an ordinary or privileged claim in the insolvency proceedings (concurso de acreedores in Spain): the original contract, every retained invoice, the calculated retention balance, the agreed release date, and the proof you formally requested release before the insolvency was declared. Most retentions lost in developer bankruptcies are lost not because the developer was broke, but because the contractor never filed the claim with proper documentation within the statutory window. dvretencionesgarantia generates that documentation pack in minutes.

Can it manage performance bonds issued via bank guarantee, not cash retention?

Yes. The extension models three retention instrument types: cash retention (withheld from progress invoices and held on the developer's balance sheet), bank guarantee (aval bancario, where you pay the bank a fee and the bank issues the guarantee letter to the developer), and surety bond (seguro de caución, issued by an insurance company). For bank guarantees, dvretencionesgarantia tracks the bank, fee accrual, expiry date, and triggers the cancellation request to the bank when the guarantee period ends — important because banks keep charging the quarterly fee until you formally cancel the line.

Does this work for installation companies and subcontractors, not just main contractors?

Yes, and arguably the value is higher for subcontractors. Main contractors typically have one developer per project and decent finance discipline. Subcontractors (electrical, HVAC, structural steel, installations) often have 20-80 active main contractors as customers, each holding retentions on each invoice, each with different DLPs. The retention register easily reaches 500-2,000 open lines for a mid-sized installer. Without a tool, recovering 100% of these retentions is mathematically impossible — the team would spend more chasing than they recover.

How long does implementation take?

If Business Central is already live, adding dvretencionesgarantia typically takes 3-5 weeks: configuration of retention types per customer/contract template, GL account mapping, alert rules, and import of the legacy retention register from spreadsheets (this is usually the longest step — cleansing the old data). If BC is also being implemented in parallel, the retention module is added inside the standard project, no separate phase. First retention recoveries usually appear within 60 days of go-live, just from chasing already-expired retentions that nobody had on a list.

Volver a dvretencionesGarantia

Projects & Construction

Retention Bond Management for Construction: ERP vs Spreadsheets

The hidden cost of forgotten retention bonds in construction — why 5-15% expire unclaimed, and how Business Central + dvretencionesgarantia fixes it natively.

7 min

Retention bond management for construction companies

In construction, the most expensive money is the money you forgot you were owed. Not the contested change order, not the disputed certification — those at least get fought for. The expensive money is the retention bond that quietly expired its release date, on a balance sheet line nobody opened, on a developer who was never going to pay it back unless you asked.

This article is an honest look at retention bond management in construction and installation businesses: how much typically gets lost, why spreadsheets fail at this, what a proper process looks like, and how to solve it natively inside Microsoft Dynamics 365 Business Central with dvretencionesgarantia, Davisa’s native AL extension.

Disclosure: Davisa Informática is a Microsoft Solutions Partner for Business Central since 2003, and the author of dvretencionesgarantia. We’ve been implementing project-driven ERPs for construction and installation companies for over 20 years. The numbers below come from real client recoveries.

The hidden 5-15% problem

Standard contractual retention in private and public construction is 5% of every progress invoice, held by the developer (or main contractor, if you’re the subcontractor) for a guarantee period — typically 12 months after provisional acceptance, sometimes longer. The retention is supposed to be released once the Defects Liability Period (DLP) closes without claims.

The dirty secret of the industry: without rigorous tracking, 5-15% of these contractual retentions expire without being claimed.

Run the numbers on your own business. A construction firm doing €50M annual revenue, with an average 5% contractual retention rate, has roughly €2.5M of cash quietly held by developers at any given moment. If 5-15% of that retention universe never makes it back to your bank account:

5% lost → €125,000/year evaporated
10% lost → €250,000/year evaporated
15% lost → €375,000/year evaporated

That is not bad luck. That is a structural process failure that compounds year after year. And it is invisible on the P&L — the retention was already booked as revenue when the invoice was issued. The loss only shows up as an aged debit balance on a “retentions receivable” account that nobody reconciles.

Why spreadsheets fail at this

We’ve audited dozens of construction and installation companies on this exact process. The spreadsheet method fails for five specific reasons:

1. The team that issues the invoice is not the team that claims the retention 12-18 months later. The site team has moved to a new project. The project manager left the company. The accountant who set up the retention line has been promoted. By the time the retention is due, organisational memory of why this line exists is gone.

2. The developer doesn’t proactively return retentions. Of course not — it’s their cash. In the developer’s accounting system, the retention is a payable, but releasing it requires the supplier to formally request release, present the contract, document the DLP expiry, and chase. Developers who systematically remind their suppliers to claim retentions are mythological creatures.

3. Accounting books the retention payable but doesn’t trigger an action when due. Most accounting setups create a “retention receivable” sub-account, post the entries correctly, and stop there. There is no date-based trigger. The retention will sit on that account for years without anyone touching it.

4. Handover between project managers loses the trail. Even with a good spreadsheet, the moment the project closes and the PM moves on, the file gets archived. Six months later, when the retention is due, nobody opens it.

5. Developers go bankrupt, get bought, or restructure between billing and claim date. A 12-month DLP plus statutory grace periods means almost two years between the first retained invoice and the latest possible claim. In construction, two years is enough time for a lot of corporate events. If you have not registered your retention claim with full documentation before the bankruptcy filing, you join the unsecured creditor queue with nothing.

What a proper retention management process looks like

A serious retention management process — independent of which software implements it — requires six capabilities:

Automatic retention calculation per contract. Each contract carries its retention percentage and release rules. Every progress invoice line automatically calculates and posts the retention without manual intervention.
Living retention register by project, developer, and due date. A single up-to-date list answering: “How much retention is outstanding, with whom, due when?” In one click, filterable by project, customer, due date band, status.
Proactive alerts 30/60/90 days before expiration. Email and dashboard alerts to the finance team and the responsible project manager before the release date arrives — not after.
Document trail. Linked to each retention: the original contract, every invoice that contributed to it, the provisional acceptance certificate, the formal release request, and the eventual collection.
Reconciliation to the General Ledger. The retention register total always reconciles exactly to the retention payable/receivable GL account. No “we’ll figure it out at year-end” gaps.
Refund workflow with bank reconciliation. When the retention is collected, automatic matching to the bank statement and clearing of the retention line.

Business Central + dvretencionesgarantia: native approach

dvretencionesgarantia implements the six capabilities above natively inside Microsoft Dynamics 365 Business Central, as an AL extension — no middleware, no separate database, no sync jobs.

Key differentiators versus a spreadsheet or an external standalone tool:

Single source of truth. The retention lives in the same database as the contract, the sales invoice, the GL entry and the bank reconciliation. There is no second system to keep in sync, no copy of the data that goes stale.
Triggered by underlying contract terms automatically. Define the retention percentage and DLP at the contract level once. Every invoice issued against that contract carries its retention line without a human deciding to add it.
Direct link to the GL retention payable/receivable account. Every movement in the retention register has a matched journal entry. The auditor can drill from the GL balance to the retention register line in one click.
Audit trail for the auditor. Spanish statutory audit and ISO 9001 quality audits both increasingly ask for retention documentation. dvretencionesgarantia produces the audit pack natively.
Bank guarantee tracking. Beyond cash retention, the module tracks bank-issued and insurance-issued performance bonds, including the bank fees accruing until you formally cancel.

For companies running construction projects, the module pairs naturally with dvproject Construcción, Davisa’s vertical extension for project-based contractors — the retention configuration flows from the project structure (chapter, work item, sub-item) and the progress billing module.

ROI of implementing retention tracking

The most surprising number in our client portfolio: the first audit of the legacy retention register typically recovers €50,000-€200,000 of retentions that had already expired without claim, sometimes years ago. In several cases, this first recovery alone has paid for the entire Business Central + dvretencionesgarantia implementation in year 1.

Steady-state ROI: once the process is live, recovery rates on contractual retentions move from 85-95% (typical for a disciplined spreadsheet approach) to 99-100%. The difference, on a €50M revenue construction firm, is €125,000-€250,000 per year of cash that previously evaporated.

Calculator: how much could you have forgotten?

We’ve built a free calculator that estimates how much your construction company may have lost in unclaimed retentions over the last 5 years, based on revenue, retention rate, and historical processes. It’s in Spanish, but the inputs and outputs are universal — euros and percentages translate.

→ Forgotten retentions calculator

When NOT to invest in this

Honest take, because we’d rather not sell a project that doesn’t pay back:

If your construction firm is below €10M revenue with 1-2 active developers, a well-disciplined accountant with a properly maintained spreadsheet can cover the basics. The combo Business Central + dvretencionesgarantia is overkill at that scale.
The combination starts paying off above €15-20M revenue with multiple concurrent developers, especially for installation companies and subcontractors with 20+ active customers.
It pays off massively above €50M with international projects, mixed cash/bank-guarantee retention models, and statutory audit requirements.

If you’re below the threshold, our honest recommendation is: tighten the spreadsheet discipline, assign one person clear ownership, and schedule a quarterly review. When you cross the threshold, call us.

Davisa Informática · Microsoft Solutions Partner for Business Central since 2003. We implement Business Central with our specialised extensions for construction (dvproject Construcción, dvretencionesgarantia) for contractors, installers and subcontractors across Spain and the EU.