Written by: JJ Tan, Founder, Jelly
Last reviewed: September 2026
SAP VIM (Vendor Invoice Management, delivered by OpenText) sits inside an SAP estate as the invoice-processing layer. For multi-site hospitality, it centralises invoice ingestion, matches PO and non-PO invoices, routes them by company code, plant and cost centre, and posts them into SAP.
Key Takeaways
- SAP VIM centralises invoice ingestion, matching and posting for multi-site hospitality groups but requires an existing SAP estate and significant implementation effort.
- The platform excels at routing PO and non-PO invoices across company codes, plants and cost centres, while leaving dish-level food cost and supplier price analytics to other tools.
- Implementation timelines span multiple months, demand clean master data and dedicated internal resources, and are unavailable on S/4HANA Public Cloud.
- For 5–50 site UK hospitality operators without SAP, the combination of limited margin insight and lengthy rollout makes SAP VIM a poor fit for protecting margins.
- Jelly delivers invoice automation, live dish costing and supplier price alerts from week one at £129 per site.
What SAP VIM Actually Is and Where Its Scope Ends
OpenText Vendor Invoice Management for SAP is a SAP-native invoice management application that runs inside SAP as an ABAP layer. It extends standard AP transactions with data enrichment, configurable business rules, multi-step workflow routing and a document-capture layer provided by OpenText Core Capture for SAP. OpenText Core Capture handles the document side of the pipeline: it receives emailed PDFs, scanned invoices and image files, performs OCR, and feeds the extracted data into VIM’s workflow.
OpenText is the vendor behind VIM. The solution is SAP-certified and extends SAP S/4HANA, SAP Business Technology Platform and SAP SuccessFactors HCM. The S/4HANA Cloud versus ECC distinction matters in practice. SAP VIM is not available on S/4HANA GROW (Public Cloud) because it is designed as a classic on-premise or private-cloud add-on. Most 5–50 site UK hospitality businesses do not run S/4HANA at all, which is the first and most important fact to establish before any evaluation goes further.
VIM’s scope covers the invoice journey: ingestion, extraction, validation, approval routing and posting. It manages invoice workflows and validations and integrates with SAP modules, a scope that focuses on the invoice journey itself rather than downstream business-intelligence visibility over food and beverage margin, supplier price creep or dish-level profitability.
How SAP VIM Routes Invoices Across a Multi-Site Hospitality Estate
In SAP, the routing model maps directly onto a hospitality group’s legal and operational structure. Company Code represents the legal entity that owns or operates the sites. Plant represents the individual property, such as the hotel in Edinburgh, the pub in Bristol or the restaurant in Shoreditch. Cost Centre represents the department within that property, such as kitchen, bar, housekeeping or maintenance.
SAP VIM routes invoices using configurable rules that reflect an organisation’s AP structure. Routing is determined by amount, vendor, cost centre, department or geography and is governed by rule-based approval chains with automatic escalation when an approver does not act.
A concrete example helps. A food supplier delivers to six sites and sends one consolidated invoice. In a correctly configured VIM estate, that invoice arrives at the central AP hub. It is then split by line item, matched to the correct Plant and Cost Centre for each site, and routed for approval to the relevant general manager or head chef. The process flow looks like this:
Invoice ingestion (email / scan) ↓ Central AP hub (OpenText Core Capture, OCR and extraction) ↓ PO or non-PO decision ↓ Coding to Company Code / Plant / Cost Centre ↓ Approval routing (including mobile approval via SAP Fiori) ↓ Posting to SAP ↓ Payment
SAP VIM approvers can act from mobile devices or SAP Fiori, which removes approval delays caused by travel and remote working. For a hospitality group where GMs and head chefs are rarely at a desk, Fiori-based mobile approval becomes the practical mechanism. That approval confirms a cost and completes the workflow. It does not interpret the margin impact of that cost.
PO vs Non-PO Invoices in Hospitality: How VIM Handles Each Type
The PO versus non-PO split behaves differently in hospitality than in many other industries. Food and beverage deliveries are often non-PO or goods-receipt-matched. A head chef orders verbally or by phone, the delivery arrives and the invoice follows. Utilities, linen, CapEx and marketing spend usually follow more structured procurement routes. The table below shows how each common hospitality invoice type is matched and approved in SAP VIM, with most F&B invoices flowing through non-PO or goods-receipt-matched routes where manual coding and approval effort concentrates.
T-codes that matter in a hospitality VIM rollout include MIRO (invoice verification against a PO), MIGO (goods receipt posting), FB60 (direct vendor invoice posting without a PO), MR8M (cancel a material document or reverse a goods receipt) and MIR7 (park an invoice for later posting). These are the transactions AP teams and SAP partners reference during configuration and testing.
| Invoice Type | Typical PO Status | Matching Method | Approval Owner |
|---|---|---|---|
| F&B supplier invoices | Non-PO or informal PO | MIGO goods receipt match or FB60 direct posting | Head Chef or Site GM |
| Linen and laundry | Standing order or PO | MIRO against PO | Housekeeping Manager or GM |
| Utilities | Contract-based, no PO | FB60 direct posting | Finance Manager or Operations Director |
| CapEx and equipment | Formal PO | MIRO three-way match (PO, MIGO, invoice) | Finance Director or Owner |
| Marketing and agency spend | Non-PO or project PO | FB60 or MIRO against project PO | Marketing Lead or Operations Director |
| Maintenance and repairs | Variable, often non-PO for reactive work | FB60 for reactive, MIRO where PO raised in advance | Facilities Manager or Site GM |
Where SAP VIM Stops for Multi-Site Hospitality
SAP VIM handles decentralised invoice ingestion, PO matching, approval routing with escalation, touchless posting for matched invoices, a full audit trail and multi-entity coding across company codes, plants and cost centres. VIM’s rule engine manages multi-step approvals across cost centres, three-way match enforcement against POs and goods receipts, and conditional GL coding by vendor or category.
For hospitality, the gaps sit in the margin story rather than the workflow. SAP VIM posts invoices but cannot tell you your food cost per dish. It cannot flag that your beef supplier has crept up 8% across twelve sites. It cannot show dish-level or menu-level gross profit margin, connect invoice line items to recipes and sales mix or produce a daily GP report that a head chef or operations director can act on without waiting for month-end.
This reflects scope rather than quality. VIM preprocesses invoices before posting them to SAP, managing invoice workflows and validations, a scope that covers the invoice journey itself rather than downstream business-intelligence visibility over food and beverage margin. For a hospitality group where food and beverage costs typically represent 25–35% of hotel revenue, the gap between posting an invoice and understanding its margin impact is where money leaks away.
See how Jelly closes that gap with live dish costing, supplier price alerts and daily GP reporting.
Implementation Reality for SAP VIM in Hospitality
SAP VIM operates as an ERP programme rather than a simple plug-in. The implementation effort mirrors that reality.
The first decision concerns the SAP platform. VIM is fully available on RISE with SAP (S/4HANA Cloud Private Edition) but unavailable on GROW with SAP (S/4HANA Cloud Public Edition). VIM versioning is tied directly to the SAP S/4HANA release, so upgrading to SAP S/4HANA 2025 requires VIM version 25.4. The ERP road map therefore constrains VIM upgrade scope and timing. SAP mainstream maintenance for ECC ends in 2027, which places any group still on ECC inside the migration planning window now.
The internal resource requirement is substantial. A core mid-market SAP implementation typically requires a project manager or steering committee lead at 30–50% of time, business process owners at 20–40% during workshops and testing, and an IT lead at 50–100% during the Realize phase. The dependency on clean master data, including supplier records, material master and cost centre hierarchy, is non-negotiable. Data quality problems are the second most common cause of SAP project delays.
A mid-size UK hospitality group without an existing SAP estate would, in effect, buy an ERP programme to solve an AP problem. For scoping, timelines and licence costs specific to your situation, engage a qualified SAP partner, because the variables are too organisation-specific to generalise reliably.
How to Automate Invoice Processing in SAP for a Multi-Site Hospitality Group
Groups with an existing SAP estate that proceed with VIM can follow the implementation sequence below, which reflects current best practice.
- Confirm the SAP platform and estate scope. Establish whether the group runs ECC, S/4HANA Private Cloud or Public Cloud, as this determines VIM availability and the correct VIM version.
- Cleanse supplier and cost centre master data. VIM routing logic depends on clean vendor records, material masters and cost centre hierarchies. Data gaps at this stage cause mis-postings that are difficult to unwind.
- Define Company Code, Plant and Cost Centre mapping per site. Document the legal entity, property and department structure before configuration begins, mapping each hospitality site to its SAP objects.
- Configure PO and non-PO invoice routes. Set the business rules that determine whether an invoice is matched via MIRO, posted via FB60 or routed for manual coding, with tolerance thresholds appropriate to each invoice type.
- Set approval workflows and Fiori mobile approvals. Configure multi-step approval chains by amount, vendor and cost centre, and enable SAP Fiori for mobile approval so GMs and head chefs can act away from a desk.
- Connect invoice ingestion channels. Establish the email gateway, scan integration and any EDI or Peppol channels through OpenText Core Capture for SAP.
- Pilot at one or two sites. Run a controlled pilot with a subset of suppliers and invoice types before full rollout, using the pilot to tune OCR confidence thresholds and exception handling.
- Roll out across the estate. Replicate the configured workflow, approval chains and ingestion channels to remaining sites, with hypercare support through the first complete financial period.
The Solution: When SAP VIM Is Right, and When Jelly Is the Smarter Buy
SAP VIM suits large hospitality groups with an existing SAP estate, complex multi-entity legal structures, a dedicated finance and IT function to configure and maintain it, and a strategic commitment to the SAP platform. When those conditions are met, VIM’s depth of workflow configuration, audit trail and multi-entity posting capability is difficult to match.
Growing UK restaurants, pubs and boutique hotels often sit in a different position. They typically operate 5–50 sites, lack an SAP estate and need clear line-item F&B cost visibility.
Jelly is built specifically for this hospitality operating model. It digitises every invoice line item via photo or email, integrates directly with Xero for accounting and turns that data into live dish costing, supplier price alerts and gross profit visibility. These capabilities fill the margin insight gap that SAP VIM leaves. Relevant features include:
- Automated Invoice Scanning, with every line item (quantity, SKU, price, tax) captured via email or photo and no manual data entry.
- Price Alert, which flags every supplier price increase or decrease and gives chefs and operators evidence to negotiate credits or switch suppliers before the margin impact compounds.
- Flash Report, which provides a daily, weekly or monthly gross profit margin view calculated from invoice costs and POS sales data.
- Menu Engineering (Sales Mix), via native POS integration with complementary tools, showing which dishes are most popular and most profitable.
- Cookbook and Live Dish Costing, with recipes built from scanned invoice ingredients and dish GP margins updating automatically as new invoices arrive.
- Xero Integration, with a one-click push of digitised invoices into accounting and a reported 90% reduction in bookkeeping time.
Jelly charges a flat rate of £129 per month per location with no variable charge per user or feature and completes onboarding within the first week. What used to take 28 minutes to cost a single menu item takes 3 minutes on Jelly. Amber, a Mediterranean restaurant in East London, saves £3,000–£4,000 per month through invoice automation, price change alerts and real-time recipe costing. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue. Populu lifted GP from 68% to 72% across 16 locations.
The contrast with an ERP programme centres on time to value as much as cost. Jelly generates initial value in the first week. A SAP VIM implementation for a group without an existing SAP estate runs as a multi-month programme before a single invoice posts.
See how Jelly handles invoice processing and F&B margin tools in action for your sites.
For further reading on invoice automation approaches, see Jelly’s guides on how to automate invoice processing and invoice automation best practices for hospitality teams.
Below are answers to the most common questions UK hospitality operators ask when evaluating SAP VIM for multi-site invoice processing.
Frequently Asked Questions
What Is the Difference Between MIRO and MIGO?
MIRO (Logistics Invoice Verification) is the SAP transaction used to post a vendor invoice against a purchase order, matching the invoice to the PO and, where applicable, to a goods receipt. MIGO (Goods Movement) is the transaction used to record the physical receipt of goods into SAP. It confirms that a delivery has arrived and updates stock levels. In a three-way match process, MIGO is completed first when goods arrive, and MIRO is then used to verify and post the supplier’s invoice against both the PO and the MIGO goods receipt document.
Can You Process an Invoice in SAP Without a Purchase Order?
Yes. Non-PO invoices in SAP are typically posted using transaction FB60 (Enter Vendor Invoice), which allows direct coding to a GL account, cost centre and company code without referencing a purchase order. In SAP VIM, non-PO invoices always require manual approval because there is no PO to match against. They route to the relevant department head or cost centre owner for coding and sign-off before posting.
What Is the Difference Between MIRO and FB60?
MIRO is used for invoice verification within the Materials Management (MM) module. It requires a purchase order and, optionally, a goods receipt, and is the standard route for procurement-linked invoices. FB60 is a Financial Accounting (FI) transaction for posting vendor invoices directly to the general ledger without a PO reference. It is used for services, utilities, non-PO spend and other invoices that do not originate from a procurement process. In a hospitality context, most F&B supplier invoices that arrive without a formal PO are processed via FB60 or a VIM non-PO workflow that ultimately posts through FB60.
How Long Does SAP VIM Take to Implement for a Multi-Site Hospitality Group?
The answer depends on whether the group already has an SAP estate. For a group with an existing SAP ECC or S/4HANA Private Cloud environment, a focused VIM rollout covering a defined set of sites and invoice types is a multi-month project. The exact duration depends on master data quality, the number of approval workflow variants required and the complexity of the ingestion channels. For a group without any SAP estate, the VIM implementation is preceded by the SAP platform implementation itself, which for a mid-market organisation is typically measured in months rather than weeks. A qualified SAP partner can provide a scoping assessment specific to your estate.
Do I Need S/4HANA to Use SAP VIM?
No. SAP VIM runs on SAP ECC as well as S/4HANA Private Cloud (RISE with SAP). However, VIM is not available on S/4HANA Public Cloud (GROW with SAP), so groups on the public cloud edition must evaluate alternatives such as SAP Central Invoice Management or a third-party AP automation tool. VIM versioning is tied to the SAP platform release, which means the VIM version must be selected based on the SAP target release rather than independently. That constraint makes the platform decision the first step in any VIM evaluation.
Conclusion: Choosing the Right Tool for Multi-Site Hospitality Margins
The problem facing multi-site hospitality finance teams in 2026 goes beyond processing invoices. Combined profits at the UK’s 100 largest restaurant groups fell 44% year-on-year despite revenues rising, and food and non-alcoholic drink inflation is forecast to reach 3.9% by December 2026. In that environment, posting invoices accurately is necessary but insufficient. The right solution for a growing UK hospitality group centralises invoice capture, surfaces line-item F&B cost changes in real time, tracks supplier price movements across every site and connects those costs to dish-level and menu-level gross profit without requiring a full ERP programme.
SAP VIM operates as a powerful AP engine for organisations already inside the SAP ecosystem. For the operators described earlier who lack an SAP estate, the implementation effort, internal resource requirement and absence of hospitality-native margin insight make it the wrong tool for the job. Jelly was built for this operating model. It delivers invoice automation that starts generating value in the first week at £129 per month per location, with the dish costing, price alerts and GP reporting that turn invoice data into margin decisions.