Payments Over €20,000 Q1 2014

Spending records

Payment date^*	Supplier	Description	Kind	Amount
31 Mar 2014	AN POST	Up to 50g registraton x 2000 30/01/14	Purchase Order	€21,000.00
31 Mar 2014	ENTERPRISE REGISTRY SOLUTIONS LTD	Fee for System Development & Administration Servic	Purchase Order	€23,694.72
31 Mar 2014	ORACLE EMEA LIMITED	SOFTWARE UPDATE LICENCE & SUPPORT 28/3/14-27/3/15	Purchase Order	€27,285.59
31 Mar 2014	ENTERPRISE REGISTRY SOLUTIONS LTD	Fee for System Development & Administration Servic	Purchase Order	€27,873.03
31 Mar 2014	ENTERPRISE REGISTRY SOLUTIONS LTD	Fee for System Development & Administration Servic	Purchase Order	€37,023.00
31 Mar 2014	ENTERPRISE REGISTRY SOLUTIONS LTD	Fee for System Development & Administration Servic	Purchase Order	€75,103.80
31 Mar 2014	ENTERPRISE REGISTRY SOLUTIONS LTD	Fee for System Development and Administration Serv	Purchase Order	€81,794.38

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