Two calendars decide when an SAP AP team has to touch OpenText VIM. One is the e-invoicing mandates of the countries you buy from. The other is OpenText's maintenance dates for the VIM release you run. Different people usually keep them. Put both in one table and a few decisions get easier.
OpenText's October update on Sweden is a good place to start, because it's mostly about waiting. In February 2026 Sweden opened an inquiry into writing the EU's VAT in the Digital Age (ViDA) rules into Swedish law, including whether domestic B2B e-invoicing should become mandatory. There's no domestic B2B mandate today. The findings are due by 30 November 2027. Cross-border B2B transactions inside the EU face mandatory e-invoicing and near-real-time digital reporting from 1 July 2030, and ViDA gives member states more room to bring in domestic mandates of their own.
Now the VIM side, from OpenText's lifecycle page as we read it on 10 October 2026:
DateCalendarEvent30 Nov 2027SwedenInquiry findings due, including whether domestic B2B e-invoicing becomes mandatory31 Dec 2027OpenTextVIM 7.6 and 20.4 leave Current Maintenance31 Dec 2028OpenTextVIM 23.4 leaves Current Maintenance1 Jul 2030EUViDA cross-border B2B e-invoicing and digital reporting begin31 Dec 2030OpenTextVIM 25.4 leaves Current Maintenance
What the table says. Three readings, all ours.
Sweden's answer lands one month before VIM 7.6 and 20.4 leave Current Maintenance. A team on either release will be choosing its next VIM release at nearly the moment it learns whether Swedish suppliers must send e-invoices. Put those two decisions in the same meeting.
A move to 23.4 doesn't reach ViDA. Its Current Maintenance ends 31 December 2028, eighteen months before the cross-border date. That doesn't rule 23.4 out. It means a 23.4 plan should already name the upgrade after it. Of the releases listed when we read the page, only 25.4 runs past 1 July 2030, and by six months.
The VIM release still follows the S/4HANA release. We covered the 7.6 and 20.4 choice and the S/4HANA pairing earlier. This table adds the mandate dates to that conversation.
Country support arrives by release. OpenText adds e-invoicing coverage to VIM release by release. Its SAP solutions release blog, for example, lists out-of-the-box mappings for Romania and Spain, and integration with SAP Document and Reporting Compliance for Romania. So the useful question for each country isn't whether VIM "does e-invoicing." It's which release carries the mapping for that country's format, and whether that release is on your plan before the date. For Sweden today, the honest answer is that there's no domestic B2B format mandate to map yet.
Keep it maintained. One person, in our view the VIM process owner, keeps the table. Add a row for each country you receive invoices from. Check OpenText's mandate posts and the lifecycle page on a fixed day each quarter, and when a row changes, tell whoever owns the S/4HANA roadmap. The value is a short list someone rereads, not a long one nobody opens.
