Purchase Orders Over €20,000 Q4 2025

Spending records

Payment date^*	Description	Kind	Amount
31 Dec 2025	Capital	Purchase Order	€3,146,040
31 Dec 2025	Communication Circuits	Purchase Order	€603,885
31 Dec 2025	Computing	Purchase Order	€10,753,707
31 Dec 2025	Direct acquired programme costs	Purchase Order	€8,441,214
31 Dec 2025	Direct commissioned programme costs	Purchase Order	€9,058,681
31 Dec 2025	Insurance policies	Purchase Order	€1,244,241
31 Dec 2025	Maintenance, rates, rent & other property related	Purchase Order	€2,154,934
31 Dec 2025	Marketing and promotional activities	Purchase Order	€1,414,765
31 Dec 2025	Other personnel related costs (including contractors)	Purchase Order	€1,412,201
31 Dec 2025	Other third-party costs	Purchase Order	€16,784,591
31 Dec 2025	Outside Broadcast Contracts	Purchase Order	€1,376,819
31 Dec 2025	Sports and other copyrights	Purchase Order	€27,502,894
31 Dec 2025	Staff travel and subsistence	Purchase Order	€637,653

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