From Record to Decision: ERP Integration, SSRS Reporting and Power BI for RICS Contract Administration

RICS asks the contract administrator to report regularly on quality, progress and cost, to monitor key performance indicators, and to maintain a secure project document management platform. None of that is credible if the contract sum in the PMIS differs from the purchase order in the ERP, or if the monthly report is re-keyed from both. PMWEB 2026 closes the loop: integration keeps the two systems in step, SSRS produces the formal outputs, and Power BI turns the record into decisions.

The previous nine articles followed a contract from commencement to the final account and showed how each RICS contract administration service becomes a structured, workflow-controlled PMWEB process. This final article covers what makes those processes part of the owner's enterprise: integration with the ERP, the reporting layer, and the key performance indicators RICS asks the CA to monitor.

It covers RICS services 1.3 (regular quality, progress and cost reports), 8.7 (monitor key performance indicators) and 8.8 (set up and maintain a secure project and document management website), and the reporting guidance in the RICS 2011 guidance note Contract administration (GN 69/2011, archived in 2022). The current RICS Black Book title Cost reporting covers cost reports in more depth.

Why this matters to you

• Commercial Directors and CFOs: one contract sum, one certified value and one anticipated final account across PMWEB, the ERP and board reports.
• Contract Administrators: formal certificates, registers and statements produced from the record, ready for signature.
• Cost Managers and controls teams: Power BI dashboards and KPIs calculated from live data rather than collected.
• IT and data teams: integration with SAP, Oracle and Microsoft Dynamics on the owner's own dedicated instance.

Why Integration Belongs in Contract Administration

The CA certifies; the employer pays. The certificate lives in the PMIS; the payment lives in the ERP. On many projects the two are connected by e-mail and manual re-entry, and the consequences are familiar: a purchase order that was never increased for approved change orders, so the ERP rejects a valid invoice; retention held in PMIS but not in the ERP; a payment made late with nobody in the contract team aware of it; and a monthly cost report that reconciles two systems before anyone can read it.

Appendix A of GN 69/2011 asks the CA to know the employer's payment procedures and payment dates. RICS Final account procedures asks for the final account to reconcile all payments made. Both depend on PMWEB and the ERP agreeing.

The Integration Touchpoints

CMCS designs PMWEB and ERP integration around a small number of touchpoints, each with a clear system of record.

Two principles keep integration safe. First, only approved transactions cross: PMWEB posts to the ERP when the workflow has completed under the DoA (Article 9), so the ERP never receives an unauthorised commitment or certificate. Second, each data item has one system of record, so there is never a question about which value is right.

Experience and architecture

PMWEB integrates through its REST and SOAP APIs and its dedicated SQL Server database. CMCS has delivered PMWEB integrations with SAP, Oracle Fusion Cloud ERP, Oracle E-Business Suite and Microsoft Dynamics 365 for owners across the GCC. Because each client has a dedicated PMWEB instance and database, whether SaaS, hosted by PMWEB (including in- Kingdom options) or on the owner's premises, the integration can be designed around the owner's ERP configuration and data residency requirements.

SSRS: The Formal Outputs of Contract Administration

RICS expects formal outputs: certificates issued to the employer with a copy to the contractor, instructions in writing, registers, and a statement of final account for signature. PMWEB produces these through SQL Server Reporting Services (SSRS).

PMWEB ships with more than 150 pre-configured SSRS reports, and every module in this series has its standard forms and logs. Across the series, the outputs used have included:

Where an output must follow the wording of a particular form of contract, such as an interim payment certificate, a completion certificate or a statement of final account, CMCS designs the SSRS layout from the same data. Every Custom Form Builder and Adaptive Form record gets its own form and register outputs in the same way. Outputs can be printed for wet signature and stamping, or saved as PDF for digital signature where the contract permits, which is how the series has shown the interim certificate, the notices register and the statement of final account.

Power BI: From Record to Decision

SSRS answers "show me the document". Power BI answers "what is happening across my contracts, and where do I need to act?". Power BI reports connect to the PMWEB database through reporting views, refresh on a schedule (daily, or more often where needed) and are embedded in the PMWEB dashboards area, so users see them in the PMWEB interface under role- based security.

The series has shown five such dashboards: the contract administration control centre (Article 1), time and completion (Article 6), claims and final account readiness (Article 7), DoA and workflow compliance (Article 9) and, below, the portfolio executive view.

completion, combining PMWEB and ERP data

Screenshot S1 shows the six contracts on the Project Alpha development. The main construction contract MC-001 has grown 6.2% from AED 412.50 million to an anticipated AED 437.94 million, above the owner's 3% tolerance and highlighted in red; three other contracts are also above tolerance. Certified values come from PMWEB progress invoices, and paid values and retention come back from the ERP, so the board sees one consistent picture across contract administration and finance.

Monitoring KPIs (RICS Service 8.7)

RICS lists "monitor key performance indicators" as an additional service, and Final account procedures notes that adherence to contractual timescales is itself a KPI for employers and contractors. Because every PMWEB record has dates, values and workflow history, contract administration KPIs can be calculated rather than collected.

A Secure Project Document Platform (RICS Service 8.8)

RICS lists "set up and maintain a secure project and document management website" as an additional service, and GN 69/2011 Appendix B warns that archived electronic data becomes unusable without active management. PMWEB's Document Manager, role-based security, version control, transmittals and archive export meet that service directly, and because the records and documents sit in the owner's dedicated PMWEB database and file store, the archive belongs to the owner, not to the consultant or to an outside platform.

Bringing the Series Together

The argument of the series is simple. RICS defines what good contract administration looks like and what a court may later judge the CA against. PMWEB 2026 provides the modules, forms, workflows, reports and integration to make that practice the way the work is done, and to leave behind a record that proves it.

What Changes for Your Organisation

What the Owner Must Put in Place

• Agree the system of record for each data item. PMWEB for contract administration transactions, the ERP for vendors, payments and accounting.
• Integrate on approval, not on entry. Only DoA-approved transactions should reach the ERP.
• Use SSRS for formal outputs and Power BI for decisions. Do not ask one tool to do the other's job.
• Keep the archive in the owner's platform. The record should outlive every appointment.

RICS references for this article

RICS documents are UK-based; apply them in the GCC subject to the governing law and the form of contract.

Do your contract administrator, your finance team and your board look at the same contract sum, the same certified value and the same anticipated final account, or three different spreadsheets?