Purchase Orders Over €20,000 Q4 2016

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Dec 2016	SirsiDynix	Software Support	Purchase Order	€33,000.00
31 Dec 2016	Airspeed	Telecoms	Purchase Order	€95,000.00
31 Dec 2016	Qualcom	Hardware Maintenance and Support	Purchase Order	€20,000.00
31 Dec 2016	Datapac	Hardware	Purchase Order	€49,000.00
31 Dec 2016	Nel Services	emergency lighing repairs	Purchase Order	€33,755.54
31 Dec 2016	Mythen Construction	instalment no 2. fit out and alteration works carried out	Purchase Order	€65,150.00
31 Dec 2016	Kevin Moore (Building Contractor) Ltd.	Fit out - Kevin Moore	Purchase Order	€31,134.44
31 Dec 2016	Mythen Construction	Instalment no. 3. fit out and alteration works carried out	Purchase Order	€80,324.03
31 Dec 2016	Merit Consulting	Professional services rendered 22.12.15 - 30.03.16	Purchase Order	€27,519.90

^* 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