SAPFree checklistPDF, Excel, Word exportSAP S/4HANA

SAP MIGO Goods Receipt Checklist for Purchase Orders

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.

0%

0 of 35 items complete

18 critical items still open - these are the highest-risk gaps.

Download checklist:

Before opening MIGO

Header and reference data in MIGO

Item level checks

Posting and verification

Exceptions and corrections

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.

Receiving process review

Walk through your goods receipt configuration with an SAP consultant: tolerances, stock types and batch rules. Optional.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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

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.

  • 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

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

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.

Frequently Asked Questions

What is MIGO in SAP?

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?

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?

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?

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.

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.