A SaaS renewal is blocked by an expired purchase order

Ask whether the customer's accounts-payable team rejected the invoice, its purchase-order reference or the renewal itself. These are different problems. Obtain the rejection message and the name of the procurement owner. A user who still wants the software may lack authority to approve the next term, so a reassuring support conversation cannot settle the billing question.

Compare the contract's renewal provisions with the purchase order's dates, value and remaining capacity. Record whether a new order is an administrative requirement under an existing commitment or part of an unresolved commercial approval. Have the commercial or legal owner interpret any conflict. Finance needs that decision before changing the receivable or treating the renewal as collectible on its normal timetable.

Collect the valid order number and the customer's required submission format. Check whether the invoice remains a draft or has been finalized. Stripe supports invoice custom fields such as purchase-order numbers, but documents that those fields cannot be changed after finalization. Use the supported correction process for your platform and the applicable invoicing rules.

Preserve the original document and link any replacement to it. Tell the customer which invoice should be paid and which earlier reference has been superseded. If their supplier portal requires resubmission, keep its acceptance receipt. Updating the PDF in an email thread without resolving the original ledger record can leave two apparent debts and two collection sequences.

Set a review date for the procurement delay and identify who can authorize continued service. Record any temporary extension, payment arrangement or exception to the ordinary collection process. The customer should know whether access will continue during the review and whom to contact if approval is still pending. Avoid promising indefinite service while a new purchase order is being discussed.

For an illustrative $12,000 annual renewal, a customer might supply an order with only $9,000 remaining. The $3,000 gap needs an amended order, another approved funding reference or a commercial resolution. Splitting the invoice merely to fit the old order does not resolve whether the customer has authorized the full commitment. Keep the gap visible until its owner closes it.

A new purchase-order number may still leave the invoice blocked if its supplier entity, currency, service period or authorized amount differs from the bill. Ask the customer's purchasing contact which fields must agree. Include any separately approved seat addition or usage charge in that comparison rather than assuming the renewed order covers everything sold to the account.

For a hypothetical $12,000 renewal plus a $1,500 approved addition, an order limited to the base renewal may explain a partial rejection. Record which amount is covered and who will authorize the remainder. The finance team can then pursue the correct procurement action without canceling a valid invoice or treating the entire balance as an unexplained collection failure.

Track the original due date, rejection date, correction date and portal acceptance date. If the agreed terms change when payment is due, retain that approval. Otherwise, preserve the earlier aging history even when the customer requests a fresh document. This lets management distinguish an administrative delay from a negotiated extension or a disputed renewal.

Before the next renewal, ask the account owner to obtain procurement requirements while the customer still has time to raise an order. Store the purchasing contact separately from the product administrator and test the reference on the draft invoice. Review repeat holds by account and cause so an expired order becomes a scheduled renewal task rather than the same overdue surprise each year.