Erasmus+ Beneficiary Module: step by step guide

The Erasmus+ Beneficiary Module is the online platform through which all KA1 and KA2 applications are submitted, all grant agreements are signed, and all progress and final reports are filed. It is the single most important technical tool in the Erasmus+ application process — and one of the most common sources of last-minute problems for first-time applicants.

Platform errors, missing OIDs, account access issues and incomplete form sections have caused strong applications to be submitted late or rejected at admissibility — not because of weak content, but because of avoidable technical failures. This guide walks you through the Beneficiary Module from first registration to final submission, step by step.

1. What Is the Erasmus+ Beneficiary Module

The Beneficiary Module — accessible at webgate.ec.europa.eu/beneficiary-module — is the European Commission’s centralised platform for managing Erasmus+ applications and grants. It is the only channel through which KA1 and KA2 applications can be submitted. There is no paper application, no email submission and no alternative route.

The platform handles the full project lifecycle: application submission, eligibility checks, evaluation, grant agreement signature, progress and final reporting, and payment requests. Every applicant — coordinator and partners — must be registered on the platform before an application can be submitted.

The Beneficiary Module is separate from — but linked to — the EU Funding and Tenders Portal (previously called the Participant Portal), where organisations register to obtain their Organisation ID (OID). Both platforms are needed, and both require an EU Login account to access.

2. Step-by-Step Registration: EU Login and OID

Before any work on the application form can begin, every person who will access the Beneficiary Module and every organisation participating in the project must complete the registration steps below. Do this at least two weeks before the deadline — processing delays at this stage have caused otherwise complete applications to miss submission windows.

Step 1 — Create an EU Login account. Go to ecas.ec.europa.eu and create a personal account using your professional email address. EU Login is a personal account — it belongs to an individual, not to an organisation. Every person who will work on the application form needs their own EU Login account. Use your work email, not a personal address — some National Agency systems require the account email to match the applicant organisation’s domain.

Step 2 — Register your organisation in the EU Funding and Tenders Portal. Log into ec.europa.eu/info/funding-tenders/opportunities/portal using your EU Login credentials. Navigate to “My organisations” and register your organisation. You will need: the organisation’s full legal name as it appears in official registration documents, the legal registration number, the organisation’s legal address, the organisation type (NGO, school, public authority, etc.) and the organisation’s bank account details for eventual grant payments.

Step 3 — Receive your OID. Once submitted, the registration is validated by the European Commission. Processing takes between 1 and 5 working days. You will receive an email confirmation containing your Organisation ID (OID) — a nine-digit number beginning with “E”. This OID is what you enter into the Beneficiary Module to link your organisation to the application. Keep it safe — you will use it for every Erasmus+ application your organisation submits.

Step 4 — Collect OIDs from all partner organisations. Every partner organisation must complete steps 1–3 independently. As coordinator, it is your responsibility to chase partner OID registrations and confirm all OIDs are received well before the application deadline. Do not assume partners have done this — confirm in writing.

3. Setting Up Your Organisation Profile

Once your OID is confirmed, log into the Beneficiary Module and link your organisation profile. This profile is the foundation of every application you submit — incomplete or inaccurate profile data can cause validation errors when you try to submit.

Link your EU Login to your organisation. In the Beneficiary Module, search for your organisation using your OID. When it appears, request access as the Primary Contact or Authorised Representative. The person with Authorised Representative access is the only one who can sign grant agreements and submit applications — this role must be assigned to the correct person before submission.

Verify your organisation data. Check that the legal name, address, organisation type and contact details in the Beneficiary Module match your official registration documents exactly. Discrepancies between the Beneficiary Module profile and your legal documents — even minor differences in punctuation or address format — can cause issues at the grant agreement stage.

Add team members. If other staff members will work on the application or reports, add them as users with appropriate access levels. The Beneficiary Module allows multiple users per organisation with different permission levels — read-only, editor or full access. Set up your team’s access before beginning the application so everyone can contribute without sharing login credentials.

Upload the financial identification form if required. Organisations receiving a grant above €60,000 must complete a financial identification form — a document that verifies the organisation’s bank account details with the EC treasury. This form must be signed by the bank and uploaded to the portal. Check the requirement for your grant size and complete it early — the form requires bank processing time.

4. Starting a New Application

Once your organisation profile is complete and all partner OIDs are confirmed, you are ready to start the application form. Do not begin entering content into the form until all preliminary steps are complete — starting a KA220 application without confirmed partner OIDs, for example, means the partner sections cannot be completed and you will need to return to them later under deadline pressure.

Navigate to the call. In the Beneficiary Module, go to “My Applications” and click “Create New Application.” Select the correct programme year (2026), Key Action (KA1, KA210 or KA220) and sector (School Education, VET, Adult Education, Youth or Higher Education). The sector you select determines which form you see — selecting the wrong sector means starting again.

Select your National Agency. The form will ask you to select the National Agency to which you are submitting. This must be the NA of the coordinator’s country — not the hosting country, not the partner with the most experience, and not the NA with the most favourable reputation. Selecting the wrong NA is an admissibility error.

Enter the project title and basic project data. The project title entered here will appear in all official correspondence and in the grant agreement if approved. Choose a clear, descriptive title — not an acronym. The title cannot easily be changed after submission.

Add partner organisations. Search for each partner using their OID and add them to the application. For each partner, confirm their role (coordinator or partner), their contact person and their legal representative. In KA220, this is also where you will later upload mandate letters for each partner.

5. Application Submission Walkthrough

The Beneficiary Module form is structured in sections — each section must be completed and validated before submission. Below is the standard section structure for KA220 applications, with key actions and common pitfalls for each.

6. Uploading Mandate Letters and Supporting Documents

For KA220 applications, mandate letters from all partner organisations must be uploaded to the Beneficiary Module before the application can be submitted. This is a hard requirement — not a recommendation. An application submitted without all mandate letters is inadmissible.

What a mandate letter must contain. The mandate letter must be on the partner organisation’s official letterhead, signed by the legal representative (the same person registered as legal representative in the EU Funding and Tenders Portal), and must explicitly authorise the coordinator to submit the application on the partner’s behalf. The Beneficiary Module provides a template — use it, adapt it with the specific project details, and ensure the signature matches the registered legal representative’s name exactly.

File format and naming. Upload mandate letters as PDF files. Name each file clearly — e.g. “Mandate_Letter_PartnerB_Poland.pdf” — so you can verify all are present before submission. The platform accepts files up to a defined size limit — keep PDFs under 5MB per file by scanning at 150–200 DPI rather than higher resolution.

Set a hard internal deadline for mandate letters. The process of sending the template to each partner, waiting for their legal representative to sign, receiving the signed document and uploading it takes longer than expected. Set an internal deadline for all mandate letters at least two weeks before the submission deadline — not two days. A partner whose legal representative is travelling or unavailable for signature can derail the entire submission timeline.

7. Most Common Beneficiary Module Errors

Wrong sector selected at the start. Selecting School Education when you meant to apply under Youth, or selecting KA210 when the project requires KA220, means the wrong form is generated. This cannot be corrected — you must start a new application. Always double-check the sector and Key Action before saving the initial draft.

Partner OID not validated by submission time. Detailed above — but worth repeating as the single most common preventable technical failure. A partner OID that is “pending validation” cannot be linked to the application. There is no workaround. Register all OIDs at least two weeks before the deadline.

Character limits exceeded in narrative fields. The form’s text fields have strict character limits. Pasting text from Word that exceeds the limit will either be cut off silently or generate a validation error at submission. Always draft in a word processor, count characters including spaces, and trim before pasting. Do not use special formatting characters — some word processors insert invisible characters that count toward the limit.

Budget tool showing WP1 above 20%. The budget tool calculates the WP1 percentage in real time. If it exceeds 20%, the form will flag this as an error and submission will be blocked. Redistribute staff days from WP1 into the relevant implementation WPs before attempting to submit.

Mandate letters signed by the wrong person. The mandate letter must be signed by the legal representative registered in the EU Funding and Tenders Portal — not the project manager, not the director’s assistant and not someone acting on behalf of the legal representative without documented authority. If the registered legal representative has changed, update the portal before requesting the signature.

Platform slow or unresponsive near the deadline. The Beneficiary Module experiences heavy traffic in the 24–48 hours before major deadlines. Pages load slowly, auto-save fails and form sections timeout. This is not accepted as grounds for late submission. Submit at least 48–72 hours before the deadline — not on deadline day.

Submission confirmation not received or saved. After submitting, the platform generates a submission confirmation with a timestamp. Save this confirmation — screenshot it and store the email. Without it, you cannot prove the application was submitted on time if a technical dispute arises.

8. Beneficiary Module Submission Checklist

• ✅ EU Login accounts created for all team members who will work on the application
• ✅ Coordinator organisation registered in EU Funding and Tenders Portal — OID confirmed
• ✅ All partner organisation OIDs confirmed — at least 2 weeks before deadline
• ✅ Correct Key Action, sector and National Agency selected in the application form
• ✅ All partner organisations added to the application using their OIDs
• ✅ Draft saved early — reference number noted
• ✅ All narrative sections drafted in a separate document before being entered into the form
• ✅ Character limits checked for every text field before pasting content
• ✅ Work packages consistent with intellectual outputs section
• ✅ Budget tool reviewed — WP1 does not exceed 20% of total grant
• ✅ Budget total does not exceed maximum grant for the Key Action
• ✅ Mandate letters collected from all partners — signed by registered legal representative
• ✅ All mandate letters uploaded as PDFs in the Documents section
• ✅ Platform completeness check run — no red validation errors remaining
• ✅ Application submitted at least 48 hours before the deadline
• ✅ Submission confirmation email saved and screenshot stored