The cost of a VIM program has three components: the software license, the implementation, and ongoing support and optimization. The license is negotiated through OpenText or SAP, and public list pricing is not available. Implementation cost depends on scope: the number of company codes and countries, invoice channels and volumes, the PO and non-PO mix, capture requirements, integrations, and how much existing custom code has to be addressed. Ongoing cost covers support, monitoring, capture training, and periodic optimization.
Because those variables move the total significantly, we scope cost through a paid assessment rather than quoting from a rate card. The assessment is deliberately small relative to the program it shapes: it examines the environment, the process, and the customization load before you commit to implementation spend, and it produces the business-case baseline of current cost per invoice, exception load, and discount leakage that the investment should be judged against. In our experience that sequence also protects you from the most expensive failure mode, which is scoping an implementation against assumptions instead of the actual state of your data, workflows, and custom code.