Procurement Spend by Category Q4 2017

Spending records

Payment date^*	Description	Kind	Amount
31 Dec 2017	Meter Rollout Programme Only - not for LA	Purchase Order	€32,317.00
31 Dec 2017	Energy Management	Purchase Order	€64,830.00
31 Dec 2017	Regulation & Commercial	Purchase Order	€456,442.00
31 Dec 2017	Customer Support	Purchase Order	€7,157,755.00
31 Dec 2017	Insurance	Purchase Order	€176,319.00
31 Dec 2017	Customer Support	Purchase Order	€550,018.00
31 Dec 2017	Facilities	Purchase Order	€63,935.00
31 Dec 2017	IT Management	Purchase Order	€3,736,187.00
31 Dec 2017	N/A	Purchase Order	€465,815.00
31 Dec 2017	Safety & Integrity	Purchase Order	€61,774.00
31 Dec 2017	Comms and Media	Purchase Order	€1,214,189.00
31 Dec 2017	Professional Consultancy Services	Purchase Order	€2,143,418.00
31 Dec 2017	HR & Training	Purchase Order	€633,679.00
31 Dec 2017	Meters	Purchase Order	€4,402,388.00
31 Dec 2017	C&I	Purchase Order	€800,790.00
31 Dec 2017	Compressors	Purchase Order	€1,992,447.00
31 Dec 2017	Pipelines	Purchase Order	€26,297,092.00
31 Dec 2017	Facilities	Purchase Order	€1,151,438.00
31 Dec 2017	AGI/DRI	Purchase Order	€3,876,855.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