How to Implement UNSPSC Classification in SAP

The SAP problem nobody talks about

SAP is the system of record for procurement at hundreds of infrastructure, manufacturing, and facilities management companies across Europe. It captures purchase orders, goods receipts, and invoices with impressive reliability. What it does not do well — and was never designed to do — is classify what was bought.

SAP stores line items as free-text descriptions entered by engineers, buyers, or suppliers. The same bolt appears as "M8 bolt galvanised," "galv bolt M8," "bolt M8 HDG," and "bolzen M8 verzinkt" across different sites and suppliers. A maintenance job might read "elektra werkzaamheden," "electrical works," or simply "works Q3." Without consistent classification, none of this data is comparable or aggregatable.

UNSPSC solves this by providing a standard four-level hierarchy — segment, family, class, commodity — that turns those free-text descriptions into consistent categories. But getting UNSPSC codes into SAP is where most procurement teams get stuck.

Three approaches to UNSPSC in SAP

Option 1: Manual coding in SAP master data

Some procurement teams try to enforce UNSPSC classification at the point of entry — requiring buyers to select a UNSPSC code when creating a purchase order or material master record.

This sounds clean in theory. In practice it fails for three reasons:

• Buyers pick the wrong code. The UNSPSC hierarchy has over 55,000 commodity codes. Without deep category knowledge, buyers default to whichever code is closest or already in the dropdown. Consistency disappears quickly.
• It only covers new data. Existing purchase history — often years of spend — has no classification at all.
• It creates admin overhead. In high-volume procurement environments, adding a mandatory field to every transaction slows down the people who matter most.

Option 2: Classification via a third-party tool integrated with SAP

Several procurement platforms offer UNSPSC modules that can be integrated directly with SAP via API or middleware. These tools classify spend automatically based on material descriptions, supplier codes, and purchase categories.

The challenge is that most of these tools are rules-based: they work well for standard materials (MRO parts, common consumables) but fail on the unusual, the ambiguous, or the industry-specific terminology that makes up a large share of FM and infrastructure spend.

A rules engine alone typically achieves 60–70% coverage. The remainder sits unclassified or is assigned to a catch-all category that defeats the purpose.

Option 3: Automated classification outside SAP, with clean data returned

The most practical approach for SAP users is to export spend data — purchase orders, invoices, or a combination — and run it through a classification engine that combines rules, machine learning, and LLM layers. Classified data is then returned in the original format and loaded back into SAP as a material attribute or spend analytics field.

This approach does not require any SAP configuration changes. It works on historical data as well as ongoing transactions. And it handles the edge cases that rules-based tools miss.

What data to export from SAP

For UNSPSC classification, you need at minimum:

• Line item description (the free-text field — usually MAKTX or the PO item text)
• Supplier name or supplier ID
• Purchase order value
• GL account or cost element (useful for routing boost — maintenance costs vs. capital expenditure)
• Existing material group or commodity code if available (used as a prior by the ML layer)

The export can be done via SAP transaction ME2M or ME2N for purchase orders, or FB03 for invoices. Most teams export to CSV and share via secure file transfer.

What good UNSPSC classification looks like in SAP output

A well-classified SAP spend dataset should achieve:

• 90–95% commodity-level classification — not just segment or family, but the four-digit commodity code
• Consistent coding across sites and suppliers — the same physical item gets the same code regardless of how it was described in the PO
• Minimal "catch-all" codes — codes like 95121500 (Paper materials) or 80101500 (Management advisory services) should cover only genuinely ambiguous items

Once classified, the data is typically loaded into SAP as a custom field on the purchase order or material master, or fed into a BI layer (SAP Analytics Cloud, Power BI, or Tableau) for spend analysis.

The review queue — and why it matters

Even the best automated classification engines leave some items below the confidence threshold. These items are flagged for human review — typically 5–10% of the dataset.

The critical thing is what happens after review. Every human decision should feed back into the classification model, so the same item type is automatically classified correctly next time. Over six to twelve months of continuous operation, the review queue shrinks to near zero as the model learns from your team's decisions.

This is the difference between a tool that classifies your spend once and a system that gets better the longer you use it.

Timing: how long does it take?

A typical SAP spend classification engagement for a mid-sized infrastructure or FM company:

| Phase | Duration | |---|---| | Data export and preparation | 1 week | | Initial classification baseline (Data Stability Baseline) | 2–3 weeks | | Review of flagged items | 1 week | | Final classified dataset returned | 4–6 weeks total |

Ongoing monthly classification of new invoice data runs automatically with no additional input from the client team.

Common questions from SAP procurement teams

Can you classify data from SAP S/4HANA as well as older ECC versions?

Yes. The classification engine works on exported data regardless of SAP version. The export format is the same for both ECC and S/4HANA.

What if our material descriptions are in Dutch or German?

Dutch and German-language descriptions are handled natively. The LLM layer has strong multi-language capability, and the rules layer can be configured with language-specific patterns.

Do you need access to our SAP system?

No. Classification runs on an export. Pearstop never needs direct access to your ERP environment.

What if we have both SAP and non-SAP systems?

Data from multiple systems can be merged and classified in a single run, with a unified taxonomy applied across all sources.

Next steps

If your SAP spend data is sitting unclassified — or classified inconsistently across sites — the fastest way to get a spend baseline is a Data Stability Baseline engagement. You export your spend data, Pearstop classifies it and returns a clean, UNSPSC-coded dataset within four to six weeks. That baseline becomes the foundation for category management, supplier consolidation, and accurate margin estimating.

Book a 7-minute discovery call to see how the classification engine would work with your SAP data.

Related reading: What Is UNSPSC — And Why Hard Services Companies Should Care | UNSPSC vs. eClass vs. CPV

Pearstop Team

Pearstop

Pearstop helps procurement and operations teams in hard services, FM, construction, and manufacturing turn messy data into a reliable foundation for decisions, AI, and category management.

LinkedIn →