Procurement, Inventory and Payables Systems

Introduction and Context

Procurement, inventory, and payables form a connected part of an enterprise resource planning (ERP) system. Together they support the movement of resources from external suppliers into an organization and the corresponding movement of cash to suppliers. The integrated process is commonly called procure-to-pay (P2P).

A well-designed P2P system does more than record purchases. It establishes authorization, creates an auditable evidence trail, protects organizational assets, supports reliable financial reporting, and provides management with information about suppliers, costs, stock levels, and cash commitments. Weak procurement systems can produce duplicate payments, unauthorized purchases, inventory shortages, excess stock, fraud, inaccurate liabilities, and poor supplier relationships.

The process normally begins with an internal need and ends when a valid supplier invoice has been approved and paid. Inventory records connect purchasing with operations and financial accounting. The ERP system therefore acts as a shared information platform in which purchasing, receiving, warehouse management, accounts payable, general ledger, and cash management use related data.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain the procure-to-pay cycle and its relationship to inventory and accounting.
2. Analyze requisitioning, purchasing, receiving, invoice processing, and payment activities.
3. Explain the purpose and operation of three-way matching.
4. Evaluate supplier master-data controls and segregation of duties.
5. Apply inventory valuation methods and calculate basic inventory measures.
6. Identify embedded ERP controls, risks, and opportunities for automation.
7. Assess ethical, governance, and professional issues in procurement and payables.

1. The Procure-to-Pay Cycle

The P2P cycle consists of linked business events rather than isolated accounting entries. A typical sequence is:

1. A department identifies a requirement.
2. An employee prepares a purchase requisition.
3. An authorized officer reviews and approves the requisition.
4. Purchasing selects an approved supplier and issues a purchase order.
5. The supplier delivers goods or services.
6. Receiving personnel inspect and record the receipt.
7. The supplier submits an invoice.
8. Accounts payable matches the invoice with the purchase order and receiving record.
9. An approved liability is recorded.
10. Payment is scheduled, authorized, and transmitted.
11. The transaction is posted to the general ledger and reconciled.

The purchase order is generally a commitment document, not an expense or liability. A liability usually arises when goods or services have been received and the supplier has a valid claim, subject to the applicable accounting framework and contractual terms. For goods received before the invoice, an ERP system may record a goods-received-not-invoiced (GRNI) or accrued-receipts balance.

A simplified accounting sequence for inventory purchased on credit is:

At receipt, when the invoice is not yet received:

When the invoice is approved:

When the supplier is paid:

The exact entries depend on the ERP configuration, perpetual or periodic inventory procedures, tax treatment, freight terms, and the applicable reporting framework.

Requisitioning

A purchase requisition is an internal request for goods or services. It normally specifies the requester, department or cost centre, required date, description, quantity, estimated price, suggested supplier, and business justification. Requisitions provide demand visibility and ensure that purchasing decisions are authorized before an external commitment is made.

A requisition should not automatically become an order. Approval may depend on monetary thresholds, budget availability, the nature of the item, supplier risk, and whether competitive quotations are required. An ERP workflow can route a requisition to the appropriate manager and prevent further processing until approval is recorded.

Purchasing and Purchase Orders

The purchasing function converts an approved requirement into a supplier commitment. A purchase order (PO) should contain a unique number, supplier identifier, item or service description, quantity, unit price, delivery location, requested date, payment terms, tax information, and relevant contractual conditions.

Common purchasing methods include:

• Catalog purchasing, using pre-approved items and prices.
• Request for quotation, in which suppliers compete for a defined requirement.
• Blanket or framework orders, used for recurring purchases over a period.
• Direct purchasing, appropriate for emergencies or specialized suppliers but requiring documented justification.
• Corporate-card purchasing, used for low-value, controlled transactions.

A PO creates standardization and evidence. It also supports commitment accounting, in which expected expenditure is compared with budgets before an invoice is received. However, a PO is not a substitute for supplier due diligence or management judgment.

Receiving

Receiving confirms what was delivered, when it arrived, and whether it conforms to the order. A receiving report should record quantities received, quantities rejected, visible damage, inspection status, and the identity of the receiving employee. For services, the equivalent evidence may be a service-entry sheet, milestone acceptance, or manager certification.

Receiving should be organizationally independent from purchasing where practical. Blind receiving—where the receiver sees the description but not the ordered quantity or price—can reduce the risk of simply accepting the order record without counting the goods.

Invoice Processing and Payment

Supplier invoices contain claims for payment. Accounts payable verifies supplier identity, invoice number, date, tax details, quantities, prices, payment terms, and supporting evidence. An invoice should be recorded once, assigned to the correct accounting period, and linked to the underlying transaction.

Payment processing includes payment selection, approval, bank-file creation or payment instruction, transmission, remittance advice, and reconciliation. Payment terms should be monitored because early-payment discounts may be financially beneficial, while late payment may damage supplier relationships or create penalties.

2. Three-Way Matching

Three-way matching compares three records:

1. The purchase order: what was authorized.
2. The receiving report: what was received.
3. The supplier invoice: what is being billed.

An invoice is normally approved when supplier, item, quantity, price, tax, and terms agree within established tolerances. A simplified quantity test is:

where Qᵢ is the invoiced quantity and Qᵣ is the accepted received quantity. The condition applies to goods invoices when overbilling is not permitted. If partial invoicing is allowed, the system must also compare cumulative invoiced quantity with cumulative accepted receipts.

A price test can be expressed as:

where Pᵢ is the invoice unit price, Pₚ is the PO unit price, and τₚ is the approved price tolerance. The absolute difference must be measured in the same currency and per the same unit of measure.

For an invoice with quantity Q and unit price P, excluding tax and other charges:

Additional terms such as freight, discounts, tax, and exchange-rate adjustments must be treated according to policy and the applicable accounting requirements.

Two-way matching compares the invoice with the PO and may be suitable for certain services or low-risk purchases. Four-way matching adds an inspection or quality-acceptance record and is appropriate where quality, serial numbers, or regulatory compliance is important.

Matching is not merely a mechanical activity. A valid exception may arise from an approved price change, partial delivery, substitute item, damaged goods, tax correction, or foreign-exchange movement. The system should route exceptions to an accountable employee rather than allowing users to override controls without explanation.

3. Supplier Master Data and Governance

Supplier master data includes legal name, address, tax identification number, bank details, contact information, payment terms, currency, and risk classification. Because payment instructions depend on this data, supplier-master maintenance is a high-risk activity.

Important controls include:

• independent verification of supplier identity;
• tax and sanctions screening where applicable;
• approval of new suppliers by authorized personnel;
• restricted access to create or amend supplier records;
• dual approval for bank-account changes;
• callback verification using an independently sourced telephone number;
• duplicate detection using tax number, bank account, address, and legal name;
• periodic review for inactive or duplicate suppliers;
• audit logs showing who changed what and when.

A supplier should not be approved solely because a requester recommends it. Conflicts of interest, related-party relationships, gifts, undisclosed commissions, and collusive bidding can undermine procurement integrity.

4. Inventory Systems and Information Flows

Inventory may include raw materials, work in progress, finished goods, merchandise, spare parts, and supplies. An ERP inventory record commonly contains an item code, description, unit of measure, location, quantity on hand, quantity available, quantity reserved, standard or moving cost, reorder parameters, lot or serial information, and status such as unrestricted, quarantined, or obsolete.

A perpetual inventory system updates quantity and value after each receipt, issue, transfer, adjustment, or sale. A periodic system determines inventory through physical counting and period-end calculations. ERP environments usually support perpetual records, but physical counts remain essential because system records can differ from physical reality.

Inventory information supports three related decisions:

• Availability: Can the organization satisfy demand?
• Replenishment: When and how much should be ordered?
• Valuation: What amount should be reported as inventory and cost of sales?

The reorder point under a basic deterministic model is:

where ROP is the reorder point in units, d is average demand per time unit, L is lead time in the same time unit, and SS is safety stock in units. The formula assumes that demand and lead time are represented consistently and that the organization has selected an appropriate safety-stock policy. It does not by itself account for order quantity, supplier minimums, seasonality, or uncertain demand.

5. Inventory Valuation

Inventory valuation affects assets, cost of sales, gross profit, and taxation. Under common financial reporting frameworks, inventory is generally measured at the lower of cost and net realizable value, subject to the applicable standard and industry-specific requirements. Net realizable value is generally the estimated selling price less costs of completion and costs necessary to make the sale.

The fundamental periodic relationship is:

All amounts must be measured on a consistent accounting basis. Net purchases may include directly attributable acquisition costs and exclude recoverable taxes, depending on the reporting framework.

Common cost-flow methods include:

• Specific identification: assigns actual costs to identifiable units. It is suitable for unique, high-value items.
• FIFO: assumes the earliest acquired units are sold first. The method is an accounting cost-flow assumption and may not reflect physical movement.
• Weighted average: calculates an average cost for units available. It is useful where units are interchangeable.

Under a moving weighted-average system, after a receipt:

The numerator and denominator must use the same currency and unit of measure. The method is not interchangeable with periodic weighted average, which calculates the average over a defined accounting period.

Worked Example: Weighted Average

An entity has 100 units costing $10 each. It purchases 50 units at $14 each and then issues 80 units.

Existing cost = 100 × $10 = $1,000.

Receipt cost = 50 × $14 = $700.

Total units available = 150; total cost = $1,700.

Average cost per unit = $1,700 ÷ 150 = $11.33, rounded to two decimals.

Cost of issue = 80 × $11.33 = approximately $906.40, subject to the ERP’s unrounded calculation.

Remaining units = 150 − 80 = 70 units.

Remaining inventory is approximately $793.60 when the rounded issue cost is used. Using unrounded cost, the remaining cost is $1,700 − ($1,700 ÷ 150 × 80) = $793.33. The difference demonstrates why systems should retain precision internally and round only for presentation.

6. Embedded Controls in ERP Systems

ERP controls combine preventive, detective, and corrective mechanisms.

Segregation of duties is central. Ideally, different individuals or teams should request goods, approve the requisition, select the supplier, receive goods, maintain supplier data, approve invoices, and release payments. In small organizations, complete separation may be impractical; compensating controls such as owner review, exception reporting, and independent bank reconciliation become important.

Access should follow least privilege. A user who can create a supplier should not automatically be able to approve invoices and release payments. Role design should be tested against combinations of conflicting permissions, often called toxic combinations.

Reconciliations provide detective assurance. Examples include:

• subledger accounts payable to the general ledger;
• inventory subledger to the general ledger;
• GRNI balances to open receipts and invoices;
• supplier statements to the accounts-payable ledger;
• bank payments to approved payment batches;
• physical inventory to system quantities.

A reconciliation is effective only when differences are investigated and resolved, not merely listed.

7. Applied Case: Northstar Equipment Ltd.

This is an illustrative case. Northstar Equipment Ltd. distributes industrial components. It experienced rising inventory, frequent supplier complaints, and unexplained payment exceptions. An internal review found that buyers sometimes created suppliers, warehouse staff entered receipts without counting cartons, and accounts payable manually changed invoice quantities to clear blocked invoices.

Problem

The company’s ERP contained duplicate supplier records and inconsistent units of measure. A supplier could be recorded as “Apex Industrial,” “Apex Industries,” and “Apex Ind.” Because duplicate detection relied only on supplier name, several duplicate records were not identified. In addition, invoices were often paid before receiving records were completed.

Analysis

The principal risks were unauthorized purchasing, duplicate payment, payment for undelivered goods, inaccurate inventory, and possible supplier-master fraud. The organization had a three-way match in its ERP, but users could override exceptions without a documented reason or secondary approval. Thus, the existence of a system feature did not ensure effective control.

Approach and Solution

Northstar redesigned the workflow as follows:

1. All purchases began with an electronic requisition and budget check.
2. Supplier creation was separated from purchasing and required tax and bank verification.
3. Bank changes required two approvals and independent callback verification.
4. Receiving staff counted goods against delivery documentation and recorded rejected quantities.
5. Invoice tolerances were standardized and overrides required finance-manager approval.
6. Unit-of-measure conversions were reviewed for high-volume items.
7. GRNI and supplier-statement reconciliations were performed monthly.
8. A dashboard reported blocked invoices, aged GRNI, duplicate suppliers, unmatched receipts, and slow-moving inventory.
9. Quarterly access reviews removed conflicting roles.

Outcome

After implementation, payment exceptions became visible rather than being silently overridden. The company reduced duplicate supplier records, improved receipt accuracy, and identified obsolete stock for management action. The most important improvement was not automation alone; it was the combination of clear accountability, reliable master data, evidence-based overrides, and regular monitoring.

Learning Points

The case demonstrates that internal control is a system of people, procedures, data, and technology. A technically sophisticated ERP can reproduce poor processes at greater speed. Effective implementation requires process ownership, quality master data, appropriate access, and management attention to exceptions.

8. Technology, Analytics, and Artificial Intelligence

Modern ERP platforms increasingly use electronic catalogs, supplier portals, optical character recognition, electronic data interchange, robotic process automation, and continuous controls monitoring. These technologies can reduce manual entry and accelerate invoice processing.

Machine-learning tools may classify invoices, identify unusual prices, detect duplicate invoices, predict late deliveries, and flag unusual supplier-bank changes. However, a prediction is not proof of fraud or error. Models may produce false positives, inherit biased historical practices, or fail when supplier behavior changes. Organizations should maintain human review for material decisions, document model logic where possible, protect supplier and employee data, and retain audit evidence for automated actions.

Electronic procurement also creates cybersecurity risks. Attackers may alter supplier bank details, compromise user credentials, intercept payment files, or exploit interfaces between purchasing and banking systems. Strong authentication, encryption, segregation of environments, transaction limits, confirmation controls, and incident-response procedures are therefore relevant to P2P governance.

9. Ethical, Legal, and Regulatory Considerations

Procurement professionals occupy positions of trust. Ethical conduct requires impartial supplier selection, avoidance of conflicts of interest, protection of confidential bids, accurate documentation, and refusal of improper gifts or inducements. Organizations should define thresholds for competition, emergency purchasing, related-party transactions, and hospitality.

Accounting personnel must not accelerate or delay recognition of liabilities to manipulate reported results. Cut-off procedures should reflect when goods or services were received and the organization’s obligations arose. Inventory quantities and valuation assumptions must not be altered to conceal theft, obsolescence, or poor performance.

Privacy and data-protection rules may apply to supplier contacts, bank details, tax identifiers, and employee information. Records should be retained according to legal, tax, contractual, and audit requirements. Controls should be proportionate to risk: a low-value office-supply purchase does not require the same review as a strategic, regulated, or high-value contract.

10. Challenges and Limitations

Several challenges commonly affect P2P systems:

• Maverick spending: employees bypass approved suppliers or POs.
• Poor master data: duplicate items, suppliers, units, or prices create errors.
• Complex services: services may not have a physical receipt, making acceptance evidence important.
• Global operations: multiple currencies, tax regimes, languages, and delivery terms complicate processing.
• Inventory uncertainty: theft, damage, obsolescence, and counting errors reduce record reliability.
• Excessive tolerances: broad matching tolerances may permit material overbilling.
• Automation complacency: users may assume that an ERP control is effective without testing it.
• Change management: new workflows fail when users do not understand responsibilities or performance measures.

Control design should balance risk reduction with operational efficiency. Excessive approval layers can encourage employees to bypass the system, while inadequate controls expose the organization to loss. The appropriate design is risk-based and supported by measurable exceptions.

11. Best-Practice Framework

A mature P2P environment generally includes:

1. Clear procurement policies and approval thresholds.
2. Standard item and supplier master-data governance.
3. Approved catalogs and contracted suppliers where appropriate.
4. Segregated roles and regular access reviews.
5. Automated budget checks and commitment visibility.
6. Receiving procedures suited to goods and services.
7. Configured two-, three-, or four-way matching based on risk.
8. Controlled exception and override processes.
9. Regular inventory counts and valuation reviews.
10. Reconciliations, analytics, and continuous monitoring.
11. Supplier performance, risk, and ethical-compliance reviews.
12. Documented business continuity and cybersecurity controls.

Management should evaluate both efficiency and control effectiveness. Useful performance measures include purchase-order compliance, invoice-cycle time, first-pass match rate, blocked-invoice aging, early-payment discount capture, duplicate-payment incidents, inventory accuracy, stockout frequency, and obsolete-inventory value. No single measure is sufficient; fast payment processing is not beneficial if it increases errors or fraud.

Chapter Summary

Procurement, inventory, and payables systems connect operational demand with financial accountability. The procure-to-pay cycle begins with an authorized requisition and proceeds through supplier selection, purchase ordering, receiving, invoice validation, and payment. Three-way matching compares the purchase order, receiving evidence, and supplier invoice to prevent payment for unauthorized, excessive, or undelivered goods. Supplier master data requires strong governance because inaccurate bank or identity information can directly cause financial loss.

Inventory systems support availability, replenishment, and valuation. Perpetual records improve visibility, but physical counts and reconciliations remain necessary. Inventory valuation methods such as specific identification, FIFO, and weighted average affect cost of sales and reported assets. ERP controls—including workflow approval, segregation of duties, access restrictions, duplicate detection, matching, audit trails, and exception reporting—must be designed and monitored rather than assumed to be effective.

The Northstar case illustrates that technology cannot compensate for weak accountability, poor data, or uncontrolled overrides. Ethical procurement, reliable cut-off, cybersecurity, privacy, and professional skepticism are integral to a sound P2P environment.

Key Terms

Procure-to-pay: The integrated process from identifying a purchase need through supplier payment.

Purchase requisition: An internal request to acquire goods or services.

Purchase order: An authorized document communicating a purchase commitment to a supplier.

Receiving report: Evidence of goods or services received and accepted.

Accounts payable: Amounts owed to suppliers for valid purchases.

Three-way matching: Comparison of the PO, receiving record, and supplier invoice.

Four-way matching: Matching that additionally includes inspection or quality acceptance.

GRNI: Goods-received-not-invoiced balance for received goods awaiting supplier invoices.

Supplier master data: Core information used to identify and pay suppliers.

Segregation of duties: Division of incompatible responsibilities among different people or roles.

Perpetual inventory: An inventory system updated continuously as transactions occur.

Periodic inventory: An inventory system in which inventory and cost of sales are determined at period end.

FIFO: A cost-flow assumption in which earliest acquired costs are assigned first to issues or sales.

Weighted average: A method assigning inventory issues an average cost per unit.

Net realizable value: Estimated selling price less costs of completion and sale.

Reorder point: Inventory level at which replenishment should be initiated.

Safety stock: Additional inventory held to protect against uncertainty.

Maverick spending: Purchasing outside approved policies, contracts, or suppliers.

Master-data governance: Policies and controls for creating, changing, and monitoring core records.

Continuous controls monitoring: Ongoing analytical review of transactions and control exceptions.

Review Questions

Short Answer Questions

1. What are the three documents used in three-way matching?
2. Why is supplier bank-account information a high-risk master-data field?
3. Distinguish a purchase requisition from a purchase order.
4. What is the purpose of a GRNI balance?
5. State two examples of segregation of duties in the P2P cycle.

Long Answer Questions

1. Explain the procure-to-pay cycle and identify the principal risks at each stage.
2. Compare perpetual and periodic inventory systems, including their control implications.
3. Explain how FIFO, specific identification, and weighted average affect inventory reporting.
4. Discuss why an ERP three-way match may still fail to prevent improper payment.
5. Evaluate the role of supplier-master governance in preventing procurement fraud.

Analytical / Application Questions

1. An invoice is for 120 units, but the receiving report shows only 100 accepted units. The supplier claims that the remaining 20 units were delivered separately. What evidence and system actions should be required before payment?
2. A company has average daily demand of 40 units, a lead time of 6 days, and safety stock of 80 units. Calculate the reorder point using ROP = dL + SS and explain the assumptions behind the result.
3. Design a control plan for a small organization that cannot fully segregate supplier creation, invoice approval, and payment release. Identify compensating controls and explain how their effectiveness should be monitored.

Multiple Choice Questions with Answers

Question 1

Which document normally communicates an authorized purchase commitment to a supplier?

A. Purchase requisition

B. Purchase order

C. Receiving report

D. Supplier statement

Correct Answer: B. Purchase order

Question 2

Three-way matching compares the supplier invoice with which two records?

A. Budget and bank statement

B. Purchase order and receiving report

C. Supplier contract and payment file

D. Inventory count and general ledger

Correct Answer: B. Purchase order and receiving report

Question 3

What is the primary purpose of a receiving report?

A. To authorize a supplier bank change

B. To record goods or services received and accepted

C. To calculate the payment discount

D. To create a supplier tax identifier

Correct Answer: B. To record goods or services received and accepted

Question 4

An organization has 100 units costing $10 each and buys 50 units at $14 each. What is the weighted-average cost per unit before any issue?

A. $10.00

B. $11.33

C. $12.00

D. $14.00

Correct Answer: B. $11.33

Question 5

Which control most directly reduces the risk of fraudulent supplier bank-account changes?

A. Allowing buyers to edit bank data freely

B. Removing receiving reports from the ERP

C. Dual approval and independent callback verification

D. Increasing invoice payment tolerances

Correct Answer: C. Dual approval and independent callback verification

Question 6

If average demand is 40 units per day, lead time is 6 days, and safety stock is 80 units, what is the reorder point?

A. 120 units

B. 240 units

C. 280 units

D. 320 units

Correct Answer: C. 280 units

Question 7

Which role combination represents a segregation-of-duties conflict?

A. Receiving goods and counting inventory independently

B. Creating suppliers and releasing payments

C. Reviewing supplier performance and preparing reports

D. Approving a requisition and monitoring its budget

Correct Answer: B. Creating suppliers and releasing payments

Question 8

What does a GRNI balance generally represent?

A. Goods received but not yet invoiced

B. Goods invoiced but never ordered

C. Cash paid before a requisition is approved

D. Inventory sold but not shipped

Correct Answer: A. Goods received but not yet invoiced

Question 9

Which inventory valuation relationship is generally correct for a periodic system?

A. Cost of sales = closing inventory − purchases

B. Cost of sales = opening inventory + net purchases − closing inventory

C. Cost of sales = cash payments − opening inventory

D. Cost of sales = purchases + closing inventory − opening inventory

Correct Answer: B. Cost of sales = opening inventory + net purchases − closing inventory

Question 10

Why should ERP payment overrides require documented approval?

A. To eliminate the need for purchase orders

B. To make all invoices payable immediately

C. To preserve accountability and evidence for exceptions

D. To prevent physical inventory counts

Correct Answer: C. To preserve accountability and evidence for exceptions