At a university spread across multiple campuses, a purchasing decision can begin in one department and end in the finance system. Procurement needs to know which supplier agreement applies, how much of its value remains and whether a new order will push spending toward a contract limit. Those answers are difficult to find when contracts are scattered across paper files and individual spreadsheets.
That was the problem facing Atlantic Technological University (ATU), formed in April 2022 when three institutes of technology in western and northwestern Ireland merged. The new university inherited three procurement teams with different working practices and contract registers. Some agreements were stored locally or in hard copy, leaving the central procurement function without a reliable view of commitments and contract spending.
ATU already used Unit4 ERP to handle purchasing transactions. Its challenge was linking that financial activity to the sourcing decisions and supplier agreements that came before it.
Contract References Connect Purchasing to Payments
ATU extended its existing ERP environment with Unit4 Source-to-Contract by Scanmarket, connecting sourcing and contract management with purchase requisitions, orders, invoices, and payments.
The process begins when an approved contract becomes active in Source-to-Contract. Its details are then available within Unit4 ERP, where an employee raising a purchase requisition can select the relevant supplier contract. The contract reference carries through the resulting purchase order, invoice and payment, giving procurement a way to connect actual spending with the agreement that authorized it.
That change removed an earlier step requiring requisitioners to upload tender documents. It also reduced some of the manual reconciliation needed to assemble contract and spending information from separate sources.
Contract, purchase order, invoice and payment records now feed into spend analytics daily. The team can view spending by department, supplier, account code, and contract, including the share of each agreement’s value already used. Also, a practical consequence is the ability to spot an agreement approaching its spending threshold before the procurement team discovers the problem during a later review.
The utilization figure is what lets procurement act early. ATU’s monitoring view marks utilization above 60 percent in amber and above 80 percent in red, which helps staff judge how quickly a contract is being consumed and whether to go back to market early to stay compliant. ATU describes the main gain as catching potential compliance problems at the start of the purchasing process, where previously they risked surfacing only in a retrospective review.
Clean Data and Simpler Requisitions Supported Adoption
Much of the integration depended on work outside the software. ATU had to match historical spending to active contracts using supplier names and account codes, and a clean and suitable chart of accounts made both the integration and the reporting more effective. The university also brought requisitioners and other stakeholders in early.
Early staff involvement helped prevent resistance before the new process went live. Employees also had a practical reason to adopt it, as selecting an approved contract in ERP was simpler than uploading tender documents.
What ATU has built is integration and reporting, and its relevance to future automation lies in the data it now generates: each purchase raised against a contract now carries a recorded link to that agreement.
What This Means for ERP Insiders
Contract-linked transactions are a readiness test for spend automation. Any tool that flags off-contract buying or forecasts renewals, whether rules-based or AI-driven, is only as reliable as the link between each invoice and its agreement. ERP buyers should ask what share of live spend carries a valid contract reference and treat that figure as a go or no-go metric before funding analytics or AI.
Claims of real-time contract visibility need checking against the refresh cycle. Unit4’s case study headlines both real-time contract utilization and a daily spend analytics feed. A day’s lag is harmless on most agreements and costly on one at 79% with large orders queued. Buyers should measure latency from invoice posting to dashboard and ask whether utilization checks can run at requisition approval, where an order can still be stopped.
Supplier master data quality becomes a compliance control. Because ATU matched past spend to contracts by supplier name and account code, duplicate or inconsistently named supplier records would appear directly as gaps in contract utilization. Teams planning similar work should measure how much historical spend they can match to a contract before go-live, since unmatched spend never reaches the alerts.
