Estimating → ERP
The awarded budget is created automatically as a project budget with cost lines.
- Method: REST API or structured export
- Lead time: 2-4 weeks
- Control: variance report per project
Which systems to connect, which data flows where — and how that stays secure.
A complete overview of integration options in construction and real estate: the software landscape, the data flows between them, recognisable example integrations, available methods and the security principles we apply.
The software landscape in construction and real estate
Almost every organisation runs a combination of the categories below. Integration starts by deciding which system leads per data domain.
- Estimating and budgeting
- Cost lines, quantities, rate cards and norms — the basis for purchasing, planning and invoicing.
- ERP and finance
- Project administration, purchasing, commitments, hours and invoices: the financial truth.
- CRM and tenders
- Relations, enquiries, tenders and quotation history — information needed again later.
- Planning and capacity
- Phasing, milestones, capacity and progress, usually in a separate planning package.
- BIM, drawings and models
- Object data and quantities (IFC), revisions and change management.
- DMS and document control
- Contracts, specifications, inspection reports and handover files with version control.
- Field and site apps
- Hours, daily reports, issues, photos, inspections and variations.
- HR, time and payroll
- Rosters, leave, hours worked and payroll per project and cost centre.
- Purchasing and suppliers
- Price lists, orders, confirmations, delivery notes and purchase invoices.
- BI and reporting
- Management information and margin dashboards built from combined sources.
From source systems to one reliable project view
The intelligence layer collects, validates and enriches data from your existing systems — without replacing them.
Concrete data flows and what they deliver
For each flow we record source, target, data, direction, frequency and the intended result — the basis for testing and acceptance.
Tip: swipe horizontally to view the full table.
| From | To | Data | Direction | Frequency | Result |
|---|---|---|---|---|---|
| BIM / IFC | Estimating | Quantities, object types, materials | One-way | On model revision | No manual re-entry of quantities; changes are visible immediately. |
| Estimating | ERP | Budget, cost lines, budget codes | One-way | On award and revision | The project budget is correct in the administration from day one. |
| CRM | ERP / project file | Client, contacts, enquiry, quotation | One-way | On status change | No duplicate entry at project start; one set of relation data. |
| Time app | ERP / payroll | Hours per project, cost centre and type | One-way | Daily (nightly) | Faster payroll and up-to-date hours per project. |
| ERP | Planning | Projects, phases, budgets, capacity | Two-way | Hourly | Planning and administration tell the same story. |
| Suppliers | Estimating / purchasing | Price lists, tiers, lead times | One-way | Weekly or monthly | Estimate with current prices instead of outdated lists. |
| Purchase invoices | ERP | Invoice headers and lines, order match | One-way | Real time on receipt | Automatic recognition and matching; fewer manual entries. |
| Field app | DMS / ERP | Daily reports, photos, inspections, variations | One-way | Real time | Variations actually get invoiced and files stay complete. |
| ERP + planning + hours | BI / dashboard | Margin, progress, hours vs budget | One-way | Daily | One steering view instead of separate exports and private spreadsheets. |
| Portal | ERP / DMS | Requests, documents, approvals | Two-way | Real time | Clients and subcontractors work in the same current data. |
Integrations we build regularly
Indicative lead times apply to a well-scoped integration with available interfaces, including testing and acceptance.
BIM/IFC → estimating
Model quantities are mapped onto estimating lines and norms.
- Method: IFC parser and mapping table
- Lead time: 4-8 weeks
- Control: deviation alerts per object type
Time app → ERP and payroll
Approved hours flow daily into project administration and payroll.
- Method: API with nightly batch
- Lead time: 2-3 weeks
- Control: rejection log with reason per row
Purchase invoices → ERP
Invoices are recognised, matched to orders and queued for approval.
- Method: email intake, OCR/AI and API
- Lead time: 4-6 weeks
- Control: human approval on deviation
Supplier prices → estimating
Current price lists and tiers imported and versioned periodically.
- Method: SFTP/CSV or API
- Lead time: 1-3 weeks
- Control: price change report
Project data → BI dashboard
Combined sources in one data model with clear definitions.
- Method: data pipeline into a warehouse
- Lead time: 4-8 weeks
- Control: definition document per KPI
Which method fits which situation
We pick the simplest method that reliably achieves the goal — and document why.
- REST API / webhooks
- Preferred: real time, controlled and easy to monitor. Requires an API on both sides.
- File exchange (SFTP/CSV/XML)
- Robust for batch processes and legacy packages. Clear agreements on format, timing and error handling.
- Database connection
- Read-only on a replica or view. Never write directly into someone else's production database.
- Middleware / iPaaS
- Worthwhile with multiple integrations: one place for mapping, logging, replay and management.
- Custom integration layer
- When domain logic, validation and mapping are too specific for standard connectors.
- RPA / UI automation
- Last resort for systems without any interface. Fragile on updates; always with a fallback.
Security, privacy and control
Integrations touch business-critical and sometimes personal data. We therefore apply the same principles to every integration, regardless of project size. These principles are documented per project so you know exactly who can access what, what is logged and what happens when something fails.
Encryption and transport
All exchange runs over TLS 1.2 or higher. Data at rest is stored encrypted; file exchange uses SFTP or encrypted storage, never unprotected email attachments.
Access and key management
Every integration gets its own service account with only the permissions it needs (least privilege). API keys and passwords live in a secure secret store, never in code or documentation, and are rotated periodically.
Logging and audit trail
Every exchange is logged with timestamp, record count, result and error. It is always traceable which data changed when and from which system.
Error handling and recovery
Failed messages are retained and retried with exponential backoff. Structural failures alert a designated administrator so an integration never fails silently.
Data minimisation
We only connect the fields required for the purpose. Personal data is avoided where possible and otherwise separated and processed sparingly.
GDPR and processing agreement
For each processing activity we record purpose, legal basis and retention. Where we process personal data we sign a processing agreement covering sub-processors and breach notification.
Hosting and data residency
By default we host inside the European Union. On request we deploy inside your own environment or cloud tenant so data never leaves your control.
Environments and acceptance
Development, test and production are strictly separated. New or changed integrations go live only after acceptance testing with representative data and a written fallback scenario.
Backup and continuity
All environments we manage are backed up and restores are tested periodically. Documentation, source code and configuration are transferable, so you are never locked in.
Security maintenance
Dependencies are monitored for vulnerabilities and patched in time. Security reports follow a fixed procedure for assessment, remediation and communication.
Frequently asked questions about integrations
Read more: Software integrations · Process automation · Knowledge base
Get started
Which processes could run smarter in your organisation?
In a no-obligation intro call we discuss where automation, integration or custom software adds value right away.