Payments over €20,000 Q3 2019

Spending records

Payment date^*	Supplier	Description	Kind	Amount
30 Sep 2019	Micromail	Circuit Court Appeals June 19 Y	Purchase Order	€73,984.75
30 Sep 2019	Public Appointment Services	Recruitment Campaigns New Panels Y	Purchase Order	€59,964.54
30 Sep 2019	Capita	Data Transformation Y	Purchase Order	€39,975.00
30 Sep 2019	Version 1	Support 01/08-31/010 Y	Purchase Order	€23,308.50
30 Sep 2019	Capita	Q4 2019 Maintenance Charge Y	Purchase Order	€25,368.75
30 Sep 2019	Dell (Ireland)	Computer Hardware Y	Purchase Order	€25,958.57
30 Sep 2019	Office of Public Works	Service Charge Waterloo Exchange 01/10/19-31/12/19 Y	Purchase Order	€20,302.10
30 Sep 2019	Office of Public Works	Rent Waterloo Exchange 24/09-23/12 Y	Purchase Order	€112,291.04
30 Sep 2019	Dept of Justice Equity & Law Reform	Secondment Q3 Y	Purchase Order	€38,485.46

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