ERP Glossary — Specialist Terms Explained

ERP selection and implementation projects produce a dense vocabulary that mixes software engineering, accounting practice, supply-chain management and US 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 US-specific context (US GAAP, SOX, IRS record-retention, sales tax nexus, 1099 reporting) is explained where the underlying concepts matter for compliance. The aim is to flatten the learning curve for stakeholders new to ERP projects, not to substitute for deeper reading.

The glossary is organized 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 (GL): the central financial accounting record that aggregates all transactions and produces the trial balance and financial statements.
Accounts Payable (AP): the module managing supplier invoices, three-way match and payment runs.
Accounts Receivable (AR): the module managing customer invoices, collections and credit control.
Fixed Assets: the module managing capitalized 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): optimized production scheduling across multiple constraints, typically layered on top of ERP's MRP-II.
Bill of Material (BOM): the structured list of components and quantities required to produce a finished product.
Routing: the sequence of operations required to produce a product, with associated work centers and times.
WMS (Warehouse Management System): specialized 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

US-specific compliance terminology that buyers and project teams regularly stumble over:

US GAAP (Generally Accepted Accounting Principles): the accounting standards issued by the FASB that govern financial reporting in the United States. ERP financial modules must produce statements consistent with US GAAP, including revenue recognition under ASC 606.
ASC 606 (Revenue from Contracts with Customers): the FASB standard defining how and when revenue is recognized. Subscription, project and multi-element deals make ASC 606 a core ERP configuration topic.
SOX (Sarbanes-Oxley Act): federal law requiring public companies to certify the effectiveness of internal controls over financial reporting. Section 404 drives ERP requirements for audit trails, segregation of duties and change control.
IRS record retention: the IRS generally requires business and tax records to be kept for three to seven years depending on the document and situation; ERP systems should support tamper-evident archiving and retrievable history to meet these obligations.
Audit trail: an immutable, time-stamped record of every transaction and change. US auditors and SOX testing rely on complete, non-editable journal records and change history.
Sales and use tax: state and local transaction taxes that replace the European VAT model. ERP tax engines must apply the correct rate by jurisdiction, often via integration with a tax-calculation service (for example Avalara or Vertex).
Economic nexus: the post-Wayfair standard under which a seller owes sales tax in a state once it exceeds that state's sales or transaction threshold, even without a physical presence. ERP must track sales by state to manage registration and filing.
1099 reporting: IRS information returns (such as 1099-NEC and 1099-K) used to report payments to contractors and other payees. ERP accounts-payable modules typically generate and file these.
W-9: the IRS form used to collect a vendor's taxpayer identification number; ERP vendor onboarding workflows capture and validate this data for 1099 reporting.
SOC 2 (System and Organization Controls 2): the AICPA attestation report covering a cloud vendor's security, availability and confidentiality controls. The US equivalent of the assurance buyers look for when evaluating SaaS ERP providers.
HIPAA: the federal health-information privacy and security rules that apply when an ERP processes protected health information, relevant for healthcare and life-sciences buyers.
FDA 21 CFR Part 11: the FDA rule governing electronic records and electronic signatures, mandatory for ERP systems used in FDA-regulated pharmaceutical, medical-device and food production.
E-invoicing: the US has no nationwide B2B e-invoicing mandate; federal agencies require electronic invoicing for procurement (B2G), and voluntary adoption is growing through the industry-led network governed by the DBNAlliance.
State data-privacy laws: a patchwork of state statutes (for example the CCPA/CPRA in California) governs consumer personal data and increasingly affects how ERP and CRM data is stored, accessed and deleted.
IFRS: International Financial Reporting Standards, used by foreign-owned US entities and multinationals that report on a non-US-GAAP basis or maintain parallel ledgers.

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 center.
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 standardized processes.
Brownfield: migration that preserves existing customizations 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 US 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: centralized repository for raw structured and unstructured data.
Data Warehouse: structured analytical database optimized 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: standardized 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 structured statement of requirements. See our requirements document template.
Functional Specification: the supplier's detailed solution design, written after vendor selection. See our requirements document vs functional specification 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): the contractual document defining scope, deliverables and acceptance criteria for the implementation.
MoSCoW: prioritization 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.
Escalation clause: contract clause specifying how subscription fees increase over time, often tied to an index such as CPI.
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 license 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: license model where each user is individually identified.
Concurrent user: license model where the number of simultaneous users is capped.
Transaction-based license: license model where pricing scales with transaction volume.
Configuration: system setup that goes beyond standard parameters but stops short of code modification; often distinguished from customization, which involves changing or extending the code.

Complete glossary index

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