Purchase Orders over €20,000 - Q1 2018

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Mar 2018	TOM MCNAMARA & PARTNERS	Contract Payment	Purchase Order	€29,134.00
31 Mar 2018	FLAGSHIP MARITIME CONSULTANTS LTD	Contract Payment	Purchase Order	€44,290.00
31 Mar 2018	BUCHOLZ MCEVOY ARCHITECTS LTD	Contract Payment	Purchase Order	€71,451.00
31 Mar 2018	STEPHEN FINN ( CONTRACTORS ) LTD	Contract Payment	Purchase Order	€20,919.00
31 Mar 2018	FINN BROS KILDYSART LTD	Contract Payment	Purchase Order	€22,700.00
31 Mar 2018	ML & S BOLAND CIVIL ENGINEERING LTD	Contract Payment	Purchase Order	€30,753.00
31 Mar 2018	WARD AND BURKE CONSTRUCTION LTD	Contract Payment	Purchase Order	€32,309.00
31 Mar 2018	JADA PROJECTS	Contract Payment	Purchase Order	€35,930.00
31 Mar 2018	JADA PROJECTS	Contract Payment	Purchase Order	€66,093.00
31 Mar 2018	SYLVIE MULLINS PLANT HIRE LTD	Contract Payment	Purchase Order	€72,024.00
31 Mar 2018	KENNY CIVILS AND PLANT LTD	Contract Payment	Purchase Order	€76,009.00
31 Mar 2018	SCOPE TECHNOLOGY SOLUTIONS LTD	Contract Payment	Purchase Order	€21,225.00
31 Mar 2018	CIARAN SUDWAY & ASSOCIATES LTD	Contract Payment	Purchase Order	€29,520.00
31 Mar 2018	CIARAN SUDWAY & ASSOCIATES	Contract Payment	Purchase Order	€24,720.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