Purchase Orders Over €20,000 Q3 2012

Spending records

Payment date^*	Supplier	Description	Kind	Amount
30 Sep 2012	Bearing Point	Bearing Point - Architect,	Purchase Order	€48,879.59
30 Sep 2012	Bearing Point	Bearing Point,	Purchase Order	€23,646.75
30 Sep 2012	Accenture	Accenture - Aug Deliverables,	Purchase Order	€257,928.54
30 Sep 2012	Bearing Point	Bearing Point - Peoplesoft,	Purchase Order	€44,710.50
30 Sep 2012	Precisely Software	TrilliumSupport 29/9/12-28/9/13,	Purchase Order	€74,953.00
30 Sep 2012	Accenture	Review of Central Procurement,	Purchase Order	€30,750.00
30 Sep 2012	Accenture	HRSSC Consulting May-Jul 2012,	Purchase Order	€773,786.85
30 Sep 2012	O.P.W. Building and	OPW Clonskeagh,	Purchase Order	€400,000.00
30 Sep 2012	Willis Risk Services	First Premium Nat. Proc. Serv,	Purchase Order	€26,149.03
30 Sep 2012	Arkphire (Zinopy	Dual ironport Web Filter Renew,VAT,	Purchase Order	€23,873.07

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