Payments Over €20,000 Q1 2020

Spending records

Payment date^*	Supplier	Kind	Amount
12 Mar 2020	Qualcom Systems Ltd IT Managed Services	Purchase Order	€20,229.66
12 Mar 2020	Yellow Wood Energy Consulting Professional Services	Purchase Order	€31,512.00
06 Mar 2020	Qualcom Systems Ltd IT Managed Services	Purchase Order	€34,273.95
06 Mar 2020	Gutteridge Haskins & Davey Ltd Professional Services	Purchase Order	€98,877.72
27 Feb 2020	Baringa Ireland Ltd Professional Services	Purchase Order	€24,020.22
20 Feb 2020	GH Investments Ltd Rent and Managed Services	Purchase Order	€102,983.25
14 Feb 2020	DNV GL Limited Professional Services	Purchase Order	€33,026.10
07 Feb 2020	Benchmark Property Rent and Managed Services	Purchase Order	€30,529.80
07 Feb 2020	South Dublin County Council Rates	Purchase Order	€32,333.40
24 Jan 2020	GL Industrial Services UK Ltd Professional Services	Purchase Order	€45,062.09
10 Jan 2020	HR Wallingford Ltd Professional Services	Purchase Order	€24,000.00
10 Jan 2020	Cambridge Economic Policy Ass. Professional Services	Purchase Order	€24,302.63
10 Jan 2020	Mason Hayes & Curran Legal Services	Purchase Order	€45,911.11

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