Purchase Orders Over €20,000 Q1 2020

Spending records

Payment date^*	Supplier	Description	Kind	Amount
26 Mar 2020	Orange Recruitment Ltd.	Temporary Staff	Purchase Order	€36,547.00
25 Mar 2020	Client Solution	IT Consultants	Purchase Order	€24,080.00
10 Mar 2020	Evros	IT Consultants	Purchase Order	€106,549.00
10 Mar 2020	Datapac	Computer Equipment	Purchase Order	€25,695.00
25 Feb 2020	IT Force	IT Consultants	Purchase Order	€54,612.00
12 Feb 2020	IT Force	IT Consultants	Purchase Order	€45,510.00
12 Feb 2020	CPL SOLUTIONS	IT Consultants	Purchase Order	€135,915.00
04 Feb 2020	Core International	Annual Software Licences	Purchase Order	€36,162.00
31 Jan 2020	Micromail	Annual Software Licences	Purchase Order	€41,467.00
27 Jan 2020	WILLIS Risk Services (Ireland) Ltd.	Insurance	Purchase Order	€58,118.83
14 Jan 2020	Fineprint	Publications	Purchase Order	€143,713.20
13 Jan 2020	IMI	Staff Learning Development	Purchase Order	€27,675.00

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