Purchase Orders Over €20,000 Q1 2016

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Mar 2016	Viatel Ireland	Bandwidth for Digital Hub	Purchase Order	€21,402.00
31 Mar 2016	Software Design	Website Redevelopment	Purchase Order	€51,291.00
31 Mar 2016	H2	Future Creators Project	Purchase Order	€42,869.00
31 Mar 2016	Acacia Facilities Management	H&S Officer	Purchase Order	€26,372.00
31 Mar 2016	Acacia Facilities Management	Operations Administration supp	Purchase Order	€46,586.00
31 Mar 2016	Acacia Facilities Management	Property Project Management	Purchase Order	€70,247.00
31 Mar 2016	Acacia Facilities Management	Derelict Sights Monthly costs	Purchase Order	€58,501.00
31 Mar 2016	Acacia Facilities Management	Emergency Works	Purchase Order	€24,600.00
31 Mar 2016	Acacia Facilities Management	Unscheduled Works/Callouts	Purchase Order	€61,500.00
31 Mar 2016	Acacia Facilities Management	FM Fixed Cost 2016	Purchase Order	€1,016,473.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