Reference · built on requestOperator by FibricInventory & supply

Receipt Variance

Matches each receipt to its purchase order line and ASN, flags shorts, overages, and damage, and proposes the follow-up.

Request accessPricing ↗

About

A receipt that does not match its purchase order is a claim waiting to be made or a bill about to be overpaid. Receipt Variance reads purchase order lines, the advance ship notice the vendor sent, the receipt the warehouse posted, and the damage or rejection noted at the dock.

Each receipt line is set against the ordered quantity and the shipped quantity on the ASN. Shorts, overages, and damage are flagged with the value involved. For each it proposes a vendor claim, a purchase order change, or a hold that keeps the goods out of pickable stock. A receiving manager or buyer approves every proposal.

This is a reference listing. It documents what Fibric would read from Receipt Variance and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Purchase order lines with ordered quantity and unit price from NetSuite or Business Central
  • X12 856 ship notices through Stedi or SPS Commerce: SN1 quantity shipped, PRF purchase order number, and REF carrier references
  • NetSuite item receipts with Quantity and Remaining Quantity per line, and the Partially Received or Pending Billing status they leave
  • Business Central warehouse receipts with Qty. to Receive and Over-Receipt Quantity per line
  • ShipHero purchase order lines with quantity_received and quantity_rejected, and the PO Update webhook
  • Carrier tracking for the shipment named on the ASN, with delivery status and exception_description from ShipEngine

Proposed actions

  • Target capability: propose a NetSuite vendor return authorization for damaged or unordered units, with quantity and value
  • Target capability: propose changing the purchase order line to the quantity actually shipped, so the bill matches the receipt
  • Target capability: propose a NetSuite Inventory Status Change to a status that is unavailable for allocation, for units awaiting inspection
  • Target capability: propose marking a damaged lot Blocked on its Business Central Lot No. Information card
  • Target capability: propose a claim note to the vendor with the ASN, the receipt, and the carrier scan attached

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Short-ship claim with the vendor's own numbers

    The 856 through Stedi shows more shipped than the NetSuite item receipt shows received. A claim note and a purchase order line change are proposed with both documents attached.

    With Stedi, NetSuite

  • Hold a damaged lot before put-away

    ShipHero records quantity_rejected on a purchase order line. A NetSuite Inventory Status Change to a status unavailable for allocation is proposed for those units pending inspection.

    With ShipHero, NetSuite

  • Tie an overage to the tolerance

    A Business Central warehouse receipt shows an Over-Receipt Quantity. The line is proposed for the buyer's approval with the SPS Commerce ASN quantity beside it.

    With Microsoft Dynamics 365 Business Central, SPS Commerce

Requirements

  • Purchase orders in NetSuite or Business Central
  • Receipts posted in the ERP or in a WMS such as ShipHero
  • Ship notices from vendors, as X12 856 through Stedi or SPS Commerce, so shipped quantities are known before arrival
  • A receiving manager or buyer named to approve claims, order changes, and holds
Authentication
ERP credentials with purchase order, item receipt, and vendor return permissions; an EDI platform API key for 856 documents; read access to the WMS and to carrier tracking.

Limits

  • Without an ASN the receipt is matched to the order only. A short against the vendor's own shipped count cannot be shown.
  • Overages need Allow Overage on Item Receipts in NetSuite, and stay inside the Over-Receipt Tolerance in Business Central. Past that, an overage is a note.
  • Damage is what the warehouse recorded. Nothing here inspects goods.
  • A claim is proposed as a return authorization or a note. The credit is the vendor's to issue.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Receipt Variance ↗

Questions and answers

What is compared?
Three quantities per line: ordered on the purchase order, shipped on the 856, and received on the receipt. Damage and rejection counts are read from the receipt. Unit price from the order turns each gap into a value.
What does the receiving manager approve?
One proposal per variance: a vendor claim with the documents attached, a purchase order line change, or a hold on the units. The card shows the three quantities, the gap, its value, and the carrier's delivery scan. The manager edits or declines.
What is never done without approval?
No return authorization is entered, no order line is changed, no status is moved, and no note reaches the vendor. Each approved action leaves a record naming the order, ASN, receipt, quantities, approver, and time, with the prior state kept.
Ask about Receipt Variance

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy