Purchase Orders Over €20,000 Q3 2018

Spending records

Payment date^*	Supplier	Description	Kind	Amount
20 Sep 2018	DBFL Consulting Engineers	Professional Services	Purchase Order	€51,955.20
07 Sep 2018	Noonan	Professional Services	Purchase Order	€28,651.08
05 Sep 2018	Grafton Recruitment Ltd	Professional Services	Purchase Order	€25,922.99
04 Sep 2018	Sean Quigley Contracts Ltd	Construction Works	Purchase Order	€216,614.48
31 Aug 2018	Duff & Phelps	Professional Services	Purchase Order	€35,780.70
23 Aug 2018	Ernst & Young	Professional Services	Purchase Order	€30,750.00
27 Jul 2018	Sherwood Systems Ltd	Professional Services	Purchase Order	€31,024.29
24 Jul 2018	Kennedy Security & Consultancy	Professional Services	Purchase Order	€55,591.70
18 Jul 2018	W S Atkins Ireland Ltd	Professional Services	Purchase Order	€38,591.25
18 Jul 2018	DBFL Consulting Engineers	Professional Services	Purchase Order	€227,783.70
18 Jul 2018	WH Stephens	Professional Services	Purchase Order	€246,246.00
18 Jul 2018	BDP Consulting Engineers	Professional Services	Purchase Order	€501,550.95
18 Jul 2018	McCullough Mulvin Architects	Professional Services	Purchase Order	€1,442,104.89

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