Core Capture for SAP 26.2: GenAI extraction for OpenText VIM without a VIM upgrade
One line in OpenText's May 2026 release blog deserves more attention from teams still on VIM 7.6 or 20.4. Describing Core Capture for SAP Solutions 26.2, OpenText says the new GenAI extraction can be activated "with a simple switch and without any mandatory VIM upgrades for all versions starting with 7.6."
Put that next to the lifecycle page. VIM 7.6 and 20.4 leave Current Maintenance on 31 December 2027. If you've been parking capture improvements until "after the upgrade," this one doesn't have to wait, provided you run Core Capture. That's useful. It's also a reason to keep the two changes apart on purpose.
What 26.2 changes. OpenText describes an "intelligent voter" that combines three capture disciplines: the knowledge base, self-adaptive learning and LLM-based extraction. The release extracts header and item fields for invoices, sales orders, order confirmations, delivery notes, remittance advices and quotations, for all languages and countries, without additional training. The VIM product page fills in the rest: Core Capture feeds extracted data into SAP workflows, keeps its configuration in SAP, uses business context during extraction, and lets users validate results in SAP Fiori.
What the blog can't give you is a number for your invoices. Nobody can, until you measure.
Treat the switch as a change with a baseline. A switch that's easy to flip is easy to flip without evidence. Before you turn it on:
Pick the suppliers. Twenty or thirty that cover your hard cases: multi-page invoices, line-heavy invoices, the languages you actually receive, and a few known troublemakers.
Record today's numbers. Field-level corrections in validation for those suppliers over two or three normal weeks, header and line items counted separately. One "accuracy" figure hides more than it shows.
Fix the comparison window. Same suppliers, same fields, same validators, a similar stretch after the switch. Keep period end out of both windows.
Write the stop rule. Decide in advance which result sends you back, and confirm with OpenText how the switch is reversed before you need to know.
Keep it apart from the VIM upgrade. If VIM 23.4 or 25.4 is also on your plan, don't let the GenAI switch and the add-on upgrade land in the same window. When first-pass quality moves after a combined change, you can't tell which change moved it. Switch, measure, settle, then upgrade VIM against a capture baseline you trust. The reverse order works too. Doing both at once is the only order we'd avoid.
Who flips it. We'd have the capture owner switch it on and the AP lead accept or reject the result against the baseline, with both names on the change record. Our September post on AI extraction ownership covers the wider question; this is the version-specific step.
A housekeeping note to finish. OpenText's lifecycle page lists Core Capture for SAP Solutions only up to release 24.2, with Current Maintenance to 30 April 2029, and has no rows yet for the 25.x and 26.x releases OpenText has announced since. SAP's upgrade checklist on SAP Community calls Core Capture the cloud-based capture option, so ask OpenText which release your tenant runs before you plan the test. Our 12 October post covers what followed 26.2.
