ERP Glossary — Specialist Terms Explained

ERP selection and implementation projects produce a dense vocabulary that mixes software engineering, accounting practice, supply-chain management and DACH-specific regulatory terminology. This ERP glossary covers more than 130 specialist terms that buyers, project managers and steering-committee members encounter routinely. The entries are written for non-specialists — each definition is short, jargon is unpacked, and DACH-specific context (GoBD, DATEV, ZUGFeRD, XRechnung, Requirements Document, Pflichtenheft) is preserved where the international equivalents would lose meaning. The aim is to flatten the learning curve for stakeholders new to ERP projects, not to substitute for deeper reading.

The glossary is organised by category so readers can navigate by topic rather than alphabetically: modules and functional areas, compliance and regulatory terminology, deployment and architecture, integration and data, implementation methodology, and commercial terminology. Each entry links to deeper editorial coverage where available. Selection teams who reach a shared vocabulary early in the project consistently move faster through requirements definition and vendor demos; investing 30 to 60 minutes in glossary review at project kickoff is one of the highest-return preparation activities available.

Modules and functional areas

The most frequently referenced glossary entries describing ERP modules and functional areas:

General Ledger (Hauptbuch): the central financial accounting record that aggregates all transactions and produces the trial balance and financial statements.
Accounts Payable (Kreditoren): the module managing supplier invoices, three-way match and payment runs.
Accounts Receivable (Debitoren): the module managing customer invoices, dunning, collections and credit control.
Fixed Assets (Anlagenbuchhaltung): the module managing capitalised assets, depreciation schedules and asset transfers.
MRP (Material Requirements Planning): calculates what materials need to be ordered or produced to meet demand, given current stock and lead times.
MRP-II (Manufacturing Resource Planning): extends MRP with capacity planning, routing and shop-floor control. Covered in detail in our production planning guide.
APS (Advanced Planning and Scheduling): optimised production scheduling across multiple constraints, typically layered on top of ERP's MRP-II.
Bill of Material (Stückliste): the structured list of components and quantities required to produce a finished product.
Routing (Arbeitsplan): the sequence of operations required to produce a product, with associated work centres and times.
WMS (Warehouse Management System): specialised software for warehouse operations including put-away, pick-pack-ship, cycle counting.
MES (Manufacturing Execution System): real-time shop-floor execution and data collection, sitting between ERP and physical machines.
PLM (Product Lifecycle Management): manages product data from design through end-of-life, including CAD integration and engineering change orders.
CRM (Customer Relationship Management): covers customer-facing pre-sale and post-sale processes. See our ERP vs CRM guide.
HCM (Human Capital Management): employee master, payroll, time and attendance, talent management.

Compliance and regulatory terminology

DACH-specific compliance terminology that international vendors and buyers regularly stumble over:

GoBD (Principles for the orderly maintenance and retention of books): deutsche principles for proper bookkeeping and electronic records retention. ERP systems must support GoBD-compliant audit trails, immutable journal records and time-stamped change history.
DATEV: a cooperative serving German tax advisors and accountants. DATEV interfaces are mandatory for many DACH ERPs because client companies often share data with tax advisors via DATEV.
ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland): a hybrid electronic-invoice format combining PDF and embedded structured data. Required for many German B2G transactions and increasingly used B2B.
XRechnung: the deutsche structured-XML electronic-invoice format for public-sector procurement. Mandatory for B2G invoicing.
Umsatzsteuer (VAT): value-added tax. The deutsche VAT rules (Umsatzsteuergesetz) have specific requirements for invoice content, reverse-charge mechanism, and intra-EU supplies.
BSI (Bundesamt für Sicherheit in der Informationstechnik): the German Federal Office for Information Security. The C5 catalogue defines security requirements for cloud services.
BDSG (Bundesdatenschutzgesetz): the German Federal Data Protection Act, layered on top of GDPR. Specific provisions for employee data processing.
Betriebsrat: the works council. Plays a formal role in any system touching HR data under the deutsche Works Constitution Act (Betriebsverfassungsgesetz).
GoBS (Grundsätze ordnungsmäßiger DV-gestützter Buchführungssysteme): the predecessor to GoBD, occasionally still referenced in older contracts.
AO (Abgabenordnung): the deutsche general tax code, which underpins many ERP-relevant retention requirements.
OSS (One-Stop-Shop): EU mechanism for simplified cross-border VAT registration for distance sales.
IOSS (Import One-Stop-Shop): EU mechanism for low-value goods imported from outside the EU.
GoB (Grundsätze ordnungsmäßiger Buchführung): the general principles of proper accounting under deutsche commercial law.
HGB (Handelsgesetzbuch): the deutsche Commercial Code, including accounting standards for non-listed companies.
IFRS: International Financial Reporting Standards, used by listed companies and increasingly by larger Mid-Market.

Deployment and architecture

Deployment-model and architecture terminology that recurs in selection conversations:

SaaS (Software as a Service): software delivered as a vendor-hosted service, multi-tenant, subscription-priced.
Multi-tenant: a single shared software stack serving many customers on a common code line.
Single-tenant: a dedicated software instance for one customer, typically hosted but not multi-tenant.
Public cloud: shared infrastructure operated by a hyperscaler (AWS, Azure, Google Cloud, sometimes Oracle Cloud).
Private cloud: dedicated infrastructure operated by the vendor, a hosting partner or the customer.
Hybrid cloud: combination of public and private cloud, often with on-premises components.
On-premises: infrastructure operated by the customer in the customer's own data centre.
RISE with SAP: SAP's bundled offering covering S/4HANA Cloud Private Edition with infrastructure and managed services.
GROW with SAP: SAP's mid-market-focused offering for S/4HANA Cloud Public Edition.
Lift-and-shift: migration that preserves the existing application configuration, moving it to a new infrastructure.
Greenfield: reimplementation from scratch, typically with standardised processes.
Brownfield: migration that preserves existing customisations and configurations.
Bluefield: middle-ground approach combining greenfield process design with selective brownfield data migration.
API-First: architectural pattern where all functionality is exposed through APIs before user interfaces.
Microservices: architectural pattern where applications are decomposed into independent services.
Composable ERP: emerging pattern combining a core ERP with surrounding specialist applications via APIs.

The deployment-model choice for DACH buyers is covered in detail in our cloud ERP vs on-premises decision matrix.

Integration and data terminology

Integration and data terminology that buyers should understand before evaluating vendor architecture claims:

REST API: the predominant modern API style based on HTTP, JSON and resource-oriented design.
SOAP: older XML-based API style, still in use for some enterprise integrations.
EDI (Electronic Data Interchange): structured B2B data exchange, common in automotive, retail and logistics.
iPaaS (Integration Platform as a Service): cloud-based integration middleware. Examples: Mulesoft, Boomi, Workato, SAP Integration Suite, Microsoft Power Automate.
ESB (Enterprise Service Bus): traditional on-premises integration middleware pattern.
Master Data Management (MDM): the discipline of governing customer, supplier and product master data across systems.
Data Lake: centralised repository for raw structured and unstructured data.
Data Warehouse: structured analytical database optimised for reporting and BI.
ETL (Extract, Transform, Load): the data-pipeline pattern for moving data between systems.
ELT (Extract, Load, Transform): modern variant that loads raw data first and transforms in the destination.
Webhook: mechanism by which one system pushes events to another via HTTP callbacks.
iDoc (SAP Intermediate Document): SAP-specific data interchange format.
BAPI (SAP Business Application Programming Interface): SAP-specific API style.
OData: standardised REST-based protocol for querying data, used by SAP and Microsoft.
Schema: the structured definition of a database or data interchange format.
Reference data: data that is rarely changed and shared across systems (e.g. country codes, currency codes).

Implementation methodology and commercial terms

Methodology and commercial terminology common in ERP selections and contracts:

Requirements Document: the buyer's requirements document. See our requirements document template.
Pflichtenheft: the supplier's functional specification, written after vendor selection. See our Requirements Document vs Pflichtenheft guide.
RFI (Request for Information): initial screening questionnaire to qualify vendors.
RFP (Request for Proposal): detailed structured questionnaire and commercial proposal.
POC (Proof of Concept): paid pilot to validate vendor capability on the buyer's critical processes.
SOW (Statement of Work): international equivalent of the Pflichtenheft, defining scope and deliverables.
MoSCoW: prioritisation method using Must / Should / Could / Won't-have categories.
Fit-Gap: structured analysis comparing requirements with a platform's standard capability.
Hypercare: intensive support period immediately following go-live.
UAT (User Acceptance Testing): end-to-end testing by business users with real scenarios.
Cutover: the formal transition from old system to new system, typically over a weekend.
Go-live: the date the new system starts operational use.
Hypercare exit: the formal end of intensive post-go-live support.
AMS (Application Management Services): ongoing operational support of the implemented system.
TCO (Total Cost of Ownership): all costs over a defined horizon, typically 5 to 7 years.
Indexation clause: contract clause specifying how subscription fees increase over time.
Indirect use: contractual term for system usage by non-licensed users, typically through portals or integrations. A material risk in SAP and Oracle contracts.
Audit clause: the vendor's contractual right to audit licence usage.
Exit clause: contract terms governing termination, data export and transition assistance.
SLA (Service Level Agreement): commitment to specific operational metrics, typically availability and response time.
Named user: licence model where each user is individually identified.
Concurrent user: licence model where the number of simultaneous users is capped.
Transaction-based licence: licence model where pricing scales with transaction volume.
Customising: term used in DACH practice for system configuration that goes beyond standard parameters but stops short of code modification.

Complete glossary index

Browse our complete library of 156 editorial entries in this category:

Frequently Asked Questions

How many entries does a comprehensive ERP glossary need?

A practical glossary for buyers and project teams covers 100 to 200 entries. Below 80 entries the glossary tends to be too shallow for serious project use; above 250 entries it becomes hard to navigate and includes terms that are rarely encountered. The 130+ entries in this glossary cover the operational vocabulary that recurs in DACH mid-market ERP projects.

Are the DACH-specific compliance terms understood by international vendors?

Variably. GoBD, DATEV, ZUGFeRD and XRechnung are routinely misunderstood by US-headquartered vendors during initial selection conversations; their DACH partners understand them perfectly. Buyers should test vendor understanding explicitly during demos and POCs rather than assume it. The depth of DACH-specific compliance handling is often a deciding factor between platforms that look comparable on functional coverage.

Should we standardise vocabulary at project kickoff?

Yes. Selection projects that establish shared vocabulary at kickoff move faster through requirements definition, vendor demos and contract negotiation. 30 to 60 minutes of glossary review with the project team and the steering committee is one of the highest-return preparation activities. The vocabulary that matters most is platform-specific terminology (RISE, GROW, SuiteSuccess, AppSource) plus the DACH-specific compliance terms.

What is the difference between MRP and APS in plain terms?

MRP (Material Requirements Planning) calculates what to buy or build and when, given demand and current stock. It assumes capacity is available. APS (Advanced Planning and Scheduling) optimises the production schedule under explicit capacity constraints, often with sequence-dependent setups and multiple alternative resources. Most ERPs include MRP; APS is usually an add-on for capacity-constrained operations. The difference is significant in practice. See our production planning guide.

What is "indirect use" and why does it matter?

Indirect use is a contractual term, particularly in SAP and Oracle agreements, for system usage by users who do not hold a named licence but interact with the system through portals, integrations or downstream applications. The contractual treatment of indirect use can produce six- and seven-figure surprises during licence audits. Buyers should request explicit clarification of indirect-use treatment during contract negotiation and revisit it before every significant integration project.