Payments/POs over €20,000 Q2 2016

Spending records

Payment date^*	Supplier	Description	Kind	Amount
30 Jun 2016	ESB	Utility	Purchase Order	€25,869.76
30 Jun 2016	ESB	Utility	Purchase Order	€26,109.66
30 Jun 2016	ESB	Utility	Purchase Order	€27,425.25
30 Jun 2016	Synergy Security Solutions	Security	Purchase Order	€31,572.80
30 Jun 2016	Synergy Security Solutions	Security	Purchase Order	€32,484.67
30 Jun 2016	Synergy Security Solutions Ltd	Security	Purchase Order	€36,951.06
30 Jun 2016	Scala Arts & Heritage Publishers Limited	Publishers	Purchase Order	€45,696.10
30 Jun 2016	Scala Arts & Heritage Publishers Limited	Publishers	Purchase Order	€38,589.00
30 Jun 2016	Indecon	Assessment (Part Payment)	Purchase Order	€29,467.72
30 Jun 2016	Indecon	Assessment	Purchase Order	€88,403.18

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