How to Receive a Purchase Order and Return Goods to a Vendor in SyteLine
how to receive a purchase order and process a return to vendor in SyteLine
Also searched as
- syteline po receipts form how to
- syteline return to vendor rtv process
- how to un-receive a po line syteline
- syteline debit memo return to vendor
Short answer
Receiving happens in PO Receipts against open PO lines, updating on-hand quantity and open PO balance. Returning goods is a separate return-to-vendor transaction that reverses the receipt, references the original PO and receipt, and should tie to an AP debit memo so the vendor invoice and payment reflect the returned quantity.
Applies to: Infor SyteLine 8.x and CloudSuite Industrial (CSI) 10.x, Purchasing, Inventory, and Accounts Payable modules.
Receive goods and process a return
- 1Open PO Receipts and select the purchase order, which shows open lines with quantity ordered, quantity already received, and quantity remaining.
- 2Enter the quantity actually received against the correct line, assigning lot/serial numbers at this point if the item is tracked.
- 3Route the receipt to the correct warehouse and, if the item is on inspection hold, confirm it lands in a QC or inspection location rather than directly to a usable location.
- 4Post the receipt. This updates on-hand inventory, reduces the open PO quantity, and creates the receipt record that vouchering will match against later.
- 5For a return, get or create an RMA/return authorization reference from the vendor if they require one, since many vendors will not credit a return without it.
- 6Process the return-to-vendor transaction against the original PO and receipt, entering the quantity being returned and the reason (damaged, wrong item, over-shipment, quality reject).
- 7Confirm the return reduces on-hand inventory and reinstates open PO quantity if you intend to receive a replacement against the same PO line.
- 8In Accounts Payable, enter or expect a debit memo from the vendor for the returned quantity, and match it against the return transaction so the vendor's account reflects the credit.
Receiving against the right line, not just the right PO
A single PO frequently has multiple lines with different items, unit prices, or delivery schedules, and it is easy to receive the correct quantity against the wrong line when a packing slip does not clearly map to your PO line numbers. Always reconcile the vendor's packing slip against the PO Receipts screen's open-line list before posting, since receiving against the wrong line throws off both inventory accuracy for two items and the voucher match later.
If the item is inspection-controlled, make sure the receipt routes to an inspection or hold location rather than a general-access warehouse. Receiving material directly into a usable location and letting production consume it before QC has signed off defeats the purpose of having an inspection step at all, and it is a common audit finding in regulated environments.
Correcting a receipt entered wrong
If a receipt was entered with the wrong quantity or against the wrong line and nothing downstream has consumed it yet, you can typically reverse or correct it directly through an un-receive or receipt correction transaction rather than trying to fix it with a manual inventory adjustment, which loses the audit trail back to the PO. Once the material has been issued to a job or shipped, correcting it gets more involved and may require separate adjustment and reconciliation steps.
Whenever you correct a receipt, check whether it has already been vouchered. Correcting inventory after a voucher has matched and posted against the original receipt quantity can create a mismatch between what AP paid for and what inventory now shows, so coordinate with AP before adjusting a receipt that is already vouchered.
Purchasing > PO Receipts > select PO > open lines
PO Receipts > receive quantity > lot/serial popup if tracked
PO Receipts > route to warehouse (inspection vs usable location)
Purchasing > Return to Vendor > reference original PO/receipt
Return to vendor and the AP side
A return-to-vendor transaction should always reference the original PO and receipt it is reversing, both for traceability and because it is what lets the system correctly reinstate open PO quantity if you plan to receive a replacement shipment against the same order. A return entered as a generic inventory adjustment instead loses that linkage and makes it much harder to reconcile later.
The AP side matters just as much as the warehouse side. A physical return without a corresponding debit memo means the vendor's invoice still bills you for goods you sent back, and if nobody catches it, you simply overpay. Track returns awaiting a vendor credit the same way you track any other open AP item, and follow up if the debit memo does not show up within the vendor's normal cycle.
Over-shipments and partial receipts
Vendors occasionally ship more than the PO quantity. Depending on your purchasing policy, you may receive only up to the ordered quantity and reject the excess, or receive the full delivered quantity with a tolerance and let purchasing decide whether to keep and pay for the overage or return it. Whichever you choose, be consistent, because a receiving team that sometimes accepts overages and sometimes rejects them without a documented rule creates inconsistent vendor expectations and inconsistent AP matching.
Partial receipts against a multi-shipment PO line are normal and do not require any special handling beyond entering the actual quantity received each time; the PO line simply stays open with a reduced remaining quantity until it is fully received or closed out.
Common pitfalls
- !Receiving against the wrong PO line when a packing slip does not clearly match, throwing off inventory and voucher matching for two items.
- !Receiving inspection-controlled material into a general-access warehouse instead of a hold location, letting it be consumed before QC review.
- !Correcting a receipt after it has already been vouchered without coordinating with AP, creating a mismatch between what was paid and what inventory shows.
- !Processing a return as a generic inventory adjustment instead of a return-to-vendor transaction tied to the original PO, losing traceability.
- !Physically returning goods but never tracking or following up on the corresponding AP debit memo, resulting in overpayment.
How an ERP-grounded AI assistant handles this
ERPray, grounded on your SyteLine PO, receipt, and AP data, can answer "which returns from the last quarter still have no matching debit memo" or "which receipts this week hit inspection hold and haven't cleared QC" directly, instead of someone cross-referencing Purchasing and AP screens by hand to find open exposure sitting in returns.
Frequently asked questions
Do I need an RMA number from the vendor before returning goods?
Most vendors require a return authorization before they will accept goods back or issue credit, so check with purchasing or the vendor before shipping anything back, even if your system does not technically require the field to process the internal return-to-vendor transaction.
Can I receive more than the PO quantity?
Depending on your configuration and receiving tolerance settings, the system may allow or block over-receipt beyond the ordered quantity; check your purchasing policy on whether to accept, reject, or receive-and-return the excess before deciding how to handle it.
What happens to open PO quantity after a return?
A properly referenced return-to-vendor transaction typically reinstates the returned quantity as open on the PO line, so you can receive a replacement shipment against the same order rather than needing a brand new PO.
How do I know if a receipt has already been vouchered?
Check the receipt's status or history in PO Receipts or the AP voucher inquiry; a vouchered receipt has a matched invoice against it, and you should coordinate with AP before adjusting quantity on a receipt that has already been matched and paid.
Related
How to Handle Landed Cost and Voucher a PO Receipt in SyteLine
Landed cost charges such as freight, duty, and brokerage are added against the PO or the receipt, allocated across the received line items by value or quantity, and rolled into the item's received cost before it is vouchered. Vouchering itself is the 3-way match between PO price, receipt quantity, and vendor invoice, and mismatches beyond your tolerance percentage get held for review instead of posting automatically.
How-toHow to Set Up Lot and Serial Number Tracking in SyteLine
Lot and serial tracking is turned on per item on the Items form, with a tracking type of None, Lot, or Serial. Once enabled, every receipt, job move, and shipment transaction for that item prompts for a lot or serial number assignment, and SyteLine keeps a full genealogy you can trace forward to customer shipments or backward to the receiving vendor.
How-toHow to Run a Cycle Count in SyteLine
Cycle counting in SyteLine runs through Inventory > Cycle Count: generate a count list by ABC class or location, print or enter tags, key the counted quantities into Cycle Count Entry, then review the variance report before posting the count to update on-hand quantity.
How-toHow to Release a Customer Order from Credit Hold in SyteLine
A customer order goes on credit hold when the customer's exposure, whether AR balance, open order value, or days past due, exceeds the limit set on the Customers form. Releasing it is a deliberate override on the order, usually restricted to users with credit management authority, and the real fix is reviewing whether the limit, the hold reason, or the customer's payment behavior needs attention.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.