The PRAG has a firmly established reputation among NGO finance and logistics teams: a several-hundred-page document opened only when in doubt — which is to say, too late. Yet for an organisation implementing an EU grant, the real question is not knowing the PRAG by heart, but knowing precisely what applies to it: the guide itself, or Annex IV of its grant contract? Confusing the two drives a significant share of procurement audit findings.
This article clarifies what the PRAG is, what Annex IV actually requires from grant beneficiaries, how the principles-based approach replaced threshold grids in recent contracts, and how an ERP like Abvius secures every procurement file all the way to the audit.
PRAG and Annex IV: what NGOs really need to apply on their EU grants
Reading time: ~7 min
- What is the PRAG?
- PRAG or Annex IV: who must apply what?
- Annex IV principles: what the auditor checks
- Procurement thresholds: from historic grids to a principles-based approach
- The auditable procurement file: documents to keep
- The most frequent procurement audit findings
- How Abvius secures your procurement procedures
- Mini FAQ
What is the PRAG?
The PRAG — the "Practical Guide to contract procedures for European Union external action" — consolidates the procedures the European Commission applies to award contracts and grants in external action. It describes procedure types (international open tender, competitive negotiated procedure, simplified procedure...), nationality and origin rules, exclusion criteria, restrictive measures, and document templates. It is updated regularly: the applicable version is the one referenced in your contract, not the latest one online.
A crucial point: the PRAG is primarily addressed to contracting authorities — the Commission itself and partner-country administrations. An NGO is directly bound by it only in specific cases, for instance when acting as a delegated contracting authority. For the most common situation — an NGO grant beneficiary purchasing goods and services to implement its project — a different text governs: Annex IV of the grant contract.
PRAG or Annex IV: who must apply what?
Annex IV ("Contract award procedures by grant beneficiaries in the context of EU external actions") is annexed to your grant contract and sets the rules for your project procurement. It explicitly provides that the beneficiary may choose to apply PRAG procedures: if followed correctly, the annex's principles are deemed complied with. It is a safe-harbour option, not an obligation.
In practice, three configurations exist: applying your own internal procedures (provided they respect Annex IV principles), applying the PRAG as a voluntary reference, or applying a stricter co-donor's rules when the project is multi-donor. In every case, the chosen rule must be written down, applied consistently and documented — because the Commission's control is ex post: nobody validates your purchases upfront, but everything can be checked afterwards, and expenditure linked to a non-compliant contract is declared ineligible.
Annex IV principles: what the auditor checks
Recent versions of Annex IV rest on principles rather than detailed procedures. The contract must be awarded to the most economically advantageous tender (best value for money) or, where appropriate, to the lowest-priced one. The beneficiary must avoid any conflict of interest, justify the choice of invited tenderers where no open tender is launched, evaluate offers against objective criteria that take price into account, and comply with EU restrictive measures — which implies screening suppliers against sanctions lists.
And above all: keeping sufficient and appropriate supporting evidence of the procedures applied, justifying both the shortlisting and the award decision. In an audit, the burden of proof is entirely on your side. A purchase made at the best price but with no trace of competition is treated as a non-competitive purchase.
Procurement thresholds: from historic grids to a principles-based approach
This is the point that most disorients teams trained "the old way". Previous contract generations imposed a precise threshold grid (one quote below a certain amount, several suppliers consulted above it, international tendering for large contracts). Recent versions of Annex IV, aligned with the EU Financial Regulation, no longer impose a uniform threshold grid: they rely on the principles above and on ex post control.
The direct consequence: your internal procurement manual becomes the enforceable standard. It must set your own thresholds (amounts above which you require three quotes, a formal consultation, an award committee), and its correct application is what the auditor will verify. A demanding but unapplied manual is more dangerous than a modest, respected one. Beware also of older contracts still running and of co-donors that keep their own grids: the version referenced in each contract prevails, hence the importance of checking the reference on your agreement. Our guide to humanitarian procurement offers a manual structure compatible with the main donors.
The auditable procurement file: documents to keep
For each contract, the file must allow the decision to be reconstructed without a witness. Expected documents: the needs assessment and reference budget, the definition of selection and award criteria, the solicitations sent (and the justification of the suppliers consulted), the dated offers received, the signed comparative evaluation grid, evaluators' no-conflict-of-interest declarations, proof of supplier screening, the contract or purchase order, then delivery and acceptance. The chain continues on the accounting side: invoice, payment, analytical allocation — see our guide to expense justification.
The most frequent procurement audit findings
Contract splitting: dividing a need into several orders to stay below your own manual's thresholds — detected by simply sorting purchases by supplier and period. Sham competition: three quotes requested from related suppliers, or received the same day with identical layouts. Criteria changed mid-course: the winning offer only wins if the announced weighting is altered. Undeclared conflict of interest: a committee member linked to a tenderer. The incomplete file: the decision may have been sound, but nothing proves it. Each of these findings translates into ineligibility of the related expenditure — sometimes years later, as detailed in our article on preparing for donor audits.
How Abvius secures your procurement procedures
In Abvius, your procurement rules become guided workflows: your manual's thresholds — or a specific donor's — are configured per contract, and the platform automatically requires the right level of competition for the amount. The procurement file builds itself as you go: requests, quotes, evaluation grids, approvals and no-conflict declarations are time-stamped and attached to the contract. Supplier screening is automatic when the feature is enabled, with the result filed into the record. At audit time, every purchase comes out with its complete chain, from needs assessment to donor-allocated payment.
Mini FAQ
Must an NGO grant beneficiary apply the PRAG?
Not directly: it must comply with Annex IV of its grant contract. Applying PRAG procedures is an option that carries a presumption of compliance with the annex's principles.
Which version of the PRAG or Annex IV applies to my project?
The one referenced in your grant contract. The rules are not retroactive: two simultaneous projects can fall under two different versions.
Does Annex IV impose amount thresholds?
Recent versions no longer impose a uniform grid: they set principles checked ex post. Your internal thresholds, set by your procurement manual, become the audited reference. Still, check your contract: older agreements and some co-donors keep precise grids.
What is at stake in case of non-compliance?
Ineligibility of the expenditure linked to the contract concerned — i.e. reimbursement to the donor — and, in serious cases, contract termination or suspension of payments.
Want procurement workflows that enforce your thresholds on their own? Request an Abvius demo.