Ariba invoice rejected because the PDF does not match

If an Ariba invoice is rejected because its PDF attachment does not match the electronic invoice, compare both documents line by line and correct the actual discrepancy. Check invoice number, PO, currency, quantities, prices, tax, and gross total. Use the buyer’s accepted correction path so the network record and supporting invoice represent the same charge.

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

A PDF may have been attached from another billing period, generated before a later invoice edit, or calculated differently from the portal draft. Some mismatches are only presentational; others change the payable amount or legal invoice identity. Resolve those differences rather than assuming the buyer will treat the attachment as the authoritative override.

How to investigate and resolve it

1. Identify the rejected comparison. Read the buyer’s comment and establish whether the problem is a missing attachment, a wrong document, or a mismatch in amounts or references. These are separate issues.
2. Confirm document identity. Match invoice number, invoicing entity, PO reference, currency, and service or delivery period. A similar amount is not evidence that the file belongs to this invoice.
3. Reconcile line calculations. Compare quantities, unit prices, discounts, freight, net totals, tax, and gross total. Check rounding and whether any extra charge exists in only one document.
4. Correct the source of truth. If your billing record is wrong, follow your internal correction controls before producing another PDF. If portal data was entered incorrectly, use the allowed document action to correct it. Ask AP which path applies to an already submitted invoice.
5. Verify the corrected pair. Review the final electronic record and attachment together before resubmitting. Retain the original and correction references in AR and monitor delivery and buyer response.

What the supplier can fix—and what the buyer must confirm

Supplier: Produce consistent source billing records and attachments, attach the correct version, and document corrections.

Buyer: Specify attachment requirements, identify the discrepancy, and confirm accepted handling of an already received document.

Example: choosing the right next action

The PDF bills a full month, but the electronic invoice was reduced for a partial service period without updating the PDF. Decide the correct charge with the source agreement, then align both documents instead of submitting competing totals.

A message you can send to AP or procurement

Invoice [number] was rejected because the PDF and electronic record differ at [field]. The correct value is [value], supported by [source reference]. Please confirm the required correction action and treatment of the original document before resubmission.

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 the buyer ignore the portal total and pay the PDF total?

Do not rely on that. Ask for a correction that leaves a consistent invoice record and clear payable amount.

Can I email the corrected PDF outside Ariba?

Only if the buyer expressly accepts that process. Emailing a file may not correct the network invoice or satisfy its required workflow.

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.