Payments or Purchase Orders Q2 2017

Spending records

Payment date^*	Description	Kind	Amount
30 Jun 2017	Utilities	Purchase Order	€10,603,153.00
30 Jun 2017	Regulatory Fees & Charges	Purchase Order	€656,135.00
30 Jun 2017	Environmental & Safety Services	Purchase Order	€705,546.00
30 Jun 2017	HR & Training	Purchase Order	€205,921.00
30 Jun 2017	Sludge & Waste Services	Purchase Order	€887,001.00
30 Jun 2017	ICT & Communications & Marketing & Legal	Purchase Order	€7,649,756.00
30 Jun 2017	Facilities Management & Offices Services	Purchase Order	€2,103,226.00
30 Jun 2017	Field Operations Support Services	Purchase Order	€1,594,992.00
30 Jun 2017	Customer Services Support	Purchase Order	€4,083,103.00
30 Jun 2017	Construction & Civil Work & Engineering Services	Purchase Order	€61,098,181.00
30 Jun 2017	Managed Services - SLA Payments to LA's	Purchase Order	€81,520,484.00
30 Jun 2017	Managed Services - DBO Operations	Purchase Order	€19,746,795.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