PIC Codes, OID Numbers and Partner Mandates: The Admin Paperwork That Delays Proposals

PIC codes, OID numbers and partner mandates are basic, but they can delay a strong proposal if you leave them to the final week. Use PIC for Horizon Europe and the EU Funding & Tenders Portal. Use OID for Erasmus+ and European Solidarity Corps actions managed through National Agencies. Treat registration and mandates as part of proposal design, not as a closing admin chore.

The short version: which identifier belongs where

A PIC, or Participant Identification Code, is the organisation identifier used in the EU Funding & Tenders Portal. You need it for Horizon Europe and other calls submitted through that portal. Coordinators use it to add partners, complete participant data, and connect each organisation to its legal and financial information.

An OID, or Organisation ID, is used for Erasmus+ and European Solidarity Corps applications handled through the Erasmus+ and ESC systems. You use it when building an Erasmus+ application, adding partners, and preparing documents for the National Agency route.

The same legal organisation may need both identifiers. A university can have a PIC for Horizon Europe and an OID for Erasmus+. An NGO that only works in Erasmus+ may have only an OID. A research institute joining both types of calls should keep both records clean and consistent.

Do not ask partners for “the registration number” without naming the system. Ask for:

• PIC for Horizon Europe, CERV calls on the Funding & Tenders Portal, and similar centralised calls.
• OID for Erasmus+ and European Solidarity Corps applications.
• The legal name, address, VAT or national registration details, and signatory details that match the identifier record.

That last point matters. Evaluators score the proposal content, but portals check the organisation data. If names, legal forms, addresses and mandate letters do not align, the coordinator loses time on avoidable fixes.

The failure timeline: the partner who registers too late

The classic problem starts with a partner who says, “We will register just before submission.” The work package text looks solid. The budget is almost done. The coordinator opens the portal, tries to add the partner, and discovers there is no usable identifier.

The partner then creates a record in a hurry. Someone uses a short English brand name instead of the legal name. The address differs from the mandate letter. The person registering the account is not the legal representative. A document is missing, or the uploaded document uses another spelling of the organisation name.

Now the coordinator has several linked problems:

• The partner cannot be added cleanly to the application.
• The mandate letter cannot be prepared with confidence.
• The budget and partner list may need corrections.
• The submission checklist shows errors or warnings.
• The final review shifts from quality control to identity repair.

This is how administrative work damages proposal quality. The coordinator stops checking logic, outputs, risks and partner roles. The team starts chasing screenshots, signatures and registration confirmations.

The fix is simple: collect identifiers when you confirm the consortium. If a partner does not have the right identifier, ask them to register before they write their section. Registration is not separate from drafting. It proves that the legal entity you describe in the proposal can actually be selected in the submission system.

How to register without creating future cleanup

For a PIC, start in the EU Funding & Tenders Portal. The partner should search first, because many organisations already have a PIC from earlier EU work. Duplicate registrations create confusion, especially for universities, municipalities, chambers, and networks with several departments.

If no existing record is found, the partner creates an organisation profile. They should use the legal name from official documents, not the project nickname. They should enter the address, legal form, registration data and contact details carefully. The person creating the profile should know who can sign documents and who handles finance.

For an OID, use the Erasmus+ and European Solidarity Corps organisation registration route. The same rule applies: search first, then register only if needed. The OID record should match the legal entity that will sign the mandate and receive or manage funds.

A practical registration pack helps. Ask every partner for:

• The correct identifier, PIC or OID, depending on the call.
• Legal name in the original language and in English, if used.
• Registered address.
• Legal representative name and role.
• Finance contact and project contact.
• Proof documents required by the portal or agency.
• Confirmation that the same legal entity appears in the budget and mandate.

Large institutions need extra care. A faculty, lab, local branch or project office may not be the legal applicant. If the legal entity is the parent university or municipality, the identifier and mandate usually need that entity, not the internal unit. You can still describe the active department in the narrative, but the portal record must point to the legal participant.

At StrandsUnited, we often help teams turn this into a small partner onboarding workflow inside their proposal workspace, alongside tasks, files and source notes. The value is not the form itself. The value is that the coordinator can see which partners are submission-ready before the final writing sprint.

Partner mandates: what they prove and what to check

A partner mandate is a signed document that authorises the coordinator to submit the proposal and act for the partner in the application process. In Erasmus+ projects, mandate letters are a familiar part of the application package. In other EU programmes, the exact documents differ, but the same principle holds: the coordinator needs formal proof that the listed organisation has agreed to join under the stated role.

A good mandate is boring. It contains the right project, the right coordinator, the right partner, the right legal names, and the right signatures. Boring is good because it passes checks.

Before collecting signatures, check the draft mandate against the identifier record:

• Does the partner legal name match the OID or PIC record?
• Does the address match the organisation profile?
• Is the signatory allowed to sign for the organisation?
• Is the project title consistent with the application?
• Is the coordinator name written exactly as used in the application?
• Are dates, stamps and signature formats acceptable for the call route?

Do not send mandate templates before the partner list is stable. Also do not wait until every paragraph is final. The best moment is after the consortium is confirmed, the call route is clear, and the legal names have been checked.

Store signed mandates in one place. Name files with partner names that the coordinator can recognise. Keep editable templates separate from signed versions. If a partner changes legal name, address or signatory during preparation, update the portal record and regenerate the mandate. Do not patch a signed PDF and hope nobody notices.

This is proposal risk management. A mandate problem rarely makes the concept better. It only consumes attention that should be spent on fit, evidence, work plan and impact.

The open-data payoff: identifiers make funding history traceable

Identifiers are not only portal plumbing. They are the identity backbone of open EU funding data. When an organisation has a stable PIC or OID, analysts can connect projects, roles, coordinators, topics and repeat collaborations across calls and years.

That matters before you invite a partner. A coordinator can check whether an organisation has coordinated before, which programmes it appears in, and who it has worked with. A grant writer can spot experienced partners, overused networks, and missing geographies. A community leader can see whether a potential partner has a real EU project footprint or only a good brochure.

Our consortium graph covers 114,731 organisations, 83,490 projects and 461,953 participation edges across Erasmus+, Horizon 2020 and Horizon Europe open data for 2014-2027. In that graph, identifiers are not a clerical detail. They are what lets us distinguish one municipality from another, connect a university across programmes, and trace an NGO’s path from partner to coordinator.

The practical next step is to create an identifier and mandate checklist for every autumn proposal pipeline. Put it next to your concept note, partner table and budget file. If you want a more durable setup, build a small consortium workspace where partner records, mandates, evidence and proposal tasks live together. Our platform work is built for that kind of operating layer.

Where this comes from

This article comes from the grant intelligence work we maintain around our consortium graph, built from CORDIS and Erasmus+ open data. It also reflects what we see when operating community and knowledge platforms such as Impactful, where clean organisation records make collaboration easier. The admin fields look small, but they decide whether a proposal team can use its final days for quality or for repair.