The quick answer
In MIRO (invoice verification), "balance not zero" means the amount you entered doesn't reconcile with what SAP expects from the purchase order and goods receipt. SAP won't post an invoice until the Balance field is 0 and the traffic light is green. The fix is to find the gap — usually a quantity, price, tax, or delivery-cost difference — and correct it until the balance clears.
Key takeaways
- MIRO checks the invoice against the PO and goods receipt (the three-way match).
- The Balance field must be 0 (green light) before you can post.
- A non-zero balance = a gap in quantity, price, tax, or delivery costs.
- Find and correct the gap; the balance clears and the invoice posts.
What the balance means
When you enter a vendor invoice in MIRO, SAP already knows what it expects: the price from the purchase order and the quantity from the goods receipt. It compares your entry to that expectation. The Balance field (top-right, with a traffic light) shows the difference. If your invoice total matches the expected amount, the balance is 0 and the light turns green — you can post. If it doesn't, the balance is non-zero and SAP stops you.
So the message isn't an error in the usual sense — it's SAP refusing to post a document that doesn't add up. Your job is to explain the difference: either fix your entry, or account for a legitimate variance.
The three-way match
Invoice verification is a three-way match — PO, goods receipt, and invoice all have to agree:
The PO sets the expected price; the goods receipt sets the expected quantity (for GR-based invoice verification); your invoice is checked against both. When all three line up, the balance is zero. A gap anywhere leaves a balance you have to resolve.
Why the balance isn't zero
You entered a quantity that doesn't match what was received (or what you intend to bill). For GR-based verification, the invoice quantity should tie to the goods receipt.
The unit price or line amount differs from the PO. A small difference may be a legitimate variance (which can block the invoice for payment); a large one usually means a keying error.
The tax code or tax amount you entered doesn't match what the PO expects, so the totals don't reconcile.
Planned delivery costs (freight on the PO) must be selected in MIRO; unplanned delivery costs must be added in the Details tab. Missed either way, the balance won't clear.
Referencing the wrong purchase order or line pulls in the wrong expected amounts. Confirm you're matching the right document.
How to fix it, step by step
Read the Balance field
Look at the Balance (top-right) and its traffic light. Note the amount and whether it's positive or negative — that tells you if you've entered too much or too little.
Compare header total vs item total
The amount in the header should equal the sum of the item lines (plus tax and delivery). If the header total was typed and doesn't match the items, that's your gap.
Check the quantity
Confirm the invoice quantity matches what you're billing and — for GR-based verification — the goods receipt quantity. Adjust the line quantity if needed.
Check the price / amount
Compare the unit price/amount against the PO. If it legitimately differs, that's a variance — the invoice may still post but be blocked for payment until released (MRBR).
Check the tax, and add delivery costs
Make sure the tax code and amount match the PO. Select any planned freight lines; enter unplanned delivery costs in the Details tab.
Clear the balance and post
Correct entries until the Balance is 0 and the light is green. Then post.
FAQ
Learn MIRO and the three-way match —
on a live SAP system, with a consultant.
VoiSAP's live SAP MM training covers invoice verification, the three-way match and MIRO on a real system, so balance errors become routine — plus full career support for the Canadian and US market.
*Hands-on training on a live SAP system. Individual outcomes vary.