Purchase Orders Over €20,000 Q4 2025

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Dec 2025	HENRY MANAGEMENT SERVICES LTD.	Security Services	Purchase Order	€29,520.00
31 Dec 2025	CUNNINGHAM CONTRACTS IRE LIMITED	Capital Contracts Construct Payments	Purchase Order	€123,888.32
31 Dec 2025	Guardian24 LTD t/a Peoplesafe	ICT & Data Service	Purchase Order	€34,068.00
31 Dec 2025	PROVIDENT CRM LIMITED	Computer Software and Maintenance Fees	Purchase Order	€21,918.60
31 Dec 2025	HENRY MANAGEMENT SERVICES LTD.	Security Services	Purchase Order	€29,520.00
31 Dec 2025	HENRY MANAGEMENT SERVICES LTD.	Security Services	Purchase Order	€29,520.00
31 Dec 2025	HENRY MANAGEMENT SERVICES LTD.	Security Services	Purchase Order	€29,520.00
31 Dec 2025	INTERNATIONAL EDUCATION SERVICES	Library Book Purchase	Purchase Order	€20,931.10

^* Payment date may be the end of the reporting quarter when the entity does not publish an exact date.

How to read these figures

These are reported values from published purchase order and payment records — not verified cash paid, and not total spending by this organisation. A row may be a purchase order, a payment, or another reported transaction; the source files often do not say which.

Coverage and quality vary. Some fields are blank, supplier names are free text (the same firm can appear under many labels), and descriptions are inconsistent rather than a controlled taxonomy. An amount alone says nothing about value for money and it may or may not include VAT.

Records are retrieved from each organisation’s published files such as spreadsheets, PDFs, and other formats of uneven quality. Extraction techniques (including automated parsing) can introduce gaps, misreads, or incomplete rows when source layout or quality is poor. Treat the data as a starting point for investigation, not a definitive ledger.

Here is a project that encountered similar issues