Ariba rejected the invoice: why the wait can start again, and how an agency counts what it costs

Why agency invoices come back

Rejections come from two places: rules the buyer configured in the portal, which fail an invoice automatically, and an approver who reviews it and says no. The published guides name the reasons, and several of them fit how agencies bill: monthly retainers against blanket purchase orders, change orders that grow scope after the PO was written, and fees billed as services rather than goods.

• PO amount used up. Puget Sound Energy’s supplier handbook says a “Contract Hard Maximum Limit Exceeded” rejection means the invoice exceeds the amount available on the blanket PO and will need a change order. A retainer billed past its PO value hits this.
• PO expired. Tirlán’s error list includes invoices against expired blanket purchase orders; the fix is asking the buyer to extend the order, then resubmitting.
• Required service fields. The same handbook says service start and end dates are required and the invoice will auto-reject in Ariba if they are not filled, and lists a missing tax rate as a rejection reason.
• Lines that do not match the PO. Quantities or amounts above what the PO line or the goods or service receipt allows, which is what happens when the SOW changed and the PO did not.
• Supplier record and remit-to details missing or incomplete.
• Duplicate invoice numbers. Ariba Network does not allow duplicate invoice numbers by default, according to the Syngenta guide, unless the buyer turns on a rule that lets a rejected invoice be resent under its original number.
• Approver rejection. Tirlán’s first listed reason is simply that its approver rejected the invoice, with the advice to contact the buyer for the reason.

None of these is about the quality of the work. Each is about information the client’s AP team needs and the agency’s invoice did not carry, which means each one can be known before the first invoice is ever sent.

Ariba and Coupa: rejected, disputed, and how to resend

The two portals use different words for the same event, and buyers configure them differently, so the resubmission rule belongs in each client’s file, not in someone’s memory.

• Ariba: the invoice shows as Rejected, with the reason on the invoice detail. Some buyers want Edit and Resubmit, as AES describes. Others say the opposite: Puget Sound Energy’s handbook says not to edit and resubmit the same rejected invoice, but to create a new invoice with the same number, with an exception for an invoice dated before the PO.
• Ariba notifications: Vestas’ supplier guide says rejection emails can be turned on in Ariba Network and that, by default, the rejected-invoices view shows the past 31 days. A rejection nobody is notified about can sit unseen.
• Coupa: the invoice shows as Disputed. The Coupa supplier guide for PO-backed invoices says the customer’s reasons appear in the comments, that disputed invoices cannot be edited in the portal, and that a new invoice must be created with a different invoice number because Coupa will not accept duplicates.
• Coupa, configured differently: Terracon’s guide says a dispute reason is shown for each disputed invoice and offers two actions, void the invoice and re-create it, or correct it.

The practical consequence: the same agency can face four different resubmission rules across four clients. The person fixing a rejection should not have to rediscover the rule each time.

The count: rejections by client, reason and days added

For the last twelve months, every invoice that went through a client portal and came back gets a row: client, portal, invoice number, amount, first submission date, rejection date, the reason in the client’s own words, the date someone at the agency noticed, the resubmission date, the acceptance date, and who fixed it. One more column carries the weight: days added, from first submission to accepted resubmission.

Illustrative example: a 30-person agency bills three clients through portals. Over a year, 18 invoices worth $264,000 in total came back. Seven were PO-related (amount used up or expired), five lacked service dates or a tax field, four had lines that no longer matched the PO after a scope change, and two had supplier-record problems. A typical case: an invoice submitted on day 0 is rejected by an approver on day 9, noticed on day 15 and accepted on day 17. If the client’s net 60 runs from the accepted submission, payment is due on day 77 instead of day 60. Across the 18, the days added averaged 16, and six of those were days before anyone at the agency saw the rejection. All of these figures are hypothetical; an agency’s own log gives its own.

Sorted by client and reason, the table shows where the fix belongs. Days between rejection and notice point to who reads the portal’s emails. PO reasons point to kickoff and to PO tracking on retainers. Line mismatches point to the change order: if the SOW grew, the PO had to grow before the invoice could.

The fix sits at kickoff, not in billing

Every reason in the list above can be known before the first invoice. The habit that removes whole categories is a short portal sheet attached to the project or retainer at kickoff, filled in with the client’s AP team rather than guessed.

• Portal and buying entity, with the agency’s supplier record confirmed active and the remit-to details checked.
• PO number, PO amount and PO end date, with a monthly check on retainers of the amount remaining against the months still to bill.
• How the PO lines are structured, and what an invoice line must match.
• Required fields: service start and end dates, tax, cost center, attachments.
• The resubmission rule: edit and resubmit, new invoice with the same number, or new invoice with a new number.
• The AP contact, and the date the client’s terms count from.

Two habits close the rest. Every change order that adds fees goes to the client with a request to change the PO before the added work is invoiced. And one named person at the agency reads portal notifications every day, so a rejection is fixed in a day instead of noticed a week later. Whether an agency may charge interest or require a different start date for terms is a contract question for its attorney; the portal sheet is the operational part, and it works either way.

When not to hire anyone for this

An agency with one portal client, few rejections and every rejection noticed the day it arrives does not need outside help here. The log above, built once, will say so, and the time is better spent elsewhere.

It is worth a second look when rejections repeat at the same clients, when the gap between rejection and notice runs to days, or when the problem sits next to others: invoices past terms with no follow-up, retainers billed past their PO, change orders that never reached the client. The page on agency operations consulting lays out where those leaks sit in a marketing, PR or consulting firm. The Revenue Review is a fixed $4,500, two weeks, read-only engagement: we read the firm’s own invoice, rejection, PO and payment records, measure the days each client’s portal adds, and put a monthly dollar figure on each leak, with a written report and a 90-day plan. We do not contact clients or their AP teams, and contract questions stay with the firm’s attorney. The free Cash Gap Calculator shows first what the extra days cost, and a free 20-minute call is enough to tell whether a Review fits.