Payments/POs over €20,000 Q4 2020

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Dec 2020	Crowe Horwath	Consultancy	Purchase Order	€21,175.00
31 Dec 2020	Domino People Limited	Lotus Notes Licences	Purchase Order	€23,548.00
31 Dec 2020	Arkphire	Citrix	Purchase Order	€25,773.00
31 Dec 2020	National Shared Services Office	HR Shared Service	Purchase Order	€27,194.00
31 Dec 2020	Mazars	Outsourcing of Audit Work	Purchase Order	€33,118.00
31 Dec 2020	Datapac	IT Equipment	Purchase Order	€36,249.00
31 Dec 2020	Datapac	IT equipment	Purchase Order	€36,249.00
31 Dec 2020	Image Supply Systems	Video Conferencing	Purchase Order	€66,473.00
31 Dec 2020	Wolters Kluwer UK Ltd	Teammate Licence	Purchase Order	€68,778.00
31 Dec 2020	CDW Limited	Microsoft SQL Server	Purchase Order	€81,960.00
31 Dec 2020	CDW Limited	Microsoft Licences	Purchase Order	€82,611.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