# SAP MIGO Goods Receipt Checklist for Purchase Orders > Source: https://netray.co/tools/sap-migo-goods-receipt-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step by step checklist to post a clean goods receipt against a purchase order in MIGO, with critical checks flagged. ## Category sap ## Erp SAP S/4HANA ## Audience - Receiving clerk - SAP MM consultant - Warehouse supervisor ## Tool **Kind:** checklist **Scoring Note:** Tick each step you completed. A receipt is safe to post when every critical item is ticked. Non critical items raise the quality of your inventory data. **Groups:** #### Before opening MIGO **Items:** **Text:** Physical delivery matches the delivery note: vendor, part number and quantity **Critical:** true **Text:** Purchase order number found on the delivery note or packing slip **Critical:** true **Text:** Purchase order is released and not blocked or deleted (ME23N status check) **Critical:** true Packaging is undamaged, damage noted on the carrier document Special handling needs checked: hazardous, temperature, serial or batch controlled Quality inspection requirement known for the material (inspection type in material master) #### Header and reference data in MIGO **Items:** **Text:** Action set to Goods Receipt and reference document set to Purchase Order **Critical:** true **Text:** Purchase order number entered and the item list loaded **Critical:** true **Text:** Document date set to the delivery note date, posting date to the actual receipt date **Critical:** true Delivery note number entered in the header text field for traceability Bill of lading or reference field filled if your invoice team matches on it **Text:** Correct movement type shown, normally 101 for stock or consumable receipt **Critical:** true #### Item level checks **Items:** **Text:** Quantity in unit of entry matches what was physically counted **Critical:** true Unit of measure matches the PO and conversion to base unit is correct **Text:** Storage location set to where the stock will be placed **Critical:** true Delivery completed indicator set only if no more deliveries will come **Text:** Over delivery or under delivery tolerance on the PO item respected **Critical:** true **Text:** Batch number entered or assigned for batch managed materials **Critical:** true **Text:** Serial numbers captured if the serial number profile requires them **Critical:** true Shelf life expiry date or manufacture date entered where managed Stock type set correctly: unrestricted, quality inspection or blocked Account assignment checked for non stock items: cost center, asset or order #### Posting and verification **Items:** **Text:** Check function in MIGO run with no error messages **Critical:** true **Text:** Item OK checkbox set on each line being posted **Critical:** true **Text:** Post executed and the material document number noted **Critical:** true Goods receipt slip or label printed if the process uses one Accounting document visible in the document display, GR/IR credited Stock check in MMBE or MB52 shows the quantity in the expected stock type Purchase order history in ME23N shows the receipt #### Exceptions and corrections **Items:** **Text:** Wrong quantity or item: cancel with the cancellation action referencing the material document **Critical:** true Damaged goods: post to blocked stock or return delivery 122 instead of unrestricted stock Goods without a PO: stop and ask purchasing, do not use 501 unless policy allows **Text:** Tolerance block: ask the buyer to change the PO tolerance, do not force the quantity **Critical:** true **Text:** Invoice already posted: tell accounts payable before any cancellation **Critical:** true Quality rejection logged in the inspection lot with usage decision recorded ## Content **Intro:** MIGO is the single screen SAP uses for goods receipts, goods issues, transfers and returns. Most receiving errors come from a handful of avoidable slips: wrong dates, wrong stock type, missing batch, forced tolerances. This checklist walks the receiver through each of them. **Sections:** #### How to use the checklist **Body:** Print it for the receiving dock or keep it on a tablet. Work top to bottom for each delivery. Items marked critical are the ones that cause financial or stock errors if skipped, so the score only reaches full when all of them are done. Export the completed checklist as PDF when you need evidence of a controlled receiving process for an audit or a supplier dispute. #### What the posting does **Body:** A standard goods receipt against a PO posts movement type 101. Quantity increases in the stock category you selected. For valuated materials, inventory is debited and the GR/IR clearing account is credited at the PO price. The invoice later debits GR/IR, and any price difference goes to the price difference account. If either side is missing, the GR/IR balance shows it, which is why an accurate receipt is a finance control and not only a warehouse task. **Bullets:** - Quantity and value posting happen together for valuated stock - Posting date decides the accounting period, so month end timing matters - Delivery completed stops open quantity on the PO from staying in MRP #### Worked example **Body:** A delivery of 500 pieces of a batch managed fastener arrives against a PO line for 450 with 10 percent over delivery tolerance. MIGO accepts 495 at most. The receiver enters 450 and a separate call to purchasing resolves the extra 50: either the buyer raises the line to 500 or the extra goods are returned. Forcing 500 by editing tolerances without buyer consent creates a receipt that cannot be matched cleanly with the invoice. #### Common mistakes **Body:** Leaving the posting date as today when goods arrived before month end shifts liability into the wrong period. Receiving into unrestricted stock when the material requires inspection bypasses quality. Posting a partial delivery with the delivery completed flag set closes the open quantity and hides the remainder. And cancelling a receipt after the invoice was posted leaves the payables team with an unmatched invoice. Use the exceptions group in the checklist before reaching for cancellation. **Cta:** If receiving is slow because people look up PO tolerances, batch rules and inspection settings by hand, we can build a read-only assistant over your SAP data that shows these in one answer. **Faq:** #### What is MIGO in SAP? **Answer:** MIGO is the combined transaction for goods movements: goods receipt, goods issue, transfer posting, return delivery and cancellation. It replaced older transactions such as MB01, MB1A and MB1B. In S/4HANA there are also Fiori apps for the same postings, but MIGO still works for most teams. #### Why does MIGO say the quantity exceeds the tolerance? **Answer:** The PO item has an over delivery tolerance and the quantity entered is higher than the ordered quantity plus that tolerance. Check the Delivery tab in ME23N. Either reduce the receipt, or ask the buyer to change the PO or its tolerance. Do not change tolerances in the material or vendor master to get around it. #### How do I cancel a goods receipt in MIGO? **Answer:** Choose the Cancellation action, reference the original material document, select the items and post. This creates a reversal with movement type 102 for a standard receipt. It only works if stock is still available and the document is not blocked by later postings such as consumption. #### Which date should I use as posting date? **Answer:** Use the date goods were physically received, unless the accounting period is closed. The document date should be the date on the vendor delivery note. The posting date decides the period for inventory and GR/IR, so wrong values distort month end accruals. ## Search terms sap migo goods receipt, migo goods receipt for purchase order steps, sap migo checklist, sap goods receipt process checklist, migo 101 posting, sap migo tolerance error, sap goods receipt best practices, migo transaction guide --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json