Plain explanations of how procurement systems work.
Catalogs, PunchOut, EDI, supplier data. Written by people who have run these systems, checked before publishing.
What is a supplier portal? What it solves and what it does not
A supplier portal moves data entry to the party that has the data. That argument is right, and it stops working once every buyer reaches it independently.
What is supplier master data? The record everything depends on
Supplier master data is the authoritative record of a supplier, held in the systems that pay them. What it carries, why duplicates cost, who may change it.
What is EDI in procurement? X12, EDIFACT and beyond
EDI is the exchange of structured business documents between trading partners. X12 and EDIFACT messages, why implementation guides matter, EDI versus cXML.
What is OCI? SAP's PunchOut interface explained
OCI is SAP's Open Catalog Interface: PunchOut with HTTP form fields, not XML. How HOOK_URL works, what NEW_ITEM fields carry, how it compares with cXML.
What is UNSPSC? Product classification explained
UNSPSC is the hierarchical code scheme most procurement platforms use to classify products and services. How it differs from eCl@ss, and where it breaks.
What is spend analysis? Making spend data usable
Spend analysis turns scattered purchasing records into a picture of what is bought, from whom, at what price. The hard part is the data, not the analysis.
What is maverick spend? Causes and cures
Maverick spend is buying that ignores an existing contract or process. It is usually blamed on discipline, and it is almost always a system failure.
What is tail spend and why it resists control
Tail spend is the mass of small transactions spread across many suppliers: most of the administrative work, little of the value. Why it resists control.
Direct vs indirect procurement: what changes
Direct buys what goes into the product, indirect what runs the business. The split changes how demand arises, which systems carry it, what failure costs.
What is a GPO? Group purchasing explained
A group purchasing organisation pools many independent members' volume to negotiate terms none could reach alone. How it is funded, and where it breaks.
What is a PunchOut gateway? Solving the N by M problem
Every buyer-supplier PunchOut connection is built and maintained separately, so effort scales with buyers times suppliers. A gateway collapses that.
Catalog management: why clean catalog data is hard
Loading a supplier catalog is easy. Keeping thousands of them accurate through price changes, unit mismatches and discontinued lines is the actual problem.
What is supplier onboarding? From first contact to first order
Supplier onboarding turns an approved vendor into one you can actually transact with: the stages, the data required, and the step most organisations skip.
What is three-way matching? Invoice controls explained
Three-way matching reconciles purchase order, goods receipt and invoice before payment. Where tolerances fit, and why most exceptions start upstream.
Purchase requisition vs purchase order: the difference
A requisition is an internal request. A purchase order is an external commitment. The boundary between them is where procurement control actually lives.
Hosted catalog vs PunchOut: how to choose
Hosted catalogs give you search and control; PunchOut gives accuracy and no maintenance. A category-by-category framework for matching model to supplier.
What is cXML? The protocol behind PunchOut
cXML is the XML dialect most procurement systems use for catalogs, orders and invoices: structure, message types, and how it compares to EDI and PEPPOL.
What is PunchOut? The cXML round trip explained
PunchOut lets an employee shop on a supplier's site from inside the procurement system and returns the cart as a requisition. The round trip, step by step.
What is a procurement catalog? Hosted, PunchOut and CIF
A procurement catalog is the structured list of what employees may buy at agreed prices: the three types, the file formats behind them, and how to choose.
What is a procurement system? Source to pay explained
A procurement system is software that moves a purchase from need to payment: what each stage does, where S2P, P2P and e-procurement fit, how they connect.
CSRD supplier data hospitality: pause or accelerate in 2026?
The CSRD Omnibus delayed Wave 2 reporting, but Wave 1 customer and lender requests still flow. How hospitality procurement should respond in 2026 and after.
EUDR compliance hotel F&B procurement: 2026 playbook
EUDR compliance hotel F&B procurement now sits on the 2026 board agenda. Build first-party geolocation traceability before the 30 December cutover hits.
PEPPOL e-invoicing hotel procurement: the 2026 shift
PEPPOL crossed 2.54M participants across 111 countries. What the network effect, the Belgian mandate, and BIS 3.0 mean for hotel AP architecture in 2026.
PMS vs P2P System of Record: F&B Demand Signals 2026
How PMS procurement integration multi-property design shifts in 2026 as API-first PMS marketplaces redraw the boundary between PMS and P2P systems of record.
AI procurement hospitality adoption: the production gap
Hackett and McKinsey 2026 data show AI procurement hospitality adoption is doubling, yet only a small share reaches production. Two paths forward for hotels.
Procurement Automation Hospitality: The 2026 Capacity Gap
Hackett forecasts an 8% workload jump against shrinking 2026 budgets and headcount. We weigh procurement automation hospitality teams need versus BPO.
Supply Chain Resilience Hospitality Procurement 2026
Hackett's 2026 study ranks supply continuity above cost. Here is how hospitality buyers should re-weight supplier scorecards for the new risk landscape.
ViDA 2026: E-Invoicing Compliance, Hospitality Europe
E-invoicing compliance hospitality Europe in 2026: choose one EU-wide AP architecture aligned with ViDA, or run four country compliance regimes in parallel.
Hello from BoreaTech
A first note from the BoreaTech team about why this blog exists and what to expect.