Capture is a separate decision once BCC and ICC drop off
The names changed. The decision did not go away.
Capture is where many VIM programs hide risk. The invoice add-on is visible. The extraction stack is a set of product names that have shifted for a decade: Business Center Capture (BCC), Invoice Capture Center (ICC), Information Extraction Services, Intelligent Capture for SAP Solutions, Capture for SAP Solutions, Core Capture for SAP Solutions. Teams still say “ICC” when the installed software is something else.
Public upgrade notes that were recirculated in 2026 are unusually direct on one point: VIM 25.4 does not support BCC or ICC components anymore. If those are still in your landscape, a move to 25.4 is not a Foundation transport plus a regression test. It is a capture program.
That is not a reason to panic. It is a reason to stop folding capture into “the VIM upgrade” as a footnote.
What the current names usually mean
Use the installed product and version, not the nickname on a runbook.
BCC / ICC — older capture generation, common in ECC-era and early VIM landscapes. Treat them as outgoing if 25.4 is the target.
IES-based on-premise capture (IC4S / C4S) — on-premise Capture for SAP Solutions. Naming has moved; the operational questions have not: Windows Server, IIS, .NET, learning data, capture profiles, and Validation Client compatibility.
Core Capture / CC4S — cloud-based IES option. The extra question is cloud readiness: connectivity, security review, and who operates the service.
Capture Imaging Plug-In — supporting imaging and rendering. Easy to omit from an inventory. Do not omit it.
OpenText’s current product page describes Core Capture for SAP Solutions as extracting data from inbound documents, feeding SAP workflows, holding configuration in SAP, using business context in extraction, and allowing validation in SAP Fiori. That is the direction of the product. Your landscape may not be there yet. Say so.
Extraction quality is operational, not a license event
A public 2026 ASUG Northern California note (March) is useful because it is modest. They listed what actually sustains automation after go-live: iterative OCR configuration and template training; honest expectations about straight-through processing; validation design and exception handling; and the way SAP refreshes and upgrades interact with capture workflows.
None of that requires a new platform. It does require an owner.
A capture upgrade that copies profiles and hopes learning data “comes along” usually produces a quiet drop in first-pass quality. Validators notice first. AP notices as exception volume. IT notices when someone asks why the new version is “worse than ICC.”
Before you touch Foundation:
Inventory templates, profiles, and languages actually in use—not the full catalog.
Identify which vendors still depend on a brittle template.
Decide who will retrain and for how many weeks after cutover.
Decide how you will measure extraction quality in the first month (field-level correction rates are more honest than a single “OCR accuracy” percentage).
Confirm the Validation Client or Fiori workplace version that must travel with the capture version.
Do not publish a target automation rate in the upgrade charter. Publish the measurement method.
On-premise IES or Core Capture is a stewardship choice
The question is not “cloud versus old.” It is who operates extraction, where images travel, and how SAP configuration stays the system of record.
Stay on-premise IES when you already have a stable capture operations practice, when data residency is a hard constraint, and when you can keep Windows and .NET current. Move toward Core Capture when you want configuration closer to SAP, Fiori validation, and less local capture infrastructure—and when security and integration reviews are actually staffed.
Either path can be clean-core. Neither path is clean-core if you keep a side database of “fixed” invoices that never update a profile.
Do not upgrade capture in the same week you rewrite rules
Capture mistakes look like process mistakes. A wrong PO number and a missing cost center produce the same work item. If you change extraction and business rules in the same window, you will not know which change caused the queue.
A measured sequence:
Freeze invoice rules that are not required by the new add-on.
Move capture to a supported product and version aligned with Foundation.
Stabilize extraction with a named owner and a short feedback loop from validators.
Only then retune rules that assumed the old capture behavior.
McCloy Data already writes about master data and capture consistency as a performance prerequisite. This article is the version-alignment companion: the product under the nickname has a support end. Plan it as a workstream.
What we will and will not do
We will help you name the installed capture product, map it to the VIM 25.4 support statement, and draft a cutover that keeps learning data and validator practice intact. We will not promise that Core Capture will remove exceptions. We will not treat a competitor’s dashboard as evidence about your queue.
If BCC or ICC is still in production and S/4HANA 2025 is on the calendar, start the capture conversation this quarter. The add-on upgrade will not wait for a vague “OCR workstream.”