SAP Ariba troubleshooting
Ariba invoice PO mismatch: prices, quantities, and remaining balance
Resolve SAP Ariba invoice PO mismatches by checking line prices, quantities, currency, receipts, and prior billing before correcting or requesting a PO change.
LedgerUp team · Updated
When an Ariba invoice fails a PO match, compare the billed lines with the current purchase order, earlier billing, and any required receipt or service acceptance. Correct genuine invoice mistakes. If the invoice accurately reflects an agreed change that is missing from the PO, ask the buyer to update the order rather than alter the charge just to pass matching.
Buyer settings, document status, and country-specific invoice rules vary. Follow the rejection message and your customer’s supplier instructions. This guide explains checks and escalation, not permission to bypass buyer approvals.
Why this happens
The mismatch may be a unit price, quantity, currency, remaining value, or extra charge not permitted by the buyer’s invoice rules. Some workflows also compare received or accepted quantities. A total that looks correct can still fail because one individual line does not match.
How to investigate and resolve it
- Read the rejection detail. Identify the rejected field and line. Check whether the failure is a network validation or a response from the buyer’s reconciliation process.
- Use the current PO version. Confirm the order reference and review the latest change. Match line identifiers, units, unit prices, and currency with the invoice rather than relying on an older PDF copy.
- Reconcile prior invoices and acceptance. Check what has already been billed and, where required, what the buyer has received or accepted. Ask AP or the service owner to clarify disputed balances.
- Choose correction or amendment. Fix wrong invoice entries in the permitted workflow. For valid additional charges, send the agreement or delivery evidence and request buyer approval and a PO change.
- Review all fields before retrying. Confirm the revised PO or acceptance appears on the network. Review tax, freight, and attachments too, then resubmit through the customer’s accepted correction path.
What the supplier can fix—and what the buyer must confirm
Supplier: Verify the billed work and source documents, map lines correctly, and prevent duplicate or over-quantity billing.
Buyer: Approve contractual changes, maintain the PO and acceptance records, and clarify tolerances or permitted additional charges.
Example: choosing the right next action
Your service rate increased under an agreed amendment, but the network PO still shows the old rate. Lowering the invoice would underbill the service. Send the amendment to procurement and request an updated PO before resubmission.
A message you can send to AP or procurement
Invoice [number] was rejected on PO [number], line [line], for [price or quantity difference]. Our source agreement shows [value]. Please confirm the current remaining balance, required receipt or service acceptance, and whether the PO needs amendment.
How to confirm the issue is resolved
Before retrying, confirm that the source of the rejection has changed—not only that you can press Submit. Keep the original and correction references linked in your AR records. After submission, inspect the document’s status and any buyer response. An accepted submission is not the same as approval or payment; if the invoice is rejected again, preserve the new reason and ask the responsible owner to address it.
Frequently asked questions
Can I change the invoice currency to make it match?
Only if the current invoice currency is genuinely wrong. Otherwise ask the buyer to resolve the order or agreed billing terms.
Will removing an extra charge always solve the rejection?
It may remove a validation problem but also remove money owed. Confirm authorization and billing treatment before changing a valid charge.
Prevent the same exception next time
Keep a customer-specific invoice checklist with required fields, documents, approvers, and correction rules. Before each submission, compare the source invoice, PO, and supporting evidence. Give one person or process clear submission ownership and track status changes so a rejected invoice does not disappear from follow-up.
For the full submission flow, use the supplier guide below. For recurring portal work, LedgerUp’s procurement portal automation is a separate option to explore; the buyer still controls order changes and approvals.