Engineering ERP Consultant, UK

How UK engineering contracts shape the ERP

UK engineering work is usually won by tender. The customer issues a specification, often with its own commercial terms or a standard form such as NEC, and expects a priced proposal with a delivery schedule, payment plan and list of deliverables. Once awarded, the contract defines when you can invoice, how much is retained until completion and how variations are instructed and valued.

That has direct consequences for system design. Billing cannot simply follow dispatch. It has to follow events: order placement, drawing approval, delivery of major items, factory acceptance, site completion and the end of the defects period. Each application for payment needs backing from the job record, and finance needs to see retention held by customer and when it falls due.

Where your team also installs equipment on site, part of that site work could come under the Construction Industry Scheme, with its own rules on paying and reporting subcontractors. Whether it applies is a question for your accountant. Either way, I check that the ERP can support the outcome, with supplier flags and payment records in place if needed.

I capture these terms early in the requirements work, because a platform that bills well on dispatch can still struggle with staged applications and retention.

Strategic export controls and controlled technical data

Many British engineering firms supply equipment, components or design work that can fall under UK strategic export controls, either as military items or as dual-use goods and technology. Licensing decisions belong to your export compliance lead and advisors, and I do not interpret the control lists. Yet the ERP is where those decisions either hold or quietly fail.

Requirements I commonly include for UK engineering clients:

• A control status and list reference held against items, assemblies and drawing records, copied automatically onto quotes and orders.
• License numbers and conditions stored against the customer order, with end-user and consignee details captured at order entry.
• A dispatch block on controlled items until the compliance lead confirms a valid license or exemption.
• Restrictions on sending controlled drawings to overseas suppliers or subcontract designers without approval.
• Reports listing controlled shipments for internal audits.

None of this replaces a compliance program. It simply means the right check happens at the right step, even when the person who knows the rules is on leave. Where a platform needs an add-on or a light customization for these holds, I make that visible in the gap analysis before you commit.

Inspection plans, material certificates and the data book

Customers buying engineered equipment in the UK, especially in energy, water, rail and defense, rarely accept it on trust. They issue an inspection and test plan with hold points and witness points, appoint their own inspector or a third-party agency, and expect a complete manufacturing record at handover.

Material certificates sit at the center of that record. Steel plate, pipe, forgings and fasteners often arrive with inspection documents issued to EN 10204, identified by heat or cast number. If those certificates are scanned into a shared folder with no link to what was received and where it was used, compiling the data book becomes a week of detective work at the end of the job.

In the ERP, I specify:

• Certificate capture at goods receipt, linked to the batch or heat number.
• Traceability from received material to the works order and the delivered assembly.
• Inspection steps on works orders that cannot be closed until a hold point is released.
• Nonconformance records tied to the job, with rework cost captured.
• A data book index generated from the job, not assembled by hand.

These requirements are tested during UAT with real certificates from a past contract.

Drawing issues, variations and development time

British engineering teams talk about drawing issues and revision letters, and the ERP has to respect that language. A drawing released at revision B for manufacture, then reissued at revision C after a customer comment, must update the parts and BOM in the system and show which purchase orders and works orders were raised against B.

I agree with your engineering manager where design data lives and when it crosses into the ERP. Usually CAD or PDM remains the master for design in progress, and a formal release creates or updates items in the ERP. An approved change then follows one of two routes: a customer variation, priced and added to the contract value, or an internal correction, costed against the job so margin erosion is visible.

Engineering time deserves the same care. Hours booked by job and activity give accurate job cost, and they also give your accountants cleaner evidence when they consider an R&D tax relief claim for development work. Eligibility and the claim itself are for your accountants. I simply make sure timesheet categories distinguish routine design from development and testing, without asking engineers to fill in long forms. The detail goes into the solution design so the configuration follows it.

Leaving Sage and spreadsheets, and working remotely

The starting point for most UK engineering firms I talk to is Sage for accounts, a job costing spreadsheet per contract, a CAD vault and a quality folder structure maintained by one diligent person. Some run an older manufacturing package that handles works orders but has no real link to contracts or stage payments.

Migration is planned around live contracts. Each one moves across with its contract value, approved variations, budget, committed orders, cost to date, applications made, retention held and remaining stages. Completed contracts stay in the legacy system, archived for reference, unless warranty claims need them in the new one.

On platforms, the right answer depends on how much you manufacture versus design. I look at whether project control or production depth matters more, then test both with the same contract scenario. If your business is closer to repeat production, my UK manufacturing ERP page covers that model, and the broader engineering ERP overview explains the engineer-to-order approach.

All work is remote: video workshops, shared requirement documents and recorded walkthroughs, with UK hours easy to overlap. For how engagements are structured, read about my ERP consulting for British businesses or start from the United Kingdom overview.