SAP's materials management module — purchasing, inventory and the invoice verification that closes the loop.
SAP MM (Materials Management) handles purchasing, inventory management and invoice verification. It owns the material master, the purchase requisition and order, goods receipt, and the three-way match against the supplier invoice. It is where most transactional volume in an SAP system sits, and where most master-data discipline is required.
MM is the module that most directly determines whether your stock figures and your payables are trustworthy. The three-way match lives here, the valuation of inventory lives here, and the material master drives behaviour across production, sales and planning. Configuration errors in MM therefore surface as problems that look like they belong to other modules.
Views by function — purchasing, accounting, MRP, storage. Each view is maintained by a different team, which is why governance matters.
Requisition captures need; the order is the commitment to a vendor, with release strategy enforcing approval.
Stock and the GRNI liability both post here. Movement type determines the accounts touched.
The three-way match. Within tolerance it posts; outside it blocks for review.
Valuation class and movement type together decide which GL accounts a stock movement hits.
A business configures a release strategy so purchase orders above a value threshold require director approval. It works well for two years. Then approvals start being bypassed, and nobody can explain how.
The mechanism is splitting. Buyers facing a slow approval queue began raising two orders just under the threshold instead of one above it. This was not fraud and was not hidden — it was a rational response to an approval process that took four days while suppliers held prices for two. The control was technically intact and operationally defeated.
The fixes are both procedural. Make approval fast enough that circumventing it is not worth the effort, which usually means delegating authority rather than escalating it. And monitor for the pattern — multiple orders to one supplier for similar materials within a short window — so splitting is visible rather than invisible. Controls that are slower than the business need are not controls; they are a tax on honesty.
| Term | What it means |
|---|---|
| Purchase requisition | An internal request to buy, before any commitment to a supplier. |
| Purchase order | The commitment to the supplier, with terms, prices and delivery dates. |
| Goods receipt | Recording what arrived, which values stock and creates the GRNI accrual. |
| Invoice verification | Matching the supplier invoice against order and receipt before payment. |
| Info record | The stored relationship between a material and a supplier, carrying price and lead time. |
Purchasing data entered by purchasing, accounting data by finance. One team guessing the others' fields produces systematic errors.
If approval can be avoided by splitting an order, it will be.
A generous tolerance passes exactly the differences the match exists to catch.
Custom movement types multiply and nobody remembers what posts where. Keep the set small and documented.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Purchase orders by approval level | Clustering just under a threshold is the signature of splitting. | |
| Requisition-to-order cycle time | Approval friction, which is what drives workaround behaviour. | |
| Receipts without purchase orders | Unauthorised buying, and a direct cause of unclearable accruals. | |
| Info record price vs actual | Whether stored prices reflect reality or have quietly gone stale. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.