4.3 MRP, ERP, and Record Keeping

MRP, ERP, and Record Keeping

To manage incredibly complex supply chains and multifaceted internal operations, modern organizations rely heavily on sophisticated software architectures. Historically, manufacturing firms developed early computer systems strictly to manage physical materials on the factory floor. Over the decades, these evolved into massive, holistic enterprise systems that run the entire business. In this section, we will carefully define and contrast Material Requirements Planning (MRP) and Enterprise Resource Planning (ERP) systems, examine the vital financial control mechanism known as three-way matching, and underscore the critical, legal importance of secure record-keeping and audit trails.

Material Requirements Planning (MRP)

Material Requirements Planning (MRP) is a production planning, scheduling, and inventory control system used primarily in manufacturing environments. Its primary purpose is to ensure that raw materials are available for production and finished products are available for delivery to customers, all while maintaining the lowest possible inventory levels to save money.

How MRP Works: The Three Inputs

An MRP system works by taking three critical inputs to calculate exactly what materials need to be ordered and exactly when they must arrive:

1. Master Production Schedule (MPS): The overarching plan detailing what finished products the company plans to produce, in what quantities, and by what specific dates.
2. Bill of Materials (BOM): The "recipe" for the finished product. It is a hierarchical document detailing every single raw material, component, and sub-assembly required to manufacture one unit of the finished product.
3. Inventory Records Data: The current, real-time stock levels of all materials in the warehouse, as well as any materials that are already on order (scheduled receipts) and their expected arrival dates.

By processing these three inputs, the MRP system calculates the exact net requirements. It essentially answers three questions for the procurement team: What is needed? How much is needed? When is it needed?

A Worked Example of MRP Logic: Imagine a bicycle manufacturer.

• MPS: States the factory must build 500 bicycles next month.
• BOM: States that each bicycle requires exactly 2 wheels and 1 frame.
• Inventory Data: Shows we currently have 150 wheels and 100 frames in the warehouse.
• Calculation: Total wheel requirement (500 x 2 = 1000). Net wheel requirement (1000 total - 150 in stock = 850 wheels). Total frame requirement (500 x 1 = 500). Net frame requirement (500 total - 100 in stock = 400 frames).

The MRP system will automatically generate purchase requisitions for 850 wheels and 400 frames. Crucially, it will look at the supplier's lead time and stagger the orders so the parts arrive exactly when the assembly line needs them, avoiding the need to store them for weeks.

Enterprise Resource Planning (ERP)

While MRP focuses narrowly on manufacturing, scheduling, and inventory, Enterprise Resource Planning (ERP) systems are vastly broader in scope. An ERP system integrates all of an organization's core business processes into a single, unified software platform utilizing a single centralized database.

The Scope and Benefits of ERP

An ERP system typically includes fully integrated modules for:

• Procurement and Supply Chain Management (often incorporating advanced MRP II capabilities)
• Financial Accounting, Accounts Payable, and Accounts Receivable
• Human Resources and Payroll
• Customer Relationship Management (CRM) and Sales
• Warehouse Management and Logistics

The most significant advantage of an ERP system is the complete elimination of data silos. When procurement creates a purchase order in the ERP, the financial commitment is immediately visible in the accounting module, affecting cash flow projections. When goods are received in the warehouse, the inventory levels are updated enterprise-wide in real-time, and the accounts payable module is instantly notified that an invoice can now be legally paid. This cross-functional visibility streamlines operations and significantly enhances the organization's ability to implement robust internal controls.

Three-Way Matching

One of the most important automated financial controls facilitated by an ERP system is three-way matching. This is a strict accounts payable process that safeguards the organization's assets by ensuring that the company only pays for exactly what was ordered and exactly what was physically received.

The Three Documents

The process involves matching three specific documents before an invoice is ever approved for payment:

1. The Purchase Order (PO): Issued by the buyer, specifying exactly what was requested, the quantity ordered, and the agreed contract price.
2. The Goods Receipt Note (GRN): Generated by the receiving department (e.g., the warehouse), detailing what was physically delivered off the truck and in what condition.
3. The Supplier's Invoice: The formal request for payment issued by the supplier, detailing the quantity billed and the price charged.

How the Match Works

The ERP system automatically cross-references these three records without human intervention.

• Quantity Match: Does the quantity billed on the invoice precisely match the quantity physically logged on the GRN? Does it also correspond to the original PO?
• Price Match: Does the unit price on the invoice exactly match the negotiated unit price on the PO?

If the system identifies a discrepancy—for example, the invoice bills for 100 units, but the GRN shows only 90 units were actually received on the loading dock—the invoice is automatically placed on "hold" or flagged as a "variance." The payment is blocked until the discrepancy is manually investigated by procurement and resolved with the supplier. This automated control is a primary defense against supplier overbilling, administrative clerical errors, and internal fraud.

Secure Record-Keeping and Data Integrity

The operational effectiveness of both MRP and ERP systems relies entirely on the accuracy, security, and integrity of the data they contain. Accurate record-keeping is not merely an administrative chore; it is a foundational pillar of organizational governance, legal compliance, and risk management.

Audit Trails

An audit trail is a secure, chronologically logged, and unalterable electronic record that provides documentary evidence of the sequence of activities that have affected a specific operation, procedure, or event within the system.

In an ERP system, if a buyer logs in and changes the price on an existing purchase order, the system automatically records who made the change (via their unique user ID), when the change was made (with a timestamp), and what the previous value was before the edit. This permanent trail is essential for:

• Internal Accountability: Ensuring employees adhere to delegated authority limits and procurement policies.
• Dispute Resolution: Providing incontrovertible, time-stamped evidence if a supplier disputes agreed-upon terms, delivery dates, or pricing.
• External Auditing and Legal Compliance: Allowing financial auditors, regulatory bodies, or tax authorities to verify that internal controls (such as the separation of duties between the person who orders goods and the person who pays for them) are functioning correctly and that no fraudulent activity has occurred.

Data Integrity

Data integrity refers to the overall completeness, accuracy, consistency, and validity of data over its entire lifecycle. In procurement, compromised data integrity (e.g., incorrect supplier banking details, outdated pricing tables, or inaccurate BOMs) can lead to severe financial losses, misdirected payments to fraudulent accounts, or complete production halts. Maintaining high data integrity requires strict system access controls, regular data cleansing exercises, and comprehensive user training.