These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Supplier Portal
- Features
- Receiving and exceptions
Receiving and exceptions
Connect physical arrivals, accepted quantities, returns and invoice discrepancies.
OverviewReceipts awaiting posting×
SCM with Supplier Portal · Receiving and exceptions
New
Receipts awaiting posting
Posting waits for the receiving clerk
| Receipt number | Receipt date | Status | PO | Supplier | Receiving location | |
|---|---|---|---|---|---|---|
| RCP-26975 | 11 Oct | Received | PO-44651 | VND-066 | LCT-120 | |
| RCP-56576 | 02 Oct | Received | PO-30441 | VND-156 | LCT-120 | |
| RCP-21309 | 07 Oct | Received | PO-97242 | VND-031 | LCT-120 | |
| RCP-67846 | 09 Oct | Received | PO-82524 | VND-044 | LCT-110 | |
| RCP-77100 | 11 Oct | Received | PO-11885 | VND-048 | LCT-110 |
6 of 6 records
PO-44651Receipts · RCP-26975
ReceivedReceipt date11 Oct
SupplierVND-066
Receiving locationLCT-120
What you can do
Receiving and exceptions
Receiving Clerk records an arrival against a purchase order and a named location. Receipt lines distinguish ordered, received, accepted and rejected quantities. Inspection status and a rejection reason help the team decide what can be accepted. The posted receipt links to the order revision and a procurement event, preserving the basis for the next financial or inventory handoff.
How the work is organized
- Record what arrived. Keep arrival, inspection and accepted quantity separate.
- Trace returns. Link the returned quantity to its receipt line and authorization.
- Resolve differences. Keep invoice discrepancies tied to the order and receipt.
A partial shipment is a useful rehearsal. Record the received quantity, inspect it, accept the usable portion and reject the damaged portion. The remaining open order quantity should still be visible at the line. If rejected goods go back to the supplier, a supplier return links to the receipt line, states the returned quantity and reason, and tracks authorization, shipment and expected credit separately. Accounts payable may return a match exception when its invoice differs from the order or receipt. Buyer and Controller can read the invoice reference, exception type and related records, then record the resolution. A correction to a receipt and a supplier re-invoice are different paths. A receipt reversal must refer to its source; it should not erase the original arrival. The handoff to connected inventory, warehouse and accounts payable systems uses procurement events and delivery status.
What to agree during setup
Define locations, inspection responsibility and the evidence required for rejected goods. Agree who authorizes returns and how an expected credit is followed. Set the connected accounts payable, inventory and warehouse destinations. Decide how a failed delivery is reconciled before downstream teams rely on it.
Check the handoff on an actual case
Receive part of an acknowledged order at a dock. Accept some units and reject the damaged balance. Raise a return against that receipt line, then examine an invoice quantity exception. Check that the open order quantity, original receipt, posted event, return and exception can all be traced without replacing one another.
What your team sees
- Receipts awaiting posting — Arrivals waiting for final receipt posting.
- Open match exceptions — Invoice differences assigned to buyers and finance reviewers.
Follow the work through
Start with the request and review path, then check the supplier delivery path. Review implementation choices with the owners before the first operating cycle.
What it keeps track of
Data model- Receipts
- Physical arrival or service acceptance against a PO.
- Receipt line items
- Per-line received quantity against a PO line.
- Supplier returns
- Controlled return of rejected arrivals or previously accepted goods.
- Match exceptions
- A mismatch returned by accounts payable when the invoice disagrees with order or receipt.
- Purchase orders
- Supplier order with immutable approved revisions.
- PO line items
- Per-item lines on a PO, the level at which receipts and invoice match reconcile.
- Locations
- Ship-to and receiving places: a dock, an office or a site.
- Procurement events
- Durable once-only business event and migration provenance.
- Integration deliveries
- Per-event destination outbox for an explicitly configured connection.
Who uses it
Permissions- Receiving Clerk
- Records and inspects arrivals.
- Buyer
- Handles returns and exceptions.
- Controller
- Reviews financial differences.
- Procurement Manager
- Oversees supplier follow-up.
- The receiving decision belongs to the person who inspected the delivery.
- Buyer
- Uses the posted quantities when following an open order line, while Controller checks the resulting event and any exception against the approved commitment.
Set up SCM with Supplier Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.