A SaaS renewal invoice is stuck in draft: separate approval holds from failures

Before manually finalizing a stale draft, read its account notes and approval history. The invoice may be waiting for corrected usage, a purchase order or an approved commercial change. Identify the person who owns the hold and the condition for release. A draft's age indicates unfinished work, but does not establish that issuing it now is the right fix.

Compare the subscription's renewal date with the expected billing calendar. Record when the draft was created, whether it has an automatic finalization schedule and whether its amount is complete. If no one recognizes the hold, ask the systems owner to inspect the integration and settings while finance preserves the current draft for comparison.

Stripe documents separate events for invoice creation and successful finalization, and notes that unsuccessful webhook responses can delay automatic finalization. Request evidence for the specific invoice rather than relying on a general integration-health indicator. A connected app can appear operational while failing on one customer's unusual data.

Ask engineering to distinguish a deliberate delay, a failed notification response, invalid invoice information and a disabled automation setting. Record the error or state that explains the hold and what must change. Do not solve a single missing invoice by turning on collection for every draft in the account; other drafts may have legitimate approval requirements.

Review the customer identity, service dates, products, quantities, discounts and agreed payment terms. Inspect usage accumulated since the original draft was created and determine which period it belongs to. Confirm whether a manual invoice was issued while the automation was stalled. Releasing the draft without this check can turn a missed bill into a duplicate charge.

Stripe explains that finalization makes an invoice payable and restricts later changes to several fields. Treat release as a reviewed action. Keep the approver, corrected preview and intended release time in the exception record. Where the invoice will be significantly late, coordinate a customer explanation and assess the payment due date under the actual agreement.

Define the normal release event for each relevant invoice group: an approved usage cutoff, a manual review or a scheduled renewal process. Then identify drafts that have passed that event without a documented hold. A draft created well before service starts may be expected, while a recent draft for a completed period may already require attention.

Give the queue an owner, expected release date, balance and reason. Review the largest customer exposures and repeated causes first. This makes the control specific enough to be useful; a report listing every draft without context can bury a failed renewal among legitimate preparatory invoices and encourage staff to finalize items that were intentionally held.

After release, verify the final invoice identifier, delivered document and collection state. A successful finalization event does not establish that the customer's purchasing team accepted the invoice or that payment succeeded. Assign each remaining step to the appropriate owner, and keep any customer dispute separate from the technical repair.

Accounting should review whether the missing invoice affected unbilled balances or revenue already recorded. Preserve the original service period rather than moving all activity into the month the problem was discovered. Add a narrowly targeted monitor for drafts beyond their expected release time, with reasons for intentional holds, so the team can find the same class of failure before the next close.