Purchase Orders Over €20,000 Q3 2014

Spending records

Payment date^*	Supplier	Description	Kind	Amount
30 Sep 2014	PeoplePoint	PeoplePoint Service Charge 2014 Jul – Dec 14	Purchase Order	€20,982.00
30 Sep 2014	Tusla	Contribution to costs for Children Services Committee Co-ordinate Kildare	Purchase Order	€22,167.00
30 Sep 2014	Irish Prison Service	Funding for Solas Project	Purchase Order	€25,000.00
30 Sep 2014	Young Social	Partner Programme with Young Social Innovators Innovators for 2014/15	Purchase Order	€35,000.00
30 Sep 2014	Perrem Design	Electronic Locks for Oberstown Childhood Programme Jul - Dec 2014 Hardware	Purchase Order	€48,613.24
30 Sep 2014	POBAL	External Service Delivery re. Area Based Programmes Oct – Dec 14	Purchase Order	€80,000.00
30 Sep 2014	POBAL	External Service Delivery re. Childcare	Purchase Order	€1,400,000.00
30 Sep 2014	POBAL	External Service Delivery re. Childcare Programmes July – Sept 14	Purchase Order	€1,400,000.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