Purchase Orders over €20,000 Q4 2017

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Dec 2017	Arup	Capital - NTA Direct Project Costs	Purchase Order	€23,151.00
31 Dec 2017	Aecom ROD	Options Assessment Study for the Liffey Cycle Route	Purchase Order	€70,520.00
31 Dec 2017	Club Travel	Travel Expenses	Purchase Order	€28,000.00
31 Dec 2017	Tech Skills Resources	Technician Services for Sustainable Transport On-Street	Purchase Order	€69,300.00
31 Dec 2017	CBRE	Rent	Purchase Order	€35,019.00
31 Dec 2017	CAAS	Environmental Consultancy Services in Cork	Purchase Order	€39,000.00
31 Dec 2017	Clifton Scannell Emerson	Celbridge Town Centre Multimodal Improvements at Liffey	Purchase Order	€43,330.00
31 Dec 2017	Irish Life	RPA Pension Scheme	Purchase Order	€26,000.00
31 Dec 2017	Dept of Transport	Pension Fund	Purchase Order	€123,284.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