DG BUDG has opened the tender window for DIMOS VII, the European Commission’s €700 million framework contract for financial IT systems across the EU institutions. Lot 1 closes on 26 October 2026, which leaves bidding consortia a narrow window to get every part of their offer in order, starting with the consultant CVs that carry real weight in the technical score.
This post walks through what changed between DIMOS VI and DIMOS VII, how the new lot structure splits the budget, and why the section of the tender scoring CV profiles deserves the same attention as the technical solution itself.
TL;DR
- DIMOS VII is DG BUDG’s €700M framework contract for financial IT systems, replacing DIMOS VI, with Lot 1’s submission window already open and closing 26 October 2026.
- Unlike DIMOS VI’s single unified structure, DIMOS VII splits the budget into two lots: Lot 1 (SAP-based systems, €270M) and Lot 2 (Financial Interoperable systems, €430M).
- Up to 4 contractors will be awarded per lot, with minimum average annual turnover thresholds of €70M for Lot 1 and €110M for Lot 2.
- 20 of the 100 technical evaluation points are scored on CV profiles, team structure, resource deployment speed, and onboarding methodology, separate from the technical solution itself.
- A new mandatory disclosure under the Foreign Subsidies Regulation applies to any tenderer or subcontractor that received €4M or more from a single third country in the past 3 years.
- Work is dispatched either through a cascading mechanism, where Time and Means and Quoted Time and Means requests go to Rank 1 first, or through a reopening of competition for Fixed Price deliverables.
- Tenderers must submit 8 to 10 verified project references from the last 5 years demonstrating SAP S/4HANA or custom financial systems integration expertise.
- 38 EU institutions, agencies, and joint undertakings will draw on the framework once it is live, from the European Parliament to eu-LISA and Europol.
What Is DIMOS VII, and Why Is the Clock Already Running?
DIMOS stands for Development, Implementation, Maintenance and Operation of Financial IT Systems. It is the European Commission’s flagship framework contract for the software running the EU’s financial infrastructure, from executing the Multi-annual Financial Framework to auditing NextGenerationEU funds. The Directorate-General for Budget, DG BUDG, manages it as Central Purchasing Body on behalf of a long list of EU institutions and agencies.
DIMOS VII is the seventh generation of that contract, procedure identifier EC-BUDG/2026/OP/0006-PIN. The Prior Information Notice went out on 30 June 2026, and the full Contract Notice, with specifications and submission guidelines, followed in early September, close to the original 25 August target. Lot 1 submissions are due 26 October 2026, which puts the deadline inside a six-week window for most bid teams reading this.
The ceiling value sits at €700,000,000, matching DIMOS VI almost exactly. What changed is everything underneath that number: how the budget is split, who can compete for which part of it, and how much of the technical score now depends on the people a company puts forward, not only the solution it proposes.
What exactly is DIMOS VII?
DG BUDG’s €700 million framework contract for the EU’s next generation of financial IT systems, running for 48 months once awarded.
DIMOS VII replaces DIMOS VI as the vehicle 38 EU institutions and agencies use to procure SAP-based and custom financial software development, from S/4HANA migrations to the API layers connecting specialized financial applications across Brussels, Luxembourg, and beyond. It is governed by the revised EU Financial Regulation, Regulation (EU, Euratom) 2024/2509.
DIMOS VI vs DIMOS VII: What Actually Changed
DIMOS VI ran as a single, unified vehicle centered on SAP and ERP, procedure BUDG/2022/OP/0010, launched in October 2022 and awarded the following spring. It worked well enough for mega-consultancies with deep SAP practices, but it left little room for companies whose strength was custom development or API integration rather than SAP itself.
DIMOS VII splits that single vehicle into two distinct lots, and the split is not cosmetic. Lot 2, the non-SAP side of the contract, now carries the larger share of the overall budget, a deliberate acknowledgment that modern EU financial operations run on far more than a SAP kernel.
| Feature | DIMOS VI | DIMOS VII |
|---|---|---|
| Procedure ID | BUDG/2022/OP/0010 | EC-BUDG/2026/OP/0006-PIN |
| Lot structure | Single unified structure | Two lots: PAR-0001 and PAR-0002 |
| Total ceiling value | €700,000,000 | €700,000,000 |
| Contractors per lot | Multiple, no fixed cap | Up to 4 per lot |
| Minimum turnover | Single capacity limit | Lot 1: €70M/yr · Lot 2: €110M/yr |
| Foreign subsidies check | Standard exclusion grounds | Mandatory FSR notification for contributions of €4M or more |
For a company that already delivered under DIMOS VI, the practical question is which lot fits the work it actually does, not whether to bid at all. Sprint CV’s own coverage of the DIMOS VI framework contract walks through how that earlier structure played out for consortia and cascade rankings, and most of the underlying mechanics carry over into DIMOS VII.
How the €700M Splits Across Two Lots
Lot 1, PAR-0001, covers SAP-based technology systems: SAP HANA, SAP S/4HANA, SAP Fiori, SAP Analytics Cloud, and the legacy ABAP environments still running underneath some institutions. It carries €270,000,000, 38.6 percent of the total budget, and requires a minimum average annual turnover of €70,000,000 across the last two closed financial years.
Lot 2, PAR-0002, covers financial interoperable systems: custom software development, API management, web applications, and the data integration middleware connecting specialized financial tools across the 38 participating institutions. It carries €430,000,000, 61.4 percent of the total, and the turnover threshold rises to €110,000,000 per year.
That allocation is the clearest signal in the entire tender. The Commission is putting more money behind API-first, microservice-oriented development than behind the SAP core itself, which opens a real path for systems integrators and software engineering companies that were effectively locked out of DIMOS VI’s SAP-centric structure.
Can a company bid for only one lot under DIMOS VII?
Yes. Lot 1 and Lot 2 are evaluated separately, and non-SAP companies can compete for Lot 2 without any SAP practice at all.
Each lot has its own turnover threshold, its own reference project requirements, and its own award. A company whose strength is API development and custom financial applications has no reason to build a SAP capability just to compete, and the €430M allocated to Lot 2 is larger than the entire DIMOS VI vehicle was.
How Work Actually Gets Assigned Once You’re In
Once a company is one of up to four awarded contractors on a lot, the framework decides how new requests reach it. Time and Means and Quoted Time and Means requests move through a cascading mechanism: the contracting authority contacts Rank 1 first, and only moves to Rank 2, then 3, then 4, if the top-ranked contractor cannot fulfill the request.
Fixed Price deliverables work differently. Every awarded contractor on the lot is invited to submit a competitive technical and financial offer for each specific piece of work, and the contract goes to whoever offers the best value for that request.
Delivery happens three ways: far-site, from contractor premises anywhere in the EU; near-site, within two hours travel time of the relevant customer premises; or on-site, at Brussels, Luxembourg, or another agency headquarters. A company’s position on the cascade, and its ability to staff near-site or on-site work quickly, both come back to the same resource: how fast it can put a verified, correctly formatted profile in front of a customer once a request lands.
Why CV Quality Carries Real Weight in the Technical Score
Technical proposals under DIMOS VII are scored out of 100 points, with an overall minimum pass mark of 65 and a minimum 60 percent pass mark on each individual criterion. Miss the threshold on any one of the three, and the rest of the score does not matter.
| Technical award criterion | Weighting | Max points | Min pass mark |
|---|---|---|---|
| Quality of Technical Solution Proposal | 70% | 70 | 42 (60%) |
| Quality of Implementation Time & Staffing | 20% | 20 | 12 (60%) |
| Assurance of Delivery Feasibility | 10% | 10 | 6 (60%) |
| Total evaluation | 100% | 100 | 65 (65%) |
The second criterion is the one bid teams tend to underweight in their own preparation.
“Quality of Implementation Time & Staff Members’ Involvement. Evaluates CV profiles, team structure, resource deployment speed, and onboarding methodology.” DIMOS VII Prior Information Notice, Technical Award Criteria
Twenty points, with a mandatory floor of twelve, are awarded on the profiles a company puts forward and how quickly it can deploy them, not on the technical architecture at all. A consortium that scores well on the solution but submits inconsistent, outdated, or poorly formatted CVs is leaving points on the table in a section that has nothing to do with its technical capability.
How much of the technical score depends on CV profiles and staffing?
20 of the 100 points, with a minimum pass mark of 12, are scored specifically on CV profiles, team structure, deployment speed, and onboarding methodology.
That criterion sits alongside the 70-point technical solution score and the 10-point delivery feasibility score, and all three need to clear their own 60 percent floor. A company can propose a strong architecture and still fail the overall pass mark if its staffing section, built on rushed or inconsistent CVs, does not hold up on its own.
The Compliance Layer: Foreign Subsidies Regulation
DIMOS VII introduces a regulatory requirement that did not exist under DIMOS VI: mandatory compliance with the Foreign Subsidies Regulation, Regulation (EU) 2022/2560.
“Any tenderer, consortium member, or subcontractor that received foreign financial contributions of at least €4,000,000 per third country in the three years prior to submission must submit a formal notification using Form FS-PP.” DIMOS VII Prior Information Notice, Section 2.1.4
Tenderers below that threshold, or with no foreign contributions at all, still need to file a formal declaration confirming that position. Neither obligation ends at submission. Any change to a consortium’s foreign contribution profile has to be communicated to the contracting authority in the same format, again at contract level if it was not already flagged to the main authority.
Do we need to file an FSR notification for DIMOS VII?
Only if the company, a consortium partner, or a subcontractor received €4 million or more from a single non-EU country in the last three years.
Below that threshold, or with no foreign contributions at all, a formal declaration confirming that still has to be submitted. Every consortium partner and subcontractor needs to be checked individually, since the obligation applies at the level of each entity, not only the lead bidder.
What to Do Before the Submission Window Closes
With Lot 1’s window already open and closing 26 October 2026, the practical preparation work needs to happen in parallel, not in sequence.
- ✓Confirm which lot actually fits the company’s core competencies, SAP-based systems for Lot 1 or custom and interoperable systems for Lot 2
- ✓Form or confirm consortium agreements if turnover alone does not clear the €70M or €110M threshold
- ✓Audit every consortium entity’s foreign financial contributions against the €4M FSR threshold and prepare Form FS-PP or the declaration
- ✓Gather 8 to 10 verified project references from the last 5 years demonstrating SAP S/4HANA or custom financial systems integration
- ✓Assemble and format consultant CVs for the key roles the criteria will score, SAP S/4HANA migration, Fiori UI/UX, API gateway engineering, and financial IT security
- ✓Subscribe to alerts on the EU Funding & Tenders Portal for updates on Lot 2 timing and any corrigenda
Where CV Readiness Fits Into a DIMOS VII Bid
The 20-point staffing criterion is where a consulting company’s internal CV process either helps or gets in the way. Verified, correctly formatted profiles across the whole team need to exist before a request lands, not get assembled from scratch once a deadline is six weeks out.
Sprint CV already supports the DIMOS VI CV template, generating a compliant CV from a consultant’s existing profile in well under a minute. The same AI CV Parser behind that conversion is being configured for the DIMOS VII format as well, mapping the summary, project description, and roles and responsibilities straight into DIMOS VII’s fields without a manual rebuild.
For a company managing dozens or hundreds of consultant profiles across an active DIMOS bid, that difference shows up directly in the 20-point criterion: CVs that are ready before the request comes in, rather than chased down candidate by candidate once it does. Companies weighing what that kind of readiness actually takes can look at how CV management for consulting companies or the broader Enterprise CV Manager fits an active EU framework contract bid, or how the same profile data feeds Enterprise API integrations for companies running their own tender pipeline.
Winning a contract like DIMOS VII comes down to that same point at a larger scale. A centralized enterprise CV manager holding every consultant’s data in one place is what lets a company respond to a tender request quickly and accurately, and DIMOS VII’s templates and calculations, tied to specific fields and specific figures, are exactly the kind of format where scattered CVs cost real time. Companies with that centralized database already in place go into a request like this able to respond in hours, not days.
Frequently Asked Questions
What is DIMOS VII?
DIMOS VII is DG BUDG’s €700 million framework contract for the EU’s financial IT systems, procedure EC-BUDG/2026/OP/0006-PIN, replacing DIMOS VI and running for 48 months once awarded.
When is the deadline to submit a DIMOS VII tender?
Lot 1, the SAP-based systems lot, has a submission deadline of 26 October 2026. Companies should confirm Lot 2’s exact date directly on the EU Funding & Tenders Portal, since lot-specific timing can shift after publication.
What changed between DIMOS VI and DIMOS VII?
DIMOS VI ran as a single SAP-focused vehicle. DIMOS VII splits the same €700M ceiling into two lots, SAP-based systems at €270M and financial interoperable systems at €430M, each with its own turnover threshold and up to 4 awarded contractors.
How much of the technical score depends on CV profiles?
20 of the 100 available points, with a mandatory 12-point floor, are scored on CV profiles, team structure, resource deployment speed, and onboarding methodology, separate from the technical solution score.
Do all tenderers need to disclose foreign financial contributions?
Only tenderers, consortium members, or subcontractors that received €4 million or more from a single non-EU country in the past three years need to file a formal FSR notification. Everyone else still files a declaration confirming that position.
Can a non-SAP company compete for DIMOS VII?
Yes, through Lot 2, which covers financial interoperable systems, custom development, and API management, and carries the larger share of the budget at €430M.
Final Thought
DIMOS VII reshapes the opportunity DIMOS VI represented. Splitting the budget into two lots opens a real path for companies that never had SAP practices deep enough to compete under the old structure, and scoring 20 points on staffing means the CV work a bid team does over the next six weeks carries as much weight as parts of the technical proposal itself.
Companies that treat CV readiness as part of the technical score, not paperwork to finish once the solution is written, go into the 26 October deadline with a real shot at clearing the 60 percent floor on the staffing criterion.
With Lot 1 of DIMOS VII closing 26 October 2026, there is a narrow window to get consultant CVs verified, formatted, and ready for the 20-point staffing criterion before the deadline.
About the Author
Seven years of watching recruiters format the same CV three different ways for three different clients led Marco Pincho to build Sprint CV, an enterprise CV manager used by companies including VASS, Fujitsu, Sword Group, and Expleo to standardize CV creation and submission. He holds an Executive Master in IT Management from Solvay Brussels School and spends most weeks on calls with recruitment leaders and HR directors, working through documentation problems like the one covered in this article. Connect with Marco on LinkedIn
