Purchase Orders Over €20,000 Q2 2017

Spending records

Payment date^*	Supplier	Description	Kind	Amount
30 Jun 2017	BRIAN FITZHARRIS JNR	Construction Costs	Purchase Order	€22,346.15
30 Jun 2017	BRETLAND CONSTRUCTION LTD	Road Maintenance/ Construction	Purchase Order	€108,146.54
30 Jun 2017	APEX SURVEYS LTD	Professional Fees	Purchase Order	€34,237.05
30 Jun 2017	APCOA PARKING IRELAND LTD	Parking Enforcement	Purchase Order	€29,112.56
30 Jun 2017	APCOA PARKING IRELAND LTD	Parking Enforcement	Purchase Order	€26,885.00
30 Jun 2017	APCOA PARKING IRELAND LTD	Parking Enforcement	Purchase Order	€28,758.10
30 Jun 2017	AIRTRICITY UTILITY SOLUTIONS LTD	Utility Charges	Purchase Order	€59,905.63
30 Jun 2017	AIRTRICITY UTILITY SOLUTIONS LTD	Utility Charges	Purchase Order	€75,074.10
30 Jun 2017	AIRTRICITY UTILITY SOLUTIONS LTD	Utility Charges	Purchase Order	€84,648.51
30 Jun 2017	AIRTRICITY UTILITY SOLUTIONS LTD	Utility Charges	Purchase Order	€82,946.83
30 Jun 2017	AGL CONSULTING GEOTECHNICAL ENGINEERS	Professional Fees	Purchase Order	€61,500.00
30 Jun 2017	AECOM Ireland Limited	Construction Costs	Purchase Order	€47,970.00
30 Jun 2017	A & L GOODBODY SOLICITORS	Professional Fees	Purchase Order	€118,449.34

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