How I built a Stripe billing health audit for SaaS

# Overview Giorgio Di Rosa built Tresvio to expose billing states in Stripe that often go unnoticed after a successful checkout. The tool is an audit and monitoring layer that highlights subscriptions, invoices, and customer records that require human review, rather than taking automated billing actions.

# What the audit looks for The first version targets specific Stripe billing states that commonly cause problems for SaaS businesses:

• Subscriptions marked past_due
• Unpaid subscriptions
• Incomplete subscriptions
• Recently expired incomplete subscriptions (incomplete_expired)
• Open invoices with an amount remaining after collection attempts
• Customers who have multiple active or trialing subscriptions at the same time

The goal is to surface these states so teams can decide the right response given their own policies.

# Read-only design and workflow Tresvio keeps the Stripe integration read-only for the monitoring workflow. The workflow is deliberately simple:

1. 1Connect Stripe
2. 2Run an audit
3. 3Review the findings
4. 4Open the relevant customer, subscription, or invoice in Stripe to act
5. 5Optionally enable continuous monitoring

Because the tool does not perform retries, cancels, refunds, or other recovery actions, each SaaS retains control over billing decisions and policy-driven responses.

# Stripe state is only half the problem Stripe's view of billing is limited to what happens on the payments side. Common mismatches between billing records and application state include:

• Stripe shows a paid subscription but the app does not grant access
• The app grants premium access even without a paid Stripe subscription

# Free audit and adoption flow

# Who should consider this The audit is aimed at SaaS teams using Stripe Billing who want a lightweight way to spot inconsistencies without introducing automated recovery logic. It's useful for engineering, support, and finance teams that need a clear list of Stripe records to inspect and reconcile.

# Practical next steps for readers If you run subscription billing on Stripe:

• Run a manual reconciliation between Stripe subscriptions and your app's entitlement system to spot mismatches.
• Start with a read-only audit before automating retries or cancellations so you can define policy first.
• Consider adding an app-level probe to detect cases where billing and access diverge.