Finance Index
Procurement Receiving in Accounts Payable
Line-level delivery confirmation that connects purchase orders, receipt records, and invoice verification for stronger financial controls and audit readiness.
Procurement receiving is the process of confirming delivery against purchase order line items by recording full or partial receipts, attaching proof of delivery, and creating an audit-ready record of what was actually received. This confirmation bridges the gap between purchase orders and invoice verification, providing accounts payable teams with the operational context needed to evaluate whether invoices reflect actual deliveries. Proper receiving controls reduce payment risk, support accurate matching workflows, and strengthen audit documentation across the procure-to-pay lifecycle.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Primary Purpose | Confirm delivery against PO line items | Prevents payment for undelivered goods |
| Recording Level | Individual purchase order lines | Supports precise quantity matching |
| Documentation | Proof of delivery attachments | Creates audit-ready receipt evidence |
| Visibility | Real-time receipt status updates | Enables informed invoice decisions |
| Integration | Connected to PO and invoice workflows | Streamlines three-way matching |
What Procurement Receiving Covers
Procurement receiving encompasses the operational confirmation that goods or services ordered through purchase orders have been delivered as specified. This process involves designated receivers recording actual quantities received, documenting delivery with supporting evidence, and updating receipt status to reflect partial deliveries, complete receipts, or items that will not be received.
The scope includes line-level quantity tracking, proof of delivery documentation, receiver assignment and notification, partial shipment handling, and the creation of receiving history that supports downstream invoice matching and audit requirements.
Receipt Confirmation and Documentation
Receipt confirmation establishes the factual record of what was delivered against each purchase order line. Receivers record actual quantities received, which may be full, partial, or zero depending on delivery circumstances. This confirmation should happen at the point of delivery or as soon as practical afterward to maintain accuracy.
Documentation requirements typically include proof of delivery such as packing slips, delivery receipts, photos, or other evidence that supports the receiving transaction. This documentation becomes part of the permanent record and should be attached at the line level to maintain clear audit trails for each item received.
Quantity Tracking and Partial Receipts
Quantity tracking maintains running totals of ordered quantities, received quantities, and remaining quantities for each purchase order line. This granular tracking supports scenarios where deliveries occur in multiple shipments or where partial deliveries require separate invoice processing.
Partial receipt handling allows receivers to record incremental deliveries while keeping purchase order lines open for future receipts. The system should clearly distinguish between items that are partially received and awaiting additional delivery versus items that are complete or will not be received.
Receiver Assignment and Notifications
Receiver assignment ensures that the appropriate person confirms delivery based on location, department, or expertise. Assignments should be made before or at the time of purchase order issuance to avoid delays when goods arrive.
Notification workflows should prompt assigned receivers when items are ready for confirmation, provide clear instructions for the receiving process, and escalate when receiving tasks remain incomplete beyond defined timeframes. Mobile accessibility supports receivers who work in warehouses, field locations, or other operational environments.
Receipt Status and Lifecycle Management
Receipt status tracking provides real-time visibility into the delivery state of each purchase order line. Standard statuses include pending receipt, partially received, fully received, and closed as will not be received. Status updates should be immediate and visible to procurement, accounts payable, and other stakeholders.
Lifecycle management includes the ability to edit or cancel receiving transactions when corrections are needed, close lines that will not be received, and maintain complete history of all receiving actions with timestamps, user identification, and supporting comments.
Integration with Invoice Matching
Receipt information should be readily available during invoice review to support two-way and three-way matching processes. Accounts payable teams need visibility into received quantities, partial receipt status, and proof of delivery documentation when evaluating whether invoices align with actual deliveries.
Exception handling becomes more precise when receipt data is integrated with invoice processing, allowing teams to identify discrepancies between billed quantities and received quantities, route invoices appropriately based on receipt status, and maintain consistent policies for handling partial deliveries.
Common Misconceptions
Receiving is not just warehouse documentation
Receiving creates financial controls that directly impact payment decisions and audit compliance, not merely operational records for inventory management.
Receipt confirmation is not automatic upon invoice arrival
Delivery must be actively confirmed by designated receivers before invoice processing can proceed with complete matching context.
Partial receipts are not processing delays
Partial receipt handling is a normal business process that requires systematic tracking and clear policies for invoice processing against incomplete deliveries.
Proof of delivery is not optional documentation
Supporting documentation creates the audit trail necessary for financial controls and may be required for dispute resolution or compliance purposes.
Where This Fits in the P2P Workflow
Procurement receiving sits between purchase order issuance and invoice processing in the procure-to-pay lifecycle. After purchase orders are approved and issued to vendors, receiving provides the operational confirmation that goods or services have been delivered as specified. This confirmation becomes essential input for accounts payable teams evaluating invoices for payment.
Upstream dependencies include purchase order creation, vendor selection, and delivery scheduling. Downstream processes rely on accurate receipt data for invoice matching, payment authorization, and financial reporting. When receiving is properly executed, it enables three-way matching that compares purchase orders, receipts, and invoices to ensure payment accuracy and reduce financial risk.
Frequently Asked Questions
Two-way matching compares purchase orders to invoices without receipt confirmation. Three-way matching adds receipt verification as a third control point, comparing purchase orders, receipts, and invoices to ensure payment accuracy.
Partial deliveries should be recorded with actual quantities received while keeping purchase order lines open for future receipts. Clear policies should define whether invoices can be processed against partial receipts or must wait for complete delivery.
Receivers should be the individuals closest to the delivery point who can verify actual receipt, such as warehouse staff, requesters, or department representatives. Assignment should consider location, expertise, and availability.
Proof of delivery typically includes packing slips, delivery receipts, photos, or other evidence that confirms what was received. Requirements should be defined based on audit needs and organizational policies.
Most systems allow corrections through cancellation and re-recording rather than direct editing to maintain audit integrity. The specific correction process should preserve the complete history of receiving actions.
Receipt status provides context for invoice matching and exception handling. Invoices may be held, routed for review, or processed based on policies that consider whether goods have been fully or partially received.
Lines should be closed with appropriate reason codes when items will not be delivered. This prevents indefinite open purchase order balances and clarifies the basis for invoice processing.
Escalation timeframes should balance operational needs with accounts payable processing requirements, typically ranging from a few days to a week depending on the organization and item type.