Moving construction procurement from spreadsheets to an ERP

The spreadsheet procurement problem

Every construction company starts with spreadsheets. They are fast, flexible, and familiar. But as projects scale, the cracks show:

• No approval trail. A purchase order approved over WhatsApp has no record attached to it. When the auditor asks who approved a 200k AED material order, nobody can point to a timestamp.
• Version confusion. Three people have different versions of the vendor comparison sheet. The PO was issued against the wrong prices.
• No connection to finance. The procurement team issues POs, but finance only sees invoices. The gap between what was ordered and what was billed is invisible until month-end.
• No goods receipt verification. Materials arrive on site, but nobody records whether the quantities match the PO. Overpayments go unnoticed.

This is not a failure of discipline — it is a failure of systems. Spreadsheets were never designed to enforce workflow controls.

What a proper procurement chain looks like

In a governed procurement system, every step connects to the next:

Step 1: Material request

A site engineer submits a material request specifying what is needed, for which project, and by when. The request links to the project and optionally to a BOQ assembly.

Step 2: Approval

The material request routes through an approval workflow based on value thresholds. Requests above a certain amount require manager or director approval. The system enforces this automatically.

Step 3: RFQ to vendors

The approved request converts to an RFQ sent to selected vendors. Vendors submit quotes against the same line items, making comparison straightforward.

Step 4: Quote comparison

Vendor quotes are compared side by side with quote comparison tools. The system highlights price differences, delivery terms, and compliance with specifications. No more manual Excel comparisons.

Step 5: Purchase order

The selected vendor quote converts to a purchase order that references the original material request, the RFQ, and the approved quote. The PO goes through its own approval workflow.

Step 6: Goods receipt

When materials arrive, the warehouse team records a goods receipt against the PO. Quantities are verified. Discrepancies are flagged immediately.

Step 7: Vendor invoice and payment

The vendor bill is matched against the PO and goods receipt — a three-way match. Discrepancies block payment until resolved. Approved bills enter payment runs.

The before and after

How to migrate without disruption

You do not need to change everything on day one. Here is a practical migration path:

Week 1-2: Start with purchase orders

Begin by creating POs in the system instead of spreadsheets. Keep everything else the same for now. This gives you a digital record of every order with approval tracking.

Week 3-4: Add material requests

Move the upstream process into the system. Site engineers submit material requests digitally, with approval routing. Approved requests convert to POs.

Month 2: Add vendor quoting

Start sending RFQs through the system and comparing quotes digitally. This eliminates the most error-prone manual step.

Month 3: Add goods receipt and three-way match

Close the loop by recording goods receipts against POs and matching vendor invoices. This is where the real savings appear — catching discrepancies before payment.

What AI can do (and what it should not)

AI can extract line items from vendor quote PDFs, flag price anomalies, and draft purchase orders. But AI should not approve spending autonomously.

The right model is assist, then approve: AI prepares the work, a human reviews and approves. Every AI action has an audit trail, a confidence score, and a safe rerun mechanism.

Related: AI procurement agent

Get started

The procurement chain is the best starting point for any construction ERP migration. It has the highest ROI, the most visible pain, and the clearest success metrics (cycle time, approval speed, discrepancy rate).

Start a 14-day trial or book a walkthrough.