The delivery arrives. The receiving team checks the paperwork, posts the purchase receipt and books the stock into the warehouse. At that point, any Business Central receipt discrepancies become part of the inventory record.

Weeks later, somebody discovers one of the most common Business Central receipt discrepancies: the quantity was wrong.

Perhaps fewer items arrived than the receipt showed. The team may have accepted the wrong product, or put damaged stock away as usable inventory. The warehouse may have kept excess stock without anyone updating the invoice. Or the goods arrived correctly, but the receipt was posted late, or against the wrong purchase order.

By then the discrepancy has travelled through the business. Inventory availability is wrong, the supplier invoice does not match, purchasing places another order it did not need, and sales promises stock that is not there.

A small receiving error has become an expensive operational problem.

Why Business Central receipt discrepancies cost more than they look

Receiving is the point where a supplier's delivery becomes part of your inventory records. If the recorded receipt does not reflect what physically arrived, every process that uses that record starts from the wrong answer. That is why Business Central receipt discrepancies spread so quickly.

The consequences include:

Paying for quantities that were not received.
Carrying excess stock that was not required.
Incorrect inventory availability in Business Central.
Warehouse time spent recounting and relocating stock.
Production or customer orders delayed by missing items.
Emergency purchasing and premium freight.
Supplier performance figures based on inaccurate receipts.
Time spent reconciling purchase orders, receipts and invoices.

Take an ordinary case. A business orders 100 units of a production component, but only 95 arrive. Nobody counts, so the team posts the receipt at 100. Two weeks later, the line stops five units short. The fix is a spot purchase at a premium, air freight instead of road, and overtime to recover the schedule — and the business pays the original supplier for 100 units unless someone also catches the invoice. None of it appears under a heading called receiving errors. It lands in purchasing, freight, production and finance separately, which is exactly why the total is easy to underestimate.

How receipt discrepancies continue after posting

Posting a receipt creates the Business Central record of what entered the organisation, and it updates inventory, availability and the quantity waiting to be invoiced at the same time. Correcting it afterwards is possible but not free. While the receipt line is un-invoiced and the goods have not moved on, Undo Receipt reverses the posted quantity; once the line has been invoiced, the correction becomes a purchase return order and credit memo, with the supplier involved. Either way, the wrong quantity has been in the system for as long as it took someone to notice. The team can catch a discrepancy most cheaply before it posts the receipt and puts the goods away.

A reliable receiving process confirms that:

The delivery belongs to the correct purchase order.
The item received matches the item ordered.
The physical quantity matches the quantity being posted.
Separate damaged or rejected goods.
Record lot, serial and expiration information where required.
Retain the supplier's delivery reference.
Document and communicate any shortage, excess or substitution.

The purpose is not to slow the warehouse down. It is to stop an unresolved exception from becoming a larger problem elsewhere.

Short receipts are Business Central receipt discrepancies that need to stay visible

A supplier may deliver only part of the quantity ordered. Business Central supports partial receipts: the user enters the quantity actually received in the Qty. to Receive field, and the remaining quantity stays outstanding on the purchase order.

That outstanding quantity matters. It may be stock needed for a production order, a customer commitment or a planned replenishment. If teams look only at the quantity received, the remaining risk disappears from view.

A short receipt should trigger clear questions:

Is the balance still expected?
Has the supplier provided a revised date?
Does the shortage affect production or customer orders?
Is an alternative supplier or substitute item available?
Should the outstanding quantity remain open?
Who is responsible for following up?

Recording the correct quantity is only the first step; someone still has to manage what is missing.

How you manage it changes the numbers. When a supplier cannot complete an order, purchasing teams handle it in one of three ways in Business Central: leave the line open until the balance arrives, delete the outstanding quantity and source it elsewhere, or reduce the order to what was delivered and raise a new order for the remainder with a new promised date. Each is legitimate, and each leaves a different trace. Fill rate and in-full measures are calculated from open purchase order lines as they stand at the time of the data refresh, so an order trimmed to what actually arrived looks completely fulfilled, while the same order left open looks late. Neither view is wrong, but they are not comparable. Read vendor fill rate alongside your purchase order clean-up routine, and keep that routine consistent.

Over-receipts hide a purchasing decision

Sometimes a supplier sends more than the quantity ordered. These Business Central receipt discrepancies may seem harmless, and keeping the excess may be practical. However, the decision should be deliberate rather than an unnoticed warehouse outcome.

Business Central supports over-receipt codes that define how much extra quantity a team can accept. Administrators assign a tolerance to items or vendors, and the business can require an approval workflow. Microsoft's guidance on correcting purchase documents covers the controls available when a purchasing record has to be corrected afterwards.

Business Central does not settle the financial treatment of an over-receipt. The business still has to agree how the supplier will invoice the additional quantity, or whether the goods go back.

There is a reporting consequence too. When the receiving team accepts an over-receipt, Business Central raises the line quantity to the quantity received and records the difference in the Over-Receipt Quantity field. From then on the order looks exactly filled in any comparison of received against ordered quantity. The excess is visible, but only to someone who looks at that field, which is why over-receipts deserve their own review rather than being left to surface as a variance.

Before accepting an over-receipt, consider:

Is there enough storage capacity?
Will the excess stock be used before it becomes obsolete?
Does it create additional working-capital pressure?
Has the supplier agreed the price?
Does the quantity exceed the approved tolerance?
Should the goods be returned instead?

An extra ten units look harmless at the receiving dock. Repeated across many deliveries, over-receipts quietly increase inventory and eat warehouse space.

Late against which date?

“Late” only means something against a date, and a Business Central purchase line carries more than one. The Requested Receipt Date records when you asked for the delivery. By contrast, the Promised Receipt Date records the date the supplier confirmed. Business Central calculates the Planned Receipt Date for arrival at your location, then adds inbound warehouse handling time and any safety lead time to produce the Expected Receipt Date.

They answer different questions. A delivery that arrives after the requested date but on the promised date is not a supplier failure: the supplier told you when it would arrive and delivered accordingly. Measure against the requested date and you are scoring your own expectations; measure against the promised date and you are scoring the supplier. A supplier scorecard usually belongs on the promised date, while replenishment and capacity planning care about the expected date.

How posting dates affect Business Central receipt discrepancies

The posting date matters just as much. A receipt line is late when its posting date falls after the date you are measuring against. If goods arrive on Monday and the warehouse posts the receipt on Wednesday, the supplier looks two days later than it was and the receipt lands in a different week's figures. Late or early posting also distorts inventory availability, replenishment suggestions, period-end purchase accruals and the apparent time taken to receive and put away stock. Agree with the warehouse when receipts are posted, and treat the posting date as an operational fact rather than an administrative field.

Two more rules are easy to miss. The report assesses open purchase order lines against the date of your most recent data refresh, so a line becomes overdue the day after its committed date passes; measures that include open orders move as time passes, while measures based only on posted receipts stay fixed. And a line with no value in the date you selected has nothing to be late against, so it counts as on time unless blank dates are excluded from the analysis.

In the Receipt Analytics reports, the Receipt Calculation Base Date selection switches every measure between the four dates, and a separate setting assigns the receipt to either its posting period or its due period.

Averages hide the problem

A monthly total can look reasonable while individual receipts contain serious problems.

Receiving 105 units against one order and 95 against another produces the expected total of 200. The aggregate is correct, but one order was over-received and the other is still short.

The level you count at matters as much as the total.

Counted by purchase order, one late line makes the whole order late. At order-line level, a twenty-line order and a two-line order are weighted by the lines they contain, which is usually the fairer basis for a supplier scorecard. A quantity-based calculation gives one late line of 10,000 pieces more weight than ten late lines of one piece each. The report assesses a partially received order as a whole: it is on time only if every line received so far arrived on time and nothing still open is overdue. A supplier being on time with the part they have delivered does not make the order on time.

Useful receipt analysis lets teams move from the summary into the underlying vendor, item, location, purchase order and receipt-line detail, and choose the level the summary is counted at. Look for vendors with repeated partial deliveries, items that regularly arrive over or under the ordered quantity, locations that post late, and sudden changes in fill rate or on-time performance.

The aim is not to find one mistake but to find where the receiving process repeatedly creates risk.

Review Business Central receipt discrepancies after every refresh

A practical review does not examine every receipt. Start with the exceptions most likely to affect the business.

After each reporting refresh:

Review incomplete receipts. Identify important purchase orders with quantities still outstanding.
Check overdue balances. Find expected quantities that have not arrived by the agreed date.
Investigate unusual quantities. Review over-receipts, repeated partial deliveries and unexpected changes.
Prioritise critical items. Focus on shortages affecting production, customer orders or low-stock positions.
Assign follow-up. Give each material exception an owner and a next action.
Review recurring causes. Separate isolated mistakes from supplier or process patterns.

The Receipt Analytics reports in Purchasing Insights support this review process. Receipt Days shows how long each supplier takes and how far from the committed date they land, by vendor, item, location, purchaser or period; its Average Delays method answers how late a supplier is when they are late. On-Time Receipt scores purchase orders, order lines, receipts or quantity against the date you choose and drills from a company-wide percentage to the individual orders that missed. Vendor Fill Rate shows how much of what you ordered arrived without being left on back-order, by order, line or quantity. The Receipt Cube puts any of these side by side — actual receipt days, on-time percentage and fill rate by vendor and month, for example — which is the basis of a supplier scorecard. The Receipt Analytics tutorial sets out each report's definitions and settings.

Separate supplier issues from internal receiving problems

A discrepancy in the report does not mean the supplier caused it.

The supplier may have delivered the correct goods while the warehouse recorded the wrong quantity. A delayed posting can make an on-time delivery look late. The report may be scoring the supplier against your requested date rather than the date they promised. An outdated purchase order may not reflect a change that both parties agreed by email or telephone, and an incorrect unit of measure can make a valid receipt look unusual.

When investigating an exception, compare:

The original purchase order.
Any confirmed amendments.
The supplier's delivery documentation.
The physical quantity received.
The quantity posted in Business Central.
The date and time of arrival.
The posting date.
Any returns, corrections or credit notes.

The distinction matters. Supplier problems need a supplier conversation; internal process problems need training, controls or better data. Treating both as the same issue stops the team fixing the underlying cause.

Business Central receipt discrepancies are one part of the picture. Our previous article explains how Business Central supplier performance reporting can reveal hidden procurement costs.

Measure the process, not just the correction

Counting corrections tells you how many problems the team found. It does not show how many went undetected or how much disruption they caused.

Combine the exceptions with the measures that show whether the process is improving:

Vendor fill rate by order, by line and by quantity.
On-time receipt percentage against the promised date, by vendor and by item.
Average delay when late, not just average lead time.
Outstanding purchase quantity, including open lines already past their committed date.
Items repeatedly received above or below the ordered quantity.
Receipts posted several days after the goods arrived.
Returns to suppliers, corrections and credit notes following receipt.
Emergency purchases and inventory adjustments following receipt.
Receipt and put-away time by location.

Tracked over time, these separate isolated mistakes from recurring supplier or warehouse problems. That shows whether receiving accuracy is improving and where intervention will pay back most.

Frequently asked questions

How does Business Central handle a partial purchase receipt? Enter the quantity actually received in the Qty. to Receive field and post the receipt. The remaining quantity stays outstanding on the purchase order, and the team can receive it later.

Can Business Central accept more than the ordered quantity? Yes, when an over-receipt code and tolerance are configured, and the business can require approval. Business Central records the excess in the Over-Receipt Quantity field on the purchase line, and the business and supplier must still agree how to treat the additional quantity financially.

Why might a supplier appear late when the delivery arrived on time? Three common causes. The report is measuring against your requested date rather than the date the supplier promised; the warehouse posted the receipt days after the goods arrived, and the report uses the posting date; or nobody updated the purchase order after both parties agreed a change by phone or email. Confirm which date the report uses before assessing the supplier.

What if a purchase line has no promised or requested date? The report counts a line as on time when the selected date field is blank. If you want the percentage to reflect only lines with a real commitment, exclude blank dates from the analysis.

Should teams review receipt accuracy by supplier or by item? Use both. A supplier view reveals relationship-level patterns; item and location analysis exposes problems with particular products, units of measure or warehouse processes.

How often should teams review purchase receipt discrepancies? Review material exceptions daily or weekly, depending on purchasing volume and operational risk. Monthly trend analysis then identifies recurring supplier and process issues.

Find receiving problems before they spread

Business Central receipt discrepancies become expensive when they stay hidden.

The sooner the team identifies a shortage, an excess quantity, an incorrect item or a posting delay, the easier it is to protect inventory accuracy, resolve the issue with the supplier and prevent disruption elsewhere in the business.

Purchasing Insights from Business Central Insights provides ready-made Power BI reports for purchase receipt analysis, supplier performance, fill rate and outstanding purchasing commitments.

To explore the reports with your own Business Central data, start a free 30-day trial or book a demonstration.

Accurate receiving is not a warehouse administration task. It is one of the controls that protects stock availability, supplier accountability and margin.

Business Central Purchase Receipt Discrepancies That Quietly Drain Your Margin