Purchase Orders Over €20,000 Q1 2022

Spending records

Payment date^*	Supplier	Description	Kind	Amount
15 Mar 2022	Core International	Annual Software Licences	Purchase Order	€44,587.50
10 Mar 2022	CPL SOLUTIONS	Temporary Staff	Purchase Order	€70,688.00
08 Mar 2022	Eir EVO	IT Consultants	Purchase Order	€112,176.00
07 Mar 2022	Kevin Burke	Consultant Fees	Purchase Order	€24,000.00
16 Feb 2022	Below the Line Training	Staff Learning Development	Purchase Order	€28,536.00
11 Feb 2022	Indiepics	Training Video	Purchase Order	€24,705.00
02 Feb 2022	CPL SOLUTIONS	IT Consultants	Purchase Order	€147,600.00
18 Jan 2022	Eir EVO	IT Consultants	Purchase Order	€135,300.00
18 Jan 2022	Eir EVO	IT Consultants	Purchase Order	€95,940.00
12 Jan 2022	Micromail	Annual Software Licences	Purchase Order	€59,535.00
11 Jan 2022	Micromail	Multi-annual Software Licences	Purchase Order	€40,171.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