52Procure to Pay: Request, Order, Receipt, Bill, Approval, and Payment

Varza promise: clear enough for a first-time learner, exact enough for a professional conversation, and practical enough to support a real decision.

Why this chapter matters

This track follows resources from supplier selection to purchase, receipt, storage, consumption, and long-term use. The central discipline is custody: knowing what was ordered, what arrived, what is owned, what it cost, where it is, and whether it can still create value.

Central question: How can a business control the complete path from internal need to supplier settlement without slowing ordinary operations?

Procure to pay separates need, authorization, commitment, receipt, invoice, approval, and payment so no single document proves every stage. Risk-based thresholds and matching allow low-risk work to flow while material exceptions receive attention.

Varza approaches the subject from life to ledger and from ledger to decision. We begin with what actually happened, identify the rights, obligations, resources, timing, and uncertainty, and only then choose the correct term, calculation, document, or account. This order protects the learner from a common error: learning a label without understanding the economic reality that the label is supposed to describe.

Learning outcomes

• Define and distinguish purchase requisition in plain and professional language.
• Define and distinguish purchase order in plain and professional language.
• Define and distinguish goods receipt in plain and professional language.
• Define and distinguish service entry in plain and professional language.
• Apply the concepts to a numerical case and explain the result rather than only calculate it.
• Identify evidence, workflow, controls, and Varza entities required for reliable use.
• Recognize when jurisdiction-specific or licensed professional advice is required.

The Varza mental model

A financial concept becomes decision-ready when six questions have answers: what, who, when, how much, based on what evidence, and under which assumption or rule. A seventh question—what should happen next—turns knowledge into management.

This chapter uses internationally recognized terminology, but it remains jurisdiction-neutral unless explicitly stated. Accounting standards, tax rules, contract law, consumer protection, labor requirements, and investment regulation can produce different legal outcomes in different countries. The global foundation gives the learner a stable map; local collections must add the binding rules.

Core concepts

1. Purchase requisition

Working definition. Purchase requisition is an internal request describing a need and seeking authority to begin or complete procurement.

A requisition should establish business purpose, quantity, specification, budget, date, owner, and suggested sourcing before commitment. The number alone is not enough; its definition determines whether comparisons are valid.

Simple example. A department requests ten laptops against its approved equipment budget.

Decision test. Which document or observation would allow another person to verify it? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

2. Purchase order

Working definition. Purchase order is an authorized commercial document issued to a supplier specifying what may be supplied and under which terms.

The purchase order is a commitment control and reference. It is not evidence that goods arrived or that an invoice is correct. This is where operational activity and financial reporting meet.

Simple example. The PO identifies item, quantity, price, delivery site, tax, terms, and project code.

Decision test. How would a different assumption change the result? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

3. Goods receipt

Working definition. Goods receipt is a record confirming the quantity, condition, location, and date of goods accepted into custody.

Receipt should be independent from invoice approval where practical and should record exceptions immediately. In Varza language, the concept becomes useful when it changes a decision.

Simple example. Warehouse staff receive 970 of 1,000 ordered units and record thirty as short.

Decision test. Who can influence the result, and who only reports it? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

4. Service entry

Working definition. Service entry is evidence that a specified service, milestone, or quantity of work was performed and accepted.

Services cannot be counted like boxes, so acceptance criteria, time, deliverables, and responsible verification become important. The professional term matters because it prevents two different realities from being recorded as though they were the same.

Simple example. A project manager approves forty verified consulting hours against a statement of work.

Decision test. Does the item affect cash now, later, or not at all? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

5. Supplier invoice

Working definition. Supplier invoice is a supplier's formal claim for amounts due for goods, services, tax, or other consideration.

The invoice should be validated against supplier identity, authorization, receipt, terms, tax, duplicate risk, and calculation before posting. A non-specialist can understand this by separating the object, the timing, and the consequence.

Simple example. An invoice quotes the purchase order and matches accepted quantities.

Decision test. What is being measured, and what has been left outside the boundary? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

6. Three-way match

Working definition. Three-way match is a control comparing purchase order, goods or service receipt, and supplier invoice before approval or payment.

Matching should allow governed tolerances and exceptions. It reduces unauthorized, duplicate, over-quantity, and price-error payments but does not prove every contract condition. The concept should be measured at the smallest level that still supports a real action.

Simple example. The system blocks an invoice for 1,050 units when only 1,000 were ordered and 970 received.

Decision test. When did the underlying right, obligation, benefit, or sacrifice arise? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

7. Accounts payable

Working definition. Accounts payable is amounts owed to suppliers for goods and services received in the ordinary course of business.

Payables require supplier-level detail, due dates, disputes, approvals, credit terms, foreign currency, tax, and reconciliation. The number alone is not enough; its definition determines whether comparisons are valid.

Simple example. A posted supplier invoice remains open until payment, credit, offset, or other settlement.

Decision test. Which document or observation would allow another person to verify it? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

8. Payment plan

Working definition. Payment plan is a scheduled allocation of available cash to obligations according to due date, priority, discount, risk, and relationship.

A payment plan should combine forecast liquidity, authorization, bank controls, sanctions or compliance checks where relevant, and confirmation of beneficiary details. This is where operational activity and financial reporting meet.

Simple example. Payroll, tax, and critical production suppliers receive priority under an approved plan.

Decision test. How would a different assumption change the result? A reliable answer should state the unit, date or period, scope, evidence, and uncertainty. When one of these is missing, the concept may still be useful for discussion, but it is not yet decision-ready information.

How the concepts connect

The concepts in this chapter are a system, not a vocabulary list. Purchase requisition, Purchase order, Goods receipt, Service entry, Supplier invoice, Three-way match, Accounts payable, and Payment plan describe different parts of the same decision. Confusing them usually creates one of three failures: the wrong amount is measured, the right amount is assigned to the wrong period or person, or a correct report is used for a decision it was never designed to support.

A useful analysis therefore preserves both classification and relationship. Classification tells us what an item is. Relationship tells us what caused it, what it affects, and what could change it. Varza should store both. A report that shows only totals may be suitable for orientation; a controlled decision requires traceability to the underlying relationships.

Formulas and quantitative relationships

Open commitment

Open commitment = Authorized purchase-order value − Received or released value, adjusted for cancellations and changes

The amount shows remaining authorized exposure.

Boundary: Currency, tax, quantity, price, and contract structure determine exact measurement.

Worked case — A three-way match catches an overbilling

A purchase order authorizes 1,000 units at CU 20. The warehouse accepts 920 units; eighty are backordered. The supplier invoices 1,000.

Item	Amount or observation
Ordered	1,000 × CU 20 = CU 20,000
Received	920 × CU 20 = CU 18,400
Invoiced	1,000 × CU 20 = CU 20,000
Quantity exception	80 units / CU 1,600
Open commitment	80 units subject to later receipt or cancellation

Calculation and reasoning

1. The invoice price matches, but invoice quantity exceeds accepted receipt by eighty units.
2. Approve and post only the supported amount or hold the invoice according to policy and local invoice rules.
3. Contact the supplier and link later delivery or credit to the same order.
4. Do not create a false receipt for the missing units; preserve the backorder and open commitment.

What the result means

Three-way matching does not accuse the supplier. It prevents intention, custody, and billing from being collapsed into one number and provides a controlled path to resolution.

The case is deliberately compact. In practice, Varza would preserve the supporting documents, currency, dates, counterparty, project or cost center, approvals, and links to the resulting records. The lesson is not merely to reach a number; it is to make the path to that number reviewable.

Practical workflow

1. Define the decision, responsible person, economic unit, period, and acceptable uncertainty. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
2. Capture need, specification, budget, requester, date, and sourcing route. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
3. Issue an authorized purchase order or controlled exception before commitment. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
4. Record independent goods or service acceptance. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
5. Match and approve the invoice, schedule payment, authorize bank release, and reconcile settlement. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
6. Reconcile the result to source evidence and investigate exceptions rather than forcing agreement. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
7. Approve the decision or record at the authority level required by value, risk, and legal consequence. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.
8. Monitor the outcome, compare it with the original assumption, and retain the learning for the next cycle. Define the owner, required evidence, status, date, and exception route. Do not allow the next step to erase the record of the previous one.

How this concept should appear in Varza

The minimum Varza data model for this chapter includes requisition, budget_check, purchase_order, goods_receipt, service_entry, supplier_invoice, match_exception, payment_batch, bank_confirmation. These names are not merely interface labels. Each entity should have a stable identifier, status history, responsible owner, applicable currency or unit, effective dates, evidence links, and access controls.

A useful Varza screen should answer four questions without forcing the user to reconstruct the story manually:

1. What happened or is expected to happen? Show the operational event, obligation, or decision in plain language.
2. What changed financially? Show cash, asset, liability, equity, income, expense, commitment, or risk effects.
3. Why should the user trust it? Show source documents, calculations, approvals, and revision history.
4. What requires attention now? Show exceptions, due dates, thresholds, and the next responsible action.

The Varza design principles most relevant here are:

• Use automation to strengthen evidence and consistency, never to remove accountability.
• Turn information into a decision, a control, or a question; otherwise it is only decoration.
• Begin with the real event, not the accounting label.

Varza AI may explain, classify, compare, simulate, and prepare a proposed action. It should not silently change a legal record, post a material transaction, close a period, release a payment, or make an investment decision on the user’s behalf. Material actions require visible evidence, permissions, validation rules, and an accountable human approval path.

Controls and professional boundaries

1. Three-way or appropriate two-way match with governed tolerances. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
2. Payment batch dual authorization. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
3. No invoice approver may manufacture missing receipt evidence. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
4. Duplicate invoice detection across supplier, number, date, amount, and bank. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
5. Stable definitions, versioned assumptions, and consistent units across plans, records, and reports. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
6. Traceability from every material total to evidence, calculation, owner, and change history. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.
7. Access and approval rights aligned with responsibility and the possible consequence of error or misuse. The control should be proportionate to value and risk, documented clearly, and tested often enough to detect failure before the consequence becomes irreversible.

A control is effective only when it operates in practice. A policy that everyone can bypass is a statement of hope, not a control. Likewise, a control that blocks ordinary work without distinguishing low-risk and high-risk cases encourages hidden workarounds.

Common mistakes and better responses

Mistake 1: Creating a purchase order after the invoice only to satisfy the system

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 2: Approving payment because budget is available without proving receipt

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 3: Ignoring partial receipt and invoicing

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 4: Changing invoice data to force a match instead of resolving the exception

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 5: Using a technically correct number outside the period, entity, currency, or decision boundary for which it was calculated

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Mistake 6: Accepting an automated result without reviewing the evidence, assumptions, exceptions, and required professional judgment

Better response. Reconstruct the underlying event, state the definition being used, obtain the missing evidence, and recalculate before making a decision. Correct the process as well as the current number so the same error does not become routine.

Decision checklist

• Can I explain purchase requisition in plain language and in professional terms?
• Can I explain purchase order in plain language and in professional terms?
• Can I explain goods receipt in plain language and in professional terms?
• Can I explain service entry in plain language and in professional terms?
• Have I stated the entity, currency or unit, date or period, and decision boundary?
• Can another person reproduce the number from retained evidence?
• Have I separated actuals, estimates, commitments, and scenarios?
• Have I tested timing, liquidity, risk, and at least one adverse outcome?
• Is the required approval proportional to the possible loss or legal consequence?
• Does the final output lead to a specific action, owner, and review date?

Practice lab

1. Explain it. Describe Purchase requisition to a person who has never studied finance. Then add the professional definition and identify one boundary your simple explanation omitted.
2. Classify it. Create five examples from your household or a small business and classify each using Purchase order. State any assumptions.
3. Calculate it. Rebuild the worked case with amounts 20% higher. Identify which conclusions change and which remain structurally true.
4. Challenge it. Describe a situation in which Goods receipt could be measured correctly but still lead to a poor decision because timing, risk, or incentives were ignored.
5. Design it. Sketch a Varza screen or report for this chapter. Include fields, evidence links, status, owner, exceptions, and one AI-assisted action.

Answer guidance

A strong answer uses consistent definitions, reveals assumptions, distinguishes fact from estimate, and connects the result to an action. More than one conclusion may be reasonable when the learner clearly states the decision objective and uncertainty. The worked-case recalculation should preserve the method even when the numbers change.

Varza AI knowledge capsule

This capsule is intentionally explicit so that a retrieval system can distinguish canonical teaching points from examples and commentary.

{
  "chapter_id": "VARZA-F100-052",
  "canonical_topics": [
    "Purchase requisition",
    "Purchase order",
    "Goods receipt",
    "Service entry",
    "Supplier invoice",
    "Three-way match",
    "Accounts payable",
    "Payment plan"
  ],
  "facts": [
    "Purchase requisition: an internal request describing a need and seeking authority to begin or complete procurement.",
    "Purchase order: an authorized commercial document issued to a supplier specifying what may be supplied and under which terms.",
    "Goods receipt: a record confirming the quantity, condition, location, and date of goods accepted into custody.",
    "Service entry: evidence that a specified service, milestone, or quantity of work was performed and accepted.",
    "Supplier invoice: a supplier's formal claim for amounts due for goods, services, tax, or other consideration.",
    "Three-way match: a control comparing purchase order, goods or service receipt, and supplier invoice before approval or payment.",
    "Accounts payable: amounts owed to suppliers for goods and services received in the ordinary course of business.",
    "Payment plan: a scheduled allocation of available cash to obligations according to due date, priority, discount, risk, and relationship."
  ],
  "formula_names": [
    "Open commitment"
  ],
  "jurisdiction_scope": "global-foundation",
  "required_answer_qualifiers": [
    "entity",
    "date_or_period",
    "currency_or_unit",
    "source_or_assumption",
    "jurisdiction_when_relevant"
  ],
  "human_approval_required_for": [
    "posting_material_transactions",
    "closing_periods",
    "changing_master_data",
    "releasing_payments",
    "submitting_filings",
    "individual_investment_execution"
  ],
  "source_ids": [
    "S009",
    "S203",
    "S204",
    "S205"
  ],
  "edition": "2026.1",
  "review_date": "2026-08-31"
}

Suggested questions for Varza AI

• Explain this chapter using an example from a household, a shop, and a service business.
• Ask me five diagnostic questions before applying this concept to my situation.
• Show the difference between cash effect, accounting effect, and decision effect.
• Recalculate the worked case using my currency and assumptions, but preserve the original definitions.
• Identify which parts require local accounting, tax, legal, labor, or investment rules.

Sources and standards horizon

This chapter is original Varza educational content. It paraphrases and synthesizes concepts; it does not reproduce a standard or third-party article. The following sources were used to establish terminology, scope, and current professional context:

• S009 — U.S. Small Business Administration, Manage your business. accessed 2026-08-31. Ongoing compliance and financial management. Source: https://www.sba.gov/counseling/manage-your-business/
• S203 — Committee of Sponsoring Organizations of the Treadway Commission, Internal Control—Integrated Framework. 2013 framework; accessed 2026-08-31. Control environment, risk assessment, control activities, information and monitoring. Source: https://www.coso.org/internal-control
• S204 — International Auditing and Assurance Standards Board, ISA 315 (Revised 2019). 2019; accessed 2026-08-31. Understanding systems and identifying risks of material misstatement. Source: https://www.iaasb.org/publications/isa-315-revised-2019-identifying-and-assessing-risks-material-misstatement
• S205 — International Auditing and Assurance Standards Board, ISA 240 (Revised). 2025-07-08. Fraud lens, risk response and transparency in audits. Source: https://www.iaasb.org/publications/isa-240-revised-auditor-s-responsibilities-relating-fraud-audit-financial-statements

Standards horizon. Reviewed through 2026-08-31. IFRS 18 and the third edition of the IFRS for SMEs Accounting Standard are included as transition knowledge where relevant; both have mandatory effective dates beginning in 2027, with early application permitted under their respective requirements.

Jurisdiction note. Global educational foundation; local law, tax, reporting, consumer-protection, licensing, and professional requirements must be checked separately.

Professional-use note. This learning material does not replace advice from a qualified accountant, lawyer, tax adviser, licensed investment professional, or other regulated specialist who has reviewed the user’s facts and jurisdiction.