What Is a Receiving Report? How It Works in the Three-Way Match
- What is a receiving report and what is it for?
- What goes on a receiving report?
- How does the receiving report fit into three-way matching?
- Do services need a receiving report?
- Why do receiving reports matter for fraud and audit?
- How do you automate receiving and matching?
- Match every invoice to what arrived with Corpay
A receiving report is the buyer's record of goods or services actually received against a purchase order, including the quantity, condition, and date of receipt. AP matches it against the purchase order and the supplier's invoice before paying, which makes it the third leg of the three-way match.
It's also the one document in that match AP usually doesn't own. Purchasing writes the PO, the supplier sends the invoice, and somebody on a loading dock, in a warehouse, or at a job site is supposed to record what showed up. When that last step slips, the invoice can't match, the payment sits on hold, and the supplier calls AP to ask why.
In my experience, a large share of the exceptions people blame on suppliers are really receiving problems. The goods arrived, someone signed the driver's packing slip, and nobody entered the receipt.
Key Takeaways
A receiving report records what actually arrived against a purchase order, in what quantity and condition, and on what date.
It comes from the buyer, while a packing slip comes from the supplier, and the two aren't interchangeable.
In three-way matching, the receiving report proves delivery, the PO proves what was ordered, and the invoice shows what the supplier is billing.
Services need an acceptance step in place of a dock receipt, such as an approved timesheet or a milestone sign-off.
Receiving controls block payment for goods that never arrived, which is one of the most common billing-fraud patterns.
What is a receiving report and what is it for?
A receiving report is a dated record, created by whoever takes delivery, that lists what arrived against each purchase order line and in what condition. In accounting terms it's evidence of delivery, and it's the document that lets AP release payment on a PO invoice.
In a distribution center the receiving dock creates it, at a construction site the superintendent might, and in an office it's often the requester. Most ERPs record it as a goods receipt transaction against the PO, and the paper form survives mainly where receiving happens away from a computer.
What is the purpose of a receiving report?
A receiving report has three jobs. It proves delivery before anyone pays, it catches shortages and damage while the supplier can still fix them, and it supplies the quantity-received figure that the three-way match needs.
A carton count noted at the dock, with "two cases crushed" written on the report, is a claim the supplier will honor. The same complaint raised six weeks later, when AP finally notices the invoice doesn't match, is an argument. Receiving is the cheapest point in the whole procure-to-pay process to catch a problem.
Is a receiving report the same as a packing slip or a goods received note?
A receiving report isn't the same as a packing slip. The packing slip comes from the supplier and lists what was shipped, while the receiving report comes from the buyer and records what actually arrived and its condition. Those two lists differ more often than anyone would like.
A goods received note is the same document under another name. "Goods received note," or GRN, is the common term in UK usage and in many ERPs, and "goods receipt" usually refers to the ERP transaction that posts it, such as a goods receipt posting in SAP. Whatever the label, the test is who created it. If the supplier wrote it, it's a shipping document rather than proof of receipt. Corpay reaches that record through 100+ ERP integrations, including NetSuite, Sage Intacct, Business Central, and Acumatica.
What goes on a receiving report?
A receiving report holds enough detail to tie a delivery to a specific PO line and to show who verified it. Complete reports include:
The PO number and line number the delivery is received against
The supplier's name
The date received
Quantity ordered and quantity received, line by line
Condition and any inspection result
A partial-shipment flag when the quantity received is short
Notes on damage, substitutions, or unit-of-measure differences
The storage location where the goods went
The receiver's name and signature, or their system user ID
Partial shipments deserve their own field because they cause the most confusion downstream. A delivery of 80 units against a 100-unit line should be received as 80, with the remaining 20 left open on the PO. Received as 100 by someone in a hurry, it lets a full invoice match and pays for goods that are still on a truck somewhere.
Who should prepare and sign a receiving report?
Someone independent of both purchasing and AP should prepare and sign it. The person who orders goods shouldn't also confirm they arrived, and the person who pays for them shouldn't either, because either combination lets one employee create and approve a payment alone.
That's the standard segregation of duties in accounts payable argument applied to the dock. Smaller companies can't always staff it perfectly, and when the requester has to receive their own order, a supervisor's review of receipts above a dollar threshold is a reasonable substitute.
How does the receiving report fit into three-way matching?
The receiving report supplies the quantity-received leg of the three-way match. AP compares the invoice to the PO for price and quantity ordered, and to the receiving report for quantity delivered, and pays only when all three agree within tolerance.
Document | Who creates it | What it proves |
Purchase order | The buyer's purchasing team | What was ordered, at what price, and on what terms |
Receiving report | Whoever took delivery | What actually arrived, in what quantity and condition |
Invoice | The supplier | What the supplier is billing for |
Tolerances keep the match practical. Most companies allow a small price or quantity variance, set as a percentage, a dollar amount, or both, so an invoice that's off by a rounding difference doesn't stop. The mechanics of setting those rules are covered in three-way matching, and the difference between the first two documents is explained in purchase order vs. invoice.
Benchmarks show how much of the work still falls outside a clean match. A median 28.0% of invoice line items are approved by three-way matching, according to APQC benchmarking data from 1,489 organizations. In a separate APQC measure covering 4,438 organizations, a median 75.0% of invoice line items match the first time. APQC doesn't publish a data year for either measure, so read them as a rough guide. Even so, a quarter of lines failing their first match is a lot of rework, and missing receipts are a big part of it.
Protect cash flow with modern AP
Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.
Download the whitepaper
What happens when an invoice arrives before the receipt?
When an invoice beats the receipt into the system, the match fails and the invoice waits. The usual sequence looks like this:
AP captures the invoice and attempts the match.
The match fails on quantity received, because there's no receipt.
The invoice goes on hold, and the due date keeps moving closer.
AP contacts the receiver or the requester to ask whether the goods arrived.
The receiver posts the receipt, sometimes days after delivery.
The match reruns and passes.
The invoice routes for approval, and payment goes out.
Steps four and five are where the time goes, and AP controls neither. The reverse timing creates its own work. When goods arrive first and the invoice lags past month-end, accounting books a goods-received-not-invoiced accrual so the liability shows up in the right period.
What causes receiving-related AP exceptions?
Most receiving-related exceptions come from a short list of causes:
The receipt was never entered, usually because the person who took delivery didn't know they were supposed to.
A partial shipment was received as complete.
The unit of measure differs, such as cases on the PO and each on the invoice.
The supplier substituted an item and nobody updated the PO.
The receipt was posted to the wrong PO line.
The purchase was a service, and there was no acceptance step at all.
None of these is a supplier error, and all of them land on AP's exception queue. Fixing them is mostly a training and workflow problem at the receiving end, which is why the invoice approval workflow should route receipt-missing exceptions to the receiver rather than to an AP clerk. Once the match clears, Corpay's fully managed AP pays the supplier by virtual card, ACH, or check.
Do services need a receiving report?
Services need the equivalent of a receiving report, even though there's no dock. The substitute is a service acceptance, meaning a record that someone with authority confirmed the work was done.
Common forms are an approved timesheet for contract labor, a milestone sign-off for project work, and a service entry sheet in SAP, which records accepted services against a PO line much as a goods receipt does for materials.
Without that step, services invoices fall back to two-way matching against the PO, or to approval alone. A two-way match confirms the price was agreed but says nothing about whether the work happened, and a month-end approver signing a stack of invoices rarely checks each one. For recurring services, a short acceptance step from the person who actually received the service closes most of that gap.
Why do receiving reports matter for fraud and audit?
Receiving reports stop payment for goods or services that were never delivered, which is the core of a billing scheme. Without a recorded receipt, a fake or inflated invoice only has to get past an approver.
Billing schemes are common and slow to surface. They made up 21% of occupational fraud cases, with a median loss of $90,000, according to the ACFE's Occupational Fraud 2026: A Report to the Nations. The same report found billing schemes ran a median 14 months before detection, against a median loss of $104,000 across all cases. The ACFE defines a billing scheme to include invoices for fictitious goods or services, inflated invoices, and invoices for personal purchases, and a receiving control is aimed squarely at the first two.
External fraud is just as present. In the 2026 AFP Payments Fraud and Control Survey, 76% of organizations reported being targets of attempted or actual payments fraud in 2025, and invoice fraud was a source for 26% of them. Business email compromise drew 24,768 complaints and about $3.05 billion in reported losses in 2025, according to the FBI IC3's 2025 Internet Crime Report. Receiving controls don't stop an email that redirects a payment, but they do stop a fraudster from billing for a shipment that never came. The rest of the defense sits in accounts payable fraud controls and an AP audit trail that ties every payment back to a recorded receipt.
Is a DD250 the same as a receiving report?
A DD Form 250 is the Department of Defense's Material Inspection and Receiving Report, so it serves the same purpose for federal contracts. DFARS Appendix F says the Wide Area WorkFlow receiving report is the electronic equivalent of the DD Form 250, and paper DD 250s are now used only by exception.
The underlying federal rule is the same idea as the commercial one. Under FAR 32.905, invoice payments, with stated exceptions, must be supported by a receiving report or other government documentation authorizing payment, including the quantities received and accepted and the accepting official. The stakes are large at that scale. Federal improper payments reached an estimated $186 billion in fiscal 2025, about $153 billion of it overpayments, according to a GAO report released in April 2026. The principle that nobody pays without documented acceptance carries over directly to commercial AP.
How do you automate receiving and matching?
Automate receiving by recording receipts in the ERP at the point of delivery, then let matching software apply tolerances and route exceptions to the right person automatically. The steps that make the biggest difference are practical ones:
Receive at the dock with a mobile device or scanner, so the receipt posts the day goods arrive.
Set quantity and price tolerances that reflect real variances, not zero.
Route receipt-missing exceptions to the requester or receiver automatically, with a reminder schedule.
Stop releasing payment on PO invoices without a recorded receipt, and make exceptions explicit.
Automation moves the chase from AP, which can't see the dock, to the person who can, and the receiving step itself stays. Invoice matching software handles the comparison, but the receipt still has to be entered by someone who saw the goods.
Match every invoice to what arrived with Corpay
The most expensive receiving problem is the invoice that sits on hold because a receipt was never posted, while the supplier waits and AP chases someone in a warehouse. Corpay invoice automation runs fast and accurate 2- and 3-way matching against purchase orders and the receipts recorded in your ERP, routes receipt exceptions to the people who can resolve them, and gives suppliers a vendor portal to check invoice status instead of calling AP.
Corpay works alongside the ERP through 100+ integrations. Those include NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica. Once an invoice clears the match, Corpay's fully managed AP enrolls suppliers and pays them by virtual card, ACH, or check, and AP teams save 40% of the time they spend on processing. For teams that want the controls upstream too, Corpay PO automation connects purchase orders to the same matching flow.
Frequently Asked Questions
What is a receiving report in accounting?
In accounting, a receiving report is the buyer's dated record of goods or services received against a purchase order, showing quantity and condition. AP uses it as proof of delivery and as the third document in the three-way match before paying a supplier's invoice.
What is a receiving inspection?
A receiving inspection is the check performed when goods arrive, covering count, condition, and sometimes quality against specifications. The result is recorded on the receiving report, and any rejected or damaged items are noted so the supplier can be asked to credit or replace them.
Who prepares a receiving report?
Whoever takes delivery prepares it, such as the receiving dock, a warehouse team, a site manager, or the original requester. Ideally that person is independent of purchasing and AP, so no one employee can order, confirm, and pay for the same goods.
Is a goods received note the same as a receiving report?
Yes. A goods received note, or GRN, is the same buyer-created record under a different name, common in UK usage and many ERPs. It differs from a packing slip, which the supplier creates to list what was shipped rather than what arrived.
What happens if the receiving report doesn't match the invoice?
The invoice fails the match and goes on hold. AP or the system then checks whether the receipt is wrong, the shipment was partial, or the supplier overbilled. Payment goes out only after the documents agree within tolerance or an authorized person approves the variance.
Do you need a receiving report for services?
You need an equivalent. Since services have no delivery, companies use an approved timesheet, a milestone sign-off, or a service entry sheet in SAP to confirm the work was done before paying the invoice against the purchase order.
- What is a receiving report and what is it for?
- What goes on a receiving report?
- How does the receiving report fit into three-way matching?
- Do services need a receiving report?
- Why do receiving reports matter for fraud and audit?
- How do you automate receiving and matching?
- Match every invoice to what arrived with Corpay
Switch to Corpay
Discover how making the move to Corpay streamlines payments and strengthens your business.
Talk to an ExpertSmarter payments. Stronger growth. Keep business moving.
Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.