Payments/POs over €20,000 Q1 2026

Spending records

Payment date^*	Supplier	Kind	Amount
31 Mar 2026	Production People (Production Operations)	Purchase Order	€20,875.01
31 Mar 2026	Cornflower Limited	Purchase Order	€22,570.50
31 Mar 2026	Strandum Ltd	Purchase Order	€29,987.40
31 Mar 2026	Storage Systems	Purchase Order	€51,824.82
31 Mar 2026	Osborne (Attentius Associates)	Purchase Order	€67,425.15
31 Mar 2026	Hays Specialist Recruitment	Purchase Order	€89,916.85
31 Mar 2026	PFH Technology Group	Purchase Order	€91,286.61
31 Mar 2026	Morgan McKinley	Purchase Order	€116,653.35
31 Mar 2026	Bord Gais Energy	Purchase Order	€123,275.71
31 Mar 2026	Top Security Ltd	Purchase Order	€143,203.71
31 Mar 2026	Electric Ireland	Purchase Order	€146,519.51
31 Mar 2026	Moore Cleaning Services	Purchase Order	€156,583.05

^* 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