Procure-to-Pay Operations and Purchasing Controls

Introduction

Procure-to-pay (P2P) is the integrated business process through which an organization identifies a requirement, obtains authorization, purchases goods or services, receives and verifies them, records the supplier invoice, and makes payment. It connects operational demand with financial stewardship. Although often represented as an administrative cycle, P2P is also a control system: every transaction must be necessary, authorized, accurately recorded, economically justified, and supported by evidence.

Effective P2P management seeks to achieve four outcomes simultaneously:

1. Service and supply continuity—materials and services arrive when required.
2. Commercial value—the organization obtains appropriate quality and total cost.
3. Transaction integrity—records, approvals, receipts, invoices, and payments agree.
4. Governance and compliance—fraud, conflicts of interest, unauthorized commitments, and regulatory breaches are prevented or detected.

The process is cross-functional. Requesters and user departments define needs; procurement manages sourcing and supplier relationships; receiving personnel verify delivery; quality personnel inspect conformance; accounts payable validates invoices; treasury or finance releases payment; and internal audit evaluates the control environment.

Learning Objectives

After studying this chapter, the learner should be able to:

• explain the stages and information flows in a P2P process;
• distinguish requisitions, purchase orders, contracts, receipts, inspection records, and invoices;
• design approval matrices and segregation-of-duties controls;
• apply two-way, three-way, and four-way matching;
• manage expediting, receiving, inspection, non-conformance, and returns;
• evaluate P2P performance using operational and control metrics;
• identify risks arising from poor master data, emergency buying, supplier fraud, and weak authorization;
• assess how ERP systems, automation, analytics, and artificial intelligence affect P2P governance.

1. The Procure-to-Pay Architecture

A standard P2P cycle contains the following linked stages:

Need identification → requisition → approval → sourcing or contract selection → purchase order → supplier acknowledgement → expediting → receipt → inspection → invoice capture and matching → payment → reconciliation and record retention.

The sequence is not always linear. A catalog purchase may move rapidly from an approved requisition to an electronic order, whereas capital equipment may require a tender, technical evaluation, contract negotiation, factory inspection, installation, and milestone payments. Services may require confirmation of hours, deliverables, or outcomes rather than physical receipt.

1.1 Requisition and purchase order: different purposes

A purchase requisition (PR) is an internal request. It states what the organization believes it needs and provides the business justification, required date, quantity, specifications, accounting information, and suggested supplier where appropriate. A requisition does not normally create a supplier obligation.

A purchase order (PO) is an authorized commercial instruction to a supplier. It normally specifies item or service description, quantity, price, delivery terms, tax treatment, payment terms, shipping address, quality requirements, and contractual conditions. Once accepted under the applicable legal framework, it may create a binding commitment.

Confusing these documents creates risk. A requester may be authorized to ask for an item but not to commit organizational funds. “Buying first and regularizing later” weakens budget control, supplier fairness, and auditability.

1.2 Core transaction data

A reliable P2P process depends on consistent master and transaction data. Important data objects include:

Data standards are operational controls, not merely information-technology preferences. For example, a unit-of-measure error can cause an order for 100 cartons to be interpreted as 100 individual units, while an outdated supplier bank account can divert a legitimate payment.

2. Requisitioning and Demand Governance

Requisitioning should begin with a validated business requirement rather than a supplier quotation. The requester should define the functional need, technical performance, quantity, required date, delivery location, and consequences of delay. Specifications should be sufficiently precise for competitive evaluation but should not unnecessarily favor a particular supplier or brand.

A sound requisition answers five questions:

• What is needed?
• Why is it needed?
• When and where is it needed?
• How much is needed, and in what unit of measure?
• Which budget, project, or cost centre will bear the cost?

For recurring materials, the requisition should be informed by inventory policies, forecasts, open orders, supplier lead times, and demand variability. For example, a buyer should not create a new order without checking whether available stock, scheduled receipts, or another location can satisfy the need.

2.1 Approval logic

Approval is a decision about business necessity, financial commitment, risk, and compliance. It should not be reduced to a routine electronic click. Approval rules may consider:

• monetary value;
• category risk, such as chemicals, information technology, or regulated goods;
• budget availability;
• supplier type and sourcing method;
• contract status;
• urgency and exception conditions;
• capital versus operating expenditure;
• related-party or conflict-of-interest indicators.

A practical approval matrix may assign higher authority to larger or more sensitive commitments. Thresholds should be stated in policy, communicated to employees, and reviewed periodically. Splitting one requirement into several smaller requisitions to remain below an approval threshold is bid splitting or transaction splitting and is a control violation.

2.2 Sourcing routes

After approval, procurement selects the appropriate route:

• catalog or blanket order for repetitive, standardized purchases;
• contracted supplier call-off where terms are already negotiated;
• competitive quotation for moderate-value purchases;
• formal tender or request for proposal for complex or high-value requirements;
• sole-source or emergency procurement where justified and documented.

The appropriate route depends on value, complexity, market conditions, urgency, and risk. Competitive sourcing is not automatically superior if transaction cost is disproportionate or if a valid long-term contract already exists. Conversely, a low-value purchase can still present high ethical or technical risk.

3. Purchase Orders and Commercial Control

The PO translates an approved requirement into a controlled commitment. A complete PO should contain, as applicable:

• unique PO number and issue date;
• legal identity and address of the supplier;
• line-level descriptions and specifications;
• quantity and unit of measure;
• unit price, discounts, freight, taxes, and total value;
• requested delivery date and destination;
• delivery, title, risk, and insurance terms;
• inspection, warranty, service-level, and acceptance clauses;
• payment terms and invoice instructions;
• applicable contract, ethical, sustainability, confidentiality, and audit clauses.

The organization should prohibit unauthorized commitments. If an employee instructs a supplier to begin work without an approved PO, the supplier may claim payment even though the organization has lost negotiating leverage. A “no PO, no pay” policy can discourage such behavior, but it must include controlled exceptions for emergencies, utilities, statutory charges, and other justified cases.

3.1 Change control

Changes to price, quantity, specification, delivery date, or scope should be made through a documented PO amendment or contract change order. The amendment should identify the original value, revised value, reason, and approving authority. Suppliers should not be allowed to rely on informal emails from unauthorized employees as evidence of a commitment.

3.2 Open orders and closure

Open POs require periodic review. An order should be closed when the supply is complete, accepted, invoiced, paid, and no further claim is expected. Closing obsolete orders improves commitment reporting and reduces the risk of late invoices being processed against stale budgets.

4. Expediting and Delivery Management

Expediting is the systematic monitoring and intervention needed to secure delivery at the required time and condition. It is especially important for long-lead materials, production-critical components, imported goods, project equipment, and items with high consequences of delay.

An expediting plan should identify:

• required delivery milestone;
• supplier manufacturing or service milestones;
• documentation requirements;
• inspection and testing points;
• transport and customs dependencies;
• responsible buyer, supplier contact, and internal user;
• escalation triggers and recovery actions.

Expediting is not merely asking, “Where is my order?” A professional expeditor compares planned and actual progress, validates evidence, and assesses the effect of delay on operations. Useful evidence includes production schedules, inspection reports, photographs where appropriate, shipping documents, and confirmed dispatch information.

4.1 Delivery performance

A common metric is on-time delivery (OTD). One simple definition is:

The organization must define whether the criterion is the requested date, confirmed date, or contractual date, and whether partial deliveries count as on time. The metric is meaningful only when these definitions are consistent.

A supplier delivering early is not automatically successful: early delivery may create storage cost, cash-flow impact, or shelf-life loss. Conversely, a late delivery may be acceptable if the date was formally changed and approved before the original due date. Metrics should therefore distinguish supplier performance from internal schedule changes.

5. Receiving, Inspection, and Acceptance

Receiving confirms that goods or services have arrived; it does not necessarily confirm that they conform to requirements. A receiving record should normally capture PO number, supplier, delivery note, date, quantity, packaging condition, lot or serial numbers, and the identity of the receiver.

5.1 Inspection levels

Inspection may be:

• quantity inspection—counting units, weighing materials, or checking dimensions;
• identity inspection—confirming item, model, grade, lot, or serial number;
• condition inspection—checking visible damage, packaging, and preservation;
• quality inspection—testing against specifications, drawings, samples, or standards;
• functional or acceptance testing—confirming performance after installation or service completion;
• document inspection—checking certificates, licenses, test reports, or traceability records.

Inspection depth should be risk-based. Critical safety components require stronger controls than low-value office supplies. Sampling can be efficient, but the sampling plan must be appropriate to the risk, lot size, supplier history, and applicable standard. Acceptance should not be recorded merely because the supplier has delivered paperwork.

5.2 Non-conformance and returns

When goods fail inspection, the organization should segregate or clearly identify them, record the non-conformance, notify the relevant parties, and decide whether to reject, return, repair, replace, rework, accept under approved concession, or dispose of the goods. The decision should consider safety, contract rights, cost, operational urgency, and regulatory requirements.

A return-to-supplier process should link the return authorization to the original PO, receipt, inspection result, and credit or replacement expectation. Without this link, the organization may pay for rejected goods or fail to recover the value of returned items.

For services, acceptance may be based on timesheets, milestone certificates, service reports, performance indicators, or a user acceptance document. “Receipt” of a service should mean that the authorized service owner confirms performance, not merely that an invoice has arrived.

6. Invoice Processing and Matching

Accounts payable should establish that an invoice is genuine, accurate, authorized, and payable. Key checks include supplier identity, invoice uniqueness, tax requirements, arithmetic, PO reference, receipt status, contract terms, and payment due date.

6.1 Two-way, three-way, and four-way matching

Two-way matching compares the invoice with the PO, usually for price, quantity, supplier, and terms. It may be appropriate for certain services or low-risk purchases where receipt evidence is handled separately.

Three-way matching compares:

1. the PO;
2. the receiving or service-acceptance record; and
3. the supplier invoice.

Payment is released when the documents agree within approved tolerances.

Four-way matching adds an inspection or quality-acceptance record. It is useful for regulated, technical, or quality-sensitive purchases.

Matching tolerances must be explicit. For example, a system may permit a small price or quantity variance, but tolerance should not allow payment for an unreceived critical item. Tolerances should be risk-based and should generate an exception trail.

6.2 Invoice amount and variance analysis

For a line item, the expected goods value may be expressed as:

If freight, tax, and other charges apply, the invoice total can be represented as:

These expressions are accounting representations, not substitutes for tax law or contract interpretation. Each term must use compatible currency and tax treatment. A tax amount should not be added twice, and credits for returns should be linked to the relevant transaction.

A useful price variance calculation is:

A positive result indicates an amount above the PO price; a negative result indicates an amount below it. This calculation assumes that both prices refer to the same specification, unit of measure, currency, and delivery basis.

Worked Example: Three-Way Match

An approved PO specifies 500 units at €24 per unit. The receiving record confirms 480 acceptable units. The supplier invoice charges €24 per unit and €180 approved freight. Tax is excluded from this illustration.

The maximum goods amount supported by the receipt is:

The invoice goods amount is also €11,520, and the freight is contractually approved. The payable amount before tax is therefore:

The remaining 20 units are not payable until received and accepted, unless the contract provides another approved arrangement. If the invoice instead charged €25 per unit, the price variance would be:

The €480 exception should be investigated rather than silently paid.

7. Payment, Reconciliation, and Close-Out

Payment should be made only after the invoice has passed applicable controls and the due date has been verified. Early-payment discounts should be evaluated against the organization’s cost of funds, liquidity position, and supplier relationship. Payment files should require appropriate approval, secure transmission, and independent bank-account validation.

Important payment controls include:

• restricting payment creation and payment approval to separate roles;
• validating changes to supplier bank details through an independent channel;
• using positive pay, dual authorization, or equivalent bank controls where appropriate;
• reviewing rejected, returned, and duplicate payments;
• reconciling subledger transactions with the general ledger;
• reconciling supplier statements and open items;
• retaining invoices, approvals, receipts, inspection evidence, and payment records.

A supplier statement reconciliation can reveal invoices not recorded internally, credit notes not applied, duplicate postings, or disputed balances. Period-end cut-off is also important: goods received before period end may create a liability even if the invoice arrives later, subject to the organization’s accounting framework.

8. Segregation of Duties and Authorization Design

Segregation of duties (SoD) reduces the opportunity for one person to initiate, approve, receive, record, and pay for the same transaction. Complete separation is not always possible in small organizations, so compensating controls such as independent review, system alerts, periodic supplier confirmation, and management oversight become necessary.

A basic SoD pattern is:

A requester may provide technical input without controlling supplier selection. A buyer may issue a PO without being able to approve the original need. Accounts payable may process an invoice without being able to create a supplier or change its bank account.

8.1 Authorization limits

An authorization matrix should define the maximum commitment each role may approve, the categories covered, and the conditions requiring escalation. Limits should apply to the total expected commitment, not merely the first invoice. Multi-year contracts, renewals, options, taxes, freight, and related POs should be considered where policy requires.

Emergency authority should be narrow, time-limited, and subject to retrospective review. Repeated emergency purchases often indicate poor planning, inadequate inventory policy, or an attempt to bypass competition.

9. Risk, Compliance, and Ethical Governance

Common P2P risks include:

• fictitious suppliers and collusion;
• conflicts of interest and undisclosed related parties;
• duplicate or altered invoices;
• payment diversion through fraudulent bank-detail changes;
• receiving goods not delivered;
• accepting substandard goods under operational pressure;
• unauthorized purchases and threshold splitting;
• bribery, kickbacks, gifts, and entertainment;
• violation of sanctions, tax, labor, environmental, or import requirements;
• excessive dependence on a single supplier;
• privacy or cybersecurity breaches in supplier data.

Controls should be proportionate to risk. A low-value catalog transaction may use automated matching and sampling, while a high-value project purchase may require tender governance, legal review, technical evaluation, beneficial-ownership checks, and executive approval.

Ethical procurement requires fair treatment of suppliers, transparent evaluation criteria, confidentiality of bids, management of conflicts, and protection against retaliation for reporting misconduct. Compliance is broader than avoiding fraud: it includes accurate tax documentation, records retention, accessibility requirements where relevant, modern-slavery expectations, environmental obligations, and contractual audit rights.

10. Technology, Automation, and Artificial Intelligence

ERP systems integrate requisitions, POs, receipts, invoices, budgets, and payments. E-procurement platforms can enforce catalogs, approval workflows, preferred suppliers, and audit trails. Optical character recognition and electronic invoicing reduce manual entry, while automated matching routes exceptions to responsible users.

Analytics can identify:

• invoices paid without a PO;
• duplicate invoice numbers or suspiciously similar amounts;
• unusual after-hours transactions;
• repeated purchases just below approval thresholds;
• rapid supplier bank-account changes;
• abnormal price or quantity variances;
• excessive use of emergency procurement.

Artificial intelligence may assist with classification, contract extraction, anomaly detection, demand forecasting, and supplier-risk monitoring. However, AI outputs require governance. Training data may contain historical bias; an anomaly is not proof of misconduct; sensitive supplier information may be exposed; and automated recommendations can reproduce poor specifications or historical favoritism. Human accountability, explainability, access control, model validation, and review of false positives remain essential.

Automation should strengthen—not eliminate—control ownership. A system can enforce that a receipt exists, but it may not determine whether the delivered material is technically safe. A workflow can route an invoice, but it cannot independently establish that a service was actually performed unless reliable evidence is captured.

11. Performance Measurement and Continuous Improvement

P2P performance should combine speed, cost, service, compliance, and control effectiveness. Examples include:

Metrics must have clear definitions, owners, data sources, and review frequency. A high first-pass match rate may indicate good process quality, but it could also result from overly broad tolerances. A low purchase-order cycle time may reflect efficiency or inadequate review. Balanced interpretation is therefore necessary.

Continuous improvement techniques include standardizing specifications, expanding catalogs, simplifying low-risk approvals, improving supplier forecasts, eliminating duplicate suppliers, revising tolerance rules, and conducting root-cause analysis of exceptions. The objective is not to eliminate every exception at any cost; it is to reduce avoidable exceptions while preserving appropriate challenge for high-risk transactions.

12. Illustrative Case: Meridian Components Ltd.

Background

Meridian Components Ltd. manufactures industrial pumps. It experienced production interruptions despite carrying substantial inventory. A review found that buyers frequently used email orders, warehouse staff recorded receipts late, and accounts payable paid invoices based on supplier statements. Three employees could request materials, create POs, and confirm receipt. Supplier bank details were maintained by the same team that processed payments.

Problem

The company’s reported on-time supplier performance was 96%, but production records showed frequent shortages. Invoice exceptions were increasing, and an internal audit identified several payments for quantities greater than the quantities accepted by quality control.

Analysis

The reported delivery metric used the supplier’s promised date, while production planning used the required date. Partial deliveries were counted as complete. The organization also lacked a defined distinction between receipt and acceptance. Consequently, warehouse receipts triggered payment even when quality inspection remained incomplete.

The SoD review identified three principal weaknesses:

1. requisitioning, buying, and receiving could be performed by one person;
2. supplier master changes were not independently verified;
3. invoice matching used PO and invoice data but ignored inspection status for critical components.

Approach and solution

Meridian redesigned the process as follows:

• requisitions became mandatory for planned purchases;
• approval thresholds were based on total expected commitment;
• strategic and critical items required procurement and technical approval;
• warehouse receipt and quality acceptance became separate records;
• four-way matching was introduced for safety-critical components;
• supplier bank changes required independent call-back verification;
• emergency purchases required written justification and monthly review;
• delivery metrics were split into requested-date performance, confirmed-date performance, and complete-quantity performance;
• aged open POs and unmatched receipts were reviewed weekly.

The company also created a controlled exception queue rather than allowing users to bypass the system. A cross-functional team examined the largest recurring exceptions and corrected item units of measure, delivery calendars, and supplier specifications.

Outcome

After implementation, the company reported fewer payments for rejected material, clearer visibility of shortages, and improved accountability for late deliveries. The apparent OTD percentage initially fell because the definition became stricter, but the measure became more useful for production planning. The case demonstrates that stronger controls may initially expose hidden problems rather than immediately improve headline metrics.

Learning points

• A receipt is not necessarily an acceptance.
• Metrics are meaningful only when definitions match operational reality.
• Segregation of duties must cover master data as well as transactions.
• Exception management is preferable to uncontrolled workarounds.
• Control redesign should be based on root causes, not merely additional approvals.

Challenges and Limitations

P2P controls can create delay, administrative cost, and user frustration. Excessive approvals may encourage off-system buying. Rigid “no PO, no pay” policies may be inappropriate for genuine emergencies or statutory payments. Automated matching can fail because of poor item descriptions, inconsistent units, partial deliveries, or legitimate contract complexity. Supplier relationships may also be harmed if inspection and rejection processes are applied inconsistently.

The answer is not minimal control but risk-based control design. Organizations should simplify low-risk transactions, strengthen high-risk transactions, define exceptions clearly, and monitor whether controls achieve their intended purpose. Periodic reviews should consider changes in technology, regulation, supply markets, organizational structure, and fraud patterns.

Best-Practice Principles

1. Start with a documented and justified business need.
2. Separate requesting, approving, buying, receiving, inspecting, recording, and paying wherever practicable.
3. Use complete, standardized specifications and units of measure.
4. Establish authorization limits based on total commitment and risk.
5. Use contracts and POs to make commercial terms explicit.
6. Track critical orders against milestones, not only final delivery dates.
7. Distinguish physical receipt from quality acceptance.
8. Apply matching rules and tolerances appropriate to the category.
9. Independently verify supplier master and bank-account changes.
10. Record and analyze exceptions instead of normalizing workarounds.
11. Retain evidence sufficient for operational, financial, legal, and audit purposes.
12. Use automation and AI with human accountability and data governance.

Chapter Summary

Procure-to-pay is an end-to-end operating and control system linking demand, sourcing, purchasing, delivery, acceptance, invoicing, and payment. Requisitions authorize internal demand; purchase orders create controlled supplier commitments. Expediting protects continuity by monitoring milestones, while receiving and inspection establish whether the expected supply arrived and conforms to requirements. Two-way, three-way, and four-way matching provide increasing levels of transaction assurance.

Effective P2P depends on segregation of duties, authorization limits, reliable master data, documented exceptions, and independent payment controls. Returns and non-conformances must be linked to receipts, inspections, credits, and replacements. Metrics such as on-time delivery, first-pass match rate, cycle time, and exception ageing are useful only when definitions and data sources are clear. ERP, automation, analytics, and AI can improve visibility and efficiency, but they do not replace professional judgment, ethical governance, or accountability. The central managerial task is to balance control strength with process usability through risk-based design and continuous improvement.

Key Terms

Procure-to-pay: The end-to-end process from identifying a requirement through supplier payment.

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

Purchase order: An authorized commercial instruction issued to a supplier.

Unauthorized commitment: A supplier commitment made without required approval or authority.

Expediting: Monitoring and intervention to secure required delivery progress.

Receiving: Recording the arrival and apparent quantity or condition of goods or services.

Inspection: Examination or testing to determine conformity with requirements.

Acceptance: Formal confirmation that goods or services meet defined requirements.

Non-conformance: Failure of a product or service to satisfy a specified requirement.

Three-way match: Comparison of PO, receipt or acceptance record, and invoice.

Four-way match: Matching that also includes quality or inspection evidence.

Tolerance: An approved variance range within which a transaction may be accepted.

Segregation of duties: Distribution of incompatible activities among different people or roles.

Authorization matrix: A documented structure of approval powers and monetary or risk thresholds.

Supplier master: Controlled record of supplier identity, tax, contact, and payment information.

Bid splitting: Dividing a requirement to avoid an approval or sourcing threshold.

Exception management: Recording, investigating, approving, and resolving deviations from standard processing.

On-time delivery: Delivery performance measured against a defined contractual or operational date criterion.

Review Questions

Short Answer Questions

1. What is the difference between a purchase requisition and a purchase order?
2. Why should receiving be distinguished from inspection and acceptance?
3. What documents are compared in a three-way match?
4. State two risks associated with combining supplier-master maintenance and payment processing.
5. Why must approval thresholds apply to total expected commitment rather than only individual invoices?

Long Answer Questions

1. Explain the complete procure-to-pay cycle and show how information and accountability move among user departments, procurement, receiving, quality, accounts payable, and finance.
2. Discuss how segregation of duties and authorization matrices reduce fraud and error while potentially creating process complexity.
3. Compare two-way, three-way, and four-way matching, including appropriate use cases and limitations.
4. Develop a risk-based approach to receiving, inspection, rejection, return, and supplier credit processing.
5. Evaluate the benefits and governance risks of ERP automation, analytics, and artificial intelligence in P2P operations.

Analytical / Application Questions

1. A supplier invoices 1,000 units, but the warehouse received 960 and quality accepted 940. Explain what amount should be considered for payment and what additional actions are required.
2. A business reports 98% on-time delivery, yet production suffers frequent shortages because partial deliveries are counted as complete. Redesign the metric and explain how it should be governed.
3. An emergency purchase policy is used repeatedly by one department, with transactions just below the normal approval threshold. Diagnose the likely control and planning problems and propose corrective actions.

Multiple Choice Questions with Answers

Question 1

Which document normally represents an authorized commercial commitment to a supplier?

A. Purchase requisition

B. Purchase order

C. Receiving report

D. Inspection report

Correct Answer: B. Purchase order

Question 2

What is the primary purpose of a three-way match?

A. To compare supplier performance with market prices

B. To compare a requisition, contract, and budget

C. To compare the purchase order, receipt or acceptance record, and invoice

D. To compare warehouse stock with production demand

Correct Answer: C. To compare the purchase order, receipt or acceptance record, and invoice

Question 3

Which activity should generally be segregated from payment release?

A. Supplier payment approval

B. Supplier bank-account creation or modification

C. Cash forecasting

D. Bank reconciliation review

Correct Answer: B. Supplier bank-account creation or modification

Question 4

A purchase order specifies 500 units at €24 each, but only 480 units are accepted. Excluding other charges, what goods amount is supported by the receipt?

A. €11,040

B. €11,520

C. €12,000

D. €12,480

Correct Answer: B. €11,520

Question 5

What does a receiving record primarily establish?

A. That the supplier has earned a profit

B. That the goods or service have arrived or been reported as delivered

C. That all technical requirements have been satisfied

D. That the invoice must be paid immediately

Correct Answer: B. That the goods or service have arrived or been reported as delivered

Question 6

Which practice is an example of bid splitting?

A. Combining compatible requirements for a competitive tender

B. Dividing one requirement into smaller transactions to avoid an approval threshold

C. Using a framework agreement for repeat purchases

D. Separating goods inspection from invoice processing

Correct Answer: B. Dividing one requirement into smaller transactions to avoid an approval threshold

Question 7

For a safety-critical component, which matching approach provides the strongest evidence among the options listed?

A. Invoice-only review

B. Two-way matching

C. Three-way matching without inspection evidence

D. Four-way matching including quality acceptance

Correct Answer: D. Four-way matching including quality acceptance

Question 8

What is the most appropriate response when delivered goods fail inspection?

A. Pay the invoice and investigate later

B. Record acceptance to avoid supplier conflict

C. Segregate or identify the goods, document non-conformance, and determine an authorized disposition

D. Delete the receiving record

Correct Answer: C. Segregate or identify the goods, document non-conformance, and determine an authorized disposition

Question 9

Which statement best describes a useful on-time delivery metric?

A. It requires a clearly defined date criterion and treatment of partial deliveries

B. It always counts early delivery as superior to on-time delivery

C. It should use different definitions for every supplier without disclosure

D. It is meaningful only when based on invoice date

Correct Answer: A. It requires a clearly defined date criterion and treatment of partial deliveries

Question 10

Why should AI-generated P2P anomaly alerts be reviewed by accountable personnel?

A. AI cannot process numerical data

B. An anomaly is evidence of guilt in every case

C. AI outputs may contain false positives, bias, or contextual errors

D. Human review prevents all supplier delays

Correct Answer: C. AI outputs may contain false positives, bias, or contextual errors