Purchase Orders Over €20,000 Q4 2013

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Dec 2013	Digiweb	Bandwidth – Annual value	Purchase Order	€53,505.00
31 Dec 2013	PriceWaterhouseCoopers	Strategy and Funding options	Purchase Order	€28,290.00
31 Dec 2013	NCAD	Future Creators project	Purchase Order	€35,000.00
31 Dec 2013	J.L.E Limited	Electrical works – Depot 2	Purchase Order	€59,747.00
31 Dec 2013	H2	Sept-Dec Learning Support	Purchase Order	€24,333.00
31 Dec 2013	H2	Future Creators project	Purchase Order	€31,000.00
31 Dec 2013	H2	Schools Broadband exemplar project	Purchase Order	€104,000.00
31 Dec 2013	Formula Network Limited	IT service providers – Annual contract	Purchase Order	€102,150.00
31 Dec 2013	David Savage Plumbing	Mechanical works	Purchase Order	€29,283.00
31 Dec 2013	Burns Construction	Construction work – Thomas street	Purchase Order	€47,306.00
31 Dec 2013	BHA Construction	Gatelodge minor works	Purchase Order	€87,435.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