Research Ireland Grant Cost Claims: Invoice Evidence

A Research Ireland grant cost claim should start from the Letter of Offer, the approved budget and the Grant Budget Policy, then tie each supplier invoice to an eligible direct-cost category, a grant or sub-account code, a purchase order or procurement reference where relevant, and the matching ledger transaction. Invoice extraction helps by turning invoice PDFs and images into a reviewable evidence register, but eligibility still belongs with the Research Finance Office, the PI review route and the award conditions.

That distinction matters in Irish higher education because the invoice is only one part of the claim. It proves that a supplier billed the institution for a stated good or service. It does not, by itself, prove that the charge sits inside the approved budget, falls within the eligible period, followed the correct procurement route, or belongs wholly to one Research Ireland award.

For a Research Finance Officer, the working question is usually narrower than "is this grant managed properly?" The question is: can a reviewer move from a cost-statement line to the exact supplier invoice, the PO or approval trail, the ledger coding and the budget heading without reconstructing the file from the AP archive?

The source hierarchy should be visible before the first invoice is reviewed. Start with the Letter of Offer, the approved budget, the General Terms and Conditions, the relevant Research Ireland policy or programme guidance, and any legacy SFI or IRC conditions that still apply to the award. Then add the local HEI controls that govern purchasing, approvals, retention, VAT handling and document storage. If those sources conflict in practice, the evidence file should show which condition was applied and who approved the treatment.

The practical evidence trail has five parts:

• The finance-system record, usually from Agresso, Unit4 or another ledger system, showing the transaction, grant code, account code, period and amount.
• The supplier invoice, with supplier identity, invoice number, date, VAT detail, line descriptions and totals.
• The budget-category mapping, showing why the cost belongs under materials, equipment, travel, access charges, publication costs or another category in the approved budget.
• The procurement and approval evidence, such as the PO, quotation record, tender reference, framework drawdown or local approval note.
• The review record, showing exceptions, split allocations, PI review and Research Finance sign-off.

This is the gap official guidance usually leaves for practitioners. Research Ireland pages define the policy surface, and HEI pages describe cost statements and audits, but the operational handover between invoice PDFs, ledger reports and audit files is usually left to internal practice. A useful grant file closes that gap by making every claimed supplier-side cost traceable from the statement total back to the source document and the rule that made it claimable.

Eligible direct costs need more than a supplier invoice

The controlling test for supplier-side evidence is identification, not just possession. The Research Ireland Grant Budget Policy states that eligible direct costs are costs that can be uniquely and unambiguously identified with a particular Research Programme. A supplier invoice helps satisfy that test only when it can be matched to the award, the budget heading, the period of activity and the institution's own approval route.

For materials and consumables, the invoice evidence usually does most of the documentary work. Lab supplies, reagents, glassware, specialist parts and similar purchases should have a supplier name, invoice number, VAT detail where charged, line descriptions, net and gross amounts, PO reference if used, and enough description to connect the purchase to the approved work. A line that says "laboratory consumables" may be acceptable in AP processing, but it is weak audit evidence if the grant file cannot show what was bought and why it belongs to the project.

Equipment needs a heavier trail. The invoice shows supplier, cost and item description, but the grant file may also need the approved budget line, capitalisation treatment, asset-register entry, delivery or installation evidence, and any approval for shared or partial use. Where one item is allocated across several grants or cost centres, the invoice should stay intact and the register should show the split basis rather than hiding the allocation inside a single summary amount.

Travel and subsistence supplier charges are mixed evidence cases. A conference registration invoice, hotel invoice or flight supplier invoice supports the cost, but the file also needs the travel approval, attendee or PI link, event purpose, dates and any local travel-policy checks. Receipts and expense-claim records may sit beside supplier invoices rather than replace them.

Contract research, access charges and specialist service invoices need the clearest description of what service was delivered. The file should connect the supplier's work to the approved programme activity, preserve any contract or statement of work, and flag procurement evidence where the value or institutional rules require it. Publication charges and article processing charges are similar: the invoice is necessary, but the file should also show the publication, author or project link, and whether the cost was allowed under the award terms.

Personnel costs sit outside this supplier-invoice model. Salary, stipend, secondment and payroll-led costs need HR, payroll, timesheet or employment records rather than invoice extraction. The same boundary applies when someone searches for an SFI grant cost claim Ireland or an IRC grant cost claim Ireland: older awards may still require supplier invoices for purchased goods and services, but payroll evidence remains a separate workstream under the award's original conditions.

Indirect costs and overheads need a different boundary again. They are not substantiated invoice by invoice. The support is usually the approved rate, the award or policy basis for applying it, the calculation against eligible direct costs where applicable, and the institution's sign-off. Mixing overhead calculation support into the supplier-invoice register makes the file harder to review because it suggests every claimed amount should have a supplier document behind it.

Build a cost-statement register that reviewers can trace

The cost-statement register is the join between the ledger report and the source documents. The ledger proves that a transaction was posted to a grant code. The invoice proves what the supplier billed. The register explains why those two records belong together and how the cost should be read against the Research Ireland award.

A useful register is not a copy of the AP export with a few extra columns. It should carry the fields a reviewer will use to test the claim line without opening several systems:

• Grant code or sub-account
• Budget category
• Ledger transaction ID or journal reference
• Supplier name
• Invoice number
• Invoice date
• PO number or purchasing reference
• Procurement reference where relevant
• VAT treatment
• Net, VAT and gross amount
• Currency
• Source file name
• Page reference
• Reviewer or preparer
• Exception notes

The source file and page reference deserve their own fields. If an audit query asks for the invoice behind a materials cost, the Research Finance Office should not have to search a shared AP folder, download a batch PDF, or ask the PI which copy was used. A file reference such as the original PDF name, together with the page number for multi-page documents, makes the evidence pack navigable.

Split allocations need careful treatment. If one supplier invoice covers two Research Ireland awards, or one grant and one departmental cost centre, the register should split the claim into separate lines while preserving the same invoice number and source file reference. The allocation basis should be visible: percentage split, line-item split, lab usage note, PI approval, or another institutionally approved method. Without that note, the register shows arithmetic but not judgement.

Exception handling is where many evidence packs become hard to review. A missing PO should be marked as an exception, not left blank. A vague line description should carry a note explaining the supporting documentation used to identify the cost. A supplier name mismatch between PO and invoice should be reconciled. A credit note should be linked to the original invoice and shown with the correct sign. Foreign-currency invoices should preserve the original currency and the euro value used in the ledger, with the conversion basis available if the institution requires it.

The register does not need to decide every accounting question. Its job is to make the cost statement readable: one row per claimable evidence line, clear references back to the source documents, and enough review notes for Research Finance, the PI and any audit team to understand what was claimed.

Procurement evidence travels with the invoice

Procurement evidence should sit beside the supplier invoice when the purchase route is relevant to the claim. The invoice shows that the institution was charged. Procurement evidence shows how the institution committed to the spend.

Older threshold shorthand is easy to misread. The current public-procurement layer is not a blanket Research Ireland rule at EUR 25,000 or EUR 144,000. The Irish Government's OGP thresholds page says goods and services contracts are advertised on eTenders from EUR 50,000 exclusive of VAT, with 2026 EU thresholds at EUR 140,000 for Government Departments and Offices and EUR 216,000 for local, regional and other public bodies. HEIs may also impose lower internal quotation, approval or purchase-order controls through local policy.

For the grant evidence pack, the safest treatment is to make the applicable procurement route visible at the invoice line. That does not mean reproducing the Public Spending Code in the cost claim. It means preserving the pieces a reviewer needs to understand why the purchase was made through that route:

• PO number and approval trail
• Quotation record or quote comparison where local rules require it
• Tender or RFT reference
• Framework or mini-competition reference
• Award decision or evaluation note
• Contract, drawdown or call-off reference
• Exception approval where the normal route was not used

The procurement field in the register can be concise. "PO 45621, MSF drawdown, contract ref X" is more useful than a separate folder of procurement files with no link to the invoice. The point is to let the reviewer move from the claimed cost to the supplier invoice and then to the purchasing route without guessing which tender, quotation or framework file belongs to that transaction.

Local HEI controls matter because a Research Ireland grant is still being spent through a public institution's finance environment. An invoice below the eTenders advertising threshold may still require quotations, budget-holder approval or a purchase order under local policy. Conversely, a high-value item should not be treated as claim-ready just because the supplier invoice is complete. The invoice and the procurement file answer different questions.

For Research Ireland grant audit documentation, this separation is useful. The audit file does not need to turn every purchase into a procurement essay. It should show that the invoice amount being claimed is supported by the correct purchasing evidence for the value, category, source of funds and institutional policy that governed the commitment.

Assemble the grant audit file around the ledger report

The ledger report is the spine of the Research Ireland evidence pack. Agresso, Unit4 or another finance system will show the grant code, transaction date, account code, supplier, posted value and period. The audit file then needs to make the source evidence available in the same order a reviewer will test it.

A practical structure starts with the grant-ledger extract and the cost-statement register, then stores the supporting documents by budget category or by register reference. Materials and consumables sit with their supplier invoices and PO records. Equipment lines sit with supplier invoices, asset-register entries and capitalisation support where required. Travel and subsistence lines sit with invoices, receipts, approval records and event evidence. Publication costs sit with publisher invoices and the article or output reference. Contract research and access-charge lines sit with the supplier invoice and the contract, statement of work or service evidence.

Where procurement evidence applies, it should not live in a disconnected folder named "tenders". The register should point to the RFT, framework, quotation or approval record that belongs to the specific invoice. This is especially important when one supplier appears repeatedly across a centre, lab or school. The supplier name alone will not tell a reviewer which approval route applied to which purchase.

Research Centres and Industry Partner cost share add another layer. A supplier invoice from a third party is one evidence type. A secondment agreement, in-kind valuation, partner contribution record or matched-funding schedule is another. They may all support the same centre or programme, but they should not be treated as interchangeable. The audit file should identify the contribution type, the supporting record, the valuation or amount and the person responsible for review.

This evidence-pack shape will feel familiar to teams working across Irish higher-education funding streams. For example, Springboard+ marketing cost evidence per programme has a similar document-assembly problem, but the funder rules, eligible costs and claim language are different. The useful crossover is the discipline: keep the source document, claim line, budget category and review decision close together.

Reporting and retention should be handled from the award documents and institutional policy, not from a single assumed rule. Some awards need periodic, annual, final or progress reporting; some audits arise at close-out or after a funder query. The file structure should be stable enough that a future reviewer can reconstruct the claim from the ledger extract, source invoices, procurement evidence, cost-share support and sign-off records without relying on the memory of the person who assembled it.

---

Use invoice extraction to create the evidence register, not to approve the cost

There are three workable routes for building the invoice side of a Research Ireland cost-claim file.

The first is manual spreadsheet extraction. It is enough for one small award or a short reporting period: open each supplier invoice, type the invoice number, date, supplier, VAT fields, line description and amount into a register, then reconcile the register to the ledger report. The weakness is not conceptual. It is the time and error risk once the file covers several grants, many suppliers, multi-page PDFs, split allocations or repeated audit queries.

The second route is the ERP or grant-module report. Agresso, Unit4 or an equivalent finance system can provide the ledger view: grant code, account code, transaction reference, supplier and posted amount. That report is essential, but it is not a substitute for the invoice evidence. It tells the reviewer what was posted. It does not show the supplier's line descriptions, invoice page, VAT detail, or the source document behind a vague transaction description.

The third route is invoice-side extraction. In this model, the Research Finance team uses the ledger report for transaction coding and totals, then uses extraction to build the source-document register that sits behind those lines. Invoice Data Extraction fits here because it lets users upload supplier invoice PDFs or supported image files, describe the fields they need in a prompt, and download structured Excel, CSV or JSON output. A grant-evidence prompt can ask for supplier name, invoice number, invoice date, VAT ID where present, PO number, line descriptions, net amount, VAT amount, gross amount, currency, grant code if printed on the document, source file and page reference.

That output can become the working register for review. A team can extract supplier invoice data into structured spreadsheets, then compare the extracted rows with the Agresso or Unit4 report, add budget-category mapping, record exceptions and attach procurement references. The result is not an eligibility decision. It is a better organised evidence layer for Research Finance and the PI to review against the award terms.

The boundary should stay visible in the process notes. Invoice Data Extraction does not determine whether a cost is eligible under Research Ireland rules, approve a budget reallocation, decide VAT treatment, apply procurement law, or replace Research Finance Office sign-off. It structures the supplier-invoice data so the people responsible for those judgements can review a complete evidence register instead of re-keying details from PDFs.

For teams looking beyond this one funder, the same document-processing pattern sits inside broader invoice processing for educational institutions: extract source-document data, preserve traceability, reconcile to the finance system, and keep the human approval route intact.

Keep legacy SFI and IRC awards on their own terms

Research Ireland was established from the amalgamation of Science Foundation Ireland and the Irish Research Council on 1 August 2024, as set out in the Irish Research Council's establishment notice. That changed the public funding landscape, but it did not make every older award subject to one new set of evidence rules overnight.

For mixed grant portfolios, the first evidence decision is classification. Identify the award, original funder, programme, Letter of Offer, approved budget version, applicable financial conditions and current reporting route before assembling the supplier-invoice pack. A legacy SFI award, a legacy IRC award and a new Research Ireland programme call may all now sit under the Research Ireland name in conversation, but the file should show which terms govern the cost claim.

That classification should be visible in the archive. Label the evidence pack with the award identifier, original funder, applicable conditions, claim period, Research Finance owner, PI or budget-holder contact and storage location. If a legacy award references older SFI or IRC financial guidance, preserve that reference with the file rather than relying on a current web page to explain past treatment. If a budget version changed during the award, keep the approved version that governed the period being claimed.

The same principle applies when comparing Research Ireland with other grant regimes. Federal grant invoice documentation under 2 CFR 200 belongs to the US Uniform Guidance world, not Irish higher-education grant finance. It is useful only as a contrast: different jurisdiction, different funder rules, same audit need to trace each claimed cost back to source evidence and approval.

For a Research Office, the working rule is simple enough to be useful: classify the award first, then assemble supplier-invoice evidence against the terms that govern that award. Current Research Ireland policy, legacy SFI conditions and legacy IRC conditions can all appear in the same institution's portfolio. A defensible cost-claim file keeps those lines visible.