Spanish Construction ERP: An International Perspective

International CFOs and group controllers evaluating Spain almost always ask the same question first: can we just deploy our existing construction ERP here? The instinct is sensible — group standardisation reduces cost and risk. The answer, however, is rarely a clean yes. Spanish construction is one of those verticals where the regulatory layer, the commercial model and the operational documentation diverge enough from US, UK or German practice that a standard rollout becomes a recurring source of friction.

This article is written for the international buyer: the CFO or COO of a construction group with Spanish operations, the Microsoft Partner from outside Iberia evaluating the Spanish vertical for a client, the multinational engineering firm bidding on Iberian infrastructure. As a Microsoft Solutions Partner for Business Central since 2003, Davisa has lived through dozens of these conversations. The goal here is to translate the Spanish construction reality into terms that a non-Spanish decision-maker can act on.

Why Spanish construction needs its own ERP layer

The Spanish construction regulatory perimeter is denser than most international buyers expect. Start with REA — the Registro de Empresas Acreditadas — a mandatory registry for any company performing subcontracted construction work. REA validity must be checked before assigning a subcontractor to a job site, renewed periodically, and documented as part of the project file. A foreign ERP will not flag an expired REA before payment is released; a Spanish vertical will.

Add TGSS (Tesorería General de la Seguridad Social) reconciliation. Spanish contractors must verify that subcontractors are al corriente with social security — current on contributions — before issuing payment, and that verification must be auditable. Then there is the AEAT modelos calendar (303, 390, 347, 349, 111, 190), the SII real-time invoice reporting regime, and from 2026 onward the Verifactu fiscalization layer for outgoing invoices. Add IGIC for Canary Islands operations and the foral regimes of País Vasco and Navarra, each with its own modelos and frequencies.

On top of compliance sits the commercial model: BC3-format budgets from the technical office, certifications (progress billing) with chapter and work-item granularity, performance retentions (typically 5%) released against bank or insurance guarantees, plusvalía municipal on land transactions, and the specific VAT inversion rules for construction subcontracting. None of these are localizations bolted onto a generic projects module — they are the daily mechanics of a Spanish job site.

5 things foreign GCs miss about Spanish construction

One: the budget is the contract. In Spain, the BC3 budget — a hierarchical structure of capítulos, partidas and unidades de obra exported from Presto, Arquímedes or Cype — is the legal reference for the contract. Certifications, modifications and final settlement all reference its structure. A project ERP that cannot import BC3 natively or that flattens it into a generic task list is fighting the workflow.

Two: retention is a financial instrument, not a line item. The 5% retention is typically backed by an aval bancario (bank guarantee) or aval de seguro (insurance bond) that has its own cost, expiry and release schedule, often tied to the project’s defect-liability period. Tracking the guarantee lifecycle is operational work that a generic AP retention field cannot do.

Three: subcontractor compliance is a daily activity. REA registration, TGSS clearance, occupational risk coordination (CAE) documents and PRL training records must be valid on the day the subcontractor enters the site. The site manager needs a mobile-friendly way to check this; the back office needs an alert before the document expires.

Four: VAT inversion rules in construction. Spain applies reverse-charge VAT for most subcontracting transactions in construction. Tax codes, invoice templates and SII reporting must handle this correctly or the company has a compliance exposure.

Five: cash collection cycles are long and irregular. Public-sector certifications (FACe portal, e-invoicing to administrations) follow statutory payment schedules but enforcement is uneven. Private developer cycles are tighter but conditioned on milestone acceptance. Treasury forecasting in Spanish construction is its own discipline; a generic AR module is insufficient.

Native Spanish vertical on Business Central with dvproject-construccion

Microsoft Dynamics 365 Business Central provides the certified Spanish accounting core: SII real-time reporting, AEAT modelos, Verifactu roadmap, foral and IGIC territories, electronic invoicing via FACe and B2B. On top of that core, dvproject-construccion adds the construction vertical: BC3 import with full hierarchy, certification engine with retention and reverse-charge VAT handling, subcontractor compliance register, site-manager mobile entry, project margin dashboards in real time.

Retentions and guarantees are managed in dvretencionesgarantia, which extends BC with the full guarantee lifecycle: issuance cost capture, renewal calendar, release clauses tied to project milestones, and reporting per contract and per insurer.

The architectural advantage is that Business Central is a standard platform — not a closed proprietary vertical. International groups get standard Microsoft licensing, standard SQL data model, standard Power BI, standard Power Automate, and standard Microsoft 365 integration. The vertical layer rides on top, not underneath.

Tender process: BC3, FACe, retentions explained

International firms bidding into Spain encounter three standards immediately. BC3 is the file format for budgets and certifications, exported by the technical office’s quantity-takeoff software (Presto, Arquímedes, Cype). The format is hierarchical and includes pricing, quantities, codes and descriptions. A construction ERP that imports BC3 directly turns a one-week budgeting exercise into a one-hour upload.

FACe is the public-administration e-invoicing portal. Any invoice to a Spanish public client (state, regional, municipal) must be issued through FACe in Facturae format with electronic signature. This is not optional and not a partner integration — it is a statutory channel.

Retentions in Spanish public works are typically structured as 5% of each certification, retained until project completion and the defect-liability period (often 12 months). Bank or insurance guarantees are common alternatives to cash retention. The contractor’s ERP must track the retained amount per certification, the guarantee covering it, the release schedule and the link to provisional and definitive acceptance.

For a fuller comparison of vertical options, our Best Construction ERP on Business Central guide walks through the alternatives.

When to localize vs centralize HQ ERP

The decision tree for international groups is fairly stable. Centralize at HQ when the Spanish entity is small (under 20 users, low transaction volume), when operations are project-light (engineering services, no site construction), or when the group operates on a single ERP mandate for governance reasons.

Localize to Business Central when the Spanish entity runs site operations (certifications, subcontractors, retentions), when transaction volume triggers SII real-time obligations, or when statutory documentation requirements (REA, TGSS, CAE) make the HQ ERP operationally insufficient.

The hybrid pattern — two-tier ERP — fits most mid-market groups: Spanish subsidiary on Business Central with dvproject-construccion for operations and compliance, monthly trial balance consolidated upward into the group ERP (SAP, Oracle, NetSuite, or another Business Central tenant) via mapped chart of accounts. IFRS reporting layer sits at HQ; Spanish GAAP and AEAT layer sits in BC. Power BI or Azure Data Factory carries the data feed.

For groups consolidating across countries, our Multi-Company Consolidation in Business Central guide covers the intercompany and currency mechanics.

The right answer is almost never “force the global ERP into Spain”. It is “let the local entity be locally compliant, and consolidate cleanly”.