v18.7.0 - Four country packs and cost control.

OpenConstructionERP 18.7 adds packs for Egypt, Saudi Arabia, Poland and France, each with its own e-invoicing route. Cost control gives owners and contractors a forecast they can trace back to its source. Schedules cut from an estimate now arrive with a budget and resources, and the fixes below remove several rough edges.

What is in version 18.7.0

• Cost control per project. One table shows for every cost line what was planned, awarded, added by changes, the expected final cost, the difference to plan, and what is certified and paid. Money that sits on no cost line shows as its own row instead of disappearing. The forecast takes the most reliable figure for each line and says which one it took, and you can overrule it with a reason and a document.
• Saved forecasts and a demo project. Forecasts are saved monthly with their stage, are never edited afterwards, and a chart shows how the cost moved. Four forecast methods are available per project and per line. A cost control demo project for training installs with python -m app.cli demo-cost-control.
• Country packs for Egypt, Saudi Arabia, Poland and France. Each pack brings its working week and public holidays, contract rules, tax regimes and identifier checks. Egypt plans on a Sunday to Thursday week. Saudi Arabia adds the summer midday work ban warning and GOSI rates. Poland adds kosztorys overhead and profit with KNR, and split payment checks. France adds late payment interest and the recovery indemnity.
• E-invoicing for four countries. Egyptian invoices are built in the ETA v1.0 format, signed as CAdES-BES and sent to the Egyptian Tax Authority. Saudi invoices follow UBL 2.1 with the ZATCA stamp and QR code, cleared or reported through FATOORA phase 2. Polish invoices use the FA(3) structure for KSeF. French invoices check SIREN and SIRET and the required mentions. Totals, parties and lines are checked before sending.
• Schedules from an estimate carry cost and resources. Every task takes its position total as planned cost and gets a labour row, and a machine row where the bill has machine hours, so a fresh plan has a budget, an S-curve and something for resource levelling. Each task also shows a confidence for its duration.
• Forecasting, benchmarks, requisitions and site logistics. Historical benchmarks from finished projects give P10 and P90 by client, region, type or classification, and can restate money to a reference month with the price index register. Requisitions take approvers in order and convert to purchase orders in parts. Site logistics zones and deliveries now link to their areas and transports in the database itself.
• A clearer validation report. The report opens on errors and warnings, groups findings by rule with a translated name and what to do, links each finding to its position in the bill, and offers a search once there are more than twenty findings.

Fixes

A change order line added to a subcontract schedule keeps the contract's cost line, and creating a change order on a project with an active variation order no longer answers 500. Tables in every module sit on a solid background. The plan room explains itself in one line and three short steps, and the dashboard shows use cases and video guides on one grid. A country pack install now says what it set up and what it did not, and the Canadian cost base shows its size. The confidence score of a generated schedule is written in the reader's number format.

Install or upgrade

pip install openconstructionerp==18.7.0

With Docker, run docker compose pull app && docker compose up -d in your install folder to move to 18.7.0.

Desktop installers for Windows, macOS and Linux are on openconstructionerp.com/download. The full list of changes for each version is in the release notes on GitHub. The macOS build is for Apple Silicon only. On an Intel Mac, install with pip or Docker. Questions or trouble upgrading, write to info@datadrivenconstruction.io.

Tell us how it went

If you have installed or tested OpenConstructionERP, we would like to hear what happened, including the parts that did not work. Open an issue on GitHub or write to info@datadrivenconstruction.io.